Project

General

Profile

PluginIssueDueDate » History » Version 3

Daniel Stonier, 2012-06-10 15:28

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 3 Daniel Stonier
An forked version compatible for Redmine 2.x. is also available on "Github":https://github.com/stonier/redmine_issue_due_date
10
11 1 Eric Davis
h2. Installation and Setup
12
13
# Follow the Redmine plugin installation steps at: http://www.redmine.org/wiki/redmine/Plugins
14
# Restart your Redmine web servers (e.g. mongrel, thin, mod_rails)
15
# *(optional step)* If you would like to convert of the existing issues, backup your database and run the rake task:
16
17
    @rake issue_due_date_plugin:update_due_dates RAILS_ENV=production@
18
19
h2. Usage
20
21 2 Eric Davis
h3. Issue edits
22 1 Eric Davis
23 2 Eric Davis
When an issue is edited, the plugin will check:
24 1 Eric Davis
25 2 Eric Davis
* If the issue's due date has been set on the Issue or
26
* the deliverable has a due date or
27
* the version has a due date
28 1 Eric Davis
29 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.
30
31
h3. Version or Deliverable edits
32
33
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:
34
35 1 Eric Davis
* Do not have a due date or
36
* Have a due date equal to the Version's old date
37
38
Example:
39
40 2 Eric Davis
* Version X with a due of 2008-01-01 and issues of
41
** Issues A (due on 2008-01-01)
42
** Issue B (due on 2008-02-01)
43
** Issue C (no due date)
44 1 Eric Davis
45
Changing Version X's date to 2008-01-15 will update the due date of:
46
47 2 Eric Davis
* Issue A to 2008-01-15. It has the same due date as the version, so it's "following" the version.
48 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.
49
* Issue B's due date will stay 2008-02-01.
50
51 2 Eric Davis
Deliverables follow the exact same behavior.
52
53
h3. Version or Deliverable reassignments
54
55 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.
56
57
Example:
58
59 2 Eric Davis
1. I have an issue assigned to Version A with a date that matches Version A
60
2. If I change the issue to be assigned to Version B, then the date should change to version B's due date.
61 1 Eric Davis
62 2 Eric Davis
Deliverables follow the exact same behavior.
63 1 Eric Davis
64
h2. License
65
66
This plugin is licensed under the GNU GPL v2.  See COPYRIGHT.txt and GPL.txt for details.
67
68
h2. Project help
69
70
If you need help you can contact the maintainer at the Bug Tracker.  The bug tracker is located at  https://projects.littlestreamsoftware.com
71
72
h2. News
73 2 Eric Davis
74
"0.1.0 Release Announcement":http://theadmin.org/articles/2009/7/19/redmine-issue-due-date-plugin