-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
7
-
Currently the Cross-Project-Release function does not allow for more than 1 release from 1 Jira project.
Scenario:
We have many components (essentially microservices) that are maintained in a single Jira project (essentially a team). Each of those components have their own versions and we track those using Jira Releases individually. For example, I have
Component A
Component B
I may have the following Releases:
Component A-1.0
Component A-1.1
Component B-3.1
Component B-3.2
Component A-1.2
And I oftentimes want to group one or more of them into a single overall release which I want to use Jira Advanced Roadmaps to track. With the current limitation of only allowing a single release from a project, there is no way to display this in Advanced Roadmaps.
- duplicates
-
- Gathering Interest
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JRACLOUD-89824] Allow Cross-project-release to add more than 1 release from 1 Jira project
this is an essential feature to plan the big releases, which involve multiple teams and multiple components and this is a very common scenario these days. Please implement this feature asap.
I would suggest everyone who is facing the same problem to have look at and vote for:
https://jira.atlassian.com/browse/JSWCLOUD-20462 (2020)
https://jira.atlassian.com/browse/JSWCLOUD-23007 (2022)
Jira classified it as a "suggestion", and since 2022 nothing happened with something that to me is a serious shortcoming of the integration of Advanced Roadmaps into Jira.