Automatic tagging/labeling for a ticket

[Ritika Ojha]

Scenario- we have multiple components & each component has its own JIRA project. When a project is started, it will have tickets under these components. 

Currently I have MANUALLY to add labels to each ticket for this cross-functional project.

I am looking for an automation rule to help me add this label when the following criteria meets :

1. If tickets are created under a specific jira project then all the tickets have a predefined lable

2. If any ticket is linked to Parent tickets/Epic/ Story , then it should auto add the predefined label for the project. 

[Utkarsh Agarwal]

Hi @Ritika Ojha 

Yes, this is possible using Jira Automation. You can set up two separate rules:

1. Label issues created in a specific project
   • Trigger: Issue Created
   • Condition (if using global rule): Project = TSM1
   • Action: Edit issue → Labels → Add tsm1
2. Label issues linked to a specific project
   • Trigger: Issue Linked
   • Branch: For linked issues
   • Condition:
     • First value: {{destinationIssue.fields.project.key}}
     • Condition: equals
     • Second value: TSM1
   • Action: Edit issue → Labels → Add tsm1

This way, your issues get automatically tagged based on where they’re created or what they’re linked to.

Kind Regards
Utkarsh

[Marc - Devoteam]

HI @Ritika Ojha @Utkarsh Agarwal 

Are you linking or setting yje parent field, if you are setting the parent field, then in the 2nd rule the Branch should be based on Parent not Linked Issues.

Otherwise you could end up with a label change on issues.

[Ritika Ojha]

I was able to create auto-tag/label for new items in a project.

Unfortunately, it's not labeling for linked issues. Not sure if something is amiss.

[Marc - Devoteam]

Hi @Ritika Ojha 

Are the linked issues, linked via the issue link or the parent field, or are they sub-tasks?

[Ritika Ojha]

So here's how i did it.  Lets say main project "TSM" , another project "KT"

I created automation in project TSM with below conditions: 

Work item linked - all link type

Branch 

Linked work items

if {{destinationIssue.fields.project.key}}

then second value is TSM

Add labels 

After that i tried creating tickets in both projects & linking it. but neither had any labels attached.

I am not a coder- so not sure if my logic is getting applied correctly via automation 

[Marc - Devoteam]

Hi @Ritika Ojha 

Can you please provide,

1. images that show your complete rule.

2. images showing the details of any relevant actions/conditions/branches.

3. images showing the Audit Log details for the rule execution.

[Ritika Ojha]

I think i figured out the issue. Apparently I noticed that when i set the conditions, the rule is restricted to current project where I am implementing. This means i can't do cross project implementation

Now not sure if this is JSM restrictions or can be changed  

[Marc - Devoteam]

Hi @Ritika Ojha 

If you create a rule in a project, the rule is limited to the project.

You would need to go to the system setting Global Automations and then find the rule and change the scope to selected projects.