Seeking root cause of "It seems that you have tried to perform a workflow operation..."

[Aisha Liebenow]

This error was triggered after a scrum master to move a sprint card from In Progress to In Review on the sprint board. As the project admin, I had just merged multiple new projects onto the same board. However, all of the new projects were clones of the same configuration as the parent project, this includes the issue workflow. The permissions for the scrum master have also not changed. Has anyone encountered this error, and found a way to restore smooth workflow operations? I am able to perform this workflow operation successfully, but my colleague is not. 

[Sramanth Pandeti · Accepted solution]

Hi @Aisha Liebenow Welcome to Atlassian Community!

I believe your workflow transition might have become corrupted due to the changes. 

Can you try the resolution mentioned in the below documentation and see if it resolves the problem for the user. https://confluence.atlassian.com/jirakb/workflow-action-invalid-error-thrown-when-moving-an-issue-between-columns-on-jira-agile-board-779159167.html

[Aisha Liebenow]

Hi Sramanth! Thank you for this suggestion - the steps offered in this solution are well-written and very clear to follow. 

My colleague is unfortunately having the same error occur, even after re-creating the workflow. Is it possible for a individual user role to become corrupt? Maybe I could try removing them from the administrator list, and adding them back to the role?

[Sramanth Pandeti]

Hi @Aisha Liebenow Sure, you can try removing and adding the user from the Administrator list too.

As a part of merge, did you change the issue filter (board filter) to include those additional projects or did you migrate all the issues to this project?

If you have changed the board filter query, can you make sure the user has permission on all the other projects too.

[Aisha Liebenow]

We solved it!

In the merge, I did expand the issue filter / board filter query to include the new projects. In cloning the project, I thought the permissions would transfer as well, but they did not. 

This seems to have been a strange combination of both issues - workflow corruption and user role permissions. This has now been solved.

Many, many thanks @Sramanth Pandeti