Skip Menu |

This queue is for tickets about the RT-Extension-RepeatTicket CPAN distribution.

Report information
The Basics
Id: 84831
Status: resolved
Priority: 0/
Queue: RT-Extension-RepeatTicket

People
Owner: cbrandt [...] cpan.org
Requestors: drew.wood [...] eurekaspringshospital.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)



Subject: Repeat ticket
Date: Wed, 24 Apr 2013 11:19:49 -0500
To: <bug-RT-Extension-RepeatTicket [...] rt.cpan.org>
From: "Drew H. Wood" <drew.wood [...] eurekaspringshospital.com>
I am having some problems with this plugin. I am not sure if I have done something incorrectly. I installed the plugin and created the cron job, and tickets are being created, but they are not being created as I would expect. I created a weekly job, to make a new ticket each Monday, and as soon as I resolve it will create another. That would be fine, except it is creating jobs months out, and today the ticket looked like this: Created: Wed Apr 24 07:46:23 2013 Starts: Mon Jan 05 00:00:00 1970 Started: Wed Apr 24 11:14:56 2013 Last Contact <http://esh-hd.esh.local:8080/rt/Ticket/Display.html?id=688&Action=SetTold> : Not set Due: Mon Jan 12 00:00:00 1970 Closed: Wed Apr 24 11:14:56 2013 Updated: Wed Apr 24 11:14:57 2013 by Drew H. Wood <http://esh-hd.esh.local:8080/rt/Ticket/Display.html?id=688&results=ffb08a9a a833ebb64a0bc00f067ee4aa#lasttrans> I went back and checked the date on the server, and it is correct. (obviously, as it knew when it created it!) Does anyone have any other ideas why this might not be working? Thanks, Drew Wood IT Administrator Eureka Springs Hospital
On Wed Apr 24 12:20:10 2013, drew.wood@eurekaspringshospital.com wrote: Show quoted text
> I am having some problems with this plugin. I am not sure if I have done > something incorrectly. I installed the plugin and created the cron job, and > tickets are being created, but they are not being created as I would expect. > I created a weekly job, to make a new ticket each Monday, and as soon as I > resolve it will create another. That would be fine, except it is creating > jobs months out, and today the ticket looked like this:
What value do you have for "Concurrent active tickets"? Show quoted text
> > > Created: > Wed Apr 24 07:46:23 2013 > > Starts: > Mon Jan 05 00:00:00 1970 > > Started: > Wed Apr 24 11:14:56 2013 > > Last Contact > <http://esh-hd.esh.local:8080/rt/Ticket/Display.html?id=688&Action=SetTold> > : > Not set > > Due: > Mon Jan 12 00:00:00 1970 > > Closed: > Wed Apr 24 11:14:56 2013 > > Updated: > Wed Apr 24 11:14:57 2013 by Drew H. Wood > <http://esh-hd.esh.local:8080/rt/Ticket/Display.html?id=688&results=ffb08a9a > a833ebb64a0bc00f067ee4aa#lasttrans> > > I went back and checked the date on the server, and it is correct. > (obviously, as it knew when it created it!) Does anyone have any other ideas > why this might not be working? > > Thanks, > > Drew Wood > IT Administrator > Eureka Springs Hospital >
Subject: RE: [rt.cpan.org #84831] Repeat ticket
Date: Thu, 25 Apr 2013 09:51:28 -0500
To: <bug-RT-Extension-RepeatTicket [...] rt.cpan.org>
From: "Drew H. Wood" <drew.wood [...] eurekaspringshospital.com>
I have concurrent tickets set to 1, and started lead time at 7 days. I have now reduced the lead time to 1 to see what happens. Show quoted text
-----Original Message----- From: Jim Brandt via RT [mailto:bug-RT-Extension-RepeatTicket@rt.cpan.org] Sent: Thursday, April 25, 2013 9:42 AM To: drew.wood@eurekaspringshospital.com Subject: [rt.cpan.org #84831] Repeat ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=84831 > On Wed Apr 24 12:20:10 2013, drew.wood@eurekaspringshospital.com wrote:
> I am having some problems with this plugin. I am not sure if I have > done something incorrectly. I installed the plugin and created the > cron job, and tickets are being created, but they are not being created as I would expect. > I created a weekly job, to make a new ticket each Monday, and as soon > as I resolve it will create another. That would be fine, except it is > creating jobs months out, and today the ticket looked like this:
What value do you have for "Concurrent active tickets"?
On Thu Apr 25 10:51:52 2013, drew.wood@eurekaspringshospital.com wrote: Show quoted text
> I have concurrent tickets set to 1, and started lead time at 7 days. I > have now reduced the lead time to 1 to see what happens.
Hmm, strange. Could you send a screenshot of your settings? Also, how many tickets did it create when the cron job ran? Thanks.
Subject: RE: [rt.cpan.org #84831] Repeat ticket
Date: Thu, 25 Apr 2013 10:14:06 -0500
To: <bug-RT-Extension-RepeatTicket [...] rt.cpan.org>
From: "Drew H. Wood" <drew.wood [...] eurekaspringshospital.com>
It would only create one at a time, though it also seems to be creating them for months from now? This ticket is a daily one. It does seem to create them every day. My second pic shows the ticket information from the ticket created today. Why is the start and end date so far out? I am running 4.06. Is there anything that might be different from the latest version, or is it possible that some library is out of date or something that might cause these strange behaviors? Thanks! Drew Show quoted text
-----Original Message----- From: Jim Brandt via RT [mailto:bug-RT-Extension-RepeatTicket@rt.cpan.org] Sent: Thursday, April 25, 2013 10:01 AM To: drew.wood@eurekaspringshospital.com Subject: [rt.cpan.org #84831] Repeat ticket <URL: https://rt.cpan.org/Ticket/Display.html?id=84831 > On Thu Apr 25 10:51:52 2013, drew.wood@eurekaspringshospital.com wrote:
> I have concurrent tickets set to 1, and started lead time at 7 days. I > have now reduced the lead time to 1 to see what happens.
Hmm, strange. Could you send a screenshot of your settings? Also, how many tickets did it create when the cron job ran? Thanks.
Download Untitled.jpg
image/jpeg 47.5k

Message body is not shown because sender requested not to inline it.

Download Untitled2.jpg
image/jpeg 23.9k

Message body is not shown because sender requested not to inline it.

On Thu Apr 25 11:14:22 2013, drew.wood@eurekaspringshospital.com wrote: Show quoted text
> It would only create one at a time, though it also seems to be > creating them for months from now? This ticket is a daily one. It > does seem to create them every day. My second pic shows the ticket > information from the ticket created today. Why is the start and end > date so far out? > > I am running 4.06. Is there anything that might be different from the > latest version, or is it possible that some library is out of date > or something that might cause these strange behaviors?
I believe the issue is you have a daily recurrence, but a 14 day lead time. The logic assumes tasks in the same recurrence will be sequential and won't overlap in time. It creates the first with a start date and a due date "lead time" days out. The next will have a start date based on the due date of the previous ticket and a due date "lead time" more days out. So I believe you're seeing each recurrence extend out by "lead time". Can you try setting lead time to 1 for a daily recurrence?