You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When a user tries to create an issue for the first time, error messages are displayed at the top of their window for each required field before they have had the chance to click create issue/submit. For example, (summary: You must specify a summary of the issue.)
I have verified that all screens have the correct fields (and no duplicates) and that they have been added to the correct screen scheme. I have also verified the required fields in field configurations. Lastly, I verified that the validators in the workflow have no effect on this issue.
After researching this issue, I have read that some community members have used scriptrunner and behaviours to validate the form before create issue/submit. I am new to Jira so any help would be greatly appreciated! @Nic Brough -Adaptavist- , you've provided a lot of answers/solutions to the posts that I have read. Perhaps you have a solution to this as well?
Welcome to the Atlassian Community!
These don't look like Scriptrunner errors, they look like your users are leaving fields blank and clicking create
For additional context, I believe that these validation errors come from custom HTML links. I've read https://confluence.atlassian.com/jirakb/how-to-create-issues-using-direct-html-links-in-jira-server-159474.html and am aware that is it is no longer supported. However, are there any existing features within behaviours or the JIRA REST API that could clear the validation errors when users click on these custom HTML links?
I've conducted some research on JIRA REST APIs but I am having a hard time implementing them in a way that would resolve this issue.