nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

You do not have permission to make the transition

Swati_Mathapati

User is unable to make the transition from Backlog to To Do status for few Epics even though he has all the permissions to the project and there is no such condition written in the workflow to block him making this transition

I have also checked the permissions helper and all the conditions are passing

Accepted answers

Swati_Mathapati

I have got the solution ,it was due to the corrupted workflow and copying/renaming the workflow solved it

Thank you all for your help

All comments

Radek Dostál

Assuming you have indeed checked all of the permissions/conditions (also status properties?), there used to be a bug which I'm not sure whether it's still relevant or not, but sometimes it helps to "switch" the workflow - i.e. copy it, assign it to the scheme instead, publish the scheme, then re-add the old workflow back. This causes the issues to get "updated" and get "re-connected" with the workflow.

The bug was principally about an issue being stuck in a status without being aware of it's workflow - you couldn't do any transition from the status, and there was a KBA for it too.

It also could happen when you're missing some of the default post-functions for the transition the issue was last moved through, is Backlog the initial status? If that issue was in fact transition to Backlog (from some other status), make sure that transition contains the 'Update change history for an issue and store the issue in the database.' post-function. It should be there, but if somebody was tinkering with the workflow, it's possible to be missing.

Vickey Palzor Lepcha

Is JIRA Admin able to move the issue ?

Kian Stack Mumo Systems

Another bug that I've seen in the past is when there is a broken condition or validator (even on another transition) it can prevent anyone from executing workflow transitions. It doesn't sound like this would be the issue, but it might be worth looking at.

Swati_Mathapati

Jira admin is also not able to move the issue

Swati_Mathapati

Yes looks like there is a bug

Swati_Mathapati

The workflow is common for all the issuetypes and only for few Epics the transitions are not visible

Kelly Arrey

If this transition works for this user for some Epics but not others, then that makes me think it's not a permissions issue. Is there some other condition or validator on that transition, and the data in the ticket doesn't pass the condition? For example, the transition could be checking that a specific field is filled in or something.

Swati_Mathapati

I have got the solution ,it was due to the corrupted workflow and copying/renaming the workflow solved it

Thank you all for your help

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

server

jira-software

jira-software-server