Dont want Sprint field mandatory for 1 project

[SUVARNA Dixit]

Dont want Sprint field mandatory for 1 project

[Trudy Claspill · Accepted solution]

Hello @SUVARNA Dixit @suvarna dixit 

As you noted, in the Field Configuration the Sprint field is locked and cannot be set to Required.

That means it likely has been set to Required through a Workflow Transition Validator and/or a Workflow Transition Condition.

Is the project a Company Managed project or a Team Managed project?

If it is a Company Managed project, the Workflow transitions will need to be examine to find where the transitions include a Validator or Condition that is requiring the Sprint field to be filled in, and that will have to be removed. If the Workflow is used in multiple Workflow Schemes that are used by other projects, or if the Workflow Scheme for the one project is used by other projects, then you will have to take extra steps to create a copy of the workflow to modify, and potentially create a new Workflow Scheme for this one project.

[suvarna dixit]

It's company managed ..yes trying to put validator. Created a separate workflow 

[Trudy Claspill]

You shouldn't be adding a Validator. That would make the field required. It is more likely that you need to remove a Validator.

Let us know if you have additional questions. 

[Dave Mathijs]

Hi @SUVARNA Dixit 

Fields are set required/optional via a Field Configuration Scheme. If you want a specific project to have the 'Sprint' field set as optional instead of required, then you'll need to create a specific field configuration scheme.

For more info, please read: Configure a field configuration scheme

[suvarna dixit]

That field is locked or otherwise are u suggesting to create diff scheme and field