I'm trying to perform a number of actions on issues found by a JQL query, but it does not seem to work: I was able to validate the if statemtent used, the rest of the automation now looks like this: The JQL also validates, it finds the issues I'm looking for But then it seems like the create issue operation is not executed. What am I missing here?

I think I know what I'm missing. You're not doing a for each on the issues found, you're doing a for each on the related issues within the issues found. Which is nothing. However, I'm trying to do the first thing. So instead I might want to use lookup issues. This actually creates an issue but not in the way I would expect. It creates one issue, with both summaries in the summary field. Instead I would like to create an issue per issue that was looked up.

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

Why does my JQL branch not process the issues it finds

Luc Evertzen

I'm trying to perform a number of actions on issues found by a JQL query, but it does not seem to work:

I was able to validate the if statemtent used, the rest of the automation now looks like this:

Screenshot 2023-08-31 at 12-45-52 Automation - Jira.png

The JQL also validates, it finds the issues I'm looking for

Screenshot 2023-08-31 at 12-45-36 Automation - Jira.png

But then it seems like the create issue operation is not executed. What am I missing here?

Accepted answers

All comments

Jack Brickey

Hi @Luc Evertzen , what does the audit log show? Can you share a screen shot if nothing pops out at you? Is it possible required fields are not being set in the action?

Marc -Devoteam-

Hi @Luc Evertzen

Is the manual rule triggered from another project than the PT project and is that project a Team Managed project?

If so in the edit action change the "Same Issue Type" to a specific Issue Type, as Team Managed projects are containers and no configuration is shared.

But as @Jack Brickey mentioned, the audit log of the rule will give more clues on what is going wrong

Luc Evertzen

I think I know what I'm missing. You're not doing a for each on the issues found, you're doing a for each on the related issues within the issues found. Which is nothing. However, I'm trying to do the first thing.

Screenshot 2023-08-31 at 12-57-56 Automation - Jira.png

So instead I might want to use lookup issues. This actually creates an issue but not in the way I would expect.

Screenshot 2023-08-31 at 13-22-18 Automation Testing Board - Agile Board - Jira.png

It creates one issue, with both summaries in the summary field. Instead I would like to create an issue per issue that was looked up.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud