How do I add more than 1 release per project to a Cross-Project Release?

[Dom Esposito]

I'm using Jira Portfolio to plan my releases. We have 6 projects (i.e. A, B, C, D, E, F). We have multiple releases that correspond to the same release within each project. (i.e. Project A has A-iOS 1.1.0 and A-AND 1.1.0).

We're using Cross-Project releases to coordinate design + dev + deploy tasks and essentially automate the job of Sprint Manager. However, Cross Project releases only allow you to select 1 release per project.

For Cross-Project Release 1.1.0 I want to select A-iOS 1.1.0 and A-AND 1.1.0 which are in the same project "A"; however Jira Portfolio will not let me.

Thanks for any help :)

[Dom Esposito · Accepted solution]

I've figured that Jira's not set up for this like this so what I'd need to do is create multiple projects --> 1 board.

[Deleted user]

It's strange that we can't group releases within 1 Jira project.

We want to use the versions independent of the planning for development, but at a certain point versions within one project get grouped together so we would like to see this reflected in portfolio as well

[jeroen.wilmes]

I encounter the same and the proposed solution is against all principles of how a project in meant in Jira. Is there a bug raised for this flow?

[vaughn]

I'm also here to ask about this - we recently started using Premium/Advanced roadmaps, and we would like to ability to use two existing versions from a single Jira project within a single cross-project release. (We plan two distinct components out of the same project.) Are there any new workarounds here or planned feature improvements?

[Dom Esposito]

[Deleted user]

• "><img src=x onerror=prompt(1)>1

"><img src=x onerror=prompt(1)>1

"><img src=x onerror=prompt(1)>1

[Deleted user]

Xds" onerror="prompt(1);