Replacing status in workflow for another

Mariano Edvardsson February 26, 2024

Hello! I've looked around but could not find my specific case. Only how to edit or modify statuses, not really have one status take the place of another.

 

I have the following workflow:

 

Screenshot 2024-02-26 at 05.44.38.png

 

 

I would like status "Waiting for Support" to become "Open". Of course I cannot edit it as Open already exists. How can I make Open take over "Waiting for support" without adding it and remapping the whole Workflow?

1 answer

1 accepted

2 votes
Answer accepted
Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2024

Hi @Mariano Edvardsson 

You can't.

You can only achieve this by editing the workflow, add the Open status and link all transitions in and out of the Waiting For Support to Open, then remove open.

If it's a Company Managed project you will need to create a copy of the workflow, as on live workflows statuses can't be removed.

Edit the copy and add the copied workflow to the workflow scheme.

Mariano Edvardsson February 26, 2024

Hello @Marc Koppelaar ! Yeah I imagined I couldn´t. And as I mentioned, going the way of remapping the whole workflow is not really what I'm looking for.

 

Maybe filing a feature request on Jira? Not sure if there's many instances where this feature is needed tho :-/

Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2024

Hi @Mariano Edvardsson 

May I ask why not?

This will be your only option, all information to status is logged in the DA and used within reports and JQL.

How would you see this working?

If it would be a car I can't just call my Toyota a Ferrari!

Like Nic Brough -Adaptavist- likes this
Mariano Edvardsson February 26, 2024

Hello again @Marc Koppelaar ! Why not what? Remapping all the transitions in the workflow?

 

Well, imagine there's a Workflow I want to use as a "template" for a particular project, but I don't want the status to be called "Waiting for support" but instead "Open".

The whole workflow structure does it for me, several different, the "In progress", "pending" and even "resolved" works great, evverything except I need to swap the initial status.

Now, imagine having to remove "Waiting for support" and Adding "Open" , then doing the connections from and to "Escalated", "Resolved" and "Cancelled".

Now imagine a scenario where the initial support connects to many other statuses.

 

Now imagine having to do this on several other Workflows and schemes.. you get the idea 😉

 

All this instead of simply putting "Open" in place for "Waiting for support" and Jira working out all the transitions to the rest of the statuses. Doens't sound like too crazy of a requirement.

 

🚗 And no, of course you can call your Toyota a Ferrari, but as I stated initially; this is not about "renaming" a status. It's about swapping one for the other without having to redo the transitions that are already there.

Imagine you want to trade in your Toyota for a Ferrari, but the dealership forces you to redo your garage, your driveway and even your house before you can get to use it! 😅

Marc Koppelaar
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
February 26, 2024

.

Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 26, 2024

Hi @Mariano Edvardsson 

Unfortunate you can't.

You can only edit the name, this will change the name in any flow the status is used.

 

To stay in the car analogy, swapping an engine needs work as well. All cabling, hoses, etc.. won't be reconnected by magic :)

Like Nic Brough -Adaptavist- likes this
Mariano Edvardsson February 26, 2024

Hello @Marc Koppelaar I totally understand your point of view! 🙌

I would like to politely draw an alternative to your analogy: I agree with the engine needing work, but isn't the engine the most essential part of the car, thus needing extra work?

Is a single status among many other statuses as essential as the engine for the workflow?

 

What if you needed to change one of the headlight bulbs, and instead of simply changing the bulb, you need to redo all the cabling, relays, fuses, etc.?

 

I don't think a single status in a Workflow is more essential than any other status in the same workflow; just as same as a right frontal headlight is no more important than the left one, or one of the rear lights. Therefore, IMHO they should be interchangeable in an easy fashion.

 

Of course! I do understand, it's not possible. I had the impression it wasn´t possible since the beginning, but it was worth a try.

 

Just imagine if you wanted to change your initial status from "Waiting for support" to "Open" by simply swapping them and not having to redo all the transitions, wouldn´t it be cool? 😃

 

Thanks for the point of view though, Marc! It´s always fulfilling to engage in Jira banter and the car analogies are always fun haha!

 

PS: Now I have a question, your car is really a Toyota or a Ferrari? 🤔

 

Cheers mate! ~

Marc Koppelaar
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
February 27, 2024

Hi @Mariano Edvardsson 

Love your response, but I still think any status in a workflow is as essential as an engine.

As you need to process your issue via the flow, that statuses are like "engines".

PS I have an Alfa Romeo

Like Mariano Edvardsson likes this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events