Cross-Project Release Management in Advance Roadmaps

[Riley Sullivan]

Hello Everyone,

We recently finished transitioning all of our projects from team-managed to company-managed, so these screenshots are only test examples. However, I need to understand cross-project releases. Finding it difficult to locate best practices for advanced roadmaps, particularly with regard to release management.

Question

Is there a simple method to view all releases and release notes in a streamlined format? Similar to the project-level view?

We have all of our releases to be aligned on the same schedule and there is a lot of cross over between each project. Each project has it own task in its own project, ex. Project 1 has Task A, and Project B has Task B, even though both tasks may be connected between both. When creating a cross-project release there is not an effective way to have a streamlined format. It would be nice to have the same link from the project release level at the cross-project release level!

Outside of viewing releases in the Timeline view in Advanced Roadmaps, which is helpful but not for release management. It seems the only way to view all issues in the release is to create JQL filter (we need to export all issues in a release). Followed by jumping into each individual project to grab release notes.

We have several projects and this method does not seem streamlined or effective, so curious if I am missing something. Any insight or ideas would helpful, thank you!

[Walter Buggenhout · Accepted solution]

Hi @Riley Sullivan,

I think the key element to understand the complexity, is that releases in Jira are linked to a (Jira) project. As your screenshots clearly illustrate, even if your releases have exactly the same name, they still are different artefacts in Jira.

It has been (and still is) common practice to set up a Jira project to manage sofware development work for an application. Applications commonly are versioned using a numerical structure alpng the lines of 1.7.23 and so on. Which makes it perfectly logical to restrict the scope of this versioning system to just the project linked to that application.

With the arrival of agile frameworks and practices like quarterly planning, releases are also being used more frequently to represent the time dimension for cross-team and cross-project planning.

Being a planning / forecasting tool, Advanced Roadmaps has introduced a vehicle that allows you to aggregate the releases coming from those different Jira projects into one umbrella release, but for planning purposes only. It lets you schedule (and review) the planning holistically in the planning tool. But indeed, when you want to manage release notes, formally release a version and so on, those things are still done from within the (separate) releases linked to each separate Jira project.

Hope this sheds some light!

[Riley Sullivan]

Thanks @Walter Buggenhout, very helpful! Understanding the main idea of Advanced Roadmaps is strictly for planning/forecasting helps shed light on how to use it properly!

For release management, we'll continue to utilize filter views and hopping into the projects to grab release notes. But will continue to look to see if there is a more streamlined process. Thank you!