nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Condition information during status change

Uwe Sauerbrei2

There is an option to define a condition before a status change takes place. In my concret case there is a value to be checked not to exceed a specific value. If the value is greater than the specified value, the status change action will not be displayed. My problem here is, that the user has no information why he can't proceed, since there is no message that he has entered a wrong value. This makes the condition option useless. Are there any recommendation to get around ?

Thanks, Uwe

Accepted answers

Nic Brough -Adaptavist-

The other option is a validator - let the user into the transition, don't use conditions. Then when the user tries to commit it with invalid information, they will be returned to the transition screen with an error message explaining why they cannot proceed.

Udo's suggestion is really good if you want to block the user before they even start a transition - that's often nicer than using a validator.

All comments

Udo Brand

Well, you could add another transition from step A to step A with the opposite condition (value must be greater than specified value) and name the transition "reduce value". Add a screen in this transition where the user can reduce the value of that field.

Nic Brough -Adaptavist-

Udo's suggestion is really good if you want to block the user before they even start a transition - that's often nicer than using a validator.

Renjith Pillai

Instead of a condition, use a validator and also add that value to the screen. This will throw and error and the user will be able to know why.

Use script runner if you need to add a validator that checks the value.

Uwe Sauerbrei2

Interesting idea. I'll try this to get some feeling for this solution. Thanks

Uwe Sauerbrei2

I used validation ( the modified basic script) to fulfill the task but was wondering, why do conditions exist without notification and if there is something I have not found.

Nic Brough -Adaptavist-

It's about human behaviour and simplicity.

If you give a human the option to do something, you need to tell them why they can't do it if you then block them (so validators have feedback)

If you do not offer them the option to do something, then you don't need to explain why you are not offering it to them. You wouldn't want to litter a screen with loads of "you can't do X because..." messages when most of the time, the users don't even want to do X

In this case though, I'd be tempted to use a message field (from the Jira Toolkit plugin) to explain why they can't do it.