Automation : Unable to identify issue

[Carlyle Brown]

When creating Jira automation and having a list of new task, it is impossible to identify the task that are created. There are no labels, this make it difficult editing tasks from an extensive list. shown below:

[Patrik Korovsky · Accepted solution]

Hi @Carlyle Brown

You can distinguish "create" rules by interlacing them with a "log action" that you label as needed.

By using "Log action" you are not changing the rule already in place, simply expanding on it.

Based on the order of the rules, you can also see which subtask has been created and know exactly which one to open if necessary.

[Carlyle Brown]

Thank you, this solution worked seemlessly. I am now able to identify each subtask and edit when necessary 

[Nic Brough -Adaptavist-]

I don't understand what you mean by "able to know what the subtask is" - the audit log you show is clearly showing you what sub-tasks were created.  As does the issue display.

Where are you "not able to know what the sub-task is"?  

[Carlyle Brown]

Please to see Patrik Korovsky Nov 25, 2022

"You can distinguish "create" rules by interlacing them with a "log action" that you label as needed.

By using "Log action" you are not changing the rule already in place, simply expanding on it."

[Vedant Kulkarni_Trundl]

@Carlyle Brown 

You can identify it from the Automation Audit logs, something similar to the below one. The automation rule will show the newly created subtasks links as well.

[Carlyle Brown]

The audit log? that is incorrect. The audit log does not show what task/subtask is run.

So that answer is not accepted

It shows issue being created, but what is the issue exactly that is not shared.

[Vedant Kulkarni_Trundl]

@Carlyle Brown , you cannot have a separate section for something like "Created Issues From the Rule" but you can see the issue keys under Associated Items from the above snapshot and which also describes the from which "Actions" the result has generated.

Or else you can try with function {{#debug}}, for more details you can refer this Debug an automation rule | Cloud automation Cloud | Atlassian Support

Thanks

[Carlyle Brown]

I dont think you are fully understanding what i am asking. It seems that what i am asking is not offered by Atlasian.

I am not able to know what the subtask is unless i open the task itself, which is frustrating, when you have twenty task and you are not able to differenciate each task without opening . Atlasian please to fix this issue