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

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

Dave Symonds_0px2ch

I have an automation that changes an issue type (A to 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?

Accepted answers

Adrien Low [ServiceRocket]

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.

All comments

Adrien Low [ServiceRocket]

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_0px2ch

Arg of course - thanks for that - all good

Adrien Low [ServiceRocket]

Hey @Dave Symonds ,

Glad to hear that.

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

Much appreciated.

Regards.

Bill Sheboy

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_0px2ch

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

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud