Automation Status Change | child to parent

[Stäwen_ Nicole]

Hello everyone, I am currently failing at an automation for the status change. We have a workflow that affects two projects.

Person 1 [Project KG] creates a ticket, subtasks are generated when the status changes to “SENT TO INT”, please see a screenshot of this automation below:

Person 2 starts working on Subtaks1 and therefore changes the status of the sub-taks to "in Bearbeitung" (inprogess)

Person 3 has not started working on Sub-Tasks 2 yet and therefore its status remains as new.

I would like the parent ticket (created by person1) to change its status to "in Bearbeitung". 

Whatever I have tried, the parent ticket does not change its status.

___

We are using a similar auotmation for creating sub-tasks in another project, like this:

I have created this automation for changing the status of the parent in this project and it workes smoothly.

I assume there is someting wrong with "issuetyp" but I cannot figure it out. I am very grateful for your support,

all the best from Hamburg,

Nicole

[Bill Sheboy]

Hi @Stäwen_ Nicole -- Welcome to the Atlassian Community!

When you post an image of the audit log details, please expand all of the areas / dropdowns in the log to show issues impacted.  That may provide more context for what is happening.

Until we see that...

You described two Jira projects are involved.  

• What is the scope of the rule (in the details at the top): single-project, multiple-projects, or global?
• What are the project types involved: company-managed or team-managed?  You may find that information in the list of projects.

For team-managed projects, the configuration of issue types, status values, etc. is distinct for each project.  Thus if the rule is for multiple projects (or was copied from one project to another) the information about the status value IDs could be different, and so cause this rule symptom.

Kind regards, 
Bill

[Rilwan Ahmed]

Hi @Stäwen_ Nicole ,

Welcome to the community !!

1. Check if the automation rule actor has the all the required permission (browse, transition) in the said project.
   When you open the rule --> Rule details and scroll down, you can see the rule actor. 

2. Check the rule audit log for failure reasons. You can open the rule --> Audit logs and expand each step and see where it is failing and the cause for it. 
 

[Stäwen_ Nicole]

Hi @Rilwan Ahmed

Thank you so much! The permissions are okay and the Audit-Log shows the following

[Rilwan Ahmed]

Hi @Stäwen_ Nicole ,

There are two main causes for the automation error:

1. The automation rule has a destination status, but there is no transition from the current status to the new status  in the workflow of the affected issue
2. The user does not have the permissions to transition the issue.
   • Along with project permissions, you need to check for workflow conditions , validators, or any properties which is blocking the transition
   • If the Actor is set to "Automation for Jira," then the "atlassian-addons-project-access" role must have this permission.