Move up/down Conditions and Validators in workflow transitions (like Post-Function)

[Reply Test Group]

Hi Atlassian team,

I want to know if there is a possibility to move up and down conditions and validators in a workflow transition, like I can already do with post-functions.

In my situation I have multiple conditions, validations and post-function for a transition, and every time I add a new condition or validation I must manually set the order execution, because I cannot move up/down conditions/validations with the arrows (present in the post-function only):

Adding a new condition or validation means deleting some of them if I must insert it between two others, and recreating the deleted ones for adjusting the order in which the error messages are displayed, and that is veeeeeeery annoying.

There is probably no way to do that, but even if there is an ongoing request about it, I'd love to know.

Bye,

Fabio

[Reply Test Group · Accepted solution]

Hi all,

only for letting you know, the respective ticket JRACLOUD-77094 was open about it.

Bye,

Fabio

[Reply Test Group · Accepted solution]

Hi Atlassian team, @Jack Brickey@John Funk 

I want to expand my example for letting you understand better how I use validations in a particularly complex transition (but here I describe the first 3 validators only).

In order to advance (from top to bottom), I check:

 1. if the current issue is NOT blocked by any open Story of the INIZIATIVE project;

 2. if the Epic of the current issue has surpassed the state "EPIC ASSIGNED";

 3. if the Epic of the current issue is linked to a ticket Capability of the PORTFOLIO project;

 ...

Now, we test this validation list.

Check 1: The current issue is blocked by an OPEN Story of the INIZIATIVE project

Check 2: The Epic of the current issue has NOT surpassed the state "EPIC ASSIGNED"

Check 3: The Epic of the current issue is NOT linked to a ticket Capability of the PORTFOLIO project

, etc...

From here, if I link another INIZIATIVE Story (open) that blocks my current issue, and try to advance, instead of seeing the Check 3 error, I see the Check 1 error instead, because the first validation is on top of all and has the highest priority:

All of this to prove that THE HIGHER A VALIDATOR IS, THE HIGHER THE PRIORITY OVER CONTROLS WILL BE !!

So, pleeeease, verify if it is possible to implement a way to rearrange the order of the validators, because for every new control I want to put in the middle of this list, I'm forced to eliminate all the ones below and re-insert them.

Thank you for your patience, I hope that someone reaches the bottom of this comment ^^

Fabio

[Jack Brickey]

I think you should be able to rearrange any conditions post functions validator's that you personally add. Any new property added will always go to the top.

[Reply Test Group]

Hi @Jack Brickey

the custom validators that you see listed below:

was all created by me, and anyway there is no thing like validators ownership in workflow transitions that could block me for changing the order.

The problem is exactly that any new validator added will always go to the top of the list, and I DON'T want that: the error message in the first (or rather, new added) validator should NOT show first of others, but later (unlike post-functions, that already let you order them, indifferently if the function is added by someone else).

Fabio

[John Funk]

Hi @Reply Test Group ,

See this previous post that describes that Jira does not fire validators in any particular order.

https://community.atlassian.com/t5/Jira-questions/Reorder-validators/qaq-p/622630

[Reply Test Group]

Hi @John Funk 

that is a 5 years old post.. I assure you that the validations cascade-order is a thing.

Maybe the conditions have no reason to be ordered, but the validations surely have: in my case I insert validations in an ordered way because I must verify different steps, first the high-level checks (like if the parent Epic is not closed) and last the field required checks (like if the fields in the transition screen have been set).

Trust me, validations are performed (and respective error messages are shown) in the order in which they were entered.

Fabio