We have projects with multiple Components (e.g. ios, android, rest, backend) etc. Rather then using seperate projects with serperate sprints, I want to keep these components within a single project and version them. I am evaluating the Component/subcomponent version plugin which seems to solve part of this, but its a bit pricey and I'm afraid it may not solve all my requirements.
We need to solve these two problems:
1. Identify a release by component versions e.g. "Release 5.3.0" is composed of specic component versions e.g. "Android 5.2.0" and "ios 5.2.4".
2. (The most important one) We need to define component dependencies within this release. e.g. "Android 5.2.0" requires minimum version of "API 5.1.5", and "PORTAL 5.2.0" requires minimum "BACKEND 5.1.0"
Is there any way to do this? Currently we're tracking this in a report manually outside of Jira whichis prone to error and would be better to maintain this within Jira.
As I said, I'm trying to avoid splitting out Components to individual projects. I'm sure someone has solved this already, and look forward to hearing from you!
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