Automation for Jira | Doesn't Recognize Labels it Creates

[AJ Depew]

I have a situation where I'm creating a label on an Epic when one of its stories gets slotted in a Sprint.  I'd like to update a service desk ticket that is linked to the Epic with a new Status when the label is applied, but Automation for Jira is not seeing the new label added by itself.  If I add the label manually, the automation works.

The problem I'm really trying to solve is that I have an Epic that was cloned from a Service Desk ticket and I'm trying to tie their progression together.  When I slot a story for a Sprint, I want the Epic and the Service Desk ticket to get updated with a new status.  One idea was creating a label and using that to flag the Service Desk update but it's not recognizing it.

Any help would be greatly appreciated!  Thank you.

[Petter Gonçalves · Accepted solution]

Hello Allen,

Welcome to Atlassian Community!

I understand that you would like to transition both Epic and the Service Desk issue linked to that Epic when any issue under the Epic is added to a Sprint.

To make it works, you configured a rule to add a Label to the service Desk issue and Epic once the child issue is added to the Sprint, configuring another rule to transition all the issues with the label to a determined status, however, the second rule is only triggered when you manually add the label to the issue but not when the first rule adds the label. Have I understood it properly?

I believe you have not allowed the second rule to be triggered by another rule. This parameter can be changed in the rule details as displayed in the screenshot below:

Please, turn this feature on and let us know if your automation works.

[AJ Depew]

Thank you!

[Petter Gonçalves]

You are welcome!

Have a nice day. :)