ATLASSIAN ACP-120 Dumps Questions Answers

To create an automation rule that triggers when a Story is updated, checks if it is unestimated (i.e., has no Story Points), and comments on its Sub-tasks, the rule requires aBranch rule on Sub-tasksto target the Sub-tasks and anIssue fields condition on whether Story Points is emptyto check the unestimated status. These two elements are essential to meet the rule’s requirements.

Explanation of the Correct Answers:

Branch rule on Sub-tasks (Option A):

The rule needs to comment on the Sub-tasks of the updated Story. ABranch ruleis used in Jira automation to perform actions on related issues, such as Sub-tasks. TheBranch rule on Sub-tasksallows the rule to iterate over each Sub-task of the Story and execute the comment action.

Exact Extract from Documentation:

Branch rule / related issues

A branch rule allows actions to be performed on issues related to the trigger issue, such as Sub-tasks, Epics, or linked issues.

To comment on Sub-tasks:

Add aBranch rule / related issuescomponent.

SelectSub-tasksas the related issue type.

Add aComment on issueaction within the branch to comment on each Sub-task.Note: The branch rule processes each related issue individually.(Source: Atlassian Support Documentation, "Jira automation actions")

Why This Fits: TheBranch rule on Sub-tasksis necessary to target the Sub-tasks of the Story and apply the comment action, satisfying the requirement to comment on Sub-tasks.

Issue fields condition on whether Story Points is empty (Option B):

The rule must check if the Story is unestimated, meaning theStory Pointsfield is empty (null or not set). TheIssue fields conditionallows checking the value of a field, such asStory Points, to ensure it meets a condition (e.g., is empty).

Exact Extract from Documentation:

Issue fields condition

TheIssue fields conditionchecks the value of an issue field against a specified criterion.

To check if Story Points is empty:

Add anIssue fields condition.

SelectStory Pointsas the field.

Set the condition tois empty.Note: This condition ensures the rule only proceeds if the field has no value.(Source: Atlassian Support Documentation, "Jira automation conditions")

Why This Fits: TheIssue fields condition on whether Story Points isemptyensures the rule only comments on Sub-tasks if the Story is unestimated, satisfying the condition requirement.

Why Other Options Are Incorrect:

Related issues condition on Issues in the sprint (Option C):

ARelated issues conditionchecks if related issues (e.g., Sub-tasks, Epics) meet certain criteria. The requirement does not involve checking the sprint status of issues, only that the Story is unestimated and comments are added to Sub-tasks. This condition is irrelevant to the rule.

Extract from Documentation:

TheRelated issues conditionchecks if related issues meet a condition (e.g., all Sub-tasks are resolved). It is not needed for commenting on Sub-tasks without additional criteria.

(Source: Atlassian Support Documentation, "Jira automation conditions")

Branch rule on Stories (Option D):

ABranch rule on Storieswould target Stories, not Sub-tasks. Since the rule needs to comment on the Sub-tasks of the updated Story, a branch on Sub-tasks (Option A) is required, not Stories.

Extract from Documentation:

ABranch ruletargets specific related issues (e.g., Sub-tasks, Epics). Choose the correct issue type to match the action (e.g., Sub-tasks for commenting on Sub-tasks).

(Source: Atlassian Support Documentation, "Jira automation actions")

Additional Notes:

The complete rule would look like this:

Trigger: Issue Updated (filter to Story issue type).

Condition: Issue fields condition (Story Points is empty).

Action: Branch rule on Sub-tasks.

Action: Comment on issue (add the desired comment).

The rule assumes theStory Pointsfield is available and Sub-tasks exist for the Story.

The rule can be configured inProject settings > Automation(for project-level rules) orSettings > System > Automation rules(for global rules).

In a company-managed project with issue-level security configured, theSecurity Leveldropdown field allows users to set the security level for an issue, restricting who can view it. If Andre only sees one security level instead of both, the most likely reason is that he lacks theSet Issue Securitypermission (Option C), which is required to view and select security levels in the dropdown.

Explanation of the Correct Answer (Option C):

TheSet Issue Securitypermission allows users to set or change the security level of an issue. Without this permission, a user may not see all available security levels in theSecurity Leveldropdown, or the field may be hidden or restricted. If Andre lacks this permission, he might only see the default security level (if set) or no options at all, depending on the configuration.

Exact Extract from Documentation:

Set Issue Security permission

TheSet Issue Securitypermission allows users to set or change the security level of an issue, which determines who can view it. Without this permission, users cannot modify theSecurity Levelfield or may only see a subset of available levels.

To check this permission:

Go toProject settings > Permissions.

Verify which users, groups, or roles have theSet Issue Securitypermission.Note: The visibility of security levels in the dropdown also depends on the user’s membership in groups or roles defined in the security levels.(Source: Atlassian Support Documentation, "Configure issue security schemes")

Why This Fits: TheSet Issue Securitypermission is directly responsible for allowing users to interact with theSecurity Levelfield. If Andre lacks this permission, he may not see both security levels, making Option C a likely reason.

Why Other Options Are Incorrect:

The other level is configured for different issue types (Option A):

Issue security levels are not tied to specific issue types; they apply to all issues in a project under the issue security scheme. The configuration of security levels is project-wide, so this is not a valid reason.

Extract from Documentation:

Issue security levels apply to all issue types in a project using the same issue security scheme. They are not restricted by issue type.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

Andre is not in a group or project role (Option B):

While security levels may restrict visibility based on groups or project roles, the question is about Andre’s ability to see security levels in the dropdown, not about viewing issues. TheSet Issue Securitypermission determines whether Andre can see and select levels, not his membership in groups or roles for visibility purposes.

Extract from Documentation:

Security levels define who can view issues (e.g., users in a group or role). TheSet Issue Securitypermission controls who can set the level, not who can view the issue.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

The other level is marked as the default (Option D):

Marking a security level as the default ensures it is automatically applied to new issues if no level is specified. However, this does not prevent other levels from appearing in theSecurity Leveldropdown for users with theSet Issue Securitypermission.

Extract from Documentation:

The default security level is applied to new issues if no level is set. All available levels are shown in theSecurity Leveldropdown to users with theSet Issue Securitypermission.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

Andre does not have Edit Issues permission (Option E):

TheEdit Issuespermission allows users to modify issue fields, but theSecurity Levelfield is specifically controlled by theSet Issue Securitypermission. A user can haveEdit Issuespermission but still not see security levels if they lackSet Issue Security.

Extract from Documentation:

TheSet Issue Securitypermission is separate fromEdit Issuesand specifically controls access to theSecurity Levelfield.

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

Additional Notes:

Another possible reason (not listed) could be that Andre is not in the groups or roles defined for the second security level, limiting its visibility in the dropdown. However, theSet Issue Securitypermission is the most direct cause listed.

To resolve the issue, check Andre’s permissions inProject settings > Permissionsand ensure he hasSet Issue Security.

To create projects in Jira Software Cloud without having full Jira administrator privileges, George needs a specificglobal permission, namely theCreate Projectspermission. This permission allows users to create new projects without granting them broader administrative access.

Explanation of the Correct Answer (Option D):

TheCreate Projectsglobal permission enables a user to create new projects in Jira. This permission is distinct from Jira administrator privileges, which include managing global settings like schemes, users, and workflows. By granting George this permission, he can create projects while maintaining a limited scope of authority.

Exact Extract from Documentation:

Global permissions

Global permissions control access to system-wide actions in Jira. TheCreate Projectspermissionallows users to create new projects without requiring full Jira administrator privileges.

To grant this permission:

Go toSettings > System > Global permissions.

Add a user, group, or role to theCreate Projectspermission.Note: Users with this permission can create projects but cannot modify global configurations like schemes or user management unless they have additional permissions.(Source: Atlassian Support Documentation, "Manage global permissions")

Why This Fits: TheCreate Projectsglobal permission directly addresses the requirement for George to create projects without needing Jira administrator privileges, making Option D the correct choice.

Why Other Options Are Incorrect:

Project role (Option A):

Project roles (e.g., Administrator, Developer) are used within a project’s permission scheme to grant project-specific permissions, such asAdminister ProjectsorBrowse Projects. They do not control the ability to create new projects, which is a system-level action.

Extract from Documentation:

Project roles are used in permission schemes to grant permissions within a specific project. They do not apply to global actions like creating projects.

(Source: Atlassian Support Documentation, "Manage project roles")

Product access (Option B):

Product access determines whether a user can use Jira Software or other Atlassian products. While George needs product access to use Jira, this does not grant the specific ability to create projects.

Extract from Documentation:

Product access allows users to log in and use Jira products. Specific actions, like creating projects, require global or project permissions.

(Source: Atlassian Support Documentation, "Manage product access")

Project permission (Option C):

Project permissions (e.g.,Administer Projects,Browse Projects) are defined in a project’s permission scheme and apply to actions within a specific project. Creating a project is a global action, not tied to any existing project’s permission scheme.

Extract from Documentation:

Project permissions control actions within a project, such as editing issues or managing components. Global permissions control system-wide actions like creating projects.

(Source: Atlassian Support Documentation, "Manage project permissions")

Product role (Option E):

Product roles (e.g., Jira Software User, Jira Service Management Agent) define access to specific Atlassian products but do not grant permissions for actions like creating projects. This is not relevant to the requirement.

Extract from Documentation:

Product roles determine access to Atlassian products and are not related to specific permissions like creating projects.

(Source: Atlassian Support Documentation, "Manage product roles")

Additional Notes:

TheCreate Projectspermission can be granted to George via a group or directly to his user account inSettings > System > Global permissions.

As a project lead, George likely already has project-level permissions (e.g.,Administer Projectsfor his projects), but these do not extend to creating new projects.