Status transition through automation rule fails even with available transition

[Samuel Tabbo]

I have setup an automation rule to transition issues linked with "cloned by", when the linked issue is transitioned, as follows:

When the rule runs, I receive the error: 

Transition issue

Destination status could not be resolved. 

which is apparently due to, according to Status transition through automation rule fails | Automation for Jira Data Center and Server | Atlassian Documentation , missing transitions.

However, in the Workflow configuration for the issue, all the same statuses from the trigger issue workflow are present, and transitions are present from "any status" to all statuses.

[Samuel Tabbo]

Thanks for the quick feedback. The workflows are different, but statuses are replicated in both. And transitions, even if not identical, are present in both workflows, as follows:

Epic workflow:

Product Roadmap Placeholders workflow:

Thanks,

Samuel

[John Funk]

Great, thanks for sharing that. For your example, and the one that you did and got the error , what was the status of the epic and to which status did it go? And for everything that’s linked, how many were linked? And what was the status that each were in at the time the epic transitioned? 

[Samuel Tabbo]

Status of the Epic: Roadmap Planning
Status where it went: Refining

2 Placeholders issues linked, both in status Roadmap Planning

Expected to transition as well to Refining. Following the Automation error log:

[John Funk]

Hi Samuel - Welcome to the Atlassian Community!

If the linked issues are not the same issue type, they might be using a different workflow which has different statuses. Or the linked issue might be in a status that cannot go to the same status as the trigger issue based on the transitions. 

Can you verify that all issues use the same workflow? Can you share screenshots of the workflows being used? 

[John Funk]

Are there any Conditions of Validators on the transition to Refining status in the Product workflow? 

[Samuel Tabbo]

No Conditions or Validators are present for these transitions, in both workflows.

[John Funk]

Check the PH project Permission Scheme to see if the atlassian-addons user has the permission for Transition Issue. 

[Samuel Tabbo]

Thanks @John Funk . This is the outcome of the permission helper query. I didn't manage to query with the specific atlassian-addons user, as the System Permission Helper doesn't allow these type of users.



Is there another way to verify this?

Thanks,

Samuel

[John Funk]

Okay, understood. Did you check the Transition Issues permission to be sure the 

• Project Role (atlassian-addons-project-access)

is there? 

[Samuel Tabbo]

Thanks @John Funk . I checked in the Access configuration of the Project, and the role atlassian-addons-project-access is not present in the list, and it is not possible to add from the search function.

[John Funk]

Okay - is there an entry in the Permission Scheme for that user/role? And if not, can you try to add it as a Group instead of a Project Role? 

[Samuel Tabbo]

Apologies @John Funk , but this is a bit too advanced for my knowledge of JIRA. I explored the Permission Scheme page, but I didn't find the Product Roadmap Placeholders project associated with a Permission Scheme, nor did I manage to associate it to one of existing Permission Schemes.

[John Funk]

Okay, no worries. Let's start with the project. Go to the project and then click the Project Settings at the bottom left of the page. You must be a project administrator to be able to see that link. 

Once on the next page, click the Summary link in the top left. On the next page you will see all of the schemes used by the project. Click on the Permission Scheme there and take a look. 

[Samuel Tabbo]

Thanks @John Funk . I tried to do as you suggested. Unfortunately, there is no Summary link nor Schemes page for this Project.

[John Funk]

Ah, that means you are using a Team-managed project. 

You either need to change the Actor for the Rule (I think that is what I would do) to say the user who triggered the event, or another user such as the project administrator (you would need to know his/her name).

Or you need to add the atlassian-addon user or group to the Access for the project. 

[Samuel Tabbo]

Thanks @John Funk . I managed to change the actor of the rule to myself, who I am also project Product Placeholder project administrator, but I get the same error from the Automation run:

Destination status could not be resolved.

[John Funk]

Can you share a screenshot of the transition details from the workflow?