As we work with Kanban projects the start of an issue is not always known, where the end date is fix, coming from a waterfall planning.
Mostly teams can work in parallel to some extend.
For that I would really appreciate a way to manage dependencies on a finish to finish relation.
It is not in the standard feature of Maps and I don't want yet another add-in (than I can better mrigrate to an alternative system)
Hi @jeroen_wilmes , I wonder if a solution whereby you have a work item, a.k.a. issue, that is actually a milestone, indicating two or more work items have completed. In this way, the work items would feed the milestone work item in a finish to start manner.
Technically this could work, but practically not.
It requires additional issues and it "blurs" the dependencies as you have to create an issue "in between". I hope that Atlassian is considering to bring functionalities of Jira Plans on par with benchmark planning tools.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I agree with this response. Not having the ability to set finish-to-finish dependencies will be the single biggest issue to people adopting Jira Plans for their project planning.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.