Remove a required field when creating issue

[Danny Teok]

Hi

I think I may have introduced a validator into our current workflow where when we create a new issue for Bug (Issue Type), it is mandatory to have an Approvers (custom field) named. Weeks have passed and I have forgotten how to undo this as the team did not like this.

However, for Story and Task Issue Type create new issue, we should have the field Approvers there. Just not for Bug. How should I remove this, please?

[Jack Brickey · Accepted solution]

First let’s check if you have a single workflow by going to project settings > workflows. If you only have one workflow then you should make a copy and rename so it is differentiated from the original. This will allow you to have a unique treatment for bugs. Then edit the new workflow under the Inactive list of workflows - Jira settings > Issues > Workflows. You will want to click on the Create transition and select Validator link. Find the Validator that requires the field, open and ensure it is the “Approver” field then remove it. Go back to your project workflow and add new workflow and choose the one you copied/edited. Associate to the Bug issuetype.

[Joe Pitt]

as @Jack Brickey said, if you did it in the workflow you need to have a different workflow. Required fields at creation time can be controlled in field configuration schemes which make requiring different fields required for different issue types easy. 

Can I have Different Required Fields for Different Issue Types?

Yes, as long as it is a different issue type. Required fields, at creation time are controlled by the field configuration scheme. That scheme is composed of one or more field configurations. Every issue type can have its own field configuration inside the field configuration scheme. If you have 5 issue types and 1 has special needs you create a field configuration for the 4 issue types and another for the 1 issue type. Then you combine them into a field configuration scheme and apply that to the project. When an issue is created, it looks for a field configuration for that issue type and uses it. If it doesn't find one it uses the default in the configuration scheme.  Copy/paste this link for more information. https://confluence.atlassian.com/adminjiracloud/configuring-a-field-configuration-scheme-844500805.html