Atlassian ACP-610 Exam Questions

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]

The two functions that are needed to use in the JQL query to find all issues that were not completed in some past sprint, and that are now part of an active sprint are closedSprints() and openSprints(). The closedSprints() function returns all issues that are assigned to a completed sprint. The openSprints() function returns all issues that are assigned to an incomplete sprint. By combining these two functions with the NOT operator, we can filter out the issues that belong to both a completed sprint and an incomplete sprint, and only get the issues that were not completed in some past sprint, and that are now part of an active sprint. For example, the JQL query could be:

project = XYZ AND issuekey NOT IN (closedSprints() AND openSprints())

This query will return all issues in project XYZ that are not in both a closed sprint and an open sprint, meaning they are either in a closed sprint only or an open sprint only. Since we are looking for issues that are now part of an active sprint, we can assume they are in an open sprint only.Reference:Advanced search reference - JQL functions,Modifying closedSprints() to return previous two Sprints,JQL - Explanation of what closedSprints() does

The only field that can definitely be set by all project team members is Labels. Labels are a system field that can be edited by any user who has the Edit Issues permission in the project, regardless of the screen configuration. The other fields may or may not be editable by the project team members, depending on how they are configured in the screen scheme, field configuration scheme, and permission scheme of the project. For example, Attachment requires both the Edit Issues permission and the Create Attachments permission, Assignee requires both the Edit Issues permission and the Assignable User permission, Fix Version/s requires both the Edit Issues permission and the Resolve Issues permission, and Issue Type requires both the Edit Issues permission and a compatible issue type scheme. For more information on how to configure fields in Jira, seeConfiguring fields and screens.Reference:Configuring fields and screens

Two project roles that must be granted to view code commits in the DEV project are:

Developers

Administrators

According to the image you sent, the View Development Tools permission determines which users can see development information from tools such as Bitbucket, GitHub, FishEye, and Crucible. This permission is granted to the Project role (Developers) and the Project role (Administrators) in the DEV permission scheme. Therefore, users who are assigned to these roles will be able to view code commits in the DEV project.

The other options are not correct because:

Users do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Sprinters do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.

Managers do not have the View Development Tools permission in the DEV permission scheme, so they cannot see code commits in the DEV project.