A team requests updates to the behavior of some fields in the project. The project uses three issue types: Problem, Incident, and Change.
The desired configuration is shown below:
Which configuration update will meet the requirements?
A team requests updates to the behavior of some fields in the project. The project uses three issue types: Problem, Incident, and Change.
The desired configuration is shown below:
Which configuration update will meet the requirements?
To meet the requirements specified for different issue types and fields, it is necessary to configure individual field configurations for each issue type. This approach allows customizing the visibility and requirement settings for each field based on the issue type. By configuring individual field configurations, you can ensure that the 'Severity' and 'Impact' fields are required for the 'Problem' and 'Incident' issue types, hidden for the 'Change' issue type, and that the 'Priority' field is shown and optional for the 'Incident' issue type, hidden for the 'Problem' issue type, and required for the 'Change' issue type.
The answers I chose were D
No field context for system fields