User Tools

Site Tools


mantisbt:due_date_requirements

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
mantisbt:due_date_requirements [2007/02/12 08:59]
azimmer "Next action expected on" field request added
mantisbt:due_date_requirements [2008/12/01 13:00] (current)
mthibeault Note about working days.
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), the default value should be HTML.  The possible values should be EMAIL_FORMAT_TEXT and EMAIL_FORMAT_HTML constants that map to values 0 and 1. 
  
 ===== Configuration Changes ===== ===== Configuration Changes =====
Line 29: Line 28:
      * Excel export      * Excel export
      * Word export      * Word export
-   * Support an "overdue" column which is typically an icon that is shown for issues that have due date, due date already passed, and the issue status is less than the configured resolved status.  In the case of csv export, use a 1/0 flag to indicate if an issue is overdue or not.+   * Support an "overdue" column which is typically an icon that is shown for issues that have due date, due date already passed, and the issue status is less than the configured resolved status.  In the case of csv export, use a 1/0 flag to indicate if an issue is overdue or not.  We may also want to consider having this as a field with a value equal to number of days to due date, which turns negative after the due date.
    * 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).  This should not be shown by default.    * Support a new block in My View page which shows overdue issues (Overdue Issues).  This should not be shown by default.
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" timestamp as a token.
    * 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.  In the case of html, issue ids must be hyperlinked to the issue view page. 
    * 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 61: Line 59:
   * 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 due date in Report, Update, and View Issue pages.
 +  * Support Filtering by Due Date.
 +  * Support in View Issues, Print Issues, CSV, Excel, and Word.
 +  * Cronjob script for email notifications.
  
  
Line 66: 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/Version Deadline, see [[Roadmap Requirements]]. Probably there should be some consistency checks when the target version, issue deadline, or version deadline is changed.
 +
  
 * 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 "SLA" timeout is the time an issue is expected to be resolved. Whenever one of this timers expires an email is sent to (configurable): the reporter, the assigned developer (if any) and the project manager. * 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 "SLA" timeout is the time an issue is expected to be resolved. Whenever one of this timers expires an email is sent to (configurable): the reporter, the assigned developer (if any) and the project manager.
Line 71: 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/category. Obviously when calculating the new date, we should only allow for working days, function can be found below: * 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/category. Obviously when calculating the new date, we should only allow for working days, function can be found below:
  
 +* 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).
 ---- ----
  
Line 98: Line 108:
 } }
 </code> </code>
- 
-* It would be helpful to have a "Next action expected on" date field.  It is somewhat similar to due date in that it is a time-related field.  It is, however, not aimed at registering the date by which the issue is about to be resolved but the date before which progress is unlikely to happen.  It is most useful when changes are pending due to something external force.  If filtering would be possible using this field (and/or display it in View Issues, My View, etc), one could avoid having to scan through issues which are pending anyways.  Currently there are possible work-arounds to this (hierarchy and a new meta-issue, custom field, continuously updating due date), none of which is quite nice. 
- 
mantisbt/due_date_requirements.1171288770.txt.gz ยท Last modified: 2008/10/29 04:31 (external edit)