Automation that keeps summary of parent task and subtask in syn

[Pauline Hild]

Hi everyone,

I'd like to create an automation rule that changes the summary of an automatically created subtask when the summary of the parent task is changed.

The problem now is that I used a value for the name of the subtask, e.g. {{triggerIssue.summary}} Sample QC and when the summary of the parent task is changed, the summary of the subtask contains just the summary of the parent task but without the "Sample QC". 

How can I change my automation rule to prevent this? 

Kind regards,

Pauline

[Gaurav]

Hello @Pauline Hild 

For your use case, where you need the text 'Sample QC' always appended to the summary of the sub-task, you will need to update the second rule.

In place of copying the value for Summary, you will need to set it like {{triggerIssue.summary}} Sample QC

Please refer to the below screenshot where the description has been updated with a description from the parent issue along with text before and after it.

Kindly acct the answer if this helps.

Regards,

--GG

[Pauline Hild]

Hi Gaurav, 

thanks for your answer. Unfortunately, I didn't exactly understand the screenshot you sent. How do I have to set the value? 

Kind regards,

Pauline

[Gaurav]

Hello @Pauline Hild 

Please follow the below steps:

• Click on the 3 dots next to the box below 'Description'.
• This provides the options to select the operations. The options are 'Set Value' and 'Copy From'; select 'Set Value'.
• This creates the text box under 'Description'. Please add '{{triggerIssue.summary}} Sample QC' or the relevant values.
• This will ensure that the appropriate data from the parent issue is copied with the additional text appended and updated to the child issue summary.

Please let me know if this helps.

Regards

--GG

[Pauline Hild]

Hi Gaurav,

I followed the steps you've described and tested the automation, but it didn't work unfortunately. 

I added two screenshots in case this might help to understand what happened: 

Screenshot 1: Automatically created subtasks (always "Name of the parent task" + "individual element"

Screenshot 2: I changed the name of the parent task and the individual elements are missing 

[Gaurav]

Hello @Pauline Hild 

It would be interesting to see the automation rule configuration. I tried to create a similar rule in a test environment and it worked as expected. The rule screenshot is as below.

I would suggest comparing the configurations and updating if required. Please share your feedback on the same.

Kindly accept the answer if this helps.

Regards,

--GG

[Pauline Hild]

Hi Gaurav,

the rule you've created does exactly what I want my rule to do so I compared the configurations and tried it out again but without success. I have no idea why it doesn't work.

The audit log shows that no action has been performed (screenshot).

[Gaurav]

Hello @Pauline Hild 

Kindly share the screenshots for the rule configurations. This would help in identifying the problem.

Regards,

--GG

[Pauline Hild]

Hello,

you'll find the rule configurations in the screenshots below.

Regards,

Pauline 

[Gaurav]

Hello @Pauline Hild 

The rule configurations seem okay. Could you please check and share the 'Audit Log' for the rule?

Regards,

--GG

[Pauline Hild]

Hi, 

I already shared a screenshot of the audit log above. Nothing has changed in the mean time.

Regards,

Pauline

[Gaurav]

Hello @Pauline Hild 

I probably did not communicate clearly. For a story with sub-tasks, please update the summary which would trigger the automation rule. Kindly share the Audit Log for this new execution. 

This would look something like the below screenshot.

Regards,

--GG

[Pauline Hild]

Hi Gaurav,

I think I misunderstood you, I'm sorry.

I created a task and then changed the summary of it which should trigger the rule. 

Here's the screenshot of the audit log: 

[Jack Brickey]

Hi @Pauline Hild , I just did a quick test using {{triggerissue.summary}} also this and it worked fine. 

[Jack Brickey]

I don't quite understand your first image though. Can I see the details of the "then edit issue"?

[Pauline Hild]

Hi Jack,

tanks for your answer. The first image is a screenshot from the automation that creates subtasks automatically, I forgot to mention it, sorry. 

Here's the screenshot you wanted to see: 

[Jack Brickey]

Ok so I expect what may be happening here is that it's a bit of a race condition. What I would suggest doing is to have a separate action to edit the summary field and preface that with a refetch data action. So basically it looks like this...

create subtask

refetch data

update summary