Hi, I have been working with JIRA workflows for awhile, and the common understanding is that you can't delete a workflow status from an active workflow, also stated in Atlassian's document:
But by chance while working on a new customer project recently, I saw that my colleague managed to delete a workflow status from an active workflow.
It seems like this is possible when there are no issues residing in that particular status. I managed to reproduce the scenario on my test instance afterwards.
Perhaps the documentation should highlight this point if this is true. Hope someone from Atlassian could take a look.
The real reason why you cannot do this is that Jira's workflow system was designed in a way that would require a complete rewrite to allow status removal, and Atlassian hasn't prioritized doing it.
For some reason this didn't work for me, though i worked before.
I added "blocked" status and when i tried to remove it i got message that it's restricted. I have checked - the are no issues in the blocked status in whole jira (all the projects), including the project that has this workflow assigned. SO i am confused how this happened.
I have removed all the transitions to this status as a workaround but I would like to remove the status from the workflow to have everything in order.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I know of a few ways to do this, but none I'd say were "good".
Could you tell us how you are doing it, and what version of Jira it is?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
My local instance is on JIRA Software 7.5, but my colleague was on 7.8.
Below is what I did to reproduce the effect:
Actually, when I relooked into the message I get when doing "step 3", the message does say that we can remove the status if the issues are moved out of it:
We can't remove this status for you
There are issues in this status that need to be moved to another status or project before we can remove this status. Please contact your JIRA administrator if you need assistance.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The "devil is in the detail" here.
On step 3 - there is no simple "edit the workflow". Did it go into "draft" mode?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Nic,
Yeah, you are right, I missed to mention I am editing the draft of the "Active" workflow, and did it from the Administration -> Issues -> Workflows section :)
The article I listed does point out that even editing the draft of the Active Workflow does not allow you to delete workflow statuses, so I think that part should be changed a bit to indicate that if there are no issues in the status, you can actually do it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Give the Docs team a chance to catch up - 7.7 can't do this, 7.8 does.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
yeah sure, not criticizing actually, but hoping to sound out the info I understand about this is correct. There is this "Advanced Workflow Badge" exam that I am about to take, you see :D
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sorry, I was slightly wrong there. Not sure exactly when it changed, but later versions of Jira do allow you to do a "full" edit on a workflow that has no issues associated with it. It used to be that if it were used in at least one workflow scheme that was active in a project (in 6.2 which is the only one I have to hand), but now it checks "am I used by any issues". The code in the background is different to the docs and the on-screen information!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
This post just saved me so much hassle kudos to all of you guys !
However one question I had with respect to a different scenario
In case of multiple projects using the same workflow does this hold good ? (Provided there are still no issues with this status)
I tried this with a workflow which was dedicated to one project only and it works.
@Alvin Chan _Ease Solutions_ Thanks for all the knowledge :) :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.