Automation creates child issue but won't copy values

Jennifer Joyce February 7, 2025

The purpose of this automation is to create a Change Ticket from an open Issue. I need some of the values of the original issue to copy over to the new issue.  I created an automation to trigger on demand from an issue.  It will create the change ticket in another project using "Create issue with Request type"  (it would not work with Create Issue action, as it kept failing saying request type is required and it won't let me set the request type in the action.)  The "Create issue with Request type" only lets me set the Summary and Reporter fields, so I am trying to set the remaining fields further down.

i then have a "From most recently created issue" branch where I update this new child issue.  The request type is changed (this works fine) and it links the new issue to the original issue (works fine) but the Edit Issues field is not working as expected.  It reports "successful" in the audit log, if I hard code values for these fields that is successful, but the "Copy from Current Issue" values all do nothing.  I also tested using a smart field and that also did nothing.  The fields are the shared between the two projects, so they're all the same data type.  The first field (Systems Affect) is a multi-choice drop down, the rest are all paragraphs.

What am i missing here?

automation_screenshot.png

 

 

1 answer

1 accepted

1 vote
Answer accepted
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 7, 2025

Is the option copy from trigger issue available?

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.
February 7, 2025

Hi @Jennifer Joyce -- Welcome to the Atlassian Community!

Adding to Jack's answer:

When the rule is inside the branch, "current issue" and "issue" refer to the branched-to issue.  In your case, that is the most-recently-created-one.  Instead you want to copy from the "Trigger Issue".

Kind regards,
Bill

Jennifer Joyce February 7, 2025

I continued playing with this and googling after posting as I suspected that was the case.  I was able to get this working by using smart values like {{triggerissue.my field}}.

HOWEVER.. for anyone coming after me, I have only just now realized that "Current Issue" is clickable and has a selection where I can choose Trigger issue.  <facepalm>  I think if I had noticed this earlier this may have saved me hours of frustration... 

Thank you both!

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