Atlassian ACP-610 Practice Test - Questions Answers, Page 6

The component configuration of the project shows that each component has a different default assignee. The default assignee is the user who will be automatically assigned to an issue when that component is selected.

The image shows that the default assignee for the Signoff component is Project admin. Therefore, if Dave creates an issue and selects Signoff as the component, the issue will be assigned to Project admin.

The other options are not correct because:

If UX is selected, the issue will not be assigned to admin, but to Unassigned. The image shows that the default assignee for the UX component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

If Login and Signoff are selected, the issue will not be assigned to Project admin, but to Project lead. The image shows that the default assignee for multiple components is Project lead, which means that if more than one component is selected, the issue will be assigned to Project lead.

If Test is selected, the issue will not be assigned to Project lead, but to Unassigned. The image shows that the default assignee for the Test component is Unassigned, which means that no user will be automatically assigned to an issue with that component.

A select list (single choice) field meets the requirements because it allows different options in different projects, allows options to be disabled where necessary, allows only a single value, and allows a default value to be configured. A select list (single choice) field is a custom field that lets the user select one option from a list of predefined values. The values can be different for each project and can be enabled or disabled as needed.The field can also have a default value that is automatically selected when creating an issue12Reference:

1: What are custom fields? | Jira Software Cloud | Atlassian Support

2: Configuring a custom field | Jira Software Cloud | Atlassian Support

Based on the current configuration, the assignee field will show Mac Taylor after creating the test issue. This is because the Macbook 13' component has Mac Taylor as the component lead and the component/s field has been configured to override the project's default assignee when using a certain component.Therefore, when creating an issue with the Macbook 13' component, the assignee field will automatically be set to Mac Taylor, regardless of the default assignee of the project or the value of the assignee field before creating the issue34Reference:

3: What are components? | Jira Software Cloud | Atlassian Support

4: How to enable and edit component/s , affects Version/s and fix version ...

The label field meets the team's requirements for flagging issues using a category. Labels are a type of custom field that allow users to add one or more descriptive tags to issues. Users can add new labels on the fly, and select existing labels from a dropdown menu. Labels can be re-used across all projects, and can be searched and filtered easily. A text field does not allow multiple values or a dropdown menu. A component does not allow multiple values or adding new values by any user. A user picker does not allow multiple values or adding new values by any user. Checkboxes do not allow adding new values by any user.Reference:[Adding, removing and searching for labels], [Managing Jira Projects Data Center and Server: Certification Bundle]

Jira administrators can create and update global priorities, which are the default set of priorities available in each project. Project administrators cannot re-order, create, or update priorities in their projects, unless they have Jira administrator access. The same set of priorities is not always available in each project, as Jira administrators can configure priority schemes to assign different priorities to different projects.Reference:[Configuring priorities], [Managing Jira Projects Data Center and Server: Certification Bundle]

Jon needs Move Issues and Create Issues permissions to move an issue from project A to project B. Move Issues permission allows him to initiate the move operation, while Create Issues permission allows him to create the issue in the destination project. Transition Issues permission is not relevant for moving issues, as it only affects workflow transitions. Administer Projects permission is not required for moving issues, unless the issue type or workflow needs to be changed during the move. Assign Issues permission is not required for moving issues, unless the assignee needs to be changed during the move.Reference:[Moving an issue], [Managing Jira Projects Data Center and Server: Certification Bundle]

Epics are moved automatically but epic links are lost when stories are moved to another project using a bulk operation. This is because epics are a type of issue, and issues can be moved across projects. However, epic links are a type of issue link, and issue links cannot be moved across projects. Therefore, the stories will lose their epic links after the move, and the epics will remain in the original project.Reference:[Moving multiple issues], [Managing Jira Projects Data Center and Server: Certification Bundle]

Three versions will be available in the versions panel of the project backlog: epsilon, delta, and gamma. These are the three unreleased versions in the project, as shown in the image. The versions panel only shows unreleased versions, as they are used to plan and track the progress of upcoming releases. Released and archived versions are not shown in the versions panel, as they are considered completed and no longer relevant for planning purposes.Reference:[Working with versions], [Managing Jira Projects Data Center and Server: Certification Bundle]

The best course of action is to restore the project, then the sub-tasks. This is because sub-tasks cannot exist without their parent issues, and parent issues cannot exist without their project. Therefore, restoring the project first will ensure that the parent issues are also restored, and then restoring the sub-tasks will re-attach them to their parent issues. Restoring the parent issues only will not restore the sub-tasks, as they are still archived. Restoring the project only will not restore the sub-tasks, as they need to be restored separately. Restoring the parent issues, then the sub-tasks will not work, as the parent issues cannot be restored without their project. Restoring the project, then the parent issues is unnecessary, as the parent issues are already restored with the project.Reference:[Restoring an archived issue], [Managing Jira Projects Data Center and Server: Certification Bundle]