many thanks for sharing your script here! It actually helped me a lot.
Your script is working in my customers JIRA (still on version 6.2.5): If the field contains more than 33 char and I click the "update" button on the edit screen, the error message pop-up is shown.
I adapted the call of the EventListener for our purpose: Now the listener is listening for events on the field itself instead of the "update" button and throws the error immediately if the field contains more than 33 char (keypress event instead of click event).
Just changed the line:
alert( "Invalid length, must be no more than 33 characters" );
Unfortunately, it never works. I can get the JS to work on test forms OUTSIDE of JIRA. But there's something I'm missing to get it working in the ticket "Edit" screen. Anyone have any suggestions?
I think that simple JS validation in the Description field is really helpful for people unfamiliar with Groovy (Script Runner), but I'm surprised how little I'm finding on it.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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