ATLASSIAN Jira Administrator ACP-120 Question # 17 Topic 2 Discussion

The users need a field namedType of Bugto capture attributes about bugs, with the ability to manage the options themselves. The field should be a custom field (to allow naming itType of Bug) and support a predefined list of options that users can manage. TheCustom field of type Select List (single choice)(Option D) meets these needs, as it provides a dropdown list with manageable options for a single selection.

Explanation of the Correct Answer (Option D):

ASelect List (single choice)custom field allows users to choose one option from a predefined list (e.g., “UI Bug,” “Backend Bug”). As a custom field, it can be namedType of Bug, and project admins or Jira admins can manage the options (add, edit, or remove) in the field’s configuration. This field type is ideal for categorizing bugs with a single attribute, and the manageable options meet the requirement for users to control the list.

Exact Extract from Documentation:

Create a custom field

TheSelect List (single choice)field type provides a dropdown menu where users can select one option from a predefined list.

To create:

Go toSettings > Issues > Custom fields.

Create a new field and selectSelect List (single choice).

Name the field (e.g., Type of Bug) and define options.

Add the field to the project’s screens.Note: Admins can manage the options (add, edit, remove) in the field’s configuration.(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

Why This Fits: TheSelect List (single choice)custom field allows naming the fieldType of Bug, provides a single-selection dropdown, and lets users manage the options, perfectly meeting the requirements.

Why Other Options Are Incorrect:

Custom field of type Select List (multiple choices) (Option A):

ASelect List (multiple choices)custom field allows users to select multiple options from a predefined list. While it could be namedType of Bugand have manageable options, the requirement implies capturing a single attribute per bug (e.g., one type), making single-choice more appropriate than multiple-choice.

Extract from Documentation:

TheSelect List (multiple choices)field allows multiple selections. UseSelect List (single choice)for single-value categorization.

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

Custom field of type Labels (Option B):

ALabelscustom field allows users to enter free-text tags, which are not predefined and can lead to inconsistent values (e.g., “UI Bug,” “UIBug”). The requirement for users to manage options suggests a controlled list, not free-text entry, making this unsuitable.

Extract from Documentation:

TheLabelsfield type allows free-text tags. For a predefined list, useSelect List (single choice)orSelect List (multiple choices).

(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")

Labels system field (Option C):

TheLabelssystem field is a global field that allows free-text tags, similar to a custom Labels field. It cannot be renamed toType of Bug, and its options are not predefined or manageable in the same way as a select list. This does not meet the naming or option management requirements.

Extract from Documentation:

TheLabelssystem field cannot be renamed and allows free-text tags. Custom fields likeSelect Listare needed for specific names and controlled options.

(Source: Atlassian Support Documentation, "Manage fields in Jira Cloud")

Additional Notes:

Steps to configure:

Create aSelect List (single choice)custom field namedType of BuginSettings > Issues > Custom fields.

Define the options (e.g., “UI Bug,” “Backend Bug”).

Add the field to the project’s screens (Project settings > Screens).

Grant users permission to manage options (typically requiresJira adminorproject adminprivileges).

Configuring the custom field requiresJira administratorprivileges, but project admins can manage options if granted access.

The field should be added to the issue layout for visibility in the issue view.