Copying Summary from Trigger Issue into Custom Field on all Linked Issues

[Jacob Dressler]

Hello!

I am trying to copy the summary of an issue into a custom field and then also copy that summary into all Linked Issues.

I have gotten the first part to work. When I originally started attempting this automation I had the custom field populated by the summary on the original issue and then tried to copy the contents of the custom field from the trigger issue into all linked issues. The audit log showed it as successful; however, only the original issue had its field updated.

I then adjusted the automation to instead of copying that custom field down to the linked issues, just Set the automation to the smart value triggerissue.fields.summary. The audit log shows that too as successful but the linked issues do not change.

I can see it targeting the correct linked issues so I don't think the problem lies there. I think something is going wrong with the smart value and/or the copy custom field portion I had before. Though I am not sure what as everything I can find says this should be working.

[Salih Tuç · Accepted solution]

First of all, can you please try to change the smart value to {{triggerIssue.summary}}, note that the convention is camel case.

And also, can you go to the "Audit log" section of your automation and send us the details of the latest failed log, please. This way, we can understand the problem better.

[Jacob Dressler]

So the audit log isn't showing anything failing. It is saying it's successful.

Both photos show the same results. The second photo is after making the change you suggested to the smart value.

[Salih Tuç]

Can you check the history of linked issues, let's say VULN-25607 in order to see the changes is in the history or not? Maybe some other automation is overwriting right after this automation. 

[Jacob Dressler]

Wow thanks for thinking of this. I had made a clone of an earlier version of the automation that was incorrect with a different trigger. So every time I was manually triggering this to test it was just being overwritten with the incorrect automation.

[Bill Sheboy]

Hi @Jacob Dressler -- Welcome to the Atlassian Community!

After you edit the trigger issue, add a Re-fetch Issue action to reload the data before the rule proceeds.  That will ensure the latest update to the field is used when you branch to the linked issues.

Kind regards,
Bill

[Jacob Dressler]

Hey, so I originally had it re-fetch the issue data when it was still just configured to try pulling the custom field "Vulnerability Description" down to the linked issues. I still had the re-fetch in place when I switched it to the triggerIssue.fields.summary and it still didn't work then.

I have since removed that re-fetch because the data it's looking for, the summary, isn't being altered in any way so that data should be present when the automation runs at all.

I also had a delay in place earlier in case it was being very slow and the re-fetch was still too quick, but that didn't help either.

I don't believe the re-fetch should be necessary at this point because I am no longer looking at the custom field being pulled over but the summary.

To be quite honest I can probably remove the custom field being updated on the original trigger issue at this point as the entire purpose of it being present before was to carry it over to the other issues, but seeing as I should be able to just copy the triggerissue summary down to the other linked issues custom field, it shouldn't be necessary anymore at this point.