After a bug is closed there are often a number of tickets that need to be worked on to ensure that this does not happen again and/or to clean-up any related issues caused by the bug. I would like to build an automation rule (or rules) that adds a label to any ticket (for the purposes below I will use "task") that is linked to a Bug so that we are able to identify what % of them get completed throughout the year. I've been able to build the following rule: * When you are in a task and link that task to a Bug, add a label to the task:* Trigger: Issue Linked * Condition: Issuetype = Bug * Branch: For Destination Issue* Action: Add a label What I am having trouble with is figuring out the condition for: * When you are in a Bug issue type and link a task, add a label to the task. Key things to consider: * The trigger for "Issue Linked" uses the following rule:* Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}} Some workarounds I've put in place for now: * Within the Bug issue type, when a manual trigger is selected add a label to any/all of its linked issues * When a Bug is updated (i.e. status changed, assignee updated, etc.), add a label to any/all of its linked issues* For some reason linking a task to the Bug does not trigger the rule. Therefore you have to actually make a change to the ticket itself (i.e. status, some other field). Any ideas?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Automation Rule: Add a label to an issue when it has been linked to a Bug or Incident

Richard Herrada_hif9q3

After a bug is closed there are often a number of tickets that need to be worked on to ensure that this does not happen again and/or to clean-up any related issues caused by the bug.

I would like to build an automation rule (or rules) that adds a label to any ticket (for the purposes below I will use "task") that is linked to a Bug so that we are able to identify what % of them get completed throughout the year.

I've been able to build the following rule:

When you are in a task and link that task to a Bug, add a label to the task:
- Trigger: Issue Linked
- Condition: Issuetype = Bug
- Branch: For Destination Issue
  - Action: Add a label

What I am having trouble with is figuring out the condition for:

When you are in a Bug issue type and link a task, add a label to the task.

Key things to consider:

The trigger for "Issue Linked" uses the following rule:
- Rule executes when an issue is linked to another issue. {{issue}} will always refer to the source issue, so if ISSUE-A is blocked by ISSUE-B, this rule will execute on ISSUE-B. To access ISSUE-A, use {{destinationIssue}}, and to access the link type, use {{linkType}} (e.g. {{linkType}}

Some workarounds I've put in place for now:

Within the Bug issue type, when a manual trigger is selected add a label to any/all of its linked issues
When a Bug is updated (i.e. status changed, assignee updated, etc.), add a label to any/all of its linked issues
- For some reason linking a task to the Bug does not trigger the rule. Therefore you have to actually make a change to the ticket itself (i.e. status, some other field).

Any ideas?

Accepted answers

Mark Segall

Hi @Richard Herrada - What type of link are you using?

All comments

Mark Segall

Hi @Richard Herrada - What type of link are you using?

Richard Herrada_hif9q3

Hi @Mark Segall i am trying to build the rule such that it can be any type of link. That way user error is lower.

That said, one of the workarounds I was able to identify was: I can make the rule work if I build the rule based off the link type and not build a condition around issue type.

However, I fear (and the feedback I received from stakeholders) was that users may not select the correct link type and therefore our data would not be as accurate as we hope.

Mark Segall

Got it. So is there a reason why you have the bug condition? Does a bug get a different label than a task? If so, you could try this:

TRIGGER: Issue Linked

BRANCH (JQL)

key = {{destinationIssue}} AND issueType = Bug

ACTION: Edit Issue (Label)

BRANCH (JQL)

key = {{destinationIssue}} AND issueType != Bug

ACTION: Edit Issue (Label)

Richard Herrada_hif9q3

The reason for the condition is because without it if we link any task to any other task then it will add a label which we don't want. We only want the label added to tasks that are linked to our Bugs.

Just to take a step back, this is what I am trying to do:

As a product manager, I'd like to track any tasks that have been linked to a bug, to ensure that all tech debt has been resolved as a result of the bug.

At our organization, the workflow for bugs is:

Prod bug occurs > we quickly resolve it > we perform a retro > during retro create tasks > we link the tasks to the bug > (this is what I am trying to figure out) linked tasks automatically get a tag/label or something else so we can track the tasks and build metrics.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-software-cloud

issue-link