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

Branch rule for sub task got triggered on non sub task issue

zuzana.moravcova

Hello, i need advice we have automation for sub task to update production date. But it got triggered and changed production day at issues that are not sub task. Can you help me why?

I have checked the issue type settings and it should be fine only issue type subtask is set as a subtask.

The automation looks like this.

Accepted answers

All comments

Sayed Bares [ServiceRocket]

@zuzana.moravcova welcome to the community!

Can you share a screenshot from your audit log?

Sayed Bares [ServiceRocket]

and can you share a screenshot from history of a non subtask issue type which was updated by this automation rule?

zuzana.moravcova

Here is the audit log - all 3 affected issues are not subtask

And here is the history - sorry bcs of company policy i had to cover all personal details and ticket details

Trudy P Claspill

Hello @zuzana.moravcova

Welcome to the Atlassian community.

Are these issues in a Company Managed project or a Team Managed project?

For the three issues that were edited, what type of issues are they?

If these issues are in a Company Managed project, can you show us that issue type in the Issue Types screen at ...?

https://<your Jira URL>/jira/settings/issues/issue-types

Or does the issue type appear in the Subtask Issue Types list at...?

https://<your Jira URL>/secure/admin/subtasks/ManageSubTasks.jspa

If the issues are in a Team Managed project can you show us the issue type in the Issue Type list under Project Settings?

zuzana.moravcova

Hello,

it is a company managed project

The issues are Improvements here is a screen od issue type.

Here is also a screen of subtasks

Trudy P Claspill

Thank you for that additional information. This is very unusual.

Was the Issue Type changed on the three edited issues? Could they have been Subtask issue types at the time the rule ran?

K3S-5501 was the issue that triggered the rule according to the Audit Log. Can you show us the details of that issue, showing the Subtasks/Child Issues section and Linked Issues section and any other section that shows the relationship between the trigger issue and the issues that were changed?

zuzana.moravcova

Hi,

the issue type didnt change at all.

Here is screenshots of issues related to K2S-5501.

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-software-cloud

automation

branch

atl-orange