You have to set the PRE / POST states of the other statuses to point to your status.

Ah thanks...I didn't realize I had to set the post statuses of the other statuses as well.

Maybe an "enhancement" to Gemini could be auto-adding a new status code to the Post Status sections of all the "Pre-Statuses" you select...?

We can not do that as some workflows would like the status to go one way only.

Maybe I don't understand the intended function of Pre and Post status, but I've always wished Gemini had the feature Ben requests.

If I say that a valid "Pre" status for "Deployed" is "Ready to Deploy," then logic follows that a valid "Post" status for "Ready to Deploy" is "Deployed."  If I don't set that "Post" status, it won't matter at all that I set the "Pre" status--as Ben discovered, I would never be able to get from "Ready to Deploy" to "Deployed."

I actually found the idea so redundant that I ditched all "Pre" status entries and exclusively use "Post" status for workflow control.  I would love a tutorial showing how to use "Pre" status correctly!

Try this scenario:

Closed state has a post state of re-open. No you do not want re-opened to move to closed without being tested for example, so you do not want Closed as post state of re-opened.

Hope this makes sense.

Yes, that totally makes sense, and that's how I use it (and have used it for a couple of years).

What doesn't make sense is where PRE-state comes into play.

Thanks for the reply!

Hi guys,

The entire workflow aspect is being revamped under 3.0 release, including differing workflow per issue type.

Did you ever find the solution? We have the same problem.

Forget my post, once I logged in I could see the solution!

The solution is posted, for a new state to show up it MUST be in the pre or post conditions of the CURRENT state. so if i am currently CLOSED then the close post/pre state must inlclude my NEW state