Nope, definitely validators. Bad prose on my part probably.
Validators either pass, or fail, and when they fail, as you say, they "allow an error collection", which then goes back to the screen that the user is returned to. They don't have anything that lets you do messaging outside that though, so message popups and so-on simply don't have anything to feed into, all you can do is add to the error collection.
I don't know jjupin well enough to be aware of it doing more clever stuff, I've only ever seen it used to write validators that work like that.
You're missing the point - a validator either passes or fails.
There's no screen to define because it goes back to where it was when the user started the transition, and there's no point in having message levels, the validator just says "failed validation", there's no other information.
There's a confusion here. I'm afraid I missed this question, and the answer will come a bit late (my bad). You cannot put a LiveFields call on a validator. You can use LF only from LF scripts or hooks and in postfunctions.
What you need is to validate that field client side. This does not absolve you to write the validator itself.
Hey Atlassian community, I help lead engineering at Sentry, an open-source error-tracking and monitoring tool that integrates with Jira. We started using Jira Software Cloud internally last year, a...
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