You can clone with
No one assigned
@duckduckhack Results seem to be fixed to the server's timezone. A difference result, eg: "After 1 hour 5 minutes" will be much better.
I feel that the @_gagan's relative time will still have the same drawback, e.g: if DDG's server time is 12PM and a cron job is run every day at 2PM, the relative result of "After 2 hours" will still be incorrect for users in, say, the DDG+4 timezone (they would expect "After 22 hours" instead).
@Habbie's fix is the best case scenario, but I fear this is beyond my skill. There are a couple of other fixes I do have in mind:
a) Show the time in UTC to eliminate confusion. e.g.
Cron will start this event next at 12:42:00 on 2 Feb, 2013 UTC.
b) Show the next 3 events to make it clearer. e.g.
Cron will start this event next at the following times:
06:01:00 on 15 May, 2012.
06:02:00 on 15 May, 2012.
06:03:00 on 15 May, 2012.
Not the best fix, but this at least clearly shows that the cron job is run per minute, irrespective of timezone.
I like option b) a lot as I often want to know a few times it will start. Also we could change the wording a bit to indicate like Cron will schedule this job at this frequency:
Fix for issue #95
This was fixed, why it wasn't closed yet?