Create issue button form on 'backend' vs on portal

Yatish Madhav
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
October 10, 2021

Hi

Apologies in advance if this has been asked elsewhere.

 I have noticed that if we created a service desk request type and set the screen fields  and configure them with some required fields and if users that are agents created an issue on the 'backend' using the Create button and not use the portal view, they can create the issue without filling out all the required fields? 

Please advise on how we can resolve this and ensure fields that are required are required on both the portal view AND the backend/agent view

Thank you
Yatish

2 answers

0 votes
G Ca
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 4, 2023

Fabform is a good [form backend service](https://fabform.io) to take a look at

0 votes
Walter Buggenhout
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
October 10, 2021

Hi @Yatish Madhav,

If you want the same restrictions to apply on both the portal and on the issue create screens in Jira, you will have to configure required fields in both places.

In the portal, when you configure your request types, you have the option to mark every field on your form as either required or optional. From your question, it seems that you have already done that.

To apply the same logic when you create issues from the create button in Jira, the recommended option is to add a required fields validator to the create transition of the workflow that is associated to the issue type you are creating. In that validator, list all the fields that you also made required on the request forms. With that, you should be good to go.

If your customer portal makes use of multiple issue types, you'll have to set this up for all your associated workflows.

Hope this helps!

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PERMISSIONS LEVEL
Product Admin
TAGS
AUG Leaders

Atlassian Community Events