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 ?
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.
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.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs