Help with auto transition subtasks when story transitions

[Madar_ Andrew]

I'm having problems getting a subtask to transition when the main story is transitioned using automation. 

Here is the flow:

The error I'm getting is this:

Transition issue

No transitions found for user. Ensure that the rule actor has permission (including issue security levels) to see issue and perform transitions.

Rule details:

Any help would be greatly appreciated!

Thank you,

Andy

[Trudy Claspill]

Hello @Madar_ Andrew 

Can you show us the entire output of the Audit Log for the rule execution? You have two transition actions in your rule, and we can't tell from what you provided which one is throwing the error.

I notice that after the trigger, which is an issue transition, you are transitioning the trigger issue to another status and updating field(s) in the trigger issue. After making changes to an issue in a rule, if you want to later reference that changed information you should use the Re-fetch Issue action to make sure your rule has the current information cached.

Within you branch can you add a Log action to print the Status of the trigger issue? That will enable us to confirm what status is trying to be used in the transition of the subtask.

[Madar_ Andrew]

Hi Trudy, I appreciate your help. 

Here is the entire error.

Thank you!

[Madar_ Andrew]

I added the log action you requested.

[Trudy Claspill]

Thank you for the additional information.

From the Audit Log details you shared we can confirm that it is the attempt to transition the subtask that is failing.

What output are you seeing in the log with the addition of the Log actions?

Does the workflow for your subtask include the Intake Validation status?

Is this rule being run against a Company Managed project or a Team Managed project?

[Madar_ Andrew]

It's running in a Team Managed project and I have the workflow same for story and Sub-task.  

I have the rule triggering on an event so the next time it triggers will update to your questions.

[Trudy Claspill]

Are the two issue types sharing one workflow, or do they each have their own workflow with the same Statuses named in both workflows?

[Madar_ Andrew]

They share the same workflow.

[Madar_ Andrew]

Hi Trudy, so the rule ran and I see the log action update showing In Basket

[Trudy Claspill]

To which status do you want to set the subtasks; In Basket or intake Validation?

In the workflow do you allow issues to transition from any status to any status? Can you share the workflow diagram with us?

What are the status values for the subtasks when this rule execution started?

[Madar_ Andrew]

To which status do you want to set the subtasks; In Basket or intake Validation?  Intake Validation

In the workflow do you allow issues to transition from any status to any status? No, but there is an exception policy for specific users.  I have the transition setup when the requestor moves the story to In Basket, automation will transition it to Intake Validation which is the rule I shared. 

Can you share the workflow diagram with us?

What are the status values for the subtasks when this rule execution started?  The subtask status are the same for the story

[Trudy Claspill]

As indicated by the Log action, the status value that the subtasks are attempting to be transitioned to is In Basket rather than Intake Validation.

You are changing the trigger issue to Intake Validation as part of the rule. If you want to get that status by copying it from the trigger issue, you will have to add a Re-fetch Issue action after the step where you transition the trigger issue to that status.

But, if you know you want to transition the subtasks to Intake Validation, why not explicitly select that in the Transition Issue step?

Correct that problem and then see if the rule runs correctly.

[Madar_ Andrew]

I'm going to try that.  I added your suggestions.  See if it works properly now.  Will let you know.  Thank you,