releases in cross-projects releases in Advanced Roadmaps

[jeroen_wilmes]

Why is it not possible to select more then one release from a project in a cross project release in Roadmaps?

When I try to do that I get the message that the project is already selected, but as you can have more than one release (fix version) in one project that is a unworkable restriction. Is there a solution for this?

[Yuri Lapin _Release Management_ · Accepted solution]

Hi @jeroen_wilmes,

Trust you are well. I might be wrong but looks like "the name" of release should be the same in all the projects for cross-project releases to work. Since you can't have duplicate names in a single project, adding multiple releases from a single projects won't work.

I bet you need to look for Marketplace Partner Apps to overcome it. Thus, you might try out Release Management for Jira where you can package multiple release from multiple projects w/o such restrictions.

If you are up to a quick demo please give our support team a shout.

Cheers,

Yuri.

[jeroen_wilmes]

Thanks Yuri,

It is not that the names should be the same. In cross project releases you can bundle releases from different projects in Jira, although only 1 release per project. Plans gives you only the option to choose one. If you try to add another release from that project it is grey-out and you cannot select. The assumption from Plans seems to be that 1 project only results in one release. However our projects have more than only just one release.

I will have a look at the Release Management for Jira app. But I realy don't understand this restriction in Advanced Roadmaps.

[Nikki Zavadska [Appfire]]

Hi @jeroen_wilmes ,

I don't think that the Advanced roadmaps team anticipated that someone would want to include 2 releases from the same project in the cross-project release.

A workaround would be to merge these 2 releases in that project together before including them into the cross-project release group in Advance Roadmaps.

Or is there any specific reason you're looking to keep both releases?

@Yuri Lapin _Release Management_ I'm really curious, is your app allowing to have 2 releases from the same project in one cross-project release group?

Thank you!

[jeroen_wilmes]

A project consists of more than one component of the same system, and both components do have there own release versions. And within the duration of the project is can happen that there will be released more than one version of the component. That all looks quite normal for a project so I wander why Advanced Roadmaps doesn't anticipate on that mechanism.

On top of that Advanced Roadmap also does not allow a release to be part of two different cross project releases

[Nikki Zavadska [Appfire]]

That makes perfect sense, thank you for clarifying @jeroen_wilmes

Although releasing component versions as part of the main project versions is common practice in many companies, Jira project versions don't really fit this use case.

There is this new tool introduced by Atlassian that helps you track component releases and upgrades and create your component catalog. Although it's quite technical maybe it's worth having a look 👉 https://www.atlassian.com/software/compass

Another option is to make use of Components in your Jira (if you don't use them already) and use them to track component versions and use your Jira project releases as Application/Project releases that bundle your component versions.

Or another option would be to look at some plugins on the marketplace that help you create component versions that are separate from project versions and can be linked to components.

I wrote this little post here in the community if you want to explore this option further.

[jeroen_wilmes]

I'm getting disapointed that Atlassian over and over again flow in integration Advanced Roadmaps into Jira, "solves" by referring to new (3rd party) applications that I can implement at substantial costs.