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

Admin override of current work flow step / status

lance_lyons

Hi, Is there an easy way to move an item back to a workflow status if that transition was not defined?

I know this can be done in the database itself but wondering if there is some way to do this in administration?

Accepted answers

All comments

Jobin Kuruvilla [Adaptavist]

Nope, Databse is the only way. Or you modify the workflow to have a transition back but one that is visible only to Admin!

Dieter

No, there is no way to do that in the adminstration area of JIRA. bear in mind that you would need to keep in synch the status and workflowid in jiraissue and the various osworkflow tables. The only way to do that safely and consistently is to execute a transition defined in the wokflow. But why not just create such a transition and add a condition that just allows the jira-administrators group to do that? whenever someone comes to me with a request like yours i add such a transition and leave it, executable only for us admins. Don't worry, the definition may look bloated but the transition is not visible for the end user. To better identify these priviledged transitions you could name them [ action (admin only)]

lance_lyons

Here is my problem. We created the workflow to have some status/states called duplicate and rejected. We only had incoming transitions. Now if one is accidently moved to duplicate we cant move it back and we can add the transtion out since it is not set that way in the active workflow?

Any thoughts or suggestions?

Nic Brough -Adaptavist-

Exactly as Dieter and Jobin say - you need to add a transition to the workflow that will enable the move back.

lance_lyons

Yeah but since the active workflow does not have a transition that leaves Duplicate, you cant add a return back transition in the draft.

JIRA will not let you. Do I need to completely redo this workflow?

Welcome!

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

Quick Links

Find more posts tagged with

jira