PluginIssueDueDate » History » Version 1
Eric Davis, 2009-07-19 01:40
Adding description of the Issue Due Date plugin
| 1 | 1 | Eric Davis | h1. Issue Due Date plugin |
|---|---|---|---|
| 2 | |||
| 3 | Issue Due Date will set the Issue due dates to the due dates of versions or deliverables. It will also track due date so if a Version's due date is changed, all of it's issues with the same due date will also be changed. |
||
| 4 | |||
| 5 | h2. Getting the plugin |
||
| 6 | |||
| 7 | A copy of the plugin can be downloaded from "Little Stream Software":https://projects.littlestreamsoftware.com/projects/redmine-misc/files or from "GitHub":http://github.com/edavis10/redmine_issue_due_date/tree/master |
||
| 8 | |||
| 9 | h2. Installation and Setup |
||
| 10 | |||
| 11 | # Follow the Redmine plugin installation steps at: http://www.redmine.org/wiki/redmine/Plugins |
||
| 12 | # Restart your Redmine web servers (e.g. mongrel, thin, mod_rails) |
||
| 13 | # *(optional step)* If you would like to convert of the existing issues, backup your database and run the rake task: |
||
| 14 | |||
| 15 | @rake issue_due_date_plugin:update_due_dates RAILS_ENV=production@ |
||
| 16 | |||
| 17 | h2. Usage |
||
| 18 | |||
| 19 | The plugin should set the Issue's due date whenever an Issue is saved to be: |
||
| 20 | |||
| 21 | * Specific Issue due date or |
||
| 22 | * Version due date or |
||
| 23 | * Deliverable due date |
||
| 24 | |||
| 25 | The plugin will also hook into Versions so when the versions' due date is updated, all issues assigned to the Version will be updated if they: |
||
| 26 | |||
| 27 | * Do not have a due date or |
||
| 28 | * Have a due date equal to the Version's old date |
||
| 29 | |||
| 30 | Example: |
||
| 31 | |||
| 32 | Version X due on 2008-01-01 with: |
||
| 33 | |||
| 34 | * Issues A (due on 2008-01-01) |
||
| 35 | * Issue B (due on 2008-02-01) |
||
| 36 | * Issue C (no due date) |
||
| 37 | |||
| 38 | Changing Version X's date to 2008-01-15 will update the due date of: |
||
| 39 | |||
| 40 | * Issue A to 2008-01-15. It has the same due date so it's "following" the version. |
||
| 41 | * Issue C to 2008-01-15. It did not have a due date so it was given the version's due date. |
||
| 42 | * Issue B's due date will stay 2008-02-01. |
||
| 43 | |||
| 44 | When reassigning an issue to a different version, if the issue due date matched the old version date, the issue will change it's due date to match the new version. |
||
| 45 | |||
| 46 | Example: |
||
| 47 | |||
| 48 | # I have an issue assigned to Version A with a date that matches Version A |
||
| 49 | # If I change the issue to be assigned to Version B, then the date should change to version B's due date. |
||
| 50 | |||
| 51 | The same behavior will be for Deliverables, if the +budget_plugin+ is installed. |
||
| 52 | |||
| 53 | h2. License |
||
| 54 | |||
| 55 | This plugin is licensed under the GNU GPL v2. See COPYRIGHT.txt and GPL.txt for details. |
||
| 56 | |||
| 57 | h2. Project help |
||
| 58 | |||
| 59 | If you need help you can contact the maintainer at the Bug Tracker. The bug tracker is located at https://projects.littlestreamsoftware.com |
||
| 60 | |||
| 61 | h2. News |