SET MANDATORY FIELDS WHEN CREATING AN ISSUE

[-Ibai Nicolás de Pedro]

Whenever an issue is created there are some fields (mandatory and optional) to fill out.
How can i turn an optional field to mandatory.

[Hamza Chundrigar · Accepted solution]

Hi @-Ibai Nicolás de Pedro 

Welcome to the community!

You can modify/specify the field behaviour inside of the field configuration settings.

Note: you need to be a Jira Admin to do this – this is someone with Administer Jira Global Permission.

In order to make a field required or optional:

1. Select (⚙️) > Issues.
2. Under FIELDS, select Field Configurations to view all your field configurations.
3. Locate the field configuration of interest and click the Configure link to open the View Field Configuration page, which lists all system and custom fields in your Jira instance for that field configuration.
4. To make a field mandatory when used through Jira's user interface, click the Required link associated with that field. The text Required will appear next to the field's name. (Hidden fields cannot be set as required.

Check out this article for more details.

Alternatively, if you would like more granular means to control fields at the step or screen level at a (company-managed) project, instead of at the project level by the project's field configuration, you can also instead choose to set up a Workflow Field Required Validator.

This validator checks that the selected fields have a value as the issue transitions in a workflow (for example in your case, when an issue is created). If any of the specified required fields are empty, the issue does not transition and an error displays.

Assuming you’re a Jira Admin, you could implement this by:

• Select ⚙️ > Issues.
• Click Workflows.
• Select the workflow transition (i.e create transition) you want to change and click Edit.
• Click on the "Validators" tab
• Click the "Add Validator" link on the right
• Add for the validator called "Field Required Validator" and choose the specific field make required

Couple of things FYR: 

• Unlike requiring a field (by modifying/specifying field behaviour) on a create screen, no asterisk (*) symbol will display for a field required by a workflow. The end user will receive an error message however, if the field is not completed.
• Any changes made to a shared workflow will impact all the projects using it.

Hope that helps. Let me know if you have any further questions!

Regards,

Hamza

[-Ibai Nicolás de Pedro]

thanks a lot for the explanation and for your time