I am curious how everyone would go about adding a validation check to a field that is only required sometimes.
Currently, we have a custom field called 'DOC REQUIRED'. So, as you can probably guess, if this dropdown is set to 'YES', then another field called 'LINK TO DOC' must be populated. This is checked on the transition between the columns 'In Progress' --> 'Ready to Review' and also 'Ready to Review' --> 'Done'. We are currently using conditions for this validation. We have one condition that says if the 'DOC REQUIRED' field is not set to 'YES', then no problem go ahead. Inside that condition we have a nested condition that states that if 'DOC REQUIRED' is set to 'YES', but there is nothing in the 'LINK TO DOC' field, then it blocks it.
The functionality works fine and it is a passable solution. The only problem is because we are not using a validator, there is no error message that shows up. So, what often happens is that developers don't know why they cannot move their tickets because they have forgotten the requirements.
Does anyone have any other possible solutions for this case or a similar case?
Is there an elegant way to use conditions and validators together?
I am looking to learn just as much (probably more) than I am looking for a perfect solution to the problem, so any constructive and related input would be cool.
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events