Value Field Condition - Current Status, Status Category

[Matus K]

Hello to all, 

I recently got rid of JMWE and Scriptrunner on one of my client's instances and I am trying to facilitate most of the advanced configuration and automation with out of the box features. 

In regards to a specific case (conditional handling of transitions based on the current status or current status category), I have found the only option to achieve this is by using Value Field Condition. 

Unfortunatelly after trying all the possible combinations of strings and Option IDs for statuses and categories using '=' operator. I can't seem to get this thing working. Can someone help me to find the right configuration for this? 

Examples: 
- Status Category | = | id=2 | Option ID
- Status Category | = | 2 | Option ID
- Status Category | = | new | String
- Status Category | = | "new" | String
- Status Category | = | to_do | String
- Status Category | = | "to_do" | String

....
 

Thx,

Matt

[JG Meillaud _]

Hi Matus,

We had a similar need today, and unfortunately Status Category was not working in workflow conditions. (which is a bug)

I suggest you put all the statuses you want to allow in an "Any of the following conditions" block or all the statuses you want to exclude in an "All of the following conditions" block.

In the end this is what works for our use case :

Cheers,
JG

[Patricia Francezi]

EDITED because after testing i figured out that strings with space need to be avoided. 

Hi @Matus K 

I know that might be late, but I was working in a scenario similar to yours. 

My problem was that I was not able to make a condition with Status field, by using != and then as string. 

My case is I dont want the issue to back to Complete if in "In review", "Resolved", Canceled Status. 

Also found that the "In progress" status as string does not match because of the space. Tried with " and ' no results. 
So I changed some to option ID and got the status ID from Admin 

THis is my screen 

Sounds to be easier when doing directly by status category, but using = status was the only way to work for me. 

I hope this helps. 

[Walter Buggenhout]

Hi @Matus K,

I think the following should work:

Hope this helps! 

[Walter Buggenhout]

Hmm; after testing it I must say I am a bit puzzled as well. I did not succeed in making this work with status category = To Do. I am wondering if that may be a bug.

Anyway, the following workaround did work successfully in a test environment:

[Matus K]

Yes, but unfortunately this would still enable the transition from statuses in category To Do to category In progress. With the original condition

Status Category will have to be equal to To Do. 

these transitions would not be visible which is not desired in my use case. 

[Matus K]

Oh sorry, 

My mistake.. in my case this workaround is not working whatsoever. :D 

[Walter Buggenhout]

I am sorry, @Matus K, but you have lost me there. I am getting the impression that you are trying to use conditions on global transitions (those are transitions from a black All lozenge to a status) to disable certain transitions you don't need.

If that assumption is correct, why don't you simply replace the transitions you don't need by actual, direct transitions between statuses like this:

That way you won't have to bother about hiding them conditionally based on status (category) at all.

[Matus K]

So my usecase is quite different.

Imagine:
To Do statuses -  Concept, Specification, Spec Review, Ready
In Progress statuses - In Progress, Testing, Review
Done statuses - Done, Canceled 

each being available by ->all transitions.

What I am trying to achieve is prevent users from seeing transitions to all In Progress Category statuses as well as Done Category statuses while issue is in To Do Category statuses (with exception of Ready).

This was previously handled by JMWE Current Status condition which right now I need to exchange for Value field condition.

To simplify the amount of conditions needed for all the current statuses on all the transitions I decided to use Status Category condition instead. 

Putting Status Category will have to be equal to To Do condition on statuses - Concept, Specification, Spec Review (not on Ready) will make sure that users can only switch between Concept, Specification, Spec Review and Ready only. Once in Ready issue is considered "ready for the next stages of the flow" and rest of the transitions to all statuses will become available. 

I hope that this clears out the mist,

Matt

[Walter Buggenhout]

That is what I was thinking indeed. So: get rid of the -> All transitions and redesign your workflow somewhat like this:

You won't need any conditions anymore, except (if you want to be really exact) on the transition to Cancelled. It would make sense there to restrict that transition by applying Status Category != Done.

[Matus K]

Unfortunately I have to keep all transitions in place. That is a requirement from the customer. 

Also even though your proposal is right for more waterfall oriented flows in this case we also need to ensure: 

make sure that users can only switch between Concept, Specification, Spec Review and Ready only 

This means from any to any freely.