Hi Jim,
Sorry for taking so long to reply.
I've done some extra testing regarding the custom fields, but I'm afraid
that in our test installation no custom fields are taken toward the new
ticket.
We're running RT 4.0.10 in our testing environment, with version 0.03 of
the RepeatTicket extension.
Below the options I've set in my RT_SiteConfig.pm, along with a list of the
other extensions that are installed:
# ---
# RT Extensions
# ---
Set(@Plugins, qw(
RT::Extension::SLA
RT::Extension::HistoryFilter
RT::Extension::MergeUsers
RT::Authen::ExternalAuth
RT::Extension::Nagios
RT::Extension::QueueChangeOnUpdate
RT::Extension::CustomFieldsOnUpdate
RT::Extension::CustomField::HideEmptyValues
RT::Extension::JSGantt
RT::Extension::RepliesToResolved
RT::Extension::SummaryByUser
RT::Extension::RepeatTicket
RT::Extension::Utils
RTx::Calendar
RTx::WorkflowBuilder
RT::Extension::CommandByMail
));
# ---
# RT::Extension::RepeatTicket
# ---
Set( $RepeatTicketCoexistentNumber, 1 );
Set( $RepeatTicketLeadTime, 14 );
What I've done is create 1 ticket with a subject, custom text for the first
message and set a few custom fields to categorize the ticket using our CF's
for that queue.
Then I manually run the cron command (it also fails whtn it runs via cron,
I just run it manually to quickly do some tests):
# /etc/cron.daily/rt-repeat-ticket
[Thu May 2 10:45:50 2013] [info]: Repeating ticket 40948
(/etc/cron.daily/rt-repeat-ticket:38)
[Thu May 2 10:45:50 2013] [info]: Repeating ticket 41791
(/etc/cron.daily/rt-repeat-ticket:38)
[Thu May 2 10:45:50 2013] [info]: Repeating ticket 41796
(/etc/cron.daily/rt-repeat-ticket:38)
[Thu May 2 10:45:50 2013] [info]: Ticket 41803 created in queue
'Projecten' by RT_System (/opt/rt4/lib/RT/Ticket.pm:688)
[Thu May 2 10:45:51 2013] [info]: Repeated ticket 41796: 41803
(/opt/rt4/local/plugins/RT-Extension-RepeatTicket/lib/RT/Extension/RepeatTicket.pm:416)
[Thu May 2 10:45:51 2013] [info]: Repeated ticket 41796: 41803
(/etc/cron.daily/rt-repeat-ticket:41)
In the beginning I got some extra messages from certain scrips, I've
disabled those to make the output as clean as possible.
The result is the above, which simply states that it created one ticket
which is what I'd expect.
But, regardless of what I try to achieve, the custom fields are always
empty.
This might be a bug (if what you say is true about CF's already being
handled), how should I tackle this/generate more detailed output to
pinpount the problem?
--
Bart G.
2013/4/25 Jim Brandt via RT <bug-RT-Extension-RepeatTicket@rt.cpan.org>
Show quoted text> <URL:
https://rt.cpan.org/Ticket/Display.html?id=84784 >
>
> On Mon Apr 22 05:14:35 2013, bart@pleh.info wrote:
> > Hi,
> >
> > We're looking into implementing this extension but are currently missing
> > two options which we'd like to have as an extra so that this feature
> > becomes even more powerfull.
> >
> > One option is about the other question which is already posted here, to
> > have the ability to add a date or some other extra information to the
> > subject which is variable. This would be a very welcome feature. In our
> > case we'de use this for making SLA reports for external end-users, e.g.
> > have a ticket being created each month and in the subject add the month
> for
> > which they need to create a report (current month - 1).
> >
> > Another thing we'de like to see is that the ticket also take the custom
> > field values of the original template ticket. In just about all cases
> (for
> > us at least) the ticket will be categorized using the same CF values.
> > Having the option to say which CF's to copy the values from (or all),
> would
> > be a very welcome feature.
> >
> > So basically my question regarding the CF's would be, can this already be
> > done using this extension, or would this have to be done by adding new
> > functionality to the extension?
> >
>
> Custom fields should already be handled in repeated tickets. As you
> mentioned, we're still thinking about the best way to tackle customizing
> the subject line. No question it's a good feature, but it gets more
> challenging when thinking about how to allow you to configure something
> like (month - 1).
>
>
>
