Hi,
I've created a condition on a transition that says 'Fix Version' must be populated in order for the transition to be available and execute. It works fine in that the transition is only visible when the has a value.
This works fine for me as I know why the transition isn't available. For other users, less familiar with the workflow this will not be obvious.
Is there a way to alert a user that a specific condition has not been met and to prompt them to complete it?
Thanks as always,
Jon C
Hi @Jonathan Cunliffe ,
Instead of Condition, you can make use of Field Required Validator as part of transition.
Can you try below steps.
Thanks,
Avinash
Excellent. Thank you all. Have a great weekend......
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As mentioned @Avinash Bhagawati {Appfire} , this is exactly what you need to do in your WF. By implement his suggestion, when users tries to transition the issue, he/she will see the pop-up transition window for "Fix Version" population, if he/she fails to provide a value the transition will failed and not be completed. Their can only cancel the transition if they don't know the appropriate Fix Version value to provide.
Best, Joseph Chung Yin
Jira/JSM Functional Lead, Global Infrastructure Applications Team
Viasat Inc.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There isn't a way to alert the user that a field must be filled in order to reveal a transition. For these cases we usually turn our attention to validators. This mean that the transition will be visible to the users, but if they try to perform it, if the fix version field is empty, the validation will fail and the transition will not take place. A message on the bottom left corner will appear.
Another solution would be the one that @Avinash Bhagawati {Appfire} suggests with the transition screen and the use of validators.
Be well!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks @Alex Koxaras _Relational_
The key was in your answer. If we want to prevent the user from a transition and display an error message we have to use the Validation instead on a Conditino
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
We should note that when we use Condition, Jira will check the condition before showing the available statuses for transition. So if condition fails, user will not see the new status and cannot select it, so the error message is meaningless here because user cannot do the transition.
from the point of view of UX, using condition leads the user to come up with a question:
"Why I cannot see the new status to select?"
But if we use Validators, user can see and select the new status. By doing this the validators will run and if the validation fails, user will see a message about it. This has a better UX
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.