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

JQL Branch not working-what is the "Issue"

daniel.jones

I am beat, cannot figure this out and I am sure I am missing something simple.

Long story short-I have a bunch of stuff above the image below and could not get my automation to update the item I wanted. So I hard coded a JQL branch for an item and it still does not update it. what am I doing wrong?

Accepted answers

Bill Sheboy

Hi @daniel.jones

The rule uses the Incoming Webhook trigger, gathering issues from the request. This means the trigger has issues, and...

A branch on JQL automagically excludes trigger issues from the JQL to prevent errors, such as runaway looping. That is, behind the scenes, it adds this to the end of the JQL expression:

AND key != {{triggerIssue.key}}

There are two possible solutions (depending upon when you need conditions in a rule)...

Need conditions: use branch on current issue. For example:
- trigger: incoming webhook, with issues
- ...
- branch: on current issue
  - condition: some condition
  - action: some action which acts on the "current" / trigger issue
- ...more steps after the branch
Do not need conditions: just perform the actions on the rule's main thread. For example:
- trigger: incoming webhook, with issues
- ...
- action: some action which acts on the trigger issue
- ...

Kind regards,
Bill

All comments

Dick

Hi @daniel.jones

{{issue.summary}} is a smart variable that hasn't been set using a create-variable step.

you can however use the field itself in the log by stripping the curly braces.

Kind regards,
Dick

daniel.jones

Thank you @Dick that helped a little, but see two images below. First is the JQL validation-shows 1 item found. Second is the result of the automation run-it says no issues found, stopping the rule?

Dick

Hi @daniel.jones

This second question (and even follow ups on that) could be prevented if you shared your whole automation, including the per-step configurations.

Let's start by sharing the automation so that we can see what goes wrong?

Kind regards,
Dick

John Funk

Hi Daniel,

Can you briefly describe exactly what you are trying to accomplish?

And please share the entire rule so we can follow the flow (even it if takes multiple screenshots).

daniel.jones

@Dick and @John Funk sure-I was trying to spare you from the long drama.

back story-we have integration with bitbucket, but we are on DataCenter so some of the neat stuff available on cloud is not an option.

We are wanting to update a sub-task in JIRA for tracking when a pull request is updated on a story. When a pull request is created or updated in bitbucket, it pushes to the webhook in JIRA in the automation.

The first part of the automation is getting the story key from the webhook from bitbucket which works, then getting the tracking sub-task with lookupIssues, which also works.

I can get the automation to update the sub-task through many trials, but could not get anything to work. So that is when I tried to just branch with the hard-coded value of the story in question. Which did NOT work. You will see some audit actions where I was trying to debug.

Dick

Hi @daniel.jones

There's a couple of potential pitfalls in your automation:

Branches fire in parallel, you do not know which will be executed first.
The result of a branch should be reached in the branch, not in consecutive statements on "the main line of execution" (the vertical grey lines mean something here!)
Your trigger has no singular issue at it's root-cause. So any reference in the main flow of the automation to the object "issue" is referring to something Jira Automation cannot handle.
Editing an issue in an automation (under Data Center) is editing in the database, not inside the automation objects and variables. If you need the results of such an edit, you need to execute a re-fetch issue action in your automation.

Kind regards,
Dick

Rudy Holtkamp

Hi @daniel.jones ,

Quick question, does the scope of your automation rule include the "GET" project?

daniel.jones

yes, it is not global but specific to the GET project

Bill Sheboy

Hi @daniel.jones

The rule uses the Incoming Webhook trigger, gathering issues from the request. This means the trigger has issues, and...

A branch on JQL automagically excludes trigger issues from the JQL to prevent errors, such as runaway looping. That is, behind the scenes, it adds this to the end of the JQL expression:

AND key != {{triggerIssue.key}}

There are two possible solutions (depending upon when you need conditions in a rule)...

Need conditions: use branch on current issue. For example:
- trigger: incoming webhook, with issues
- ...
- branch: on current issue
  - condition: some condition
  - action: some action which acts on the "current" / trigger issue
- ...more steps after the branch
Do not need conditions: just perform the actions on the rule's main thread. For example:
- trigger: incoming webhook, with issues
- ...
- action: some action which acts on the trigger issue
- ...

Kind regards,
Bill

daniel.jones

@Bill Sheboy the webhook does not include the issues, which is why I had to parse out the issue key from the webhook title.

Bill Sheboy

The image you show in this post linked below indicates the trigger uses "Gather issues from request":

https://community.atlassian.com/forums/Jira-questions/JQL-Branch-not-working-what-is-the-quot-Issue-quot/qaa-p/3144769#M1157184

daniel.jones

this is the body of the webhook data (maybe bitbucket is not set up right)

John Funk

So, if the JQL is returning the right Sub-task, what id not working? It is not updating the Summary field as you expect? Can you share a screenshot with the details of the Edit to that field?

Welcome!

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

Quick Links

Find more posts tagged with

jira

jira-data-center

automation

data-center

branch

jira-automation

datacenter