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 linked issues results in an incorrect value

Matt Noe_cnh3z5

I created an automation in a project that is a manually triggered rule (for now).

In the automation, I do a lookup with the following query: "issue in linkedissues({{issue.key}}) and type = bug "

When I run the same query in ScriptRunner, I get 11 results for the target issue, so I believe this is correct:

Scriptrunner results automation.png

In the automation, I then edit the issue using {{lookupissues.size}}. When I run to automation, the field is set to zero, and not the expected 11.

What am I doing wrong here?

automation setup.png

I did try changing the edit value from "{{lookupIssues.size}}" to "={{lookupIssues.size}}" and then got the following error in the audit log:

Action details:

MANUAL TRIGGER

The user Matthew Noe triggered the rule

LOOKUP ISSUES

A search during custom value definition found no issues.

EDIT ISSUE

Could not convert the field value to a number. Please ensure the value is a number, math expression or smart-value that can be converted into a number.

Bug Count: =0

No fields or field values to edit for issues (could be due to some field values not existing in a given project):

CBE-16626

Accepted answers

Alex Koxaras -Relational-

Hi @Matt Noe

Works fine here:

Is the field you are trying to edit available on the specific project?

All comments

Alex Koxaras -Relational-

Hi @Matt Noe

Works fine here:

Is the field you are trying to edit available on the specific project?

Matt Noe_cnh3z5

The field is available on the project. The only thing that I can think of is that the linked issues is a part of a separate project? Does my automation have to be moved to global because of it?

Project being run against is CBE-XXXXX Linked issues are BUG-XXXXX

Alex Koxaras -Relational-

Prior of changing the rule to global, try the following query on your lookup component:

issue in linkedIssues(CBE-16626) and issuetype = bug

Click validate query and see how many issue it will return

Matt Noe_cnh3z5

Thanks @Alex Koxaras -Relational- . I tried it on both the project specific automation and the global. Project specific returns 0 and global returns 11. Looks like that is my problem.

Thank you for your help!

Welcome!

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

Quick Links

Find more posts tagged with

automation