(PDF) Jira Administrator ACP-120 Exam and Certification Test Engine
Use ACP-120 Exam Dumps (2026 PDF Dumps) To Have Reliable ACP-120 Test Engine
The Atlassian ACP-120 (Jira Cloud Administrator) Certification Exam is a valuable certification for professionals who work with Jira Cloud on a daily basis. It demonstrates the candidate's expertise in administering and managing Jira Cloud instances and validates their skills in implementing best practices for improving the performance and stability of Jira Cloud. Jira Cloud Administrator certification can help professionals enhance their career prospects, gain recognition in the industry, and differentiate themselves from peers.
ATLASSIAN ACP-120 (Jira Cloud Administrator) Exam is an online exam that consists of 60 multiple-choice questions. Candidates have 90 minutes to complete the exam, and a passing score of 65% or higher is required to earn certification. ACP-120 exam covers a wide range of topics related to Jira Cloud administration, including user management, project management, issue management, and system administration.
NEW QUESTION # 31
Max wants you to change the way the system fields Created or Updated are being displayed when viewing an issue.
How can this be achieved?
- A. Adjust the jira.date.time.picker.java.format in the advanced settings configuration.
- B. Adjust the jira.date.picker.java.format in the advanced settings configuration.
- C. Adjust the language and time zone preferences in Max's user profile.
- D. Adjust the Day Format in the Jira look and Feel configuration.
- E. Adjust the Complete Date/Time Format in the Jira Look and Feel configuration.
Answer: C
Explanation:
Reference: https://virginpulse.zendesk.com/hc/en-us/articles/206180140-The-time-on-my-Max-is-wrong-
NEW QUESTION # 32
A team complains that many of their issues are in the Closed status, but do not have a resolution set, which causes problems with reporting. The project uses a single workflow.
You want to set the resolution to Done on all existing issues in the Closed status.
Which combination of workflow elements and a bulk operation will achieve this?
- A. - A temporary transition and a trigger
- An Edit Issues bulk operation - B. - A screen and a custom field
- An Edit Issues bulk operation - C. - A screen and the Resolution field
- A Move Issues bulk operation - D. - A temporary transition and a post function
- A Transition Issues bulk operation - E. - A temporary transition and a screen
- An Edit Issues bulk operation
Answer: A
NEW QUESTION # 33
Two users have access to the same filter and see the same issues in a company-managed project. One of them can perform a bulk operation to watch issues in the filter, but the other user cannot. What should you investigate?
- A. Project roles
- B. Product access
- C. Groups
- D. Default user preferences
- E. Project permissions
Answer: E
Explanation:
The scenario describes two users who can view the same issues in a filter (indicating they have theBrowse Projectspermission), but only one can perform a bulk operation towatchissues. The ability to watch issues is controlled by theView Issue WatchersandManage Watcher Listpermissions in the project's permission scheme. Therefore, you should investigateproject permissions(Option A).
* Explanation of the Correct Answer (Option A):
* Performing a bulk operation to watch issues requires theManage Watcher Listpermission, which allows users to add themselves or others as watchers to an issue. Since both users can see the issues (via the filter), they likely have theBrowse Projectspermission, but the user who cannot perform the bulk operation may lack theManage Watcher Listpermission.
* Exact Extract from Documentation:
Manage Watcher List permission
TheManage Watcher Listpermission allows users to add or remove watchers from an issue, including via bulk operations. This permission is granted via the project's permission scheme.
Note: To view the watcher list, users also need theView Issue Watcherspermission. Both permissions are required to perform actions like bulk watching issues.
To check permissions:
* Go toProject settings > Permissions.
* Review theManage Watcher ListandView Issue Watcherspermissions to see which users, groups, or roles have them.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: The difference in the users' ability to perform the bulk watch operation is most likely due to a difference in theirManage Watcher Listpermission, which is defined in the project's permission scheme. Investigating project permissions will reveal whether the second user lacks this permission.
* Why Other Options Are Incorrect:
* Product access (Option B):
* Product access determines whether users can use Jira Software. Both users can view the filter and issues, indicating they have product access. Product access does not control specific permissions like managing watchers.
* Extract from Documentation:
Manage product access
Product access grants users the ability to use Jira products. Specific actions, like managing watchers, are controlled by project or global permissions, not product access.
(Source: Atlassian Support Documentation, "Manage product access")
* Groups (Option C):
* Groups may be used in permission schemes to grant permissions, but the root cause is the permission itself, not the group membership. Investigating groups might be a secondary step after checking project permissions, butproject permissionsis the more direct answer.
* Extract from Documentation:
Groups are used in permission schemes to grant permissions to multiple users. To determine why a user lacks a permission, check the permission scheme first, then verify group membership if relevant.
(Source: Atlassian Support Documentation, "Manage groups")
* Default user preferences (Option D):
* Default user preferences (e.g., notification settings) control whether a user receives notifications for watched issues, not their ability to watch issues.The issue is about performing a bulk operation, not receiving notifications.
* Extract from Documentation:
Manage user preferences
Users can manage their notification preferences inPersonal settings > Email notifications. These settings affect notification delivery, not the ability to perform actions like watching issues.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails")
* Project roles (Option E):
* Project roles are used in permission schemes to grant permissions. Like groups, roles are a means to assign permissions, but the issue lies in the permission itself (Manage Watcher List). Investigating project permissions directly addresses the root cause.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions likeManage Watcher List. Check the permission scheme to identify the root cause of permission differences.
(Source: Atlassian Support Documentation, "Manage project roles")
* Additional Notes:
* Both users can see the filter and issues, so they likely have theBrowse Projectspermission. The difference in their ability to perform the bulk watch operation points to theManage Watcher List permission, which should be checked inProject settings > Permissions.
* If the permission is granted to a group or role, verify the users' membership in those groups or roles as a follow-up step.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage groups
Atlassian Support Documentation:Manage your Jira notification emails
Atlassian Support Documentation:Manage project roles
NEW QUESTION # 34
You are a site admin for your company.
Which function can you NOT perform? (Choose one)
- A. Enable invite links for your products
- B. Manage users and groups
- C. Enable Single Sign On for your Atlassian Cloud site(s)
- D. Deactivate a Cloud site
- E. Configure products in your Atlassian Cloud site(s)
Answer: C
NEW QUESTION # 35
Users have been adding sensitive information into the Description field of issues in a particular project. You must secure the project by any means necessary so that only members of the Managers group can view the contents of the Description field.
Which approach will definitively satisfy this requirement? (Choose one)
- A. Remove the description field from the screen used by the view operation
- B. Remove everyone from the browse projects permission
- C. Hide the description field in the field configuration
- D. Remove everyone except the managers group from every project role
- E. Remove everyone except the managers group from every project permission
Answer: A
NEW QUESTION # 36
Below are the requirements for two new fields to be used in a company-managed project:
* Allow a single option from a dropdown list of options.
* Allow bold and underlined text.
Identify the two field types you need to use. (Choose two.)
- A. Short text
- B. Checkboxes
- C. Paragraph
- D. Radio buttons
Answer: C,D
Explanation:
To meet the requirements for two new fields in a company-managed project, one field must allow selecting a single option from a dropdown list, and the other must allow bold and underlined text.The appropriate field types areRadio buttons(Option C) for the dropdown list andParagraph(Option B) for bold and underlined text.
* Explanation of the Correct Answers:
* Radio buttons (Option C):
* The requirement toallow a single option from a dropdown list of optionsis met by a Radio buttonscustom field. This field type presents a list of predefined options in a radio button format, allowing users to select exactly one option, similar to a dropdown list. In Jira, radio buttons are often used interchangeably withSelect List (single choice)for single- selection lists, and both fulfill the requirement.
* Exact Extract from Documentation:
Custom field types
TheRadio buttonsfield type allows users to select one option from a predefined list, presented as radio buttons.
To create:
* Go toSettings > Issues > Custom fields.
* Create a new field and selectRadio buttons.
* Define the list of options.Note: Radio buttons are similar toSelect List (single choice) and are used for single-selection dropdown-like functionality.(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Why This Fits: TheRadio buttonsfield type provides a single-selection list, meeting the requirement for a dropdown list of options.
* Paragraph (Option B):
* The requirement toallow bold and underlined textis met by aParagraphcustom field (also known asText Field (multi-line)). This field type supports rich text input, including formatting options like bold and underlined text, using a WYSIWYG editor or wiki-style markup.
* Exact Extract from Documentation:
Custom field types
TheParagraph(orText Field (multi-line)) field type allows users to enter multiple lines of text with rich text formatting, including bold, underline, and other styles.
To create:
* Go toSettings > Issues > Custom fields.
* Create a new field and selectParagraph.Note: The rich text editor supports formatting like bold and underline, or users can use wiki-style markup (e.g.,bold, underline).(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Why This Fits: TheParagraphfield supports rich text formatting, including bold and underlined text, meeting the second requirement.
* Why Other Options Are Incorrect:
* Short text (Option A):
* AShort text(orText Field (single line)) custom field allows single-line text input but does not support rich text formatting like bold or underlined text. It is unsuitable for the second requirement and does not provide a dropdown list for the first requirement.
* Extract from Documentation:
TheShort textfield type is for single-line plain text and does not support rich text formatting like bold or underline.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Checkboxes (Option D):
* ACheckboxescustom field allows users to select multiple options from a predefined list.
The first requirement specifies asingle option, making checkboxes unsuitable, as they are designed for multiple selections.
* Extract from Documentation:
TheCheckboxesfield type allows multiple selections from a list. For single-selection lists, useRadio buttonsor Select List (single choice).
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Create aRadio buttonscustom field inSettings > Issues > Custom fields, name it appropriately, and define the options.
* Create aParagraphcustom field inSettings > Issues > Custom fieldsfor rich text input.
* Add both fields to the project's screens (Project settings > Screens).
* Configuring custom fields requiresJira administratorprivileges.
* TheRadio buttonsfield may display as a dropdown-like list in some interfaces, aligning with the requirement.
:
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screens in Jira Cloud
NEW QUESTION # 37
No one should be allowed to edit issues in a particular workflow status of a company-managedproject. Which element must be configured?
- A. Condition
- B. Status Property
- C. Trigger
- D. Post function
Answer: B
Explanation:
Okay, let's analyze this question again with the revised options.
The requirement is to preventanyonefromeditingan issue when it resides in aspecific workflow status.
As established previously:
* Conditions (A):Control whether atransitionout of or into a status can occur. They check criteriabeforea transition starts. They don't prevent editingwhilean issue is sitting in a status.
* Post Functions (Implied by B & C):Actions that executeaftera transition is successfully completed (e.
g., updating a field, sending a notification). They don't affect editability within the status itself.
* Triggers (D):Automatically initiate a workflow transition based on external events (like code commits). Not relevant to editing permissions within a status.
The correct way to achieve this in Jira is by setting aStatus Property:
* Navigate to Workflow configuration.
* Select the relevant status.
* Go to its 'Properties'.
* Add a property: jira.issue.editable with the value false.
NEW QUESTION # 38
Which three statements are correct about deleting a user account (Choose three)
- A. Organization admins can delete managed accounts
- B. Issues that were created by a deleted account will be deleted
- C. Individual users can delete their unmanaged accounts
- D. Accounts can only be deleted if they have no issues assigned
- E. Access to all products and administration functions will be lost
Answer: A,C,E
NEW QUESTION # 39
Your Jira has 25,000 active users across the globe using 100 projects with over a million issues.
Another administrator has made a change to a field configuration scheme and you now need to re-index Jira.
What would be the impact of rebuilding the index in the foreground?
- A. Issues will take longer to display during the re-index.
- B. The configuration change will not be applied until re-indexing is complete.
- C. Searches using the field may show erroneous results.
- D. Database backups cannot be run until the re-indexing is complete.
- E. All users will be locked out of Jira until re-indexing completes.
Answer: B
NEW QUESTION # 40
Your marketing company wants to evaluate Jira and purchased a 10-user license. A frequently changing group of key stakeholders - both internal employees and external customers - will participate in the evaluation.
If the evaluation is successful the company wants all 50 employees to start working with the tool.
You have to manage the frequently changing group of stakeholders and need to make sure only the intended users participate in the evaluation.
How should you meet these requirements?
- A. Create and manage the users for stakeholders manually in the internal directory.
- B. Enable public signup and CAPTCHA but limit account creation to stakeholders.
- C. Disable public signup and grant all project permissions to Group Anyone.
- D. Connect Jira to your internal LDAP directory and whitelist the IPs of stakeholders.
Answer: C
NEW QUESTION # 41
Your administration project is configured as follows:
- there are three issue types that all share a single workflow
- all project users are members of the Project Users project role
- all members of the Administrators project role have the Set Issue Security permission
- project administrators are the only users who can create issues
You are tasked with replacing the Project Users project role with three distinct team project roles, each solely responsible for one of the issue types.
Which additional requirement can be met by individual workflows per issue type?
- A. Individual notifications should be sent out depending on the selected issue type.
- B. The reporter and current assignee of each issue should always have access to view it.
- C. Each issue type needs a dedicated set of individual project components.
- D. Only members of the dedicated teams should be able to view and work on the issues they are responsible for.
- E. The system field Component/s needs to be required when creating two out of the three existing issue types.
Answer: B
NEW QUESTION # 42
A new user needs access to all applications of your Atlassian Cloud site to configure projects without consuming any user licenses.
Select two items which, when combined, will satisfy this requirement? (Choose two)
- A. Individual users
- B. Product access
- C. Administration access
- D. User groups
- E. Site access
- F. Trusted user role
Answer: C,E
NEW QUESTION # 43
You are the project administrator in a team-managed project and a company-managed project. You have no other administrative privileges. Identify the action you definitely cannot perform in a company-managed project.
- A. Create automation rules.
- B. Restrict who can see certain issues.
- C. Restrict who can use workflow transitions.
- D. Manage project access.
- E. Manage notifications and recipients.
Answer: C
Explanation:
As a project administrator in a company-managed project with no other administrative privileges (e.g., Jira admin or system admin), your permissions are limited to specific project-level settings defined by the permission schemeand other configurations. The action youdefinitely cannot performin a company- managed project isrestrict who can use workflow transitions(Option B), as this requires editing the workflow, which is a Jira admin privilege.
* Explanation of the Correct Answer (Option B):
* Restricting who can use workflow transitions involves addingconditionsto transitions in a workflow (e.g., restricting a transition to specific users, roles, or groups). In company-managed projects, workflows are managed at the system level, and editing them requiresJira admin permissions. Project admins cannot modify workflows or their conditions.
* Exact Extract from Documentation:
Edit workflows in company-managed projects
Workflows define the statuses and transitions for issues in a project. To edit a workflow (e.g., add conditions, validators, or post functions):
* Go toSettings > Issues > Workflows.
* Select the workflow and make changes.Note: Only Jira administrators can edit workflows.
Project administrators can view the workflow inProject settings > Workflowsbut cannot modify it. To restrict transitions, add conditions like "Only users in a specific role" or
"Only the assignee."(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: As a project admin in a company-managed project, you lack the permission to edit workflows, including adding conditions to restrict who can use transitions. This makes Option B the action you definitely cannot perform.
* Why Other Options Are Incorrect:
* Restrict who can see certain issues (Option A):
* Project admins in company-managed projects can restrict who can see issues by configuring issue security levels(if an issue security scheme is assigned to the project). They can manage security levels inProject settings > Issue securityand assign users, roles, or groups to specific levels.
* Extract from Documentation:
Configure issue security
Issue security levels restrict who can view issues. Project administrators can manage security levelsinProject settings > Issue security, provided an issue security scheme is assigned to the project.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Manage project access (Option C):
* Project admins can manage project access by adding or removing users, groups, or roles in Project settings > People. This controls who has access to the project based on the permission scheme'sBrowse Projectspermission.
* Extract from Documentation:
Manage project access
Project administrators can add or remove users, groups, or roles inProject settings > Peopleto control project access, as defined by the permission scheme.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Manage notifications and recipients (Option D):
* Project admins can manage notifications by configuring thenotification schemeinProject settings > Notifications(if permitted by the permission scheme). They can add or remove recipients for events, such as users, roles, or groups.
* Extract from Documentation:
Configure notifications
Project administrators can edit the notification scheme inProject settings > Notificationsto define who receives notifications for specific events, provided they have theAdminister Projectspermission.
(Source: Atlassian Support Documentation, "Configure notification schemes")
* Create automation rules (Option E):
* Project admins can createproject-level automation rulesin company-managed projects usingProject settings > Automation. These rules are limited to the project and do not require Jira admin permissions.
* Extract from Documentation:
Create automation rules
Project administrators can create automation rules inProject settings > Automationto automate tasks within their project. Global automation rules require Jira admin permissions, but project-level rules do not.
(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")
* Additional Notes:
* Inteam-managed projects, project admins have broader control, including the ability to configure workflows and restrict transitions, as workflows are project-specific. However, the question specifies acompany-managed project, where workflow management is restricted to Jira admins.
* TheAdminister Projectspermission (granted to project admins) allows managing most project settings, but workflow editing is a system-level task requiring higher privileges.
:
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Configure notification schemes
Atlassian Support Documentation:Automate your Jira Cloud instance
NEW QUESTION # 44
You have a project with several issue types, associated unique workflows, and a number of components.
The decision has been made to have all new issues assigned automatically.
To that end, you've set default assignee(s) for the project lead, component leads, and removed the Assignee field from the screens associated with the Create Issue operation.
One of the issue types is still being created without an Assignee.
What is the most likely cause of the problem?
- A. The assignee is being set to Unassigned in the first post-function of the create transition.
- B. The default assignee for the issues' component is still set to Unassigned.
- C. Users creating this issue type do not have the Assign Issue permission.
- D. The post function Assign to Lead Developer is missing in the create transition.
- E. The issue type's field configuration for Component/s is not set to Required.
Answer: A
NEW QUESTION # 45
Your Jira cloud instance has hundreds of projects which are used only by the development team at your organization.
All projects share a single permission scheme New business requirements state:
* Customer support staff at your organization need to view all issues in all projects
* They also need to share filters with other users
* They should not be granted too much access
Identify the appropriate way to configure customer support staff in Jira (Choose one)
- A. With the Trusted role
- B. As a new group
- C. As a security level
- D. As a new project role
- E. With an approved domain
Answer: B
NEW QUESTION # 46
Boris is reviewing his assigned issues. He wants to move them from the backlog into a planned sprint so he can work on them. Which two permissions does he need? (Choose two.)
- A. Move Issues
- B. Manage Sprints
- C. Work On Issues
- D. Assignable User
- E. Schedule Issues
- F. Edit Issues
Answer: E,F
Explanation:
To move issues from the backlog to a planned sprint in a Jira Software Cloud project, Boris needs permissions to modify the issue's sprint field and edit the issue itself. The two permissions required areSchedule Issues (Option B) andEdit Issues(Option D).
* Explanation of the Correct Answers:
* Schedule Issues (Option B):
* TheSchedule Issuespermission allows a user to add issues to a sprint, remove issues from a sprint, or move issues between sprints. This permission is necessary to move issues from the backlog (which is not part of a sprint) into a planned sprint.
* Exact Extract from Documentation:
Schedule Issues permission
TheSchedule Issuespermission allows users to:
* Add issues to a sprint.
* Remove issues from a sprint.
* Move issues between sprints or to the backlog.This permission is required to manage the sprint field in issues, such as moving an issue from the backlog to a planned sprint.Note: This permission is granted via the project's permission scheme.(Source:
Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: Moving an issue to a planned sprint involves updating theSprintfield, which requires theSchedule Issuespermission.
* Edit Issues (Option D):
* TheEdit Issuespermission allows a user to modify issue fields, including theSprintfield.
Without this permission, Boris cannot edit the issue to set its sprint, even if he has the Schedule Issuespermission.
* Exact Extract from Documentation:
Edit Issues permission
TheEdit Issuespermission allows users to modify issue fields, such as Summary, Description, or Sprint. This permission is required to update an issue's details, including moving it to a sprint if combined with the Schedule Issuespermission.
Note: This permission is granted via the project's permission scheme.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: Editing theSprintfield to move an issue into a planned sprint requires the Edit Issuespermission, as it involves modifying the issue's metadata.
* Why Other Options Are Incorrect:
* Work On Issues (Option A):
* TheWork On Issuespermission allows users to log work on issues (e.g., record time spent). It is not related to moving issues to a sprint or editing issue fields.
* Extract from Documentation:
Work On Issues permission
Allows users to log work on issues using the time tracking feature. This does not include editing issue fields or managing sprints.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Move Issues (Option C):
* TheMove Issuespermission allows users to move issues between projects or change their issue type within the same project. Moving an issue to a sprint does not involve changing its project or issue type, so this permission is not required.
* Extract from Documentation:
Move Issues permission
Allows users to move issues to a different project or change their issue type. This is not required for moving issues to a sprint within the same project.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Manage Sprints (Option E):
* TheManage Sprintspermission allows users to create, start, complete, or delete sprints.
While this permission is necessary for managing the sprint itself, it is not required to move issues into a planned sprint, as Boris is not creating or modifying the sprint.
* Extract from Documentation:
Manage Sprints permission
Allows users to create, start, complete, or delete sprints. Moving issues to an existing sprint requires the Schedule IssuesandEdit Issuespermissions, notManage Sprints.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Assignable User (Option F):
* TheAssignable Userpermission allows a user to be assigned to issues (i.e., set as the Assignee). It does not affect the ability to move issues to a sprint.
* Extract from Documentation:
Assignable User permission
Allows users to be set as the assignee of an issue. This does not include editing other fields like the Sprint field.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* Boris likely already has theBrowse Projectspermission, as he can review his assigned issues. The Schedule IssuesandEdit Issuespermissions are specifically required for the action of moving issues to a sprint.
* These permissions are granted via the project's permission scheme, which can be checked in Project settings > Permissions.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage sprints in company-managed projects
NEW QUESTION # 47
Your team creates issues directly in the Kanban board of a company-managed project. You must ensure that all their newly created issues are not left unassigned. Which entry must you select in the project's Default Assignee dropdown?
- A. Board administrator
- B. Component lead
- C. Project admin
- D. Project lead
- E. Reporter
Answer: D
Explanation:
To ensure that newly created issues in a company-managed project's Kanban board are not left unassigned, you must configure theDefault Assigneesetting in the project's settings. TheProject lead(Option B) is a valid and appropriate choice, as it assigns new issues to the project's designated lead by default.
* Explanation of the Correct Answer (Option B):
* In a company-managed project, theDefault Assigneesetting determines who is automatically assigned to new issues when no assignee is specified during creation (e.g., when creating issues directly on a Kanban board). TheProject leadis a predefined user set in the project's settings and can be selected as the default assignee to ensure issues are not left unassigned.
* By selectingProject leadin theDefault Assigneedropdown, all new issues created in the project, including those created on the Kanban board, will be automatically assigned to the project lead, meeting the requirement.
* Exact Extract from Documentation:
Configure the default assignee
TheDefault Assigneesetting in a company-managed project determines who is assigned to new issues when no assignee is specified.
Options include:
* Project lead: Assigns issues to the user designated as the project lead.
* Unassigned: Leaves issues unassigned (if allowed by the project's permission scheme).To configure:
* Go toProject settings > Details.
* SelectProject leadin theDefault Assigneedropdown.Note: Ensure the project lead has the Assignable Userpermission in the project's permission scheme.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Why This Fits: SelectingProject leadensures that all newly created issues are automatically assigned to the project lead, preventing them from being unassigned, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Board administrator (Option A):
* There is noBoard administratoroption in theDefault Assigneedropdown. Board administrators manage Kanban or Scrum boards but are not a predefined assignee role for issues.
* Extract from Documentation:
TheDefault Assigneedropdown includesProject lead,Unassigned, or specific users, but notBoard administrator.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Component lead (Option C):
* TheComponent leadis not an option in theDefault Assigneedropdown. Component leads are assigned to specific components, and issues are only assigned to them if a component with a default assignee is selected during issue creation, which is not guaranteed for Kanban board creations.
* Extract from Documentation:
Component leads are assigned to issues only when a component with a default assignee is selected. They are not part of theDefault Assigneesetting.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Project admin (Option D):
* There is noProject adminoption in theDefault Assigneedropdown. Project administrators have theAdminister Projectspermission but are not a predefined assignee role. TheProject leadis the designated user for default assignments.
* Extract from Documentation:
TheDefault Assigneesetting does not includeProject admin. UseProject leadorUnassigned.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Reporter (Option E):
* TheReporteris the user who creates the issue and is not an option in theDefault Assignee dropdown for company-managed projects. Assigning issues to the reporter would require a custom automation rule or manual assignment, not a default setting.
* Extract from Documentation:
TheReporteris not a valid option forDefault Assignee. UseProject leadorUnassignedfor automatic assignments.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Additional Notes:
* TheDefault Assigneesetting is configured inProject settings > Details, requiringproject admin privileges.
* Ensure the project lead has theAssignable Userpermission in the project's permission scheme to be eligible as an assignee.
* IfUnassignedis selected, issues could remain unassigned, which violates the requirement.
:
Atlassian Support Documentation:Manage project settings in Jira Cloud
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud
NEW QUESTION # 48
George is the project lead of several projects. Now, he needs to create projects but should not have Jira administrator privileges. What does George need?
- A. Project permission
- B. Project role
- C. Product access
- D. Product role
- E. Global permission
Answer: E
Explanation:
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 Projects for his projects), but these do not extend to creating new projects.
:
Atlassian Support Documentation:Manage global permissions
Atlassian Support Documentation:Manage project roles
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Manage product roles
NEW QUESTION # 49
Users in a company-managed project need to capture various attributes about incoming bugs. They want to manage the options themselves and name the field 'Type of Bug'. Which field type meets their need?
- A. Labels system field
- B. Custom field of type Select List (multiple choices)
- C. Custom field of type Select List (single choice)
- D. Custom field of type Labels
Answer: C
Explanation:
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 admin privileges).
* 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.
:
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Manage fields in Jira Cloud
NEW QUESTION # 50
......
ACP-120 Dumps Full Questions with Free PDF Questions to Pass: https://www.latestcram.com/ACP-120-exam-cram-questions.html
ACP-120 PDF Recently Updated Questions Dumps to Improve Exam Score: https://drive.google.com/open?id=1rpPA-7WczFMcUH0WAMnZeaLt8ldGo80h
