[Q20-Q44] Download ATLASSIAN ACP-120 Sample Questions [Jan-2026]

Download ATLASSIAN ACP-120 Sample Questions [Jan-2026]

Real ACP-120 Exam Questions and Answers FREE

The ACP-120 exam covers a range of topics related to Jira Cloud administration, including user management, project configuration, issue tracking, and reporting. ACP-120 exam is designed to test the candidate's ability to configure and manage Jira Cloud instances to meet specific business requirements. ACP-120 exam also tests the candidate's ability to identify and troubleshoot common issues that may arise in Jira Cloud instances.

The ACP-120 exam covers a wide range of topics, including Jira Cloud architecture, user management, project configuration, issue management, and reporting. ACP-120 exam is designed to test the candidate's ability to configure and customize Jira to meet the needs of different organizations and teams. It also assesses the candidate's ability to troubleshoot issues and resolve problems that may arise during the administration of Jira Cloud.

 

NEW QUESTION # 20
A team requests updates to the behavior of some fields in the project. The project uses three issue types: Problem, Incident, and Change.
The desired configuration is shown below:

Which configuration update will meet the requirements?

• A. Configure individual field contexts for each custom field and update the priority scheme.
• B. Configure individual screens for any combination of issue operation and issue type.
• C. Configure individual field configurations for each issue type.
• D. Create unique field contexts for each issue type for the desired fields.
• E. Configure individual field configuration for each custom field and update the priority scheme.
• F. Configure individual screens for each issue type and update the priority scheme.

Answer: A

NEW QUESTION # 21
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. Administration access
• B. Product access
• C. Individual users
• D. Site access
• E. User groups
• F. Trusted user role

Answer: C,E

NEW QUESTION # 22
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. Work On Issues
• B. Edit Issues
• C. Move Issues
• D. Schedule Issues
• E. Manage Sprints
• F. Assignable User

Answer: B,D

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 # 23
Inspect your current Incoming Mail Handler configuration:

Identify one reason why the current configuration is not fetching emails as planned.

• A. The blank space in the Incoming Mail Handler name will cause internal errors.
• B. The syntax of the specified Folder Name is invalid and should be corrected to '/spam'.
• C. A delay of 10000 minutes is not a valid setting and will cause an error.
• D. The external mail service is not able to write the messages to the specified folder.

Answer: D

Explanation:
Reference: https://confluence.atlassian.com/jirakb/troubleshoot-incoming-mail-in-jira-service-desk-790960076.html

NEW QUESTION # 24
Your business users want to know more about what is happening with the issues raised by their business unit. They gave you a list of situations in which they want to get emails, so you know which parts of the shared notification scheme they want to be added to.
You consult with the project owner.
He doesn't want any changes to the emails that go to developers and testers.
The project owner approves of the business users getting the emails, but he would like to retain control of who gets emails for his project.
How can you satisfy these requests?

• A. Modify the events in the workflow so they send the emails to the business users.
• B. Create a role for business users and add that role to the events in the notification scheme.
• C. Add the business users as Watchers on the issues.
• D. Place the business users in a group and add that group to the events in the notification scheme.

Answer: D

NEW QUESTION # 25
Your business owners have told you to use roles as much as possible in Jira because it allows them to do things that groups cannot do.
When considering this, you need to be aware of those actions in Jira that require the use of groups rather than roles.
Identify two actions in Jira that require the use of groups. (Choose two.)

• A. granting system administrative rights
• B. controlling who can perform Bulk Change in a project
• C. granting Project Administration rights
• D. granting permissions to teams coming from Active Directory
• E. allowing users to use transitions in all the workflows
• F. defining Issue Security levels

Answer: C,F

Explanation:
Reference: https://confluence.atlassian.com/adminjiracloud/managing-project-roles-776636382.html

NEW QUESTION # 26
Your management team needs to see a list of only those issues that were resolved in the previous week, from Sunday to Saturday. The list needs to be sent to them each week on Tuesdays. You plan to create a saved filter and filter subscription to do this.
Which JQL query will Mum the correct results?

• A. resolved end0fWeek(1)
• B. status changed TO RESOLVED BEFORE startOfWeek()
• C. resolved>=startOfDay(-7) AND resolved < startOfDay()
• D. resolved ,= start0fWeek(-1) AND resolved start0fWeek0

Answer: D

Explanation:
A). Incorrect. -resolved >. end0fWeek(1. will return all issues resolved this week, up until Tuesday when the filter is sent.
B). Correct. ^resolved ,= start0fWeek(1 AND resolved < start0fWeeklr ensures that only issues created in the previous week, from Sunday to Saturday, are returned by the query. The start0fWeek0 function returns Sunday 00:00 by defauk.
C). Incorrect. Resolved issues do not necessarily have their status changed to Resolved. Issues may be resolved with a status of Done or Closed as long as the Resolution field is set. Additionally, the query will return all issues that have ever been transitioned to Resolved status, not just from last Sunday to Saturday.
D). Incorrect. -resolved >= start0fDay(-7). is actually a Tuesday. So this filter will return all issues resolved from Tuesday of last week to Monday of this week.

NEW QUESTION # 27
You set up a new project for a team. Soon afterward, users report that a field is missing from one of their screens. You check the screen configuration in the administration panel and you see that the field should be present.
Why can't the users see the field?

• A. The issue operation wasn't mapped to a screen.
• B. The changes to the screen were not published.
• C. The field context does not include the project and/or issue type.
• D. The users don't have permission to view that field.

Answer: D

NEW QUESTION # 28
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. Disable public signup and grant all project permissions to Group Anyone.
• B. Enable public signup and CAPTCHA but limit account creation to stakeholders.
• C. Create and manage the users for stakeholders manually in the internal directory.
• D. Connect Jira to your internal LDAP directory and whitelist the IPs of stakeholders.

Answer: A

NEW QUESTION # 29
The HR team approaches you with new requirements they want you to implement:
- Allow users to send requests into Jira by emailing "[email protected]."
- Have those emails automatically turned into "Holiday Requests" in the HR project.
You have already 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 this mail configuration? (Choose three.)

• A. Set Environment.
• B. Set default Reporter.
• C. Set Assignee and Watchers.
• D. Create new Jira users based on the From address.
• E. Set a custom field.

Answer: A,B,E

NEW QUESTION # 30
Peter is building a workflow in his team-managed project. He can add several rules to his workflow except for one rule. Identify that rule.

• A. Rule to ensure only Peter can approve Stories.
• B. Rule to ensure only the Reporter can close bugs.
• C. Rule to reopen Sub-tasks when reopening Stories.
• D. Rule to clear the Assignee when closing.
• E. Rule to clear the Description when reopening.

Answer: C

Explanation:
In team-managed projects, workflows are simplified and configured withinProject settings > Workflow.
Users (typically project admins) can add rules to transitions, such as clearing fields, restricting transitions, or setting field values. However, team-managed workflows do not support complex automation-like rules, such as automatically reopening Sub-tasks when a Story is reopened, as this requires interacting with related issues (Sub-tasks), which is not supported out-of-box in team-managed workflow rules.
* Explanation of the Correct Answer (Option B):
* The rule toreopen Sub-tasks when reopening Storiesrequires a workflow rule to detect the transition of a Story to an open status and then automatically transition its Sub-tasks to an open status. Team-managed workflows do not support rules that affect related issues (e.g., Sub-tasks) during a transition. This functionality requires Jira automation or a company-managed project workflow with custom post functions, which are not available in team-managed projects.
* Exact Extract from Documentation:
Configure workflows in team-managed projects
Team-managed projects use simplified workflows that allow adding rules to transitions, such as:
* Restricting transitions to specific users or roles.
* Setting or clearing field values (e.g., Assignee, Description).
* Requiring fields to be filled.Rules are limited to the issue being transitioned and cannot affect related issues (e.g., Sub-tasks, Epics). To automate actions on related issues, use Jira automation rules.Note: Team-managed workflows are project-specific and edited inProject settings > Workflow.(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Why This Fits: The rule to reopen Sub-tasks requires interacting with related issues (Sub-tasks), which is beyond the capabilities of team-managed workflow rules, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Rule to clear the Assignee when closing (Option A):
* Team-managed workflows support rules to clear fields during a transition. A rule can be added to the transition to theClosedstatus to clear theAssigneefield.
* Extract from Documentation:
You can add a rule to a transition to clear a field, such as Assignee, when moving to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to ensure only Peter can approve Stories (Option C):
* Team-managed workflows allow restricting transitions to specific users or roles. A rule can be added to the transition to anApprovedstatus to allow only Peter to perform it.
* Extract from Documentation:
Add a rule to restrict a transition to a specific user (e.g., Peter) or role, ensuring only they can move issues to a status like Approved.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to clear the Description when reopening (Option D):
* Team-managed workflows support clearing fields during transitions. A rule can be added to the transition to anOpenstatus to clear theDescriptionfield.
* Extract from Documentation:
Rules can clear fields like Description during a transition, such as when reopening an issue.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Rule to ensure only the Reporter can close bugs (Option E):
* Team-managed workflows allow restricting transitions to specific users, including the Reporter. A rule can be added to the transition to theClosedstatus for bugs to allow only the Reporter to perform it.
* Extract from Documentation:
Restrict a transition to the Reporter to ensure only they can move issues to a status like Closed.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
* Additional Notes:
* Team-managed workflows are designed for simplicity, with rules limited to the issue being transitioned. Complex logic, such as affecting Sub-tasks (Option B), requires Jira automation rules, which are separate from workflow rules.
* Peter, as a project admin in a team-managed project, can edit the workflow inProject settings > Workflow.
:
Atlassian Support Documentation:Configure workflows in team-managed projects Atlassian Support Documentation:Automate your Jira Cloud instance

NEW QUESTION # 31
Your organization has two Cloud sites. You will use the "Import Jira Cloud" feature to migrate from one Jira site to the other. What can you not import?

• A. Attachments
• B. Custom fields
• C. Automation rules
• D. Team-managed projects
• E. Deleted issues

Answer: E

Explanation:
TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including projects, issues, configurations, and attachments. However,deleted issues(Option C) cannot be imported, as they are not included in standard Jira Cloud backups or export data.
* Explanation of the Correct Answer (Option C):
* Deleted issuesare permanently removed from Jira Cloud and are not included in backups or export files created for migration. TheImport Jira Cloudfeature only imports data that exists in the source site's backup, which excludes issues that have been deleted.
* Exact Extract from Documentation:
Import Jira Cloud data
TheImport Jira Cloudfeature allows migration of data between Jira Cloud sites, including:
* Projects (company-managed and team-managed).
* Issues, comments, and attachments.
* Configurations (e.g., custom fields, workflows, automation rules).Limitations:
* Deleted issues are not included in backups or exports and cannot be imported.To import:
* Create a backup from the source site inSettings > System > Backup manager.
* UseSettings > System > Import Jira Cloudon the target site.Note: Requires Jira administrator permissions and may involve Atlassian support for full migrations.(Source:
Atlassian Support Documentation, "Import data to Jira Cloud")
* Why This Fits:Deleted issuesare not part of the data exported from the source site, making them impossible to import, so Option C is the correct answer.
* Why Other Options Are Incorrect:
* Automation rules (Option A):
* Automation rulesare included in Jira Cloud backups and can be imported to the target site using theImport Jira Cloudfeature, provided they are compatible with the target site's configuration.
* Extract from Documentation:
Automation rules are included in Jira Cloud backups and can be imported, though some rules may require reconfiguration if dependencies (e.g., custom fields) differ.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Custom fields (Option B):
* Custom fieldsare part of the configuration data in a Jira Cloud backup and are imported to the target site. Their contexts and options are preserved during migration.
* Extract from Documentation:
Custom fields, including their configurations and contexts, are included in backups and imported to the target site.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Team-managed projects (Option D):
* Team-managed projectsare fully supported in Jira Cloud backups and can be imported to the target site, including their issues, configurations, and settings.
* Extract from Documentation:
Both company-managed and team-managed projects are included in Jira Cloud backups and can be imported to another site.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Attachments (Option E):
* Attachments(media files) are included in Jira Cloud backups and can be imported to the target site, provided the backup includes media data.
* Extract from Documentation:
Attachments are included in Jira Cloud backups and imported to the target site if media import is enabled.
(Source: Atlassian Support Documentation, "Import data to Jira Cloud")
* Additional Notes:
* TheImport Jira Cloudfeature is accessed viaSettings > System > Import Jira Cloudand typically requiresJira administratorprivileges, with possible Atlassian support for full migrations.
* Deleted issues are permanently removed and cannot be recovered unless a backup from before deletion is available, but even then, they are not part of standard exports.
* Other data (e.g., automation rules, custom fields) may require post-import reconfiguration if there are incompatibilities between sites.
:
Atlassian Support Documentation:Import data to Jira Cloud
Atlassian Support Documentation:Back up Jira Cloud data

NEW QUESTION # 32
A public relations firm is using Jira to track projects by client engagement. Each new engagement with a client is tracked in a new project. Users are complaining that it is hard to navigate and search hundreds of projects.
View the Exhibit, which shows a sample of their projects on the View All Projects page.

Identify three project settings that will immediately improve the viewing of projects on this page and the search results in Issue Navigator. (Choose three.)

• A. Create project categories by client.
• B. Add project descriptions.
• C. Add client logos as project avatars.
• D. Set the project lead to the appropriate Project Administrator.
• E. Add URLs for search engine optimization.
• F. Add project tags.

Answer: B,E,F

NEW QUESTION # 33
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 everyone from the browse projects permission
• B. Remove the description field from the screen used by the view operation
• C. Hide the description field in the field configuration
• D. Remove everyone except the managers group from every project permission
• E. Remove everyone except the managers group from every project role

Answer: B

NEW QUESTION # 34
In project ENG, components are configured as shown:

The Default Assignee for ENG is the Project Lead. You select all four components on a new issue and leave Assignee as Automatic. To whom will the issue be assigned?

• A. User 1
• B. Project Lead
• C. User 2
• D. User 3
• E. Unassigned
• F. User 4

Answer: B

Explanation:
In Jira Software Cloud, theAssigneefield for a new issue can be set toAutomatic, in which case Jira determines the assignee based on the project'sDefault Assigneesetting and any component-specificDefault Assigneesettings. The issue in the ENG project has all four components selected (Activation, Bin, Cart, Database), and the Assignee is left asAutomatic. The issue will be assigned to theProject Lead(Option E) due to the rules for handling multiple components with conflicting default assignees.
* Explanation of the Correct Answer (Option E):
* Project Default Assignee: The project ENG has itsDefault Assigneeset to theProject Lead, meaning that if no component-specific assignee is determined, the issue will be assigned to the Project Lead.
* Component Default Assignees:
* Activation: Default Assignee isComponent lead(User 1).
* Bin: Default Assignee isProject default(Project Lead).
* Cart: Default Assignee isComponent lead(User 3).
* Database: Default Assignee isUnassigned.
* Automatic Assignment Logic with Multiple Components: When an issue has multiple components selected, Jira evaluates theDefault Assigneefor each component:
* If all components have the same default assignee, that user is assigned.
* If components have different default assignees (or some are unassigned), Jira falls back to the project'sDefault Assignee(Project Lead in this case).
* In this scenario:
* Activationassigns to User 1.
* Binassigns to the Project Lead (via project default).
* Cartassigns to User 3.
* Databaseassigns to Unassigned.
* Since the components have conflicting default assignees (User 1, Project Lead, User 3, Unassigned), Jira cannot resolve to a single assignee and uses the project'sDefault Assignee, which is theProject Lead.
* Exact Extract from Documentation:
Configure default assignees
TheDefault Assigneefor a project or component determines who is assigned to new issues when theAssignee field is set toAutomatic.
Multiple components:
* If an issue has multiple components with different default assignees, Jira assigns the issue to the project'sDefault Assignee.To configure:
* Go toProject settings > Componentsto set component default assignees.
* Go toProject settings > Detailsto set the project'sDefault Assignee.Note: The project's Default Assigneeis used when component assignees conflict.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Why This Fits: With conflicting default assignees across the four components, Jira assigns the issue to the project'sDefault Assignee, which is theProject Lead, making Option E the correct answer.
* Why Other Options Are Incorrect:
* User 1 (Option A):
* User 1 is the default assignee for theActivationcomponent (as the Component lead).
However, with multiple components selected and different assignees (User 1, Project Lead, User 3, Unassigned), Jira falls back to the project'sDefault Assignee(Project Lead), not User 1.
* Extract from Documentation:
If multiple components have different default assignees, the project'sDefault Assigneeis used, not a component-specific assignee.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* User 2 (Option B):
* User 2 is the Component lead forBin, but the default assignee forBinis set toProject default(Project Lead), not the Component lead. Even if it were User 2, the conflicting assignees across components would result in the Project Lead being assigned.
* Extract from Documentation:
TheProject defaultsetting for a component assigns issues to the project'sDefault Assignee, not the Component lead.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* User 3 (Option C):
* User 3 is the default assignee for theCartcomponent (as the Component lead). However, the conflicting assignees across components (User 1, Project Lead, User 3, Unassigned) result in the Project Lead being assigned, not User 3.
* Extract from Documentation:
Conflicting component assignees result in the project'sDefault Assigneebeing used.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* User 4 (Option D):
* User 4 is the Component lead forDatabase, but the default assignee forDatabaseis Unassigned, not User 4. Even if it were User 4, the conflicting assignees would result in the Project Lead being assigned.
* Extract from Documentation:
TheUnassigneddefault assignee for a component does not override the project'sDefault Assigneein conflicts.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
* Unassigned (Option F):
* While theDatabasecomponent has a default assignee ofUnassigned, the presence of other components with different assignees (User 1, Project Lead, User 3) creates a conflict, and Jira assigns the issue to the Project Lead, notUnassigned.
* Extract from Documentation:
Unassignedas a default assignee is overridden by the project'sDefault Assigneein cases of conflict.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
* Additional Notes:
* TheDefault Assigneefor the project is set inProject settings > Details, and component-specific default assignees are set inProject settings > Components.
* The user creating the issue must have theAssign Issuespermission, and the Project Lead must have theAssignable Userpermission to be assigned.
* If only one component were selected (e.g., Activation), the issue would be assigned to User 1, but selecting all four components triggers the conflict resolution to the Project Lead.
:
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 # 35
Users complain that they can see a particular custom field in all company-managed projects except one.
Identify two possible reasons. (Choose two.)

• A. Groups
• B. Validator
• C. Issue layout
• D. Project roles
• E. Security levels
• F. Step property
• G. Screen

Answer: C,G

Explanation:
The issue is that a custom field is visible in all company-managed projects except one, indicating a project- specific configuration is preventing the field from being displayed. The two possible reasons areScreen (Option D) andIssue layout(Option E), as these configurations control whether a field appears in a project's issue operations or view.
* Explanation of the Correct Answers:
* Screen (Option D):
* In company-managed projects,screensdetermine which fields are displayed during issue operations (Create, Edit, View) for specific issue types, as defined by thescreen scheme. If the custom field is not included on the screen(s) used by the problematic project's issue types, users will not see the field when creating, editing, or viewing issues in that project.
This could explain why the field is missing in one project but visible in others.
* Exact Extract from Documentation:
Configure screens in company-managed projects
Screens define which fields are available during issue operations (Create, Edit, View). Each project uses a screen scheme to map screens to issue types and operations.
If a field is not on a project's screen:
* Users cannot see or interact with the field in that project.To check:
* Go toProject settings > Screens.
* Verify if the custom field is included on the relevant screens.Note: A field must be on the screen to be visible during issue operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Why This Fits: If the custom field is not on the screen(s) used by the project, it will not be visible, makingScreena possible reason for the issue.
* Issue layout (Option E):
* Theissue layoutin a company-managed project controls which fields are displayed, hidden, or placed in the context panel in the issue view. If the custom field is moved to theHidden fieldssection in the issue layout for the problematic project, users will not see it when viewing issues, even if the field is on the screen and contains data. This could explain the field's absence in one project.
* Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts determine which fields are displayed or hidden in the issue view.
To hide a field:
* Go toProject settings > Issue layout.
* Move the field to theHidden fieldssection.Impact: Hidden fields are not shown in the issue view, even if they areon the screen and have values.Note: Issue layouts are project-specific and can differ between projects.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Why This Fits: If the custom field is hidden in the issue layout for the problematic project, it will not be visible in the issue view, makingIssue layouta possible reason.
* Why Other Options Are Incorrect:
* Groups (Option A):
* Groups are used in permission schemes or field configurations to control access or behavior, but they do not directly determine field visibility. If the field is visible in other projects, the issue is not group-related, as groups apply globally or via schemes shared across projects.
* Extract from Documentation:
Groups are used for permissions or field restrictions, not for controlling field visibility on screens or layouts.
(Source: Atlassian Support Documentation, "Manage groups in Jira Cloud")
* Project roles (Option B):
* Project roles are used in permission schemes to grant permissions (e.g.,Edit Issues). They do not control whether a field is displayed on a screen or in the issue layout. The issue is about visibility, not permissions.
* Extract from Documentation:
Project roles manage permissions, not field visibility. Check screens or issue layouts for display issues.
(Source: Atlassian Support Documentation, "Manage project roles")
* Security levels (Option C):
* Security levels (part of an issue security scheme) restrict which issues a user can view, not which fields are displayed within an issue. If users can see issues but not the field, security levels are not the cause.
* Extract from Documentation:
Issue security levels control issue visibility, not field visibility within an issue.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
* Validator (Option F):
* Validators ensure conditions are met before a workflow transition (e.g., a field is filled).
They do not affect whether a field is visible in the issue view or during operations.
* Extract from Documentation:
Validators enforce conditions during transitions, not field visibility.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Step property (Option G):
* Step properties (workflow properties) control behaviors like editability in a status (e.g.,jira.
issue.editable). They do not directly control field visibility on screens or in the issue view.
* Extract from Documentation:
Workflow properties manage status behaviors, not field visibility. Use screens or issue layouts for display issues.
(Source: Atlassian Support Documentation, "Use workflow properties")
* Additional Notes:
* To resolve the issue, check:
* Project settings > Screens: Ensure the custom field is on the relevant screen(s) for the project's issue types.
* Project settings > Issue layout: Verify the field is not in theHidden fieldssection.
* These configurations requireproject admin(for issue layout) orJira administrator(for screens) privileges.
* Other potential causes (not listed) includefield configurations(if the field is hidden for all issue types in the project), but screens and issue layouts are the most direct reasons.
:
Atlassian Support Documentation:Configure screens in Jira Cloud
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Manage groups in Jira Cloud
Atlassian Support Documentation:Manage project roles
Atlassian Support Documentation:Configure issue security schemes
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Use workflow properties

NEW QUESTION # 36
You need to identify issues that meet both conditions:
* Tom set the priority value to "Highest" sometime this month.
* The priority value may or may not be "Highest" now.
Which JQL query returns the expected results?

• A. priority was Highest by tom after startOfMonth()
• B. priority was Highest by tom and (priority = Highest by tom after startOfMonth() or priority != Highest)
• C. priority changed to Highest by tom before endOfMonth()
• D. priority was Highest by tom during (startOfMonth(), endOfMonth()) and priority = Highest or priority !
  = Highest

Answer: A

Explanation:
To find issues where Tom set theprioritytoHighestduring the current month, regardless of the current priority value, the JQL query must use theWASoperator to check the historical priority value and theBYclause to specify the user (Tom), along with a time range for the current month. The correct query ispriority was Highest by tom after startOfMonth()(Option B).
* Explanation of the Correct Answer (Option B):
* The conditionTom set the priority value to "Highest" sometime this monthrequires checking the issue's change history for thepriorityfield. TheWASoperator checks if a field had a specific value at some point, and theBYclause filters for changes made by a specific user (Tom). Theafter startOfMonth()clause ensures the change occurred within the current month (from the first day of the month to the present).
* The conditionthe priority value may or may not be "Highest" nowmeans the query should not filter based on the current priority value, whichOption Bcorrectly avoids by not including a current-state condition (e.g.,priority = Highest).
* The querypriority was Highest by tom after startOfMonth()returns issues where Tom changed the priority toHighestafter the start of the current month, satisfying both conditions.
* Exact Extract from Documentation:
Advanced searching - operators reference
TheWASoperator checks if a field had a specific value at some point in the issue's history.
* priority was Highest by tom after startOfMonth() returns issues where thepriorityfield was set toHighestby the usertomafter the start of the current month.Note: TheWASoperator does not check the current field value, only historical values. Useafterto specify a time range.(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Why This Fits: The query usesWASto check historical priority changes by Tom toHighestwithin the current month, without restricting the current priority, making Option B the correct answer.
* Why Other Options Are Incorrect:
* priority changed to Highest by tom before endOfMonth() (Option A):
* TheCHANGEDoperator checks for transitions in field values, butbefore endOfMonth() includes all changes up to the end of the current month, including past months, which is too broad. The query needs to limit changes to the current month (e.g.,after startOfMonth()).
* Extract from Documentation:
TheCHANGEDoperator requiresFROMandTOclauses for specific transitions.before endOfMonth() includes all prior changes, not just the current month.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* priority was Highest by tom during (startOfMonth(), endOfMonth()) and priority = Highest or priority != Highest (Option C):
* Theduring (startOfMonth(), endOfMonth())clause is valid for time ranges, but the additional conditionpriority = Highest or priority != Highestis redundant and always true (it includes all issues). However,duringis less precise thanafter startOfMonth(), as it may exclude changes on the last day of the month depending on timezone handling. This makes the query less optimal.
* Extract from Documentation:
Theduringclause defines a time range but may have edge cases with end dates.after startOfMonth()is simpler for current-month filtering.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* priority was Highest by tom and (priority = Highest by tom after startOfMonth() or priority != Highest) (Option D):
* The clausepriority = Highest by tom after startOfMonth()is invalid, as theBYclause cannot be used with current-state conditions likepriority = Highest. TheWASoperator already covers the historical change, and the additionalor priority != Highestis unnecessary and complicates the query.
* Extract from Documentation:
TheBYclause is used withWASorCHANGED, not with current-state conditions likepriority = Highest.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* Additional Notes:
* The query assumesHighestis a valid priority value (check inSettings > Issues > Priorities).
* The query can be tested inIssues > Search for issuesand saved as a filter.
* Ensure Tom's user account is correctly referenced (e.g., username or user ID) and that the user running the query hasBrowse Projectspermission.
:
Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Search for issues using JQL

NEW QUESTION # 37
Your marketing group is using Jira to track media print advertisements. They would like to track TV and radio commercials as well.
The same team handles all three formats, but each format requires a unique workflow. The team would like to keep everything on the same dashboard, and they will also be using the same permissions, notifications and screens.
Without using third-party apps, how should you configure Jira to meet these requirements?

• A. Create two new projects for TV and Radio.
• B. Create a sub-component hierarchy.
• C. Use issue types of Print, Radio and TV in the existing project.
• D. Add TV and Radio into the existing project as components.
• E. Copy the existing permissions and notification schemes, and associate them with new projects for TV and Radio.
• F. Clone the existing project and key for TV and Radio.

Answer: A

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

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

Answer: E

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 # 39
You want to restore a Cloud instance with another Jira Cloud backup. Which is not a valid option?

• A. Import apps
• B. Merge with existing Cloud users
• C. Overwrite existing Cloud users
• D. Import media
• E. Import data

Answer: A

Explanation:
Restoring a Jira Cloud instance with a backup involves importing data, users, and media from thebackup file.
Valid options include importing data, merging or overwriting users, and importing media. However, importing apps(Option B) is not a valid option, as apps are not included in Jira Cloud backups and must be reinstalled separately.
* Explanation of the Correct Answer (Option B):
* Jira Cloud backups include issues, configurations, users, and media (e.g., attachments) but do not include installed apps or their data. Restoring a backup does not involve importing apps, as apps must be reinstalled from the Atlassian Marketplace and configured separately.
* Exact Extract from Documentation:
Restore Jira Cloud from a backup
A Jira Cloud backup includes:
* Issues and their history.
* Configurations (e.g., workflows, schemes).
* Users and groups.
* Media (e.g., attachments).When restoring:
* Import data: Restore issues and configurations.
* Merge with existing Cloud users: Add users from the backup without overwriting existing users.
* Overwrite existing Cloud users: Replace existing users with those from the backup.
* Import media: Restore attachments and other media.Note: Apps and their data are not included in backups. Reinstall apps from the Atlassian Marketplace after restoring.(Source:
Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Why This Fits:Importing appsis not a valid option for restoring a Jira Cloud backup, as apps are excluded from backups, making Option B the correct answer.
* Why Other Options Are Incorrect:
* Import data (Option A):
* Importing data is a valid option, as it restores issues, configurations, and other Jira data from the backup.
* Extract from Documentation:
Import data to restore issues, projects, and configurations from a Jira Cloud backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Merge with existing Cloud users (Option C):
* Merging users is a valid option, allowing users from the backup to be added to the existing Cloud instance without overwriting current users.
* Extract from Documentation:
ChooseMerge with existing Cloud usersto add users from the backup while preserving existing user accounts.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Overwrite existing Cloud users (Option D):
* Overwriting users is a valid option, replacing existing users with those from the backup.
* Extract from Documentation:
ChooseOverwrite existing Cloud usersto replace current users with those from the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Import media (Option E):
* Importing media is a valid option, restoring attachments and other media files from the backup.
* Extract from Documentation:
Import media to restore attachments and other files included in the backup.
(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")
* Additional Notes:
* Restoring a Jira Cloud backup requiresJira administratorororganization adminprivileges and is done viaSettings > System > Restore.
* After restoring, apps must be reinstalled, and their data may need to be reimported if the app supports it.
:
Atlassian Support Documentation:Restore your Jira Cloud site from a backup Atlassian Support Documentation:Manage apps in Jira Cloud

NEW QUESTION # 40
Which configurations do Not have any impact on email notifications sent to users

• A. Version Configurations
• B. Workflow post functions
• C. Premission Schemes
• D. Custom Events

Answer: A

Explanation:
A). Incorrect. Workflow post functions fire events. These can be mapped to recipients in a notification scheme.
B). Correct. Versions can neither be configured to send notifications nor will they trigger notifications.
C). Incorrect. Notification schemes can pick up custom events if they are configured to be fired in a workflow.
This way a custom event can impact notifications.
D). Incorrect. A permission scheme is related to notifications. Users will only receive notifications for projects and issues they can assess.
E). Incorrect. Saved filters can be used for filter subscriptions to send out filter results. So they are related to notifications

NEW QUESTION # 41
A dashboard displays an Issue Statistics gadget as shown.

The dashboard owner wants to change the order of the statuses shown in the gadget to appear as follows.
1. To Do
2. In Progress
3. Ready For QA
4. Blocked
5. Rejected
6. Done
Which action will permanently arrange the statuses into the required order?

• A. Change the category of the statuses.
• B. Change the Sort Direction option in the gadget to Ascending.
• C. Reorder the statues on the Status administration page.
• D. Add numbers to the status names to allow them to be sorted in numerical order.
• E. Change the gadget Sort By field to Total.

Answer: D

Explanation:
Reference: https://community.atlassian.com/t5/Jira-questions/How-to-change-order-of-statuses-in-a-Two- Dimension-filter/qaq-p/320423

NEW QUESTION # 42
You want to introduce Jira to your small non-profit organization.
Since you are unsure of the optimal deployment option you have gathered some requirements:
- You need to manage a team of up to 15 employees.
- You need to be able to track a backlog of staff action items.
- You want to easily visualize the progress of ongoing work.
The solution must require minimal administration since your organization only has a part-time IT volunteer.
What solution is most appropriate for your organization?

• A. Jira Service Desk Data Center
• B. Jira Service Desk Cloud
• C. Jira Software Data Center
• D. Jira Core Server

Answer: B

NEW QUESTION # 43
You are adding a user to Jira software using the invite users method in user management Which setting on the page guarantees the user access to Jira software (Choose one)

• A. Group membership
• B. Product access
• C. Email domains
• D. Email address

Answer: B

NEW QUESTION # 44
......

Truly Beneficial For Your ATLASSIAN Exam: https://www.actualpdf.com/ACP-120_exam-dumps.html

View All ACP-120 Actual Exam Questions, Answers and Explanations for Free: https://drive.google.com/open?id=11Re8lhIJLcy8ehcxQF9_ckTtH0DaqNBP