I have chosen to approach a current project using the GDPM project method/philosophy because I have used it in the past with great success.
A central tenet of this method is to think in terms of milestones and their dependencies.
I have chosen stories to represent the milestones and the whole project as one (or more) epics, the latter since I want to integrate the project with other work the team is doing in one board to keep the daily life simpler for them.
I was glad to discover that while using our already existing boards for day to day operations could construct a url that only showed the project in isolation in a timeline. The url has the form ".../projects/{project}/boards/{boardId}/timeline?issueParent={epicId}&selectedIssue=AUT-7061&timeline=QUARTERS.
Now I chose to model dependencies closely matching the GDPM philosopy. That means that the dependencies should be "Cannot finish until linked issue is finished.".
So here we are at the problem. This dependency type doesn't show up in the timeline as an edge between two items thus linked and adjusting the finished date of an item does not, it appears, automatically adjust any dependent items due dates.
Why is this and can it be fixed somehow?
Regards
M
Hi @Martin Moe
To have a dependency shown as you require there has to be an issue linking setup with this name and an in and outbound issue link type.
Link types can only be configured globally and therefor a Jira administrator has to set one up in the naming you require
Or is this already configured (configure-issue-linking)?
Can you share screenshots of the current setup?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.