Add number of linked issues to the custom field

[Nikki Zavadska [Appfire]]

Hi 👋 ,

I'm trying to create automation rule in Automation for Jira where a number of linked issues would be stored in the custom field.

My use case:
I have a Project with customer feedback with 2 types of tickets - Suggestions (stuff that our customers raise) and Improvements (Stuff that we're delivering to solve customers suggestions).
We link Suggestions to Improvements to keep track of which of the improvements are most popular and also to make sure we know who raise them.

Now for that, I created custom field Raised (total) where I want to store how many times Improvement was raised = How many linked issues this improvement has.

Here is what I have done in Jira automation so far:

1. My trigger is when Issue is Linked to the ticket
2. Then I store an issue key as {{issuekey}}
3. Then I use Lookup issues with this JQL issue in linkedIssues({{issueKey}})

4. Then I Edit issues field Raised (total) with {{lookupIssues.issue.count}}

It doesn't seem to work, any suggestions on how to improve? Did anyone tried something similar? :)

Thank you!

[Dirk Ronsmans · Accepted solution]

Hi @Nikki Zavadska [Appfire] ,

You mention "it doesn't work", do you get any errors on the automation or just nothing happens?

What exactly do you put in your variable?

For one you could already change the JQL you use (without knowing what's in the variable) This could just be replaced with

issue in linkedIssues({{issue}})

[Dirk Ronsmans]

did some testing.. and had to rework the structure a bit.

Mine currently is:

this will basically do the query that we want (I think?, to see how many items are related to and you could even only run the rule if the issue type is Suggestion) and then I changed the edit field to:

{{lookupIssues.size}}

That works for me!

[Nikki Zavadska [Appfire]]

Thanks @Dirk Ronsmans for your help!

I did adjust the rule in the way you mentioned and it worked! I just removed the variable because it wasn't needed and {{lookupIssues.size}} as a value instead of {{lookupIssues.issue.count}}.

Here is the final rule for anyone else reference if needed :)

[Nelly Sammak]

Hello @Dirk Ronsmans 

I need to perform the same calculation but the suggested rule didn't work for me.

I have a support ticket (issue type A) in project AA, and bugs and change requests (issue type B, C) in project B.

Each time I link a support ticket to a bug/CR, I need a field in the bug/CR tickets that counts the number of linked support tickets to that bug/CR.

I tried the last shared rule, but I got 0 always.

Do you have a suggestion?

Thanks

[Vanjinathan Ramalingam]

Similar ask, I wanted to get the linked issue keys(multiple) and to add those KEYs in comment section. Could you please give some tips?