Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

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

Jira Service Desk fix version how to auto update fix version from JIRA backlog project

Project JIRA Service Desk has its own fix version.  This ticket is paused waiting for backlog ticket fix via another Jira project. 

How do I get a report to extract when backlog ticket is changed OR is there any automation to update the JIRA Service Desk fix version when backlog ticket gets reprioritised  and fix version changes as currently this is all done manually.  I

 

PROJECT-123 [Jira Service Desk project]  will be fixed by   ABC-123 [Jira project]  fix version 21.02

ABC-123 later gets prioritised to fix version 21.03 - in order to update PROJECT-123 to correct fix version (in JIRA Service Desk) a manual check is performed.

1 answer

Hi @Julie Sagar 

Versions are project specific - so even if they have the same name, they're technically two unique Versions.

There are some options though...

--------------

Automation Rules would need to be per FixVersion for this to work. This is because Automation Rules could not reference the "same" FixVersion name across two projects. 

There might be something you can do using Smart Values, for example using {{issue.fixVersions.name}} to compare name similarities? I haven't been able to get this to work effectively though.

To build a rule per FixVersion, you'll need to be a Jira Admin and then:

  1. Go to Jira Settings > System > Automation Rules
  2. Press the blue Create Rule button
  3. For the Trigger, select Field Value Changed. Choose to monitor the FixVersion field.
  4. Add a Condition, JQL Condition - enter the JQL: project = ABC and fixVersion = 123
  5. Add a Branch, set "Type of Related Issues" to Linked Issues. Choose the appropriate link type (eg. blocks)
  6. Under the Branch, add an Action - Edit Issue. Set the FixVersion to 123 (or to the matching Version under the linked project)
  7. Give the rule a name, and publish it

Then create more rules, one per FixVersion. You'd need to add rules whenever a new Version is created.

You could also do this by using the If/Else Block condition and run it all under one rule - although it could get quite complicated over time.

These instructions assume there's only one trigger project, and one linked project, issues are within. It also assumes the FixVersions can be easily identified for the Action (eg. they have a UID per project).

--------------

Alternatively, you can search for FixVersion changes - although it would still work best per FixVersion.

Natively, what you could do is:

  1. Create/Save a filter for each version - the JQL would be: fixVersion was "FV1" AND fixVersion != "FV1"
  2. Once all are created, create a new filter which references all the other filters - the JQL might be: project = ABC AND filter in (Filter1, Filter2) and updated >= -24h
  3. Either create a Dashboard to list the issues from (2), or a Subscription which sends you the results within a given timeframe.

You could then use this check to see where FixVersions have changed, and update the related issues. You'd need to add more filters as you add Versions.

I would change the updated parameter in (2) based on whether it's a Dashboard (eg. change to ORDER BY updated DESC), or to align to the timeframe chosen in your Subscription.

--------------

If you'd like to go further than this with search - such as comparing two different FixVersions using JQL - you'll need an app offering more advanced JQL functions, like ScriptRunner.

Then you could compare where FixVersions don't match in the same query, using linkedIssuesOf

--------------

Let us know if any of these options work for you!

If you'd like further help to implement any of these, please provide more specifics around your Projects and FixVersions.

Ste

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Confluence Cloud

Confluence Bingo Round 3!

That’s right! Grandma’s back at it again, and this time she’s brought all her friends. In honor of Team '21, this Bingo round is dedicated to all things team-related, and the prizes are no exception....

39 views 0 3
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