Why do I get the error: "We couldn't create your workflow Status must have an inbound transition."

[Svetlin]

When trying to copy a workflow, I get the following error: 

"We couldn't create your workflow

Status must have an inbound transition."

Background Info 

This occurred in production where we had one status floating around in the workflow not having any transition. After the holidays though trying out with the very same workflow with the above mentioned status, not related to any transition, we could not replicate the error on production anymore. In the sandbox I removed the status in question, so I assumed that solved my problem there, so that I never saw that error.

Could it be a bug on Jira side? Or if something else, does anyone have an idea why does this error occur? 

[Rebekka Heilmann _viadee_ · Accepted solution]

Can you post a screenshot of the workflow you are trying to copy?

I am a bit confused by the background info... In Sandbox, you removed the status from the workflow, then copied it and still had the same error message?

[Svetlin]

No, on the Sandbox I first removed the status that was floating around and there I never got the error. On Production however, since I was a bit scared removing the status might affect the users, I did not remove that unused status. So I assume, that the error came up on production for that reason. Today however, the error was gone from production so I cannot give you much more info than this. 

Here the requested screenshot: 

[Rebekka Heilmann _viadee_]

So now you can copy the workflow without an error? That's odd.

Either way - having a status with no in- or outgoing transition isn't recommended. So even in your productive workflow, you should transition all exisiting issues in that status to a different one (-> for that you need an outgoing transition to at least one other status) and then delete the Status "In Progress". You could also just try to delete the status - if there are any issues still in that status you will get an error message.

Unless you want to keep it -> then add transitions accordingly.

At the moment, you may or may not have issues that stay in limbo which may cause issues later on.

[Svetlin]

Hi @Rebekka Heilmann _viadee_ , thank you for the prompt responses! 

Can you elaborate why is it not recommended to have a status without a transition?

[Svetlin]

I think the other admins on our instance have some considerations regarding using statuses without transitions, this is why I ask you for more detailed response. I'd like to hear what arguments (pros and cons) do we have that support the thesis that it is not a good practice after all.  @Rebekka Heilmann _viadee_ 

[Rebekka Heilmann _viadee_]

I cannot think of a single use case, where you would need statuses without transitions.

Speaking from a archtitectural POV, an Issues's goal in Jira is to be transitioned into a "final" status. The final status usually has no outgoing transition (apart from possibly "reopen") and sets a Resolution to the issue (if not set already) ergo has a meaning of "This issue has no more work done on it".

Even Issues, that in reality do not get finished, would have a Resolution and be in a final status. That's why you can configure custom values such as "Duplicate", "Won't Do", "Ignored", "Not a bug" and so on.

In your case, the status doesn't even have an ingoing transition. Therefore, no issue could ever be moved into that status, not even forcefully. There is no point in having a status, that cannot be used. If you have issues that are already in that status, it's either, because there used to be a transition going in, or they are using a different workflow, that has the exact same status but with transitions.

If your "lost" status would be a final status, there might have been historic reasons why other admins are holding on to it. But it is named "In Progress" and of the status category "In Progress" so there really couldn't be a reason to keep it the way it is.

No need for pro/con, it's just not logical to have statuses you cannot use ;) if any of the other admins say otherwise, I highly recommend booking a Jira Training for Admins.