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; } } }

Linked Issues Count

Mia Bright

Hi Team,

We are trying to create a known issue register and want to be able to see the total number of linked issues for each issue e.g. each product team has their own Jira board which they will create am issue in for each bug. They will then link any incidents raised via our service desk to that bug. We need a quick way to see the total number of linked issues.

I have trawled through the community pages and seen lots of similar questions but they are never exactly what we are after so don't pull the right results. This is the automation I have tried so far and it works perfetcly when I link the first issue, but then never updates past "1" when I link further issues.

What am I doing wrong here? I have also tried {{destinationIssue}} instead of {{issue}}

Thanks,

Accepted answers

Kalyan Sattaluri_iinm1n

Hello @Mia Bright

Where do you want this linked issue count to get updated? In the Bug?

If so, your workflow context is important on how you set up the rule.

So for that, you need to be clear on how are users linking these issues.

Scenario 1: If they navigate to the bug in Jira and then linking the incident by putting the key, you use {{issue}}. Then your logic is fine.
Scenario 2: If they are navigating to the newly created incident and linking to the bug from there, then you need to use {{destinationissue}} in your lookup and then you need to "Branch" over to {{destinationissue}} and edit the issue that way.

You have scenario 1 set up.

I am sharing how to set up scenario 2 in below screenshot.

You should have both these 2 rules to complete your requirement.

Also, good practice to log as much as you can so you can follow along your progress.

Hope it helps.

All comments

Trudy P Claspill

Hello @Mia Bright

What is in the Audit Log for the rule execution when you link the second and later issues?

What are the details of the Edit action?

In the second and later link creations, from which issue are you initiating the link creation; the Bug or the Service issue?

Kalyan Sattaluri_iinm1n

Hello @Mia Bright

Where do you want this linked issue count to get updated? In the Bug?

If so, your workflow context is important on how you set up the rule.

So for that, you need to be clear on how are users linking these issues.

Scenario 1: If they navigate to the bug in Jira and then linking the incident by putting the key, you use {{issue}}. Then your logic is fine.
Scenario 2: If they are navigating to the newly created incident and linking to the bug from there, then you need to use {{destinationissue}} in your lookup and then you need to "Branch" over to {{destinationissue}} and edit the issue that way.

You have scenario 1 set up.

I am sharing how to set up scenario 2 in below screenshot.

You should have both these 2 rules to complete your requirement.

Also, good practice to log as much as you can so you can follow along your progress.

Hope it helps.

Mia Bright

Thanks for your reply, I am wanting the count to display on the bug in a newly created field called "linked issue count" and I need the issues to be able to be linked from either the bug or the incident.

Kalyan Sattaluri_iinm1n

Please implement another rule like i have in my screenshot. Together, the 2 rules (one you earlier authored and the new one) will complete your requirement.

Please let me know if issues, do share screenshot of audit log so we can see whats the issue.

Mia Bright

I have added the second rule as advised

Linked Issue Rule 2.PNG
However it doesn't appear the branch is working. When I try to link from the incident to the bug I get the following in the audit log, no issue count.

Incident Audit Log.PNG

If I link from the bug to the incident it doesn't run at all.

Hannes Obweger - JXL for Jira

Hi @Mia Bright

I'm glad to see you got this to work using Automation.

Just for future reference, if you're open to solutions from the Atlassian Marketplace, I think you might like the app that my team and I are working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a number of so-called smart columns that aren’t natively available, including the number of issue links, along with many other issue-link-related columns.

This is how it looks in action:

As you can see above, you can easily sort and filter by your smart columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting.

This all just works - there's no automation or scripting whatsoever required.

Any questions just let me know,

Best,

Hannes

Petar Cvetanovic_jgriyv

@Kalyan Sattaluri
Hey, what should I put in the edit field in the first formula check SS?

Can you verify the solution check video https://www.loom.com/share/d180900f3f43410983d08e94616e013e Screenshot 2024-07-10 at 15.06.43.png

Laura Anhorn

@Petar Cvetanovic You can use {{#increment}}{{Total Assets}}{{/}} if you want the number be updated every time a link is made.

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-cloud