How can I restrict the submisson JSM form only when user hit Send button

Question

This topic was already discussed and closed, as you can see below.

I’m extremely disappointed with Atlassian. How can you take a feature that worked perfectly well like preventing a form from being submitted when certain conditions aren’t met and break it?

This is exactly the kind of change that makes users lose trust in the product. Instead of improving things, Atlassian keeps removing or breaking functionality that already worked and replacing it with things that simply don’t make any sense.

Now, from what I can see, users can submit forms with incorrect data ... wonderful!

Honestly, congratulations, Atlassian. You’re making an already frustrating tool more and more hated by the people who have to use it.

https://community.atlassian.com/forums/discussion/3072947/how-can-i-restrict-the-submisson-jsm-form-only-when-user-hit-send-button

Marcelo Montaño Sánchez · Answer

Hi

I think there is also a distinction between validating the form and validating whether the information entered is actually correct.

No form can guarantee that free-text information is correct. You can validate required fields, formats, lengths, allowed values, and relationships between fields, but if you ask a user to enter a name, for example, there is no way for the form to know whether that is actually the correct name. That's not really a Jira-specific limitation; it's a general limitation of user-entered data.

For that reason, I prefer to control the input as much as possible. If the information should come from a known set of values, use selects, checkboxes, radio buttons, Assets fields, or other controlled fields instead of free text. The user is then choosing from values that have already been defined and validated.

Free text is useful when the information genuinely cannot be predefined, but if the requirement is to guarantee the data is correct, I don't think trying to solve everything at the Create button is the best approach. Good form design can prevent many of those validation problems in the first place.

Regards

Calvin · Answer

Not sure if I'm answering what your asking appropriately but if your asking how to stop an accidental enter we have a field we mark as mandatory that says "I have reviewed the above and wish the ticket to be submitted" option.

If your asking whether you can put some "smarts" before hitting enter, the quirky work around is we have a custom workflow for that request type, in the transtaiation to "new" (the create one) we add required fields in here. This allows us to block the form being created and give an error.

* For example we have a field that needs a date/time in the future, so in the transistion to "new" I require the "field > now()". And if it isn't, Atlassian won't submit the form at all and give an error instead.

Mario Coluzzi · Answer

Thank you for your reply.

Unfortunately, that option did exist six months ago, when I last worked with Forms in JSM.

Using the old Add Section, I could prevent a form from being submitted by using a hidden “trap”. This worked perfectly fine.

Now, in order to make it work, the “trap” has to be visible on the form.

In my opinion, Atlassian should have prioritised to fix the almost 8-year-old issue “Form Wide” WYSIWYG instead of introducing the new “Section” functionality.