mantisbt:due_date_requirements
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
mantisbt:due_date_requirements [2006/10/18 10:48] – cas | mantisbt:due_date_requirements [2023/09/23 04:03] (current) – [Due Date Requirements] kevin_kuo | ||
---|---|---|---|
Line 10: | Line 10: | ||
* Add an optional due_date field to the issue table. | * Add an optional due_date field to the issue table. | ||
- | * Add a configuration option for preferred email format (email_format), | ||
===== Configuration Changes ===== | ===== Configuration Changes ===== | ||
Line 29: | Line 28: | ||
* Excel export | * Excel export | ||
* Word export | * Word export | ||
- | * Support an " | + | * Support an " |
* Support for filtering by due date, this is by specifying a date range to match against. | * Support for filtering by due date, this is by specifying a date range to match against. | ||
* Support a new block in My View page which shows overdue issues (Overdue Issues). | * Support a new block in My View page which shows overdue issues (Overdue Issues). | ||
Line 36: | Line 35: | ||
===== Reminders ===== | ===== Reminders ===== | ||
- | * Provide a script that can be called from a cronjob to send reminders for due / overdue issues. | + | * Provide a script that can be called from a cronjob to send reminders for due / overdue issues. I'm think this can be done from the same script that sends queued emails, in such case we make want to save the "last executed" |
* Each user that is a handler in one or more projects and has one or more issues that are due or overdue should receive only one email whenever this script is called. | * Each user that is a handler in one or more projects and has one or more issues that are due or overdue should receive only one email whenever this script is called. | ||
* The recommendation will be to execute this script once every morning. | * The recommendation will be to execute this script once every morning. | ||
- | * Support for both html/text emails. | ||
* The formatting of each issue should be done through a custom function that takes the issue number and the user preferred format as an input. | * The formatting of each issue should be done through a custom function that takes the issue number and the user preferred format as an input. | ||
* The reminder layout will look as follows: | * The reminder layout will look as follows: | ||
Line 60: | Line 58: | ||
* It would be nice to allow users to click on an icon to download a calendar (e.g. iCal) or todo entry that automatically gets added to user's todo list or calendar (e.g. Outlook). | * It would be nice to allow users to click on an icon to download a calendar (e.g. iCal) or todo entry that automatically gets added to user's todo list or calendar (e.g. Outlook). | ||
* It would also be nice to have some sort of integration with online calendars (e.g. Google, Live, Yahoo, etc). | * It would also be nice to have some sort of integration with online calendars (e.g. Google, Live, Yahoo, etc). | ||
+ | |||
+ | ===== Development Stages ===== | ||
+ | |||
+ | Following are the development stages of this feature in order to avoid one big patch: | ||
+ | |||
+ | * Database Schema Changes. | ||
+ | * Support Filtering by Due Date. | ||
+ | * Support in View Issues, Print Issues, CSV, Excel, and Word. | ||
+ | * Cronjob script for email notifications. | ||
Line 65: | Line 72: | ||
Please add your comments and feedback in this section. | Please add your comments and feedback in this section. | ||
+ | |||
+ | * The due date of tasks should also be integrated with the Roadmap/ | ||
+ | |||
* My suggestion is to be able to assign two time limits for each priority (by project). The inactivity timeout is the time an issue can stay without updates. The " | * My suggestion is to be able to assign two time limits for each priority (by project). The inactivity timeout is the time an issue can stay without updates. The " | ||
Line 70: | Line 80: | ||
* Would suggest that the Due date could be calculated by Mantis based upon a set number of days in config_inc.php or even better based upon a number of days set by project/ | * Would suggest that the Due date could be calculated by Mantis based upon a set number of days in config_inc.php or even better based upon a number of days set by project/ | ||
+ | * The concept of working days can definitively be different from one business model to the other. There is some time or type of business that could require due_date other than weekdays (ie newspaper would appreciate to be able to get a saturday or sunday due date for release of their news). | ||
---- | ---- | ||
- | /* | + | <code php> |
- | This functions | + | # |
- | 2 parameters, the startdate | + | # This function |
- | */ | + | # @param |
+ | # @param duedays | ||
+ | # | ||
+ | function calcduedate( $p_startdate, | ||
+ | $t_datecalc = $p_startdate; | ||
- | function calcduedate($datecalc, | + | |
- | $i = 1; | + | while ( $i <= $p_duedays |
- | while ($i <= $duedays) { | + | $t_datecalc |
- | $datecalc | + | $t_date_info |
- | $date_info | + | |
- | if (($date_info[" | + | |
- | $datecalc += 86400; // Add a day. | + | |
- | continue; | + | |
- | } | + | |
- | $i++; | + | |
- | } | + | |
- | return $datecalc ; | + | |
- | } | + | |
- | ---- | + | |
+ | if ( ( $t_date_info[" | ||
+ | $t_datecalc += 86400; // Add a day. | ||
+ | continue; | ||
+ | } | ||
+ | |||
+ | $i++; | ||
+ | } | ||
+ | |||
+ | return $t_datecalc; | ||
+ | } | ||
+ | </ |
mantisbt/due_date_requirements.1161182927.txt.gz · Last modified: 2008/10/29 04:31 (external edit)