PluginIssueDueDate » History » Version 4
Daniel Stonier, 2012-06-10 15:31
| 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 | 2 | Eric Davis | h3. Issue edits |
| 20 | 1 | Eric Davis | |
| 21 | 2 | Eric Davis | When an issue is edited, the plugin will check: |
| 22 | 1 | Eric Davis | |
| 23 | 2 | Eric Davis | * If the issue's due date has been set on the Issue or |
| 24 | * the deliverable has a due date or |
||
| 25 | * the version has a due date |
||
| 26 | 1 | Eric Davis | |
| 27 | 2 | Eric Davis | If any of those are true, the issue will have it's due date updated. If multiple of them are true, the first one will be used. |
| 28 | |||
| 29 | h3. Version or Deliverable edits |
||
| 30 | |||
| 31 | The plugin will also hook into Versions so when the version's due date is updated, all issues assigned to the Version will be updated if the issues: |
||
| 32 | |||
| 33 | 1 | Eric Davis | * Do not have a due date or |
| 34 | * Have a due date equal to the Version's old date |
||
| 35 | |||
| 36 | Example: |
||
| 37 | |||
| 38 | 2 | Eric Davis | * Version X with a due of 2008-01-01 and issues of |
| 39 | ** Issues A (due on 2008-01-01) |
||
| 40 | ** Issue B (due on 2008-02-01) |
||
| 41 | ** Issue C (no due date) |
||
| 42 | 1 | Eric Davis | |
| 43 | Changing Version X's date to 2008-01-15 will update the due date of: |
||
| 44 | |||
| 45 | 2 | Eric Davis | * Issue A to 2008-01-15. It has the same due date as the version, so it's "following" the version. |
| 46 | 1 | Eric Davis | * Issue C to 2008-01-15. It did not have a due date so it was given the version's due date. |
| 47 | * Issue B's due date will stay 2008-02-01. |
||
| 48 | |||
| 49 | 2 | Eric Davis | Deliverables follow the exact same behavior. |
| 50 | |||
| 51 | h3. Version or Deliverable reassignments |
||
| 52 | |||
| 53 | 1 | Eric Davis | 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. |
| 54 | |||
| 55 | Example: |
||
| 56 | |||
| 57 | 2 | Eric Davis | 1. I have an issue assigned to Version A with a date that matches Version A |
| 58 | 2. If I change the issue to be assigned to Version B, then the date should change to version B's due date. |
||
| 59 | 1 | Eric Davis | |
| 60 | 2 | Eric Davis | Deliverables follow the exact same behavior. |
| 61 | 1 | Eric Davis | |
| 62 | h2. License |
||
| 63 | |||
| 64 | This plugin is licensed under the GNU GPL v2. See COPYRIGHT.txt and GPL.txt for details. |
||
| 65 | |||
| 66 | h2. Project help |
||
| 67 | |||
| 68 | If you need help you can contact the maintainer at the Bug Tracker. The bug tracker is located at https://projects.littlestreamsoftware.com |
||
| 69 | |||
| 70 | h2. News |
||
| 71 | 2 | Eric Davis | |
| 72 | "0.1.0 Release Announcement":http://theadmin.org/articles/2009/7/19/redmine-issue-due-date-plugin |