When a label is added to a task in one project can it be a trigger for other actions

[Pete Robbins]

We have two company-managed projects: a SWdev project and a relatedDocs project. If label1 is added to any task, epic, subtask, etc. in SWdev, we want label2 to get added automatically to the SWdev object.

We already have automation in place such that when label1 or label2 is added to SWdev tickets, the system creates a ticket in the relatedDocs project.  Currently adding label1 creates a releaseNotes ticket in the relatedDocs project. When label2 is added, a userDocs ticket is created in the relatedDocs project. It is thought that this automation will ensure that we don't miss any documentation of SW features.

[Bill Sheboy]

Hi @Pete Robbins 

From what you describe, you have a rule in place which is triggered by the addition of labels to issues in the SWdev project and then creating issues in the relatedDocs project.  And now you want to add those specific labels to the issues.

If that is the case, what is not working as you expected?

For a question like this, context is important.  Please post an image of your complete automation rule, images of any relevant actions / conditions / branches, an image of the audit log details showing the rule execution, and explain what is not working as expected.  Those will provide context for the community to offer ideas.  Thanks!

Kind regards,
Bill