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

Transitions not available

Geoff Goodhew_iniikk

Hi there,

I have a project where I cannot transition issues once they reach the final status (Deployed, in this case).

Unfortunately, when the workflow was set-up, they didn't populate the Resolution. I've fixed the workflow so any issues being moved to Deployed in the future will be fine. But we now have old issues in the 'Deployed' status without a resolution. I want to transition the issue out and back into the final state to force the resolution. But I'm told, "You don't have permission to transition this issue".

I've done a search for answers here - I found this similar post https://community.atlassian.com/t5/Jira-questions/Cannot-transition-issue-with-all-permissions-only-1-issue/qaq-p/1230550.

It's not my permissions: I'm a Jira admin, project admin, and can transition issues from other statuses on the project. I was able to reopen issues on a different workflow in this project. I've been able to re-open and resolve issues on other projects.

I can't see anything specific in the transitions going into this status (no conditions, properties, validators, or triggers; the only post functions are the standard ones plus setting the resolution).

The only thing I can think of is that the final status has no outbound transitions; that means I can't add an outbound transition. Although on another project: I got around this by adding an 'All' transition, which worked perfectly; it isn't working on this project for some reason.

Any thoughts on what I can do to fix this would be appreciated.

Accepted answers

John Funk

Hi Geoff - Welcome to the Atlassian Community!

This happens from time to time. When it does, if you will copy the workflow, make your changes and then update the workflow scheme to sub in the new version of the workflow for the old one.

Be sure to map the new workflow to the same issue types as they are currently mapped.

And finally, be sure to publish the edited workflow scheme.

All comments

John Funk

Hi Geoff - Welcome to the Atlassian Community!

This happens from time to time. When it does, if you will copy the workflow, make your changes and then update the workflow scheme to sub in the new version of the workflow for the old one.

Be sure to map the new workflow to the same issue types as they are currently mapped.

And finally, be sure to publish the edited workflow scheme.

Jack Brickey

here are two options to consider:

edit the workflow and create a transition from Deployed back to itself. Call it say "fix-it". in that transition you can create a post function to set the resolution to done. publish this workflow and use bulk edit ... project = abc and status =deployed and resolution is empty. Use Bulk edit to transition all of the issues using "fix-it". Once fixed go back and get rid of that fix-it transition.
using the aforementioned jql use bulk edit to add a label ,e.g. fix-resolution. then use a second bulk edit to reopen all issues. once reopen use another jql leveraging the label to find them this time and transition all to deployed.

adjust things to meet your specific situation.

Geoff Goodhew_iniikk

Thanks - this worked.

I was hoping to avoid switching the workflows, but given nothing else seemed to fix it, I was out of options.

Geoff Goodhew_iniikk

Thanks. That was the process I'd done with other workflows. But the problem was the transition wasn't available. I needed to switch out the workflows to get around that, then use the process you've outlined to fix it.

John Funk

Well, I am glad you at least got it up and running even if it's not the ideal solution.

Mark Deschamps_bifh55

I had a similar situation. Was beating my head against the figurative wall, because it *should* have been working but as not, the transitions *should* have been there but were not. This solution ended up working. I'm breaking this down, for future reference.

Made a copy of the existing workflow
Added copy of workflow to the schema
Associated the issue type (Story) with the copy of workflow
Published update
Refreshed the trouble record & the transition states magically appeared.
Went back in, changed the workflow for the issue type back to original (the workflow copy went into the inactive category)
Published the change (back to the original)
It's behaving as it should have been

This was occurring with a handful of records, most of which were a year old. I'm wondering if these records got into a weird condition as we had made some changes to validation rules since then (?)

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-software