Required field error not easily visible when creating long requests

[Kaleeswari G]

All, 

I'm trying to get the visible alert on missing required fields to coming as alert while submitting a request on JSD customer portal without filling all the mandatory fields. But,  the current existing feature is about to show the errors nearby the field itself which is not aware of the customer to understand that the request is not being created for this field to be filled. 

Below are my tries which are not supposed to help me getting this alert:

• Tried adding helpText on field's behaviour (which will be loaded prior to the submission)
• Tried adding Simple script validator in a create transition of the workflow to make the field mandatory (which will be executed only after the successful submission of the create request form)
• Tried adding the Scriptrunner Listener for Create event (Which also works after a submission of the create request form)

Note: I have noticed the open ticket JSDSERVER-4060 for this already exists 

So, posting here to get an expert's solution or at least a workaround to handle this. 

Cheers, 

Kaleeswari G

[Anh Nguyen]

Hi @Kaleeswari G ,

Thanks so much for your question. As you noticed, there is already a ticket JSDSERVER-4060 to resolve the issue. Please refer to Atlassian Data Center and Server Bug Fix Policy for further information about how we triage and resolve bugs.

Thank you,

Anh Nguyen
Jira Service Management

ps. if this answer is correct, please select the ‘accept answer’ button

[Kaleeswari G]

Hi @Anh Nguyen 

Thanks for your response!

I could understand the policy that is being followed, But I'm looking for an alternate or a workaround to handle this. It would be helpful If you share any idea/suggestion that would work. 

Thanks & Regards, 

Kaleeswari G

[Anh Nguyen]

Hi @Kaleeswari G 

I appreciate a lot for having tried out different workarounds to this issue. At the moment, there is no available workaround that I can recommend but I will definitely response when the issue is fixed or when I find a good alternative workaround to handle this issue.

Thank you very much for your time.

Anh Nguyen
Jira Service Management