Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Add number of linked issues to the custom field

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:
Screenshot 2020-09-23 at 09.29.38.png

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!

1 answer

1 accepted

0 votes
Answer accepted
Dirk Ronsmans Community Leader Sep 23, 2020

Hi @Nikki Zavadska _jexo_ ,

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

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

Mine currently is:

 

image.png

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!

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 :)

Screenshot 2020-09-23 at 16.18.53.png

Like # people like this

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Apps & Integrations

Send an Email or Publish to Confluence - What should you do with your release notes?

Background When you hear the words ‘Release notes’, almost always you think of an unsolicited email from a software vendor. But I am here to tell you that from our data, sending release notes via E...

65 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you