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

Counting of issues with {{lookupIssues.size}} does not work

Iris Studeny

Hello Atlassian Community!

I have a question regarding to the function {{lookupIssues.size}}. With that function we want to count our linked issues.

Our use case is that smartphones get linked to a purchase order and with our field "Cycle Count" we would like to see how often the smartphones were linked.

But now this seems to not work, even though no error is shown in the audit logs.

We created following automation:

Cycle Count function.PNG Maybe someone can help us with our problem.

I look forward to hearing from anyone.

P.S. If further information would be needed, please feel free to ask and comment.

Thank you in advance.

With best regards,

Iris Studeny

Accepted answers

All comments

Trudy Claspill

Hello @Iris Studeny

Welcome to the community.

In what way exactly is this not working? Are you not getting the value you expect from {{lookupIssues.size}} ?

Have you used the JQL you have in the Lookup Issues action in the Advanced Issue Search screen to confirm that it is actually finding any matching issues? Of course, you will need to substitute the actual issue key value for the smart value when you do that.

Iris Studeny

Hello @Trudy P Claspill

Thank you for your reply.

Yes that is exactly our problem: We do not get the expected value of it. For example, there are two linked issues and it gives us 0.

No we did not try your hint, should we?

Trudy Claspill

Hello @Iris Studeny

Yes, you need to try that.

It is highly probably that your JQL is not finding any matching issues and that lookupIssues.size is giving the correct data.

Iris Studeny

Hello @Trudy P Claspill

Ok so you mean to give our following JQL in the search field: issue in linkedIssues({{issue.key}}) and issueLinkType = "has active Hardware assigned"

Thank you in advance!

Evan Reeves

@Trudy P Claspillis it possible that the automation does not have access to the project? I was just able to get this working after I changed the scope of the JQL query. The automation did not have access to the project being used in the JQL query.

When I changed this to the project it did have access to I was able to get the count correctly via the {{lookupIssues.size}} smart value.

Trudy Claspill

Hello @Evan Reeves

Yes, that is a possibility.

Each Automation Rule has an Actor setting which specifies the identity under which that rule will run. The specified Actor needs to have appropriate permissions in the target project(s) to execute the actions specified in the Rule.

Melissa C

Hello Everyone & @Iris Studeny

Is there an update to this?
I'm also looking to get a count of all the Tasks in an Epic.

I'm using Jira Server and testing with 9.0, which has the lookup feature.
{{Issues.Size} give me the count of Epics in my Query not the count of Tasks.

Trudy Claspill

Hello @Melissa C

Please provide the details of your query/automation. Your query doesn't sound the same as the original poster. You should be able to get the list of tasks under the epic with this JQL in your Lookup Issues action.

"Epic Link" = <Epic issue key> and issuetype=Task

Melissa C

@Trudy P Claspill Thanks for the reply

let me elaborate on what I'm trying to accomplish and perhaps you can give me some suggestions.

I want to get the number of Task in each Epic. The idea is that I would send a weekly report stating the following Epic have been approved but still have X number of Tasks open.

When I use the {{Issues.Size}} it gives me the number of Epics in my query Not the number of Tasks in each Epic.

Does that make sense?

Trudy Claspill

Hello @Melissa C

{{Issues.size}} is not the same smart value as {{lookupIssues.size}}, so that is the first thing that needs to be cleared up through our ability to examine your rule.

Second, {{lookupIssues.size}} indeed will give you the count of issues returned by the query in your Lookup Issues action. It can't be used to get the count of issues related to the ones returned by your query.

Given that your question concerns Epic and child issues, not linked issues like the original question, I recommend that you start a new Questions post.

In your new post please provide screen images to show your entire automation rule and the details of each step. Without that information it is difficult to debug your situation and our suggestions will be educated guesses at best.

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