Time interval and cron settings [#11120]

The Project module hard codes some time intervals (e.g. 14 days before fixed issues are closes). Some other time intervals are read from the database, with a hard coded default value, but are never writen to the database (e.g. project_reminder_interval, default value 28 days).
It would be nice if we were able to set all these values on a page like admin/project.

Comments

Comment #1

pfaocle

He/Him

English

commented 11 October 2005 at 12:25

+1 for a couple of options - especially for fixed->closed interval, as then I'd have the ability to turn this off by entering, eg, 0 or -1

May brew up a patch later, seeing as though I;'ve just dug this issue up from a year ago... ;)

Comment #2

pfaocle

He/Him

English

commented 11 October 2005 at 14:07

Title:

Hard coded time intervals should be variable

» Time interval and cron settings

A new 'cron options' settings tab could house these settings. Some common optional scheduled features could be:

close fixed | won't fix issues after n days/weeks/months
delete
mark long-standing critical issues as hot, or 'emergency' or somesuch (I think Dries mentioned this somewhere, not sure where)

I know there is a call for less options ATM, but this would be an additional plus in terms of letting the user know whats going on with their issues, as we could incorporate some checks to see whether cron or poormanscron module is enabled,