nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Multiple products, single release process

Francis Peixoto

Is there a way for me to align several product based projects to a single release management process? Release to QA and to Prod for all projects are all triggered at the same schedule, weekly, so we need to gather version notes from all the projects into a single document to prepare the release packages.

For example: if I run an query "fixVersion = Prod_20180410", create that version ID in all the projects and associated issues to that ID in all the in-scope projects, will the results show the issues from those projects that are labeled with that version ID?

Accepted answers

Tarun Sapra

Hello @Francis Peixoto

Your assumption is correction i.e. if you execute the JQL

fixVersion = <name>

Then it should return issues from all projects which have the mention fixVersion. But I am not sure if this approach is scalable because you will have to make sure that different projects have same versions, which over a period of time won't work.

Thus, my suggestion to you is to use an alternate approach. Basically create a project especially for Releases and have a super type issue in that project like "Initiative" or "Release" and link all the issues from other projects under this super type issues using Portfolio/Structure plugin and then do your releases. In this way you enter fixVersion in only 1 project and the whole hierarchy of issues being released is also visible to you and this should make things more simpler.

All comments

Tarun Sapra

Hello @Francis Peixoto

Your assumption is correction i.e. if you execute the JQL

fixVersion = <name>

Francis Peixoto

In my scenario, all projects will have the same version naming convention. If project A doesn't have anything to release in a given version, but project B does, then the release notes would only include issues from project B. Project A would essentially "skip" this version. Projects would skip whatever version number doesn't align with the weekly release schedule.

I'll still backpocket your suggestion, which is a scenario I looked into as well. I figured that my initial assumption would be more of a first step towards a more mature process that requires more extensive tooling.

Thanks!

Mark_vbi77k

@Francis Peixoto This is a great question. Did you ever come up with a good solution for your use-case?

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

automation

release-management