Add a transition on draft workflow

Question

Hi,

For god's sake, will Atlassian really care about users' everyday use of their product?

I understand that a draft workflow cannot get new transitions because of the poor technical design of Jira internals. Right? After all I have read, I could not find any good official explanation to this limitation. It's more or less "because it's like that".

But is there any real, logical reason why Atlassian does not want to improve their product by addressing such trivial issue?

Come on, look at that:

Is it rocket science to allow me to add a transition going out from "TERMINE"? It raises issues? Fine, so... Atlassian developers can not fix them?

I'm not speaking about workarounds, because they all involve painful operations. Jira Software is not able to let us add a transition between states under certain circumstances, and that alone is a mystery.

Instead of redesigning the interface with more or less success, would it be possible to put some effort in common daily cases that stuck the users?

Or... if I am wrong, if it really is impossible to solve because of a definitive singularity, please can someone help me understand what on earth makes the concept fail?

Thank you everyone. Regards.

Nic Brough -Adaptavist- · Answer

Yes, it is at least consistent.  I don;t think this is bad - trivial problem affecting a tiny sub-set of people, with a clear tested work-around in a system that is on the way out.  I would not bother to try to fix it either.

Adrien Morel · Answer

Yes... and this answer has been given on so many so-called "minor" issues.

Well, at least the decisions are consistent.

Regards

Nic Brough -Adaptavist- · Answer

This has been discussed several times, and when Atlassian have spoken about it, the response boils down to:

* It's complicated and hard to fix (i.e. expensive)
* It only affects a tiny number of people - inexperienced administrators who don't know that they should always add at least one outgoing transition to every status, and administrators inheriting systems with workflows set up be people who don't know about the problem
* There's a standard process that fixes it perfectly (albeit not always a simple one, and never quick)
* And, more recently, "we're moving away from doing workflows this way"

Which essentially means that it's never going to make it up the list of priorities - there's far more urgent things to fix, affecting more people, not having work-arounds, cheaper and/or not going away.