Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Add to fixVersion when issues is closed

April_Delay
Contributor
July 21, 2023

I'm trying to make an automation that does the following:

 

When and issue is closed

If the FixVersion is not empty

Then ADD TO the FixVersion with the next unreleased version

AND

If the FixVersion is empty

Then add to the FixVersion with the next unreleased version

 

 

All I can seem to do is clear and replace the field. I want to keep the original version, so I know when it was originally scheduled. I do have Scriptrunner

2 answers

0 votes
Hieu
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 22, 2023

How about add fixVersions to the transition screen when you close the ticket?

0 votes
Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2023

Hi @April_Delay 

You can use Automation to execute this for you.

A rule like this should be able to for see in your request

Screenshot 2023-07-21 at 13.35.49.png

April_Delay
Contributor
July 21, 2023

Hi Marc, this is close, but the problem is I want the issue to add a FixVersion when closed, even if it already has one.

 

So like... issue has FixVersion 1.1

It closes

Add FixVersion 1.2

New value is 1.1, 1.2

Marc - Devoteam
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
July 21, 2023

Hi @April_Delay 

Short version: you cannot do that without a work-around

Longer version:

JQL knows about Next Unreleased Version for queries, and rules know about that value for field edits, but the issue fields know nothing about other versions/releases: only their current values.

One work-around would be:

  • save the current value of fixVersion in a created variable
  • use edit to set the value of fixVersion to the Next unreleased version
  • use the re-fetch action to reload the trigger issue
  • and now edit the issue again, adding the saved values from the created variable using the JSON edit format

So I made this rule:

Screenshot 2023-07-21 at 17.07.24.pngScreenshot 2023-07-21 at 17.07.41.png

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events