We have one ticket on a JSD. For some reason, there is no ability to transition it.
The only fix was to transition it to a separate JSD and back, then the transition states appeared. Is this a one-off bug or maybe Atlassian needs to be aware of it.
Thank you for reaching out.
Per your description, it seems you were not able to transition a specific issue, however, when you moved it to a different project and them moved it back to the original, the transition appeared in the Issue view. Is that correct?
There are quite a few workflow settings that might have caused that issue. I suggest you try the following steps to troubleshoot it:
1 - As a project administrator, Navigate to your project > Project settings > Workflows > Click to Edit the workflow related to the issue type of the ticket
3 - Also, double-check in the history tab of the ticket if you did not change the issue type when moving the ticket from one project to another. In JIRA Service desk, issue types use different workflows with different statuses, so a change in the issue-type can display different transitions for the ticket.
Let me know if this information helps.
I am an Org admin and have access to all projects. There are no conditions or properties associated with these projects (pretty simple implementation.
Prior to changing the ticket from one project to another and back, I tried changing the issue type back and forth and did not help.
My workflow -
My conclusion is that it was a bug. I have not seen this before. This is not related to conditions or workflow settings because this ticket is like many others on the board.
I just encountered the same issue!
Designer created a issue in Backlog, Lead Engineer assigned it and wanted to move it in Selected for Development but it said 'You do not have permission to transition this issue.' He then asked me to transition it and i don't have permission either. Asked another user with full permissions within the project and has the same result.
We cannot even click the 'View workflow' button as it's greyed out.
Funny...because we can literally transition any other issues out of the 613 we currently have in that project, except this 1.
I should also mention that both the Lead Engineer and myself are org & site admins with no restrictions and the 3rd user has just full permissions granted.
We still have the issue in our database, was not edited or moved if it adds anything.
I just would like to mention that your issue seems to be different from the original post in this community because the transition is returning a permission error in your case, while the original request it simply didn't appear.
Additionally, being an org-admin or Site-admin does not impact on the project permissions, so you can still be restricted to the issues by a project admin if the workflow or the permission scheme is changed.
That being said, please check the steps below:
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events