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

How to change issue field for all created issues in current rule?

Dmytro Komlyk

Hi everyone,

Please help me understand what I'm missing.

I have actions which are creating new issues in "For Each Branch". After the issues were created I would like to change "Due Date" field for each of those.

From one hand I understand that Branches are isolated structures. From the other hand the warning tells me that "For Each Branch" should fit the requirements for the action "For: All Created Issues". However the rule could not be saved because the Branches are not seeing each other. Maybe I'm understanding something wrong in this warning?

If I create issue outside the branch the warning disappears.

If shown structure is not working, so how can I change "Due Date" field for every created issue in current rule?

Thanks for the reply.

Accepted answers

Trudy P Claspill

Hello @Dmytro Komlyk

Welcome to the Atlassian community.

Refer to this document for more information about branches:

https://confluence.atlassian.com/jirakb/in-the-automation-parallel-execution-of-the-branches-to-main-thread-can-produce-incorrect-unexpected-outcome-1115147731.html

You cannot have one branch dependent on the completion of another branch because the branches may execute at the same time.

You don't need a separate branch to edit the Due Date of each created issue. You can set the value of that field in the same action you use to create the issues.

All comments

Trudy P Claspill

Hello @Dmytro Komlyk

Welcome to the Atlassian community.

Refer to this document for more information about branches:

https://confluence.atlassian.com/jirakb/in-the-automation-parallel-execution-of-the-branches-to-main-thread-can-produce-incorrect-unexpected-outcome-1115147731.html

You cannot have one branch dependent on the completion of another branch because the branches may execute at the same time.

You don't need a separate branch to edit the Due Date of each created issue. You can set the value of that field in the same action you use to create the issues.

Dmytro Komlyk

Hi @Trudy P Claspill

Action "Create Issue with a Request Type" does not have Due Date as Common Field, but action "Create Issue" does have Due Date as Common Field. But I need to use the fist one.

In my case request type I have created has Due Date as Context Field in Issue View. Action "Create Issue with a Request Type" is reflecting Due Date field only in case the field is placed to Request Form. But I do not need Due Date on Request Form. This is why I can't set Due Date field value in the same action I use to create the issue.

On the screen it is shown the Due Date is absent in the list, however it is present in Request Type as Context Field in Issue View, as I told earlier.

I have tried to set Due Date field using JSON with no luck. Audit log always says the field is skipped.

Any other suggestion, guys, of how I would achieve editing Due Date in my case?

Thanks in advance.

Trudy P Claspill

Hello @Dmytro Komlyk

Why must you use Create Issue with Request Type?

An alternate solution is to set up a separate rule for the actions of the second branch. In the current rule add some unique value (unique to this rule) to each of the issues that is created. Then set up a second rule that is triggered by issue created, determine if that issue has that unique value, edit the Due Date field, and remove that unique value from the issue.

Dmytro Komlyk

Hi @Trudy P Claspill

Using Create Issue with Request Type is a requirement from the customer.

I have solved the problem using variables and For: JQL branch. I am triggering other rule after the action Create Issue with Request Type which is using For: JQL branch to find the value from the parent issue and calculate Due Date. Then I am saving Due Date to a variable and apply it to my newly created issue. It works really nice.

Thanks for giving me that idea.

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-service-management-cloud

jira-service-management