So, I have recently become a Jira Admin in the company I`m currently in and we have an issue with Statuses.
Prior to my arrival, there was no Status management whatsoever, thus we have today for example 5 statuses that indicate blocked:
-Blocked // Bloqueado // Bloqueados // Bloqueada // Bloqueado(a)
I`m currently with the task to clean this and merge all these statuses to only 1.
Is there any way to do this that isn't switching the existing workflows by a new one with the correct statuses? i.e. a bulk change from one status to another (where it changes also the workflows)
I did not find anything regarding this topic yet. If there are no better options for this... then monkey job it is.
Hi @Alex Borges da Silva and congrats to becoming Jira Admin :)
With the right permission (which you should have as jira administrator) you are able to do the bulk transition:
Hope this helps. Please let us know if there are any further questions.
Best
Stefan
Hey, @Stefan Salzl Thanks for the quick response!
See, it is not a status transition (i.e. from "to do" to "doing"), it is between different workflows...
Example:
I have Workflow A with:
To-Do, Doing, blocked, and Done
Workflow B with
To-Do, Doing, Bloqueado, and Done
(Bloqueado means Blocked in Portuguese)
Thus we want every workflow and issue to have Blocked and not Bloqueado... Since the workflows are currently active I cannot simply enter on each one and change it... :(
The solution I`m going through right now is deactivating the workflow, changing the status to the correct one, reactivating it, and then bulk changing... but this approach will take a great amount of time...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
okay. are those workflows withn the same project? or is it:
and you would like to have workflow A also in project B ?
In this case you could associate the workflow scheme from project A to project B. You will then be asked how you want to map the status:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Sadly it is WF A in Proj A and WF B in Proj B
Right now I cannot use WF B in Proj A (since it is not a feasible resolution for most of the projects)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As you described in a former post:
I have Workflow A with:
To-Do, Doing, blocked, and Done
Workflow B with
To-Do, Doing, Bloqueado, and Done
(Bloqueado means Blocked in Portuguese)
The only difference I see in the workflow is blocked vs Bloqueado (which as far as I understood is exactly what you want to change).
So are there any other differences in these two workflows? Maybe I missunderstand the requirement. What prevents you from using workflow A in project B?
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Stefan Salzl These are not the actual workflows, they are just an example, a real case would be:
WF A - To do, In Progress, Done, Homologation, Blocked
WF B - To do, In progress, Done, Bloqueado
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Alex Borges da Silva ,
I guess the following question from the community sounds similar to yours:
As from that answer there is no bulk function for workflows. Best practice is to harmonize and re-use workflows and if not possible at least re-use statuses.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Even if there is no propper solution for bulk-function for workflows please let us know if your initial question was answered and if so please check the answer as accepted in order to mark this question as solved.
Best
Stefan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Join the largest European gathering of the Atlassian Community and reimagine what’s possible when great teams and transformative technology come together. Plus, grab your Super Fan ticket now and save over €1,000 on your pass before prices rise on 3 June.
Register nowOnline 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.