Hello - I'm just wondering if there were any existing notions of Jira to handle project versions dependencies. Let's say I have one product, product A, which is based on product B and version A1 cannot be released without B3 to be so. Is it somehow achievable already or is it somewhere on your radar?
Pierre, to some extent this can be achieved by representing versions with "meta" issues of a special type or project, and organizing them into hierarchy. However, there are two shortcomings: a) you can interpret an issue as a version, but JIRA won't - so you'll need to keep manual mapping between those meta issues and versions; b) so far a structure may have a single issue only in one position, so if your dependency graph is not a tree, you won't be able to represent it in a structure.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs