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

Unable to move issue to "Done"

Robert Oxford

We are unable to move an issue to "Done".

Other issues in the project have the Workflow options, but not this issue. What do we need to adjust so that this issue has the same workflow options as all the other tickets in the project?

We have resolved similar situations with other issues by moving the issue to a different project and back again, but this process risks losing custom data that was in a custom field that is not in the project into which you are moving the issue.

There has to be a better way.

These two issues are from the exact same project, yet VE-11839 does not have access to the Workflows

Any help would be appreciated.

Accepted answers

Radek Dostál

This sometimes happens (for unknown reasons), and the official way to resolve any such unexplainable issue states is to copy the workflow, and re-associate it with the project (this causes a workflow migration for all issues using this workflow). This will make the issue get "mapped" back to the workflow.

However, this should really occur veeery rarely (perhaps a few times in my practice, but really, a handful situations).

If you are however able to reproduce this, or if this happens to you often, then the chances are something is brute-forcing something around there - either brutalizing the issue itself, or brute-forcing workflow changes without issue migration. Neither are exactly easy to do even if you tried, without using sql, so probably not the case there. Probably something to do with permissions/conditions as Fernando suggested.

All comments

Fernando Eugênio da Silva

@Robert Oxford

If the transition does not appear, it must be because there are conditions in the flow that prevent it from appearing.

You can check the workflow if the transition you want to apply has "Conditions" added and what they are.

A quick troubleshooting is for you to use the "Permission helper", it will tell you why you can't perform the action.

Just click the "Admin" button and click "Permission helper".
Enter the user and the action (transition issue), in this case and click "Submit".

It will show you why you can't handle the issue.

If one of these two things doesn't work, let us know.

Fernando.

Radek Dostál

However, this should really occur veeery rarely (perhaps a few times in my practice, but really, a handful situations).

Radek Dostál

^ this of course is the first step rather than mine's

Fernando Eugênio da Silva

You can generate a troubleshooting and support in the System section and check the log why this error is suddenly occurring.

With the log, you would know exactly where the problem is.

Robert Oxford

This did not work. I think it may be related to Jira going down for some reason. I will see if Radek's suggestion works.

Thank you.

Robert Oxford

Radek,

I tried your suggestion. It worked.

I did the following

Copied the workflow in use by the project. called the new one: Temp
Created a new workflow scheme and included the new "Temp" workflow: called the new Workflow Scheme: Temp
Switched the Workflow scheme for the project in question
Switched the Workflow scheme for the project back to the original Workflow scheme

I believe the original issue may have been caused by a Jira application crash.

Thank you for your suggestion

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