Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

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

zuzana.moravcova July 13, 2023

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. 

Screenshot_1.png

2 answers

0 votes
Trudy Claspill
Community Champion
July 13, 2023

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 July 13, 2023

Hello, 

it is a company managed project :) 

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

Screenshot_3.png

Here is also a screen of subtasks :)

Screenshot_2.png

Trudy Claspill
Community Champion
July 14, 2023

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 July 17, 2023

Hi, 

the issue type didnt change at all. 

Here is screenshots of issues related to K2S-5501. 

Screenshot_4.pngScreenshot_5.pngScreenshot_6.png

Trudy Claspill
Community Champion
July 17, 2023

I am not seeing any reason why those three issues should've been updated.

At this point I recommend that you contact Atlassian support directly to get additional assistance.

https://support.atlassian.com/contact/#/

And please report back here what you learn from them.

Like zuzana.moravcova likes this
Trudy Claspill
Community Champion
July 24, 2023

Hello @zuzana.moravcova 

Did you open a support case with Atlassian? Did you get any feedback that you can share with us?

0 votes
Sayed Bares [ServiceRocket]
Community Champion
July 13, 2023

@zuzana.moravcova welcome to the community!

Can you share a screenshot from your audit log? 

Sayed Bares [ServiceRocket]
Community Champion
July 13, 2023

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

Like John Funk likes this
zuzana.moravcova July 13, 2023

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

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

Screenshot_3.png

Like John Funk likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events