We have premium and are deep diving into the possibilities in Advanced Roadmaps, specifically the cross-project releases.
We have team-based project setup in Jira, meaning that one team (aka 1 project) work with different applications/modules. Each project use project specific releases to tagg issues into. Since each team work with several applications/modules, this means that 1 jira project have several "live" releases ongoing. This ensures clear labelling/tagging of issues to each product-specific release.
In Advanced Roadmaps, cross-project releases may be created, making it possible to create a holistic overview of all the different issues from different projects. Typically for biannual, quarterly company-wide releases.
Only one (1) project specific release may be included into the same cross-project release. With a team-based set up of Jira-projects with several ongoing project-releases, this really means that I cannot use cross-project releases as I want to. When I cannot add several releases from the one project into the same cross-project release - my proof of concept fails big-time.
So, am I missing something vital in the roadmap setup? Or am I correct in assuming that what I want cannot be done?
Hello Community! We thoroughly enjoyed this just-for-fun conversation in the Jira Admin Group about what it's like to be a Jira Admin. For #JiraJuly, our talented designers created these graphics t...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events