Releases shared across projects

[Michael Holian]

I have read the articles related to use Jira Plans to manage cross-project releases, but that still leaves me with assuring that projects individually create and maintain their releases in their project.

What if a different approach were taken, perhaps by enabling Releases to be shared through Atlas much in the same way components are being shared? Is that feasible?

I couldn't find an enhancement request related to this, but to me, it seems to make sense.

[Danut M _StonikByte_]

Hi @Michael Holian,

You are right, the releases can only be added for individual projects, not cross-projects. But, nothing prevents you to create the same release in multiple projects. For example, add "Version 1" release in Project A and Project B. 

Once you do this, when filtering by FixVersion = "Version 1" in JQL queries/filters will actually return issues from both projects A and B. And this is great, because you can create agile boards based on a filter like this, which brings all items with "Version 1" from project A and project B in the same board. 

In addition, by using such filter in combination with a Jira plugin such as our Great Gadgets, you can create cross-project burndown chart and all kind of analytics for tracking your cross-project release. See https://community.atlassian.com/t5/App-Central-articles/Creating-a-cross-teams-release-burndown-chart-in-Jira-with-Great/ba-p/1803421 

Danut.

[Michael Holian]

yes, and that is what we do. However, we run into issues when a release name is entered incorrectly, maybe a trailing space or capitalization. Also, when the release is completed, it must be updated in each project. A centralized release repository might make a lot more sense.

If it is done for components, why not releases?