-
Suggestion
-
Resolution: Duplicate
-
None
-
Standalone.
When you move a bug from one milestone to another, that has implications for all the linked bugs/tasks It would be helpful for Jira to present a tree of the linked bugs/tasks with their milestones so that you can a) assess whether you should really should be making that change and b) have an easy one-button method to adjust everything in the tree to match.
Can we also get a report that flags any incompatible milestone settings (i.e. task/bug A is set for completion April 1, but is marked as blocked by task/bug B which is set for completion May 1. Either A needs to move to May 1 or B needs to move to April 1.
It would be even better if we had a way to mark when work on a task has actually begun (see https://jira.palm.com/browse/ES-2398 ) and then a way to generate reports that flag which bugs/tasks are due in some period of time N (say, 2 weeks from today) and have blocking bugs/tasks on which work has not yet begun.
- duplicates
-
JRASERVER-2544 Graph link dependency map
- Closed
-
JRASERVER-13362 Allow JIRA issues to be scheduled based on either Issue Due Date, Issue Start Date, Version Due Date, Version Start Date, Linked Due Date or Linked Start Date
- Gathering Interest
- relates to
-
JRASERVER-5431 Gantt chart support
- Closed
-
JRASERVER-9633 provide features to suport planning and replanning of a roadmap
- Closed