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

Incoming webhook not edit issue fields in branch JQL, Why?

Marcos Milanesio

Hello!

I have an Incoming webhook executed with "Issues provided by running the following JQL search" option. Definition JQL: "key = MPP-16"

We update start date on this issue in a first component edit issue, MPP-16 edited okay!

Then, execute the branch FOR: JQL "key in (MPP-16,MPP-17)"

And edit duedate in both issues, on MPP-17 this work, but on MPP-16 not.

Can someone tell me why?

Screens:

Accepted answers

Marcos Milanesio

NOTE:

The fields used are just an example to show the problem, they are not the real business problem.

All comments

Marcos Milanesio

NOTE:

The fields used are just an example to show the problem, they are not the real business problem.

Jehan Bhathena

Hi @Marcos Milanesio ,

Does the Automation rule's log show any clue?

Marcos Milanesio

Hi @Jehan Bhathena

This is the log:

Jehan Bhathena

HI @Marcos Milanesio ,

I created a similar rule at my end, and turns out I face the same behavior.

In order to work around it, I kept the JQL for the incoming webhook, and the Branch condition to be the same :

I did not find any documentation that mentions this exclusion or vague behavior, but I did find a few old community posts that MIGHT point to the same thing :

Tagging @Bill Sheboy, since he provided some good inputs to the other threads.

Bill Sheboy

Hi @Marcos Milanesio and @Jehan Bhathena

That symptom is curious...

I have observed there are some single-issue related triggers, which later in a rule exclude the trigger issue from some branches (like on JQL), which I hypothesize is to prevent errors / loops. Although I have not found this documented for automation rules, and so I would welcome an Atlassian employee to confirm this...

Marcos, a work-around for your scenario is to first update the trigger issue directly with an edit and then branch to the other issue.

Kind regards,
Bill

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