Download Exam ACP-120 Practice Test Questions with 100% Verified Answers [Q20-Q42]

Download Exam ACP-120 Practice Test Questions with 100% Verified Answers

Share Latest ACP-120Test Practice Test Questions, Exam Dumps

NEW QUESTION # 20
One of the HR managers created a filter and shared the subscription with members of the hr- managers group. The filter contains the following valid JQL query:
Manager = currentUser() AND Manager in membersOf("hr-managers")
Which issues will be included in the subscription?

• A. All issues where the user listed in the Manager field is a member of the hr-managers group.
• B. Only issues where the user who created the filter is listed in the Manager field.
• C. Only issues where the group hr-managers is listed in the Manager field.
• D. Only issues where the recipient of the email is listed in the Manager field.
• E. All issues that are assigned to any member of the hr-managers group.

Answer: A

NEW QUESTION # 21
Sundar's development projects are falling behind.
He wants to write a JQL query to find issues that meet all three of these criteria:
1. He is the project lead of the project or the project is DEV.
2. fixVersion had been set to 4.3 at some point but was later removed.
3. Issues were created in the first 15 days of this month.
The Exhibit shows the JQL query he created.

Which statement about Sundar's query is true?

• A. The query will not return the right set of issues because line 2 only is wrong.
• B. The query will not return the right set of issues because lines 2 and 3 are wrong.
• C. The query will not return the right set of issues because the parentheses are wrong.
• D. The query is valid, but it will not run without a Jira Marketplace app.
• E. The query is well written and will return the right set of issues.
• F. The query will return the right set of issues, but it is inefficient.

Answer: D

NEW QUESTION # 22
You want to use a bulk operation to move issues between two company-managed projects that use different field configurations. Which field will definitely be updated?

• A. Resolved Date
• B. Assignee
• C. Status
• D. Components
• E. Custom fields

Answer: C

Explanation:
When moving issues between two company-managed projects with different field configurations using a bulk operation, certain fields may need to be updated due to differences in workflows, field configurations, or project-specific settings. The field that willdefinitelybe updated isStatus(Option E), as issues must be mapped to a valid status in the target project's workflow.
* Explanation of the Correct Answer (Option E):
* Each company-managed project can have its ownworkflow scheme, which assigns workflows to issue types. When moving issues between projects, the source project's workflow may have different statuses than the target project's workflow. During a bulk move, you must map the current status of each issue to a valid status in the target project's workflow, as the source status may not exist in the target workflow. This status mapping is a mandatory step in the bulk move process, ensuring thatStatusis always updated.
* Exact Extract from Documentation:
Move issues between projects
When moving issues to a different project in Jira Cloud, you must map the issue's status to a valid status in the target project's workflow.
To move issues:
* Select issues and chooseBulk change>Move issues.
* Choose the target project and issue type.
* Map the source status to a target status for each issue type.Note: Status mapping is required because projects may use different workflows with distinct statuses.(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Why This Fits: The bulk move operation always requires mapping theStatusfield to a valid status in the target project's workflow, makingStatusthe field that will definitely be updated.
* Why Other Options Are Incorrect:
* Assignee (Option A):
* TheAssigneefield is not necessarily updated during a move. If the assignee is a valid user in the target project and has theAssignable Userpermission, the assignee remains unchanged. Only if the assignee is invalid (e.g., lacks permissions) might you need to update it, but this is not guaranteed.
* Extract from Documentation:
TheAssigneefield is preserved during a move unless the user is not assignable in the target project, in which case you may be prompted to choose a new assignee.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Custom fields (Option B):
* Custom fieldsmay need to be updated if the target project's field configuration requires values for fields that were not required in the source project. However, this is not guaranteed, as it depends on the specific field configurations. If the custom fields are optional or have compatible values, no update is needed.
* Extract from Documentation:
Custom fields may require updates if the target project's field configuration mandates values not required in the source project. This is not always necessary.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Resolved Date (Option C):
* TheResolved Date(orResolution Date) is a read-only system field set automatically when an issue'sResolutionis set (e.g., via a workflow transition). It is not directly updated during a move unless the status mapping triggers a resolution change, which is not guaranteed.
* Extract from Documentation:
TheResolution Dateis set by workflow transitions, not directly by moving issues. It remains unchanged unless the move alters the resolution.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Components (Option D):
* Componentsare project-specific, and the target project may have different components.
During a move, you may need to map or clear components if the source components do not exist in the target project. However, this is not guaranteed, as components may be compatible or optional.
* Extract from Documentation:
Components may need to be mapped or cleared if the target project has different components, but this is not always required.
(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")
* Additional Notes:
* The bulk move operation is performed viaIssues > Search for issues > Bulk change > Move issues, requiring theMove Issuespermission.
* The mandatory status mapping ensures compliance with the target project's workflow, making Statusthe only field always updated.
* Other fields (e.g.,Assignee,Custom fields) may be updated depending on configurations, but only Statusis certain.
:
Atlassian Support Documentation:Move issues in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows

NEW QUESTION # 23
Managers want to ensure that every issue in Jira always has an assignee.
Which change will definitely meet this requirement?

• A. Set Default Assignee to Project Lead in every project.
• B. Make the assignee required through field configurations.
• C. Update post functions to set the assignee appropriately at each workflow transition.
• D. Use components for automatic assignment in every project.
• E. Make the assignee required on workflow transition screens.
• F. Set the global option "Allow unassigned issues" to OFF.

Answer: C

Explanation:
Reference: https://community.atlassian.com/t5/Answers-Developer-Questions/Conditional-Post-Function/qaq-p/561594

NEW QUESTION # 24
You renamed a value in the Resolution field from Done to Finished. What might need to be updated as a result?

• A. Issue Statistics gadgets
• B. Workflow post functions
• C. Issues in team-managed projects
• D. Saved filters
• E. Issue detail view

Answer: D

Explanation:
Renaming a value in theResolutionfield (fromDonetoFinished) changes its display name globally in Jira Software Cloud. This can impact configurations or features that reference the resolution value by name, particularly in JQL queries. The element most likely to need updating issaved filters(Option B), as they often use JQL queries that include resolution values.
* Explanation of the Correct Answer (Option B):
* Saved filtersoften use JQL queries that reference resolution values (e.g., resolution = Done). If theResolutionfield value is renamed fromDonetoFinished, any filters using resolution = Done will no longer match issues with the renamed resolution (Finished), as the old value is no longer valid. These filters must be updated to use resolution = Finished to continue returning the correct issues.
* Exact Extract from Documentation:
Manage resolutions in Jira Cloud
Resolutions are global values used in theResolutionfield to indicate an issue's resolution state.
Impact of renaming a resolution:
* JQL queries in filters, boards, or gadgets referencing the resolution name (e.g., resolution = Done) will no longer match issues if the value is renamed (e.g., to Finished).To update:
* Go toIssues > Manage filters.
* Edit filters to use the new resolution name (e.g., resolution = Finished).Note: Renaming a resolution affects all projects and requires updating JQL-based configurations.(Source:
Atlassian Support Documentation, "Manage resolutions in Jira Cloud")
* Why This Fits: Renaming a resolution value impactssaved filtersthat use JQL queries referencing the old value, requiring updates to maintain functionality, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Workflow post functions (Option A):
* Workflow post functionscan set theResolutionfield (e.g.,Set Issue ResolutiontoDone).
These post functions typically use the resolution's internal ID, not its display name, so renamingDonetoFinisheddoes not require changes to post functions.
* Extract from Documentation:
Post functions reference resolution IDs, not names. Renaming a resolution does not affect workflow configurations.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Issue detail view (Option C):
* Theissue detail viewdisplays theResolutionfield value as configured. RenamingDoneto Finishedupdates the display automatically without requiring manual changes to the issue detail view or its configuration (e.g.,issue layout).
* Extract from Documentation:
The issue detail view reflects the current resolution name automatically. No changes are needed after renaming a resolution.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Issue Statistics gadgets (Option D):
* Issue Statistics gadgets(e.g., on dashboards) can display data based on fields like Resolution. While gadgets may reference resolution values in their configuration, they typically use resolution IDs or dynamically update to reflect the renamed value. The impact is less direct than with saved filters, which rely on explicit JQL queries.
* Extract from Documentation:
Gadgets like Issue Statistics use field values or IDs. Renaming a resolution may not require gadget updates unless JQL queries are explicitly used.
(Source: Atlassian Support Documentation, "Manage dashboards in Jira Cloud")
* Issues in team-managed projects (Option E):
* Resolutionsare global and apply to both company-managed and team-managed projects.
RenamingDonetoFinishedupdates the value for all issues, including those in team- managed projects, without requiring changes to the issues themselves. The change is reflected automatically.
* Extract from Documentation:
Resolutions are global and apply to all projects. Renaming a resolution updates its display for all issues without requiring issue-level changes.
(Source: Atlassian Support Documentation, "Manage resolutions in Jira Cloud")
* Additional Notes:
* Renaming a resolution is done inSettings > Issues > Resolutionsand requiresJira administrator privileges.
* Other JQL-based features (e.g., automation rules, boards) may also be impacted if they reference the resolution name, butsaved filtersare the most commonly affected.
* To minimize impacts, use resolution IDs in JQL queries (e.g., resolution = 10000), though this is less common.
:
Atlassian Support Documentation:Manage resolutions in Jira Cloud
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage dashboards in Jira Cloud

NEW QUESTION # 25
The Customer Relations team has just been given access to Jira. They can see two projects but not the project boards. They created several advanced searches and want other project members to see the results. Which permission do they require without receiving too much access?

• A. Board administrator
• B. Administer Jira
• C. Browse Projects
• D. Share dashboards and filters

Answer: D

Explanation:
The Customer Relations team can see two projects (indicating they haveBrowse Projectspermission) but not the project boards, and they want to share advanced searches (filters) with other project members. The permission required to share filters without granting excessive access is theShare dashboards and filters global permission (Option B).
* Explanation of the Correct Answer (Option B):
* TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, or roles. This permission is necessary for the team to make their advanced searches visible to other project members. It is a targeted permission that does not grant additional administrative or project-level access.
* Exact Extract from Documentation:
Share dashboards and filters permission
TheShare dashboards and filtersglobal permission allows users to share filters and dashboards with other users, groups, projects, or the entire organization.
To grant this permission:
* Go toSettings > System > Global permissions.
* Add a user, group, or role to theShare dashboards and filterspermission.Note: This permission is required to make filters or dashboards accessible to others, but it does not grant access to view issues or manage boards.(Source: Atlassian Support Documentation,
"Manage global permissions")
* Why This Fits: TheShare dashboards and filterspermission directly enables the team to share their advanced searches (filters) with other project members without granting unnecessary privileges, making Option B the correct choice.
* Why Other Options Are Incorrect:
* Browse Projects (Option A):
* TheBrowse Projectspermission allows users to view issues in a project. Since the team can already see two projects, they likely have this permission. It does not control the ability to share filters or access project boards.
* Extract from Documentation:
TheBrowse Projectspermission allows users to view issues and projects. It does not include sharing filters or managing boards.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Board administrator (Option C):
* TheBoard administratorrole (orManage Sprintspermission for company-managed projects) allows users to manage boards, including viewing and editing them. While this would allow the team to see project boards, it grants excessive access (e.g., modifying sprints) and does not address sharing filters.
* Extract from Documentation:
Board administrators can manage board settings and sprints. This role is not required to share filters or dashboards.
(Source: Atlassian Support Documentation, "Manage boards in Jira Cloud")
* Administer Jira (Option D):
* TheAdminister Jirapermission (Jira administrator role) grants full access to global settings, including user management, schemes, and permissions. This is far too much access for the team's needs, which are limited to sharing filters.
* Extract from Documentation:
TheAdminister Jirapermission grants access to all global settings. It is not needed for sharing filters or viewing boards.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Additional Notes:
* The team's inability to see project boards likely stems from lacking theView Development Tools orManage Sprintspermission, or not being board administrators. However, the question focuses on sharing filters, soShare dashboards and filtersis the relevant permission.
* The permission can be granted to the team via a group inSettings > System > Global permissions.
:
Atlassian Support Documentation:Manage global permissions
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Manage boards in Jira Cloud
Atlassian Support Documentation:Manage filters in Jira Cloud

NEW QUESTION # 26
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. Product access
• B. Groups
• C. Default user preferences
• D. Project permissions
• E. Project roles

Answer: D

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 # 27
You need to implement a change to several classic projects in your Jira instance
* A defined set of users needs to be able to create issues on behalf of other users It is important to note that
* Project administrators should be able to decide which users are able to perform this operation
* Some projects use a shared permission scheme
Which combined use of two administrative items will meet this requirement? (Choose two)

• A. Global permission
• B. Individual users
• C. Project role
• D. User group
• E. Project permission

Answer: C,E

NEW QUESTION # 28
One of your teams is maintaining and updating an application that has grown into three distinct modules.
The modules are on different release cycles. The team is struggling to track the versions of the modules, because they have similar numbering schemes.
Which action would you recommend?

• A. Define an issue type for each module.
• B. Split the project into several projects, one for each module.
• C. Create a new Version field for each module.
• D. Split the modules into separate components.

Answer: C

Explanation:
Reference: https://jira.atlassian.com/browse/JRACLOUD-3501?page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel&showAll=true

NEW QUESTION # 29
You must add a new issue type to an existing company-managed project. Identify the configuration item that is definitely not impacted.

• A. Issue type screen scheme
• B. Issue security scheme
• C. Workflow scheme
• D. Issue layout
• E. Field configuration scheme

Answer: B

Explanation:
Adding a new issue type to a company-managed project requires updating configurations that map issue types to various settings (e.g., screens, workflows, fields). The configuration item that isdefinitely not impactedis theissue security scheme(Option C), as it controls issue visibility and is not directly tied to issue types.
* Explanation of the Correct Answer (Option C):
* Anissue security schemedefines security levels that restrict which users can view issues in a project, based on criteria like users, groups, or roles. It is applied at the project level and is not specific to issue types. Adding a new issue type does not require changes to the issue security scheme, as security levels apply to all issues in the project regardless of their type.
* Exact Extract from Documentation:
Configure issue security schemes
Issue security schemes define security levels to control who can view issues in a project.
Impact of issue types:
* Security levels are applied to all issues in a project, regardless of issue type.
* Adding a new issue type does not affect the issue security scheme.To check:
* Go toProject settings > Issue security.
* Review the security levels and their criteria.Note: Issue security is independent of issue type configurations.(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Why This Fits: Theissue security schemeis not impacted by adding a new issue type, as it operates at the project level and does not depend on issue type configurations, making Option C the correct answer.
* Why Other Options Are Incorrect:
* Issue layout (Option A):
* Theissue layoutdefines which fields are displayed or hidden in the issue view for each issue type. Adding a new issue type may require configuring a new issue layout to specify field visibility for that type, impacting this configuration.
* Extract from Documentation:
Issue layouts are configured per issue type inProject settings > Issue layout. Adding a new issue type may require a new layout configuration.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Issue type screen scheme (Option B):
* Theissue type screen schememaps screens to issue types for operations (Create, Edit, View). Adding a new issue type requires assigning a screen to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the issue type screen scheme to assign screens for the new type.
(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")
* Workflow scheme (Option D):
* Theworkflow schememaps workflows to issue types. Adding a new issue type requires assigning a workflow to it in the scheme, impacting this configuration.
* Extract from Documentation:
Adding a new issue type requires updating the workflow scheme to assign a workflow for the new type.
(Source: Atlassian Support Documentation, "Configure workflow schemes")
* Field configuration scheme (Option E):
* Thefield configuration schememaps field configurations to issue types, defining field behavior (required, optional, hidden). Adding a new issue type may require assigning a field configuration to it, impacting this configuration.
* Extract from Documentation:
Adding a new issue type may require updating the field configuration scheme to assign a configuration for the new type.
(Source: Atlassian Support Documentation, "Configure field settings")
* Additional Notes:
* Steps to add a new issue type:
* Add the issue type to the project's issue type scheme inProject settings > Issue types.
* Update theissue type screen scheme,workflow scheme, andfield configuration schemeto include the new issue type.
* Configure theissue layoutfor the new issue type if needed.
* These changes requireJira administratorprivileges for schemes andproject adminprivileges for issue layout.
* Theissue security schemeremains unaffected, as it applies to all issues in the project.
:
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure screen schemes in Jira Cloud
Atlassian Support Documentation:Configure workflow schemes
Atlassian Support Documentation:Configure field settings

NEW QUESTION # 30
On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What does Taylor definitely need?

• A. Organization admin privileges
• B. Project administration privileges
• C. Global permissions
• D. Project permissions
• E. Jira administration privileges

Answer: D

Explanation:
The inability to choose theDelete Issuesbulk action on the Bulk Operation screen indicates that Taylor lacks the necessary permission to delete issues in the project. TheDelete Issuespermission, which is a project-level permission defined in the project's permission scheme, is required for this action. Therefore, Taylor definitely needsproject permissions(Option D).
* Explanation of the Correct Answer (Option D):
* TheDelete Issuespermission allows users to delete issues, including via bulk operations. This permission is granted through the project's permission scheme and is specific to the project containing the issues. If Taylor cannot select theDelete Issuesbulk action, she lacks this permission for the project.
* Exact Extract from Documentation:
Delete Issues permission
TheDelete Issuespermission allows users to delete issues, either individually or via bulk operations. This permission is granted via the project's permission scheme.
To perform bulk operations:
* Run a filter to select issues.
* On the Bulk Operation screen, choose an action (e.g., Delete Issues).Note: Users must have the relevant permission (e.g.,Delete Issues) for allselected issues to see the action in the bulk operation wizard.To check permissions:
* Go toProject settings > Permissions.
* Verify which users, groups, or roles have theDelete Issuespermission.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: TheDelete Issuespermission is a project-level permission, and granting it to Taylor will enable her to choose theDelete Issuesbulk action, makingproject permissions (Option D) the correct answer.
* Why Other Options Are Incorrect:
* Organization admin privileges (Option A):
* Organization admins manage Atlassian organization settings, such as user access and billing. They do not directly control project-level permissions likeDelete Issues.
* Extract from Documentation:
Organization admins manage user access and organization settings. Project-specific actions, like deleting issues, are controlled by project permissions.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Jira administration privileges (Option B):
* Jira administrators manage global settings, such as schemes and user management. While they can modify permission schemes, theDelete Issuespermission is project-specific and does not require Jira admin privileges to grant or use.
* Extract from Documentation:
Jira administrators can modify permission schemes, but theDelete Issuespermission is applied at the project level and does not require admin privileges to use.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Global permissions (Option C):
* Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific actions like deleting issues. TheDelete Issuespermission is project- level, not global.
* Extract from Documentation:
Global permissions control system-wide actions, such as administering Jira or sharing filters. Project permissions, likeDelete Issues, are specific to projects.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Project administration privileges (Option E):
* Project administration privileges (via theAdminister Projectspermission) allow users to manage project settings, such as components and permission schemes. However, deleting issues is an issue-level action that requires theDelete Issuespermission, not administrative privileges.
* Extract from Documentation:
TheAdminister Projectspermission allows managing project settings. Deleting issues requires theDelete Issuespermission, which is separate.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Additional Notes:
* To resolve the issue, check Taylor's permissions inProject settings > Permissionsand ensure she has theDelete Issuespermission, either directly, via a group, or via a project role.
* If the issues in the bulk operation span multiple projects, Taylor needs theDelete Issues permission for all relevant projects.
:
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage global permissions

NEW QUESTION # 31
Currently, several groups and project robs are listed in every system event of the DEV Notification Scheme and should remain that way. A new requirement states that when DEV issues move from the status Open to status Assigned, only Project Rob (Managers) should be notified. DEV project does not share any of its schemes.
Identify the event that needs to be configured.

• A. Issue Assigned
• B. Issue Moved
• C. Work Started On Issue
• D. Custom event

Answer: A

NEW QUESTION # 32
You are a site administrator.
You have created an account fo rAshley
You need to log in as Ashley to ensure his permissions are set correctly Identify why you are unable to log in as Ashley (Choose one)

• A. Ashley has not accessed your site yet
• B. Ashley does not have a managed account
• C. You are not an organization admin
• D. Ashley has the role of site admin

Answer: B

NEW QUESTION # 33
You created a new "Create a new issue or add a comment to an existing issue" mail handler. What two fields have specific settings in the handler? (Choose two.)

• A. Priority
• B. Custom Field
• C. Reporter
• D. Epic Link
• E. Watchers

Answer: A,C

Explanation:
The question pertains to configuring a"Create a new issue or add a comment to an existing issue" mail handlerin Jira Software Cloud. Mail handlers process incoming emails to create issues or add comments, and certain fields can be specifically configured to control how the handler behaves. According to Jira Cloud documentation, the two fields with specific settings in this type of mail handler areReporterandPriority.
* Explanation of the Correct Answers:
* Reporter (Option C):
* TheReporterfield specifies the user who is set as the reporter of the issue created by the mail handler. In the mail handler configuration, you can define whether the reporter is set to a default user, derived from the email's "From" address (if the email address matches a Jira user), or another specified user.
* Exact Extract from Documentation:
Configuring an email handler
When setting up a mail handler like "Create a new issue or add a comment to an existing issue," you can configure the following settings:
* Reporter: Specify the user who will be set as the reporter for new issues. Options include:
* The user associated with the email's "From" address (if they have a Jira account).
* A default user (e.g., a project lead or a specific user account).
* If no valid user is found, the handler can be configured to reject the email or use a fallback user.This setting ensures that the issue is attributed to the correct user as the reporter.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Why This Fits: The Reporter field is a critical setting in the mail handler, as it determines who is recorded as creating the issue, which affects permissions, notifications, and reporting.
* Priority (Option D):
* ThePriorityfield allows you to set a default priority for issues created by the mail handler if the email does not explicitly specify a priority. This ensures that new issues have a consistent priority unless overridden by the email content.
* Exact Extract from Documentation:
Field settings for mail handlers
For the "Create a new issue or add a comment to an existing issue" handler, you can specify default values for certain fields, including:
* Priority: Set a default priority for new issues (e.g., Medium, High). If the email contains a specific priority value (e.g., via a keyword or mapping), it can override the default.These settings allow you to control the behavior of issue creation and ensure consistency in field values.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Why This Fits: The Priority field is explicitly configurable in the mail handler to ensure that new issues are assigned an appropriate priority, making it one of the two fields with specific settings.
* Why Other Options Are Incorrect:
* Epic Link (Option A):
* TheEpic Linkfield is not specifically configurable in the mail handler settings. While you can map email content to fields like Epic Link using advanced configurations (e.g., regex or scripting in Automation), it is not a standard field with specific settings in the mail handler configuration interface.
* Extract from Documentation:
Mail handlers allow mapping of email content to standard fields like Summary, Description, or Priority.
Advanced field mappings, such as Epic Link, require custom automation rules or third-party apps.
(Source: Atlassian Support Documentation, "Automate email processing with Jira Automation")
* Custom Field (Option B):
* While custom fields can sometimes be populated via email content (e.g., through regex or automation), the mail handler's standard configuration does not provide specific settings for custom fields. The handler focuses on system fields like Reporter and Priority.
* Extract from Documentation:
Custom fields are not directly supported in the default mail handler settings. To populate custom fields, you may need to use Jira Automation or a third-party mail handler app.
(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")
* Watchers (Option E):
* TheWatchersfield is not a configurable setting in the mail handler. You cannot specify default watchers or automatically add watchers based on email content in the standard mail handler configuration. Watchers are typically managed manually or via automation rules.
* Extract from Documentation:
Watchers are not a configurable field in mail handlers. To add watchers automatically, use JiraAutomation or a workflow post function.
(Source: Atlassian Support Documentation, "Configure notifications and watchers")
* Additional Notes:
* The"Create a new issue or add a comment to an existing issue" mail handleris one of several mail handler types in Jira Cloud. Its configuration focuses on ensuring that issues are created with the correct metadata (e.g., Reporter, Priority) and that comments are added to existing issues based on issue keys in the email subject.
* Configuring the Reporter and Priority fields ensures that issues created via email align with project workflows and notification schemes.
:
Atlassian Support Documentation:Configure email handlers in Jira Cloud
Atlassian Support Documentation:Automate email processing with Jira Automation Atlassian Support Documentation:Configure notifications and watchers

NEW QUESTION # 34
Users need to be able to select Browser Type when editing bugs in the DEV project. However, they cannot see the field. Identify three possible root causes. (Choose three.)

• A. Issue security scheme
• B. Field configurations
• C. Project permissions
• D. Custom field context
• E. Project roles

Answer: B,C,D

Explanation:
The issue is that users cannot see theBrowser Typefield when editing bugs in the DEV project, a company- managed project. This suggests a configuration issue preventing the field from being displayed or accessible.
The three possible root causes arefield configurations(Option B),custom field context(Option C), and project permissions(Option D), as these can affect field visibility or editability.
* Explanation of the Correct Answers:
* Field configurations (Option B):
* Field configurationsdetermine whether a field is required, optional, or hidden for specific issue types in a project. If theBrowser Typefield is marked asHiddenin the field configuration for bugs in the DEV project, it will not appear on any screens (Create, Edit, View), preventing users from seeing or selecting it when editing bugs.
* Exact Extract from Documentation:
Configure field settings
Field configurations control field behavior (required, optional, hidden) for issue types in a project.
If a field is hidden:
* It does not appear on any screens, including Create, Edit, or View.To check:
* Go toProject settings > Fields.
* Review the field configuration for the issue type (e.g., Bug).
* Ensure the field (e.g., Browser Type) is not marked asHidden.Note: Hidden fields are completely removed from issue operations.(Source: Atlassian Support Documentation, "Configure field settings")
* Why This Fits: IfBrowser Typeis hidden in the field configuration for bugs, users will not see it when editing, making this a possible root cause.
* Custom field context (Option C):
* Thecustom field contextdefines which projects and issue types a custom field applies to. If theBrowser Typefield's context does not include the DEV project or theBugissue type, the field will not be available for bugs in that project, causing it to be invisible during editing.
* Exact Extract from Documentation:
Manage custom field contexts
A custom field's context determines the projects and issue types where it is available.
If a field is not visible:
* Check the field's context inSettings > Issues > Custom fields.
* Ensure the context includes the project (e.g., DEV) and issue type (e.g., Bug).Note:
A misconfigured context can prevent a field from appearing in a project.(Source:
Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Why This Fits: If theBrowser Typefield's context excludes the DEV project orBugissue type, it will not be available, making this a possible root cause.
* Project permissions (Option D):
* TheEdit Issuespermission in the project's permission scheme determines whether users can edit issues, including fields likeBrowser Type. If users lack this permission for bugs in the DEV project, they will not be able to edit the field, which could manifest as the field being invisible or non-editable during editing attempts.
* Exact Extract from Documentation:
Manage permissions in Jira Cloud
TheEdit Issuespermission allows users to modify issue fields, including custom fields.
If users cannot edit a field:
* CheckProject settings > Permissions.
* Ensure the user, group, or role has theEdit Issuespermission.Note: Lack of edit permission can prevent users from seeing or interacting with editable fields.(Source:
Atlassian Support Documentation, "Manage permissions in Jira Cloud")
* Why This Fits: If users lack theEdit Issuespermission, they may not be able to edit or see theBrowser Typefield as editable, making this a possible root cause.
* Why Other Options Are Incorrect:
* Project roles (Option A):
* Project roles are used in permission schemes or other configurations to grant permissions (e.
g.,Edit Issues). While a role could be part of the permission scheme affectingEdit Issues, the root cause is the permission itself (Option D), not the role. Roles do not directly control field visibility.
* Extract from Documentation:
Project roles are used to assign permissions, not to control field visibility directly. Check permissions likeEdit Issuesfor editability issues.
(Source: Atlassian Support Documentation, "Manage project roles")
* Issue security scheme (Option E):
* Anissue security schemerestricts which issues a user can view based on security levels. If users can see the bug issues but not theBrowser Typefield, the issue is not about issue visibility but field visibility or editability, sothe security scheme is not a root cause.
* Extract from Documentation:
Issue security schemes control which issues are visible, not which fields within an issue are displayed.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Additional Notes:
* To troubleshoot:
* CheckProject settings > Fieldsto ensureBrowser Typeis not hidden in the field configuration for bugs.
* Verify the field's context inSettings > Issues > Custom fieldsincludes the DEV project and Bugissue type.
* Confirm users have theEdit Issuespermission inProject settings > Permissions.
* Other potential causes (not listed) include the field not being on theEdit screen(screen configuration) or being hidden in theissue layout, but these are covered byfield configurations and permissions broadly.
* Resolving these issues may requireJira administrator(for field configurations, contexts) or project admin(for permissions) privileges.
:
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Manage permissions in Jira Cloud
Atlassian Support Documentation:Manage project roles
Atlassian Support Documentation:Configure issue security schemes

NEW QUESTION # 35
Your Jira instance has a Select List custom field named Application, which lists all the Atlassian offerings. You need to write a JQL query that shows all issues due within the next month for Jira, Trelb, and Jira Align applications.
Which query will satisfy the requirement?

• A. Application = ^Jim^ OR Application = OR * Application = ^Jim Align^ AND duedate startOrMonth(1) OR duedate <= endOrMonth(1)
• B. Application IN (Jira, Trelb, ^Jim Align-) AND * (duedate>= startOrMonth(1) OR duedate <= endOrMonth(1))
• C. Application IN (Jira,Trelb,Jira Align) AND * (duedate>= startOrMonth(1M) AND duedate<= endOrMonth(1M))
• D. Application IN (Jira,Trelb, ^Jim Align.) AND * &iodate >. startOrMonth(1) AND &iodate <= endOrMonth(1)
• E. (Application =^Jire^ OR Application = ^Trelb. OR Application = ^Jim Align-) AND duedate startOrMonth(1m) AND duedate <= endOrMonth(,m)

Answer: D

NEW QUESTION # 36
You set up an incoming mail server and a mail handler to Create a new issue or add a comment to an existing issue Which three additional options can you set with the mail configuration

• A. Set a default reporter
• B. Set the environment system field
• C. Set a custom field
• D. Set watchers
• E. Create new users based on the From address

Answer: A,C,D,E

NEW QUESTION # 37
Two projects share all their schemes. Which two configuration changes would impact both projects?

• A. Archiving a version
• B. Removing shortcuts
• C. Making the Assignee required
• D. Adding a new component
• E. Adding a new field to a screen
• F. Updating the project category

Answer: C,E

Explanation:
When two projects in Jira Software Cloud share all their schemes (e.g., issue type scheme, workflow scheme, screen scheme, field configuration scheme, permission scheme, notification scheme), any changes to these shared schemes will impact both projects. The two configuration changes that would affect both projects are adding a new field to a screen(Option A) andmaking the Assignee required(Option C), as these involve modifications to shared schemes.
* Explanation of the Correct Answers:
* Adding a new field to a screen (Option A):
* Screens in Jira are associated with projects through ascreen scheme, which maps screens to issue operations (e.g., Create, Edit, View) for specific issue types. If two projects share the same screen scheme, adding a new field to a screen (e.g., a custom field or system field) will affect all projects using that screen scheme, as the field will appear on the screen for the corresponding operation.
* Exact Extract from Documentation:
Configure screens
Screens define which fields are displayed during issue operations (Create, Edit, View). Screens are associated with issue types via a screen scheme, and multiple projects can share the same screen scheme.
To add a field to a screen:
* Go toSettings > Issues > Screens.
* Select the screen and add the field.Impact: Adding a field to a screen affects all projects using the same screen scheme, as the field will appear for the associated issue types and operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Why This Fits: Since the projects share all schemes, including the screen scheme, adding a field to a screen will impact both projects by altering the issue creation, editing, or viewing experience.
* Making the Assignee required (Option C):
* Making theAssigneefield required involves modifying thefield configurationwithin afield configuration scheme. The field configuration determines whether a field is required, optional, or hidden. If two projects share the same field configuration scheme, making the Assignee field required will affect both projects, as issues in both projects will require an assignee to be set.
* Exact Extract from Documentation:
Configure field settings
Field configurations define the behavior of fields (e.g., required, optional, hidden) for specific issue types. A field configuration scheme maps field configurations to issue types, and multiple projects can share the same scheme.
To make a field required:
* Go toSettings > Issues > Field configurations.
* Select the field configuration and mark the field (e.g., Assignee) asRequired.Impact:
Changes to a field configuration affect all projects using the associated field configuration scheme.(Source: Atlassian Support Documentation, "Configure field settings")
* Why This Fits: Since the projects share the field configuration scheme, making the Assignee required will enforce this rule in both projects, impacting their issue creation and editing processes.
* Why Other Options Are Incorrect:
* Adding a new component (Option B):
* Components are project-specific and configured inProject settings > Components.
Adding a component to one project does not affect another project, even if they share schemes, as components are not part of any shared scheme.
* Extract from Documentation:
Manage components
Components are unique to each project and configured inProject settings > Components. They are not shared via schemes, so changes to components in one project do not affect others.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Removing shortcuts (Option D):
* Shortcuts (project-specific links to external resources) are configured inProject settings > Shortcutsand are unique to each project. Removing shortcuts in one project does not impact another project, regardless of shared schemes.
* Extract from Documentation:
Manage project shortcuts
Shortcuts are project-specific links to external resources, configured inProject settings > Shortcuts. Changes to shortcuts in one project do not affect other projects.
(Source: Atlassian Support Documentation, "Manage project settings")
* Updating the project category (Option E):
* The project category is a project-specific attribute set inProject settings > Details.
Changing the project category for one project does not affect another project, even if they share schemes, as categories are not tied to schemes.
* Extract from Documentation:
Change project details
The project category is set inProject settings > Detailsand is unique to each project. It does not impact schemes or other projects.
(Source: Atlassian Support Documentation, "Manage project settings")
* Archiving a version (Option F):
* Versions are project-specific and managed inProject settings > Releases. Archiving a version in one project does not affect another project, as versions are not part of shared schemes.
* Extract from Documentation:
Manage versions
Versions are project-specific and configured inProject settings > Releases. Archiving a version affects only the project it belongs to, not other projects, even if they share schemes.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
* Additional Notes:
* Shared schemes ensure consistency across projects, but they also mean that changes to schemes (e.g., screens, field configurations) have a broad impact. Project admins must coordinate with Jira admins to modify schemes, as these changes require system-level permissions.
* Project-specific settings like components, shortcuts, categories, and versions allowfor customization without affecting other projects.
:
Atlassian Support Documentation:Configure screens in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage components in Jira Cloud
Atlassian Support Documentation:Manage project settings
Atlassian Support Documentation:Manage versions in company-managed projects

NEW QUESTION # 38
Martin has Create Attachments permission in a software project, but he cannot attach anything to issues in Approved status.
What is the problem?

• A. He does not have the correct project permission.
• B. The Attachment field is missing from the screen for that issue type.
• C. He is not a member of a security level.
• D. There is a workflow step property configured.
• E. There is a workflow condition configured.

Answer: A

Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/configuring-file-attachments-818578880.html

NEW QUESTION # 39
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. Component lead
• B. Reporter
• C. Project admin
• D. Board administrator
• E. Project lead

Answer: E

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 # 40
Which three statements are correct about deleting a user account (Choose three)

• A. Accounts can only be deleted if they have no issues assigned
• B. Access to all products and administration functions will be lost
• C. Organization admins can delete managed accounts
• D. Individual users can delete their unmanaged accounts
• E. Issues that were created by a deleted account will be deleted

Answer: B,C,D

NEW QUESTION # 41
You created a new project and need to configure notifications.
Managers should be notified when
* Someone mentions them while adding or editing a comment
* The issue assignee or reporter is changed
* Issue links are added or deleted
You assume that users have not turned off any notifications through their Personal settings Identify the two notification events to which managers should definitely be added (Choose two)

• A. Generic Event
• B. Issue Updated
• C. Issue Assigned
• D. Issue Commented
• E. Issue Deleted

Answer: B,C

NEW QUESTION # 42
......

Positive Aspects of Valid Dumps ACP-120 Exam Dumps!: https://www.actualvce.com/ATLASSIAN/ACP-120-valid-vce-dumps.html

First Attempt Guaranteed Success in ACP-120 Exam: https://drive.google.com/open?id=1wuMPIBIXSHgRSGfS9X0iOBv0J-Q-eg38