I manage one of the JIRA projects for my company and, therefore, have admin privileges. I am able to edit everything on respective issues, including the Status tab.However, there are a couple random issues that are not able to have their Status changed by myself or general JIRA admins. The most recent case is caused by bulk updates, where I have about six open tickets that cannot be transitioned by Status.Is this a known issue?
did you drill down into the transitions themselves (double-click the transition) and check for Conditions? You mention they are "random issues" but I suspect there is something unique about those you cannot transition unless you are saying that an issue can be transition one moment but not the next.
Not able (or unsure how) to double-click the transitions themselves, but I went into the respective workflow scheme:
The "Task To Do" Status is defaulted whenever an issue is created in this particular project. I'm not sure, however, if the problem occurs during the issue creation or after the ticket is updated in some way other.
are you an admin? If so go to project > project settings > workflows and edit the associated workflow in diagram mode. Double click on one of the transitions that you are not able to execute. From your initial images it appears that when an issue is in the To Do status you cannot transition it which is pretty bizarre given your workflow image. That would seem to say that you cannot transition out of To Do via any transitions (In use, Not in use, Complete, etc.). One question do you only have a single workflow for all issue types? If multiple be sure to edit the one that is associated w/ the issuetype where you are seeing the problem.
From the "Task To Do" status, it appears there are no conditions preventing transitions.
I am an admin and able to edit just about anything, including the Status tab. These problems are one offs from my normal activities, where I can freely make Status transitions (which is why I provided the pictures in my original post). This workflow works for 2 issue types, but they are exclusive to this project and appear to be fine.
I do not believe so. Out of 131 issues I recently bulk updated, only 1 ran into the Status problem. These issues are generated by the Scheduled Issues extension every day only for the project I manage. I can't say if the issue occurs when an issue is initially created since that's an absurd amount to manually check.
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