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

Is it possible to use workflows to automatically change the release version?

l bascle

We are currently using Sprints but not Versions.

We have synched JIRA with Stories on Board, a tool to help with long-term planning. This tool is using versions, not Sprints.

I would like to create a trigger whereby if I change the value of the 'sprint' from empty to a value, that same value is copied across to 'version'. is that possible?

Essentially, I want to ensure that sprint=version without having to set them both every time manually.

Accepted answers

l bascle

OK both @Bill Sheboy @John Funk , I have finally managed to set it up thanks to your contributions. Thank you so much! I am summarising below for visibility

Go to Automation Rules under JIRA settings
Create Rule. I have created a global rule for all projects, but you could just as well create a rule per project
CONDITION/TRIGGER: Field value changed: SPRINT.
ACTION: Create version with version name: {{sprint.name}}
BRANCH: for current issue
ACTION: edit issue field 'fix versions' with {{sprint.name}} (that was the bit that was previously missing and meant my 'fix version field was blank).

A screenshot below.

All comments

John Funk

Hi @l bascle ,

I don't think you are going to be able to use automation to populate the release if the value of the release does not exist already. If it does, then you can certainly copy the value into that field. But it can't Create the release on the fly.

l bascle

Thanks John. So do you think creating placeholders in releases would do the trick then? If so, what is even the basic workflow, because all I could seen in terms of triggers came from the change of status.

John Funk

If you know what your releases are going to look like as far as naming, I would go ahead and create those in your project. Then you just need to make sure you use those same exact value for the Sprint.

So your rule would be based on a Field value changed on the Sprint field.

Then you would do a new Action for Edit Issue and copy the value from the Current Issue.

Click on the word Current Issue then and select the Sprint field to copy from.

Bill Sheboy

Hi @l bascle

Is this what you are trying to do with a rule?

Trigger: sprint created
Action: create version, with the name of {{sprint.name}}

Or, change your trigger to sprint started, and then you could set the Fix Version for the included issues after the version is created using a Lookup action and JQL on the sprint field.

Best regards,

Bill

l bascle

exactly (if possible)

Trigger: sprint created
Action: create version, with the name of {{sprint.name}}

Bill Sheboy

Great; please look here for documentation on how to create and manage your rules:

https://support.atlassian.com/jira-software-cloud/docs/automate-your-jira-cloud-processes-and-workflows/

l bascle

Gaaah sorry! At least this link has allowed me to have a little play with automation rules and understand how they work., and i realised that it was a bit different

- trigger= sprint value created/updated

- action: create/update value with the name of {{sprint.name}}

@John Funk I tried the basics of what you suggested but maybe it doesn't work because i needed to create the releases first and name them exactly the same? is that done properly

Screenshot 2020-07-16 at 16.09.16.png

l bascle

OK both @Bill Sheboy @John Funk , I have finally managed to set it up thanks to your contributions. Thank you so much! I am summarising below for visibility

Go to Automation Rules under JIRA settings
Create Rule. I have created a global rule for all projects, but you could just as well create a rule per project
CONDITION/TRIGGER: Field value changed: SPRINT.
ACTION: Create version with version name: {{sprint.name}}
BRANCH: for current issue
ACTION: edit issue field 'fix versions' with {{sprint.name}} (that was the bit that was previously missing and meant my 'fix version field was blank).

A screenshot below.

Bill Sheboy

Great; I am glad you got it to work. Thanks for summarizing!

John Funk

Yes, thanks for the response and glad it is working for you!

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-software