Automation - changed field value not being picked up in cloned ticket

Dave Symonds
Contributor
November 20, 2023

I have an automation that changes an issue type (A to B) and then clones the issue to a new project.  The issue on the new project board has the original value  (A) for issue type even though it is cloned after the change is done.

I did a display of that value and sure enough it is set as A even though the change has been done.  When the automation finishes the original ticket has the new value of B.

 

Is the changed field value not available until after the automation has completed  - like a commit?

 

2 answers

1 accepted

1 vote
Answer accepted
Adrien Low _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2023

Hello @Dave Symonds ,

I was able to replicate your behavior and was able to resolve it by adding a Re-fetch issue data action before the Clone issue action:-

Screenshot 2023-11-21 122615.png

Give it a try and let us know how it goes.

Hope this helps.

Regards.

Dave Symonds
Contributor
November 20, 2023

Arg of course - thanks for that - all good

Adrien Low _ServiceRocket_
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
November 20, 2023

Hey @Dave Symonds ,

Glad to hear that.

If this had helped, please mark my response above as the answer.

Much appreciated.

Regards.

0 votes
Bill Sheboy
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.
November 21, 2023

Hi @Dave Symonds 

I suggest not editing the issue type with an automation rule, but instead perform a clone to the new type and then abandon (or delete) the original issue.

Changing an issue type is a complicated operation that can run into problems due to differences of fields, workflow, parent/child relationships, etc.  This is one reason the Jira UI has a specific function to do this: Move.  That allows the move to ask any necessary questions to ensure success, or to prevent the move when it is not possible.

An automation rule can do none of those things.  And so a work-around for rules is to clone and use a new issue type for the issue.

Kind regards,
Bill

Dave Symonds
Contributor
November 21, 2023

I suggest not editing the issue type with an automation rule, but instead perform a clone to the new type and then abandon (or delete) the original issue.

 

Yep, that's what I have done - I have learnt to deal with the inadequacies of Atlassian software over the years :)

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