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; } } }

Why do random issues block me from updating the status even with admin access?

corey_rotterman

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. Screen Shot 2019-11-11 at 10.21.34 AM.png 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?

Accepted answers

All comments

Vickey Palzor Lepcha

I am making a wild guess - maybe the issue is shared in multiple projects/boards with varying permissions ?

Not sure though

Jack Brickey

check your workflow for a Condition that restricts who can transition.

corey_rotterman

No restrictions are visible. The workflow is the same between completed issues and the bugged issues. Screen Shot 2019-11-11 at 11.53.59 AM.png

corey_rotterman

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.

Jack Brickey

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.

corey_rotterman

Not able (or unsure how) to double-click the transitions themselves, but I went into the respective workflow scheme:

Screen Shot 2019-11-11 at 12.35.30 PM.png 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.

Welcome!

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

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

status