Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can I use automation to ensure a specific version is always added to the existing fixVersions

The problem is this: my teams manage their work to multiple releases, a "milestone" release and a "all complete" release.  I want to create an automation that ensures the "all complete" release is added to each and every card.   

Finding the cards that need to have the release version added is pretty simple, something like:

project=PROJ and fixVersion != "all complete"

The problem is the only way I know to add the fixVersion is to use the Edit issue action.  The edit issue action will allow me to set the fix version to the specific version, but then it will replace all existing values (including the "milestone" release(s)).  If I copy it from another issue, then it can be appended, but as near as I can tell there isn't a way to append a specific release version.

Any other ideas? What am I missing? Thank you!

2 answers

1 accepted

0 votes
Answer accepted

Hi @Joel Gillespie ,

The fix version field can contain many versions, even in the "edit issue" screen you can select as much versions as you like.

All of the above said in case you don't have some custom scripts running on your Jira to disable users from adding more than a single version to this field.

 

BTW - you should be able to change the fix versions field by clicking on the value of fix versions fields when viewing an issue in full screen.

Elad, thanks for the response.  I am able to set the fix versions manually.  The problem I'm having is how to set them automatically.  Basically I want to make sure to always add an "all complete" version to every card so that, in addition to tracking the progress towards the "milestone" version, we can track towards the final release.  We are currently doing this manually by setting the list of versions on the cards themselves, but would like to simplify the process by using jira automation (now that it is built in)

@Joel Gillespie 

Using the Jira automation is pretty simple:

You need to decide what's the trigger: You should probably use "issue created" or "issue transition" (or use a scheduled trigger to run every day if you want less automation runs)

You can then filter irrelevant issues such as subtasks (JQL: issuetype not in subtaskissuetypes() AND fixversions != "all complete" )

And the last step should be "edit issue", in this step you select "fix versions field" and on the "add" select the "all complete" version.

You can find some good tips to start with Jira automation in my presentation here: https://bit.ly/2VKW7TD

Let me know if you don't succeed.

That is what I've done, the problem is that while I can add fixVersions from the parent epic to the current issue:

add-to.png

 

I cannot do the same thing for setting a specific version:

no-add.png

 

So, as nearly as I can tell, if I set any of the version specifically, it will wipe out all the values that already exist, which isn't what I want.

Use this json command instead: (remove the fix version field from the edit itself so it won't override)

{
"update": {
"fixVersions": [{
"add": {
"name":"sdasd"
}
}]
}
}

see image:

ans3.png

Like # people like this

Hi @Elad Ben-Noam 

Thanks, your suggestion worked for me however I have another problem.

Problem is I want that if Sprint is changed to A, Fix version should also reflect A (we are using same naming conventions) and if we change Sprint field to Z, it should update JIRA with Fix version as Z and remove Fix version A 

so is there a way we can use some sort of regular expression eg below: 

 

{
"update": {
"fixVersions": [{
"add": {
"name":"CCS PI21.3 Sprint 3"
""remove":{
"name":"CCS PI*.*
}
}]
}

so is there a way we can use some sort of regular expression eg below as I w`ant to first remove all FIx version which starts with CCS PI*.* and then add CCS PI21.3 or value which is in Sprint field

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
Community showcase
Published in Confluence

Introducing External Collaboration for Confluence

We’re excited to introduce external collaboration for Confluence, now available in early access. It is available to preview for Confluence Cloud Premium and Enterprise customers. (If you're not on ...

205 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you