Field Configurations page under Project Settings currently lets users customize fields that they want to hide from Cases/Sets/Cycles screen as well as choose which fields should be mandatory in those screens.
This article shows steps to enable/disable fields and steps to mark them as mandatory. Users can also define which Custom fields should be mandatory, click here for details.
Accessing Field Configurations
Click on the cog icon and select Project Settings and then select Field configurations as shown below.
Field Configurations page
The page is divided into 3 groups - Cases, Sets and Cycles. Each group shows the list of fields that are available for enabling/disabling and marking as mandatory/non-mandatory. Next to each field are two check-boxes
Enabled: If checked, the field is visible across the app. If unchecked, field will not be visible in respective create and edit screens, in filters and column selector and in respective right hand panels (RHSPs)
Required: If checked, users will need to add data to the field while creating, editing, bulk editing, etc. the respective entity.
If the case/cycle is being created from Jira panel and mandatory fields have been defined, users will be prompted to add additional details in a pop-up screen
While quick executing a case from Jira panel, if users choose to add the case to a new cycle and mandatory fields have been defined, users will be asked to create a cycle first and then execute the case in the newly created cycle
By default, all fields are enabled and none of the fields are mandatory.
As of now, for the below scenarios, even if fields are marked as mandatory, cases will be allowed to be created
importing cases using Excel, CSV, Feature files
copying cases from one project to another
creating cases via import of automation results (from app as well as from REST APIs)