in Team-Managed project, transition already exists but can't be reused ?

Question

Hi,

Decided to go for a team-managed project for someone that wants a small project with basic needs.

I usually never go for newer feature as I find its ALWAYS badly designed, when it's not completely useless or broken. 
But this time I felt like "yeah, let's try it again it's been months now since these projects have released".

Obviously already regretting that as I have to write a post for such a stupid issue :

So I created a new BLANK project and I'm currently creating the workflow, using basic statuses like "TO DO", "IN PROGRESS", and I've added a few like "BLOCKED" or "READY".
I was expecting the statuses to be shared between company-managed and team-managed projects but it aint. I've add to CREATE all the statuses in this workflow and it hasn't been an issue.

The problems come with the transitions, I want to setup a transition named "in progress", to transition to the status of the same name, or "Done" to transition to the Done status. But trying to create those fails and shows the error message :

["Already exists. Try a different name."]

Yes... I'm afraid you understood the same thing as I did. These transitions already exists in the other "part" of my instance, which is the company-managed projects part. And of course, there isn't such thing as "reusing a transition" like you can do in company-managed projects. So yeah, all I can do is finding another name that isn't yet taken by transitions from company-managed projects... lol.. Isn't that genius ?..

Jerome F__qhxqr1 · Answer

Interesting,

Indeed it is now working after removing the "transition from any", since it already wears the destination status' name.

So I either had something wrong with my browser cache or something (??), or they fixed it, which I know sounds ridiculous ^^ but i'm certain of what I've seen yesterday, I had the issue even with the statuses I had just created (and didn't have the "transition from any").

Anyways, I might have forgot to remove the "any transition" at that time but I'm also certain I've tried very specific status names for transition, and I would get the same message even tho the said transition is from company-managed projects, now all that is also working !

So yeah, I should have taken screenshots at least to prove it xD

Trudy P Claspill · Answer

Hello @Jerome F_

Yes, I have worked with Team Managed projects. Without the exact steps you used I tried to recreate your scenario. With a workflow that looks like this:

I tried to add transitions named "To Do", "In Progress", and "Done". Each one produced the error that you saw. I also tried adding a transition with a name I know exists in another workflow, and did not get the error.

If I delete the existing transition, to "To Do" for instance, then I was able to create a new transition named "To Do".

Perhaps if you show a screen image like the last one I pasted above, showing the current workflow and the dialog for adding a transition, then we will be able to provide additional useful information to you about the root cause of your problem.

Jerome F__qhxqr1 · Answer

Man I know all that stuff, but i'm talking about Team-Managed projects !! Have you ever tried team-managed projects ? Cuz what you say doesn't apply there.

Default workflow had :

3 statuses : To do, in Progress, Done

1 transition : Create

and all the statuses have the "from any" transition.

I've tried to name transitions after these 3 statuses => doesn't work, then tried choosing specific transition names I had created in company-managed projects, didn't work either.

Just try it for yourself...