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; } } }

Using Automation to Create/Release Versions across Projects

James Delloso

We have multiple company-owned projects all supporting one product. Each project has the same Release version in it.

Rather that go into each project and mark the unreleased version as released , I want to use a manual trigger in global Automation to do it. It appears that the only way to do this is to add a Component for each Project and use the defaults to set the release date as the current. Is this correct?

And, is there any way to create a manual trigger that can apply to multiple projects and create a new version with the same version number?

Thanks.

Accepted answers

Yuri Lapin _Release Management_

Hi @James Delloso

Trust you are well.

I do not think you can get such automation out of the box. If you are up to Marketplace Partner Apps I would suggest to look into Release Management for Jira . There you can find an ability to "package" multiple versions from different company- & team-managed projects and sync between them. You can also choose what exactly you want to sync - just name, description, start/release dates or the combination of it.

You can also reach out to our support team for a quick demo.

Hope this helps.

Cheers,

Yuri.

All comments

Bill Sheboy

Hi @James Delloso -- Welcome to the Atlassian Community!

First thing, I have not tried this approach...

First, bootstrap this technique by creating an indicator-story in each project, assigned to the next release version, and with a unique field value searchable with JQL
I wonder if in your manually triggered rule,
Could use JQL to gather all of the relevant indicator-issues for the projects for a branch,
- Then call release version by issue/project. My understanding is this would release the version for whatever the current issue is; that is, the one currently looked at in the branch loop.
- You could then create the next version for the project, and
- Create a new indicator-story assigned to the version.

Kind regards,
Bill

Yuri Lapin _Release Management_

Hi @James Delloso

Trust you are well.

You can also reach out to our support team for a quick demo.

Hope this helps.

Cheers,

Yuri.

James Delloso

Thank you for responding. I didn't think we could do it out of the box. We need to do it on a temporary basis until we can automate it via the REST API.

James Delloso

Thank you for responding. As I mentioned above, we will eventually do this work via the REST API. I think your version could work but a little too complicated for our area.

Karyna Tyrnavska _SaaSJet

Hi, @James Delloso !

I suggest you to try out Business Process Manager add-on.

My SaaSJet team has developed it to manage business processes.

In your case, you can convert the product release procedure into Template, step = Jira issue

Also, you can add approver or conditions to your workflow to streamline processes.

Manual start is also available.

You`re welcome to set a demo call with our product manager to get a closer look at your case.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud