Mar 29, 2026 Step by Step Guide to Prepare for ACP-120 Exam BrainDumps
Jira Administrator ACP-120 Real Exam Questions and Answers FREE Updated on 2026
The Jira Cloud Administrator certification exam covers a wide range of topics related to Jira Cloud administration. These topics include user management, project and issue configuration, workflow management, and integrations with other tools. ACP-120 exam is designed to test an individual’s ability to manage Jira Cloud effectively and efficiently, ensuring that teams can collaborate and deliver high-quality work.
ATLASSIAN ACP-120 (Jira Cloud Administrator) Certification Exam is a renowned certification program designed for professionals who want to demonstrate their expertise in administering Jira Cloud. Jira Cloud Administrator certification exam is administered by ATLASSIAN, a leading provider of software tools and solutions. ACP-120 exam is designed to assess the knowledge and skills of candidates in administering Jira Cloud and providing solutions to common issues that arise in the platform.
ATLASSIAN ACP-120 (Jira Cloud Administrator) Certification Exam is designed for individuals who are interested in becoming proficient in administering Jira Cloud. Jira is a project management tool designed to help teams track and manage their work. As a Jira Cloud Administrator, you will be responsible for configuring and maintaining Jira Cloud for your organization. The ACP-120 certification exam covers a range of topics related to Jira Cloud administration, including user management, project management, and system administration.
NEW QUESTION # 24
Gary is no longer receiving notifications when his colleagues modify issues that he is watching. You already verified that watchers should be notified. Which personal setting did Gary update?
- A. You make changes to the issue
- B. Email notifications format
- C. Notifications for relevant issues
- D. Watch your issues
Answer: C
Explanation:
The scenario indicates that Gary is no longer receiving notifications for issues he is watching, despite the notification scheme being correctly configured to notify watchers. This suggests that Gary has modified a personal setting that controls whether he receives notifications for watched issues. Based on Jira Software Cloud documentation, the relevant personal setting is "Notifications for relevant issues" (Option D).
Explanation of the Correct Answer (Option D):
In Jira Cloud, users can control their notification preferences through their personal settings in the user profile. The setting "Notifications for relevant issues" determines whether a user receives email notifications for events they are associated with, such as being a watcher of an issue.
If Gary disabled this setting (i.e., turned off notifications for relevant issues), he would stop receiving notifications for issues he is watching, even if the project's notification scheme is configured to notify watchers.
Exact Extract from Documentation:
Manage your Jira notification emails
You can choose whether you want to receive email notifications about activity in your Jira products. For example, you can choose to receive emails when you're added as a watcher to an issue, or when an issue you' re working on is updated.
To manage your notification preferences:
From your Jira site, select your profile picture in the top right and select Personal settings.
Under Email notifications, select whether you'd like to receive notifications for relevant issue activity.
On: Receive emails for issue activity you're associated with, like when you're a watcher, assignee,or reporter.
Off: Don't receive emails for issue activity, even if you're associated with the issue.
Note: This setting doesn't affect emails about your account, like password resets. To manage those, update your Atlassian account preferences.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails") Why This Fits: The documentation explicitly states that turning off the "Notifications for relevant issues" setting prevents a user from receiving emails for issue activity they are associated with, including as a watcher. Since Gary is no longer receiving notifications for watched issues, this is the most likely setting he updated.
Why Other Options Are Incorrect:
Watch your issues (Option A):
This option refers to a setting that automatically adds a user as a watcher to issues they create or are assigned to. However, the question states that Gary is already watching the issues (since he was receiving notifications previously), so this setting is not relevant. Disabling this setting would only prevent Gary from being automatically added as a watcher to new issues, not stop notifications for issues he is already watching.
Extract from Documentation:
Watching issues
You can watch an issue to receive email notifications whenever it's updated. By default, you may automatically watch issues you create or are assigned to, depending on your notification settings.
To change your auto-watch settings:
Select your profile picture and then select Settings.
Under Jira settings, select whether to automatically watch issues you create or are assigned to.
(Source: Atlassian Support Documentation, "Watch issues and manage your watchlist") You make changes to the issue (Option B):
This option is not a standard personal setting in Jira Cloud. There is no user-level setting that specifically toggles notifications based on whether the user themselves makes changes to an issue. Notifications are controlled by the notification scheme and the user's email notification preferences, not by a setting tied to the user's own changes.
Email notifications format (Option C):
This setting allows users to choose the format of email notifications (e.g., HTML or text). Changing this setting affects how notifications are displayed, not whether they are sent. Therefore, it would not cause Gary to stop receiving notifications entirely.
Extract from Documentation:
Email format
You can choose whether notifications are sent in HTML or text format. This is managed in your Atlassian account settings, under email preferences.
(Source: Atlassian Support Documentation, "Manage your Atlassian account") Additional Notes:
The question specifies that the notification scheme is correctly configured to notify watchers, so the issue lies with Gary's personal settings, not the project or system configuration.
The "Notifications for relevant issues" setting is a global toggle that affects all notifications for issue activity a user is associated with, making it the most direct cause of Gary's issue.
References:
Atlassian Support Documentation: Manage your Jira notification emails
Atlassian Support Documentation: Watch issues and manage your watchlist Atlassian Support Documentation: Manage your Atlassian account
NEW QUESTION # 25
All company-managed projects share the same permission scheme and workflow scheme. New requirements state:
* Only auditors should be able to use the 'Needs Audit' workflow transition.
* All auditors work across all the projects.
How should auditors be configured?
- A. As a Group custom field
- B. As a group
- C. As single users
- D. As a User custom field
Answer: B
Explanation:
To restrict theNeeds Auditworkflow transition to auditors across all company-managed projects, which share the same permission and workflow schemes, auditors should be configuredas a group(Option B). This allows the group to be referenced in a workflow condition to limit access to the transition efficiently across all projects.
* Explanation of the Correct Answer (Option B):
* The requirement to restrict theNeeds Audittransition to auditors can be achieved by adding a conditionto the transition in the shared workflow scheme. A common condition, such asUser Is In Group, restricts the transition to members of a specific group.
* Since all projects share the same workflow scheme, configuring auditors as a group (e.g.,
"Auditors") allows you to create the group once, add all auditors to it, and reference it in the workflow condition. This ensures that only auditors can use theNeeds Audittransition across all projects.
* Exact Extract from Documentation:
Configure workflow conditions
Conditions restrict who can perform a workflow transition in a company-managed project.
To restrict a transition:
* Go toSettings > Issues > Workflows.
* Edit the workflow and select theNeeds Audittransition.
* Add a condition, such asUser Is In Group, and select the group (e.g., Auditors).Note:
Using a group is efficient for managing permissions or conditions across multiple projects with a shared workflow scheme.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Why This Fits: Configuring auditors as a group allows a single workflow condition to restrict the Needs Audittransition to group members across all projects, meeting both requirements efficiently.
* Why Other Options Are Incorrect:
* As a User custom field (Option A):
* AUser custom field(e.g., User Picker) stores a single user for an issue and is not suitable for defining a set of users who can perform a workflow transition. Workflow conditions cannot reference custom fields to restrict transitions.
* Extract from Documentation:
User custom fields store user data for issues but cannot be used in workflow conditions to restrict transitions.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* As a Group custom field (Option C):
* AGroup custom field(e.g., Group Picker) stores a group for an issue, but workflow conditions typically reference groups directly, not group picker fields. This approach is unnecessary and overly complex for restricting transitions.
* Extract from Documentation:
Group custom fields are not used for workflow conditions. Use direct group references for transition restrictions.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* As single users (Option D):
* Configuring auditors as individual users in a workflow condition (e.g.,User Is In Any Users) is inefficient, as it requires listing each auditor manually. This approach does not scale well for multiple auditors working across all projects and is prone to maintenance issues if auditors change.
* Extract from Documentation:
Listing individual users in conditions is not recommended for scalability. Use groups for managing multiple users across projects.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
* Additional Notes:
* Steps to configure:
* Create an "Auditors" group inSettings > User management > Groups.
* Add all auditors to the "Auditors" group.
* Edit the shared workflow inSettings > Issues > Workflows.
* Add aUser Is In Groupcondition to theNeeds Audittransition, selecting the "Auditors" group.
* Configuring the group and workflow requiresJira administratorprivileges.
* The shared workflow scheme ensures the condition applies to all projects.
:
Atlassian Support Documentation:Configure advanced work item workflows
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Manage groups in Jira Cloud
NEW QUESTION # 26
Jon needs to create groups and manage membership in groups. Which administrator privilege does Jon need?
- A. Project administrator
- B. System administrator
- C. Product Admin role for Jira
- D. Jira administrator
- E. Organization admin
Answer: D
Explanation:
Creating groups and managing group membership in Jira Software Cloud are system-level tasks that require theJira administratorprivilege. This privilege allows Jon to access user management settings and perform group-related actions.
* Explanation of the Correct Answer (Option D):
* TheJira administratorprivilege grants users the ability to manage global settings, including creating groups and managing their membership. This includes adding or removing users from groups, which is necessary for Jon's requirements.
* Exact Extract from Documentation:
Jira administrator permissions
Jira administrators can manage global settings, including:
* Creating and deleting groups.
* Adding or removing users from groups.
* Managing global permissions and user access.To create or manage groups:
* Go toSettings > User management > Groups.
* Create a new group or edit existing group membership.Note: Only Jira administrators or organization admins with user management permissions can perform these actions.(Source:
Atlassian Support Documentation, "Manage groups in Jira Cloud")
* Why This Fits: TheJira administratorprivilege directly enables Jon to create groups and manage their membership, making Option D the correct choice.
* Why Other Options Are Incorrect:
* Organization admin (Option A):
* Organization admins manage the Atlassian organization, including user access to products and billing. While they can manage users and groups at the organization level, creating groups specifically in Jira requiresJira administratorprivileges unless the organization admin also has this role.
* Extract from Documentation:
Organization admins manage user access, billing, and security at the Atlassian organization level. Managing Jira-specific groups requires Jira administrator privileges.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
* Product Admin role for Jira (Option B):
* TheProduct Adminrole for Jira grants access to manage product-specific settings, such as user access to Jira Software. However, creating and managing groups is a system-level task that requiresJira administratorprivileges.
* Extract from Documentation:
Product admins manage user access to specific products (e.g., Jira Software). Group management requires Jira administrator or organization admin privileges.
(Source: Atlassian Support Documentation, "Manage product access")
* System administrator (Option C):
* The termsystem administratoris not a standard role in Jira Cloud. In some contexts, it may refer toJira administratorsororganization admins, but it is not a distinct privilege for group management.
* Extract from Documentation:
Jira Cloud uses roles like Jira administrator and organization admin. There is no distinct "system administrator" role for group management.
(Source: Atlassian Support Documentation, "Manage users and groups")
* Project administrator (Option E):
* Project administrators manage settings for specific projects (e.g., permissions, components) but cannot create or manage groups, as these are global settings.
* Extract from Documentation:
Project administrators manage project-specific settings but cannot access global settings like user or group management.
(Source: Atlassian Support Documentation, "Manage project permissions")
* Additional Notes:
* Jon's tasks require access toSettings > User management > Groups, which is restricted toJira administrators.
* If Jon is also an organization admin, he might have overlapping permissions, but theJira administratorrole is the most direct for group management in Jira.
:
Atlassian Support Documentation:Manage groups in Jira Cloud
Atlassian Support Documentation:Manage your Atlassian organization
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project permissions
NEW QUESTION # 27
You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.
- A. resolution = EMPTY AND assignee not in membersOf("jira-software-users")
- B. statusCategory != Done AND assignee not in organizationMembers()
- C. resolution is EMPTY AND assignee in inactiveUsers()
- D. statusCategory = Done AND assignee not in activeUsers()
- E. resolution = Unresolved AND assignee changed to inactive
Answer: C
Explanation:
To find unresolved issues assigned to suspended users in Jira Software Cloud, the JQL query must check for issues with no resolution (unresolved) and an assignee who is inactive (suspended). The correct query is resolution is EMPTY AND assignee in inactiveUsers()(Option A), as it uses the appropriate field ( resolution) and function (inactiveUsers()) to identify these issues.
* Explanation of the Correct Answer (Option A):
* Unresolved issues: In Jira, an issue is considered unresolved if itsresolutionfield is empty (i.e., not set to Resolved, Done, or similar). The JQL clauseresolution is EMPTYidentifies unresolved issues.
* Suspended users: Suspended users are those whose accounts are inactive (e.g., deactivated or removed from the organization). TheinactiveUsers()function returns all inactive users in the Jira instance. The clauseassignee in inactiveUsers()filters for issues assigned to these users.
* Combined query:resolution is EMPTY AND assignee in inactiveUsers()returns all unresolved issues assigned to inactive users.
* Exact Extract from Documentation:
Search for issues using JQL
* resolution is EMPTY: Finds issues with no resolution set (unresolved issues).
* assignee in inactiveUsers(): Finds issues assigned to users who are inactive (e.g., deactivated or suspended).Example:
* resolution is EMPTY AND assignee in inactiveUsers() returns unresolved issues assigned to inactive users.Note: TheinactiveUsers()function is specific to Jira Cloud and includes users who are no longer active in the instance.(Source: Atlassian Support Documentation,
"Advanced searching - functions reference")
* Why This Fits: The query correctly usesresolution is EMPTYfor unresolved issues and inactiveUsers()for suspended users, making Option A the correct answer.
* Why Other Options Are Incorrect:
* statusCategory != Done AND assignee not in organizationMembers() (Option B):
* statusCategory != Donechecks the status category (e.g., To Do, In Progress) but is less precise thanresolution is EMPTY, as some statuses in non-Done categories may still be resolved.assignee not in organizationMembers()is incorrect, asorganizationMembers() is not a valid JQL function in Jira Cloud, and it would not specifically target inactive users.
* Extract from Documentation:
statusCategory != Doneis broader thanresolution is EMPTYand may include resolved issues. No organizationMembers()function exists in JQL.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* resolution = Unresolved AND assignee changed to inactive (Option C):
* resolution = Unresolvedis incorrect, asUnresolvedis not a valid resolution value; use resolution is EMPTYinstead.assignee changed to inactiveis invalid, aschanged to inactiveis not a supported JQL operator for theassigneefield.
* Extract from Documentation:
Useresolution is EMPTYfor unresolved issues. Thechangedoperator does not supportinactiveas a value for assignee.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
* statusCategory = Done AND assignee not in activeUsers() (Option D):
* statusCategory = Doneis the opposite of what is needed, as it selects resolved or completed issues, not unresolved ones.assignee not in activeUsers()might include inactive users but is less precise thaninactiveUsers(), and thestatusCategoryclause makes the query incorrect.
* Extract from Documentation:
statusCategory = Doneselects issues in completed statuses, not unresolved issues. UseinactiveUsers()for precise inactive user filtering.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
* resolution = EMPTY AND assignee not in membersOf("jira-software-users") (Option E):
* resolution = EMPTYis correct, butassignee not in membersOf("jira-software-users")is incorrect, asjira-software-usersis a default group for active users with Jira Software access, not a reliable indicator of suspended users. This would exclude active users in the group, not specifically target inactive ones.
* Extract from Documentation:
ThemembersOf()function checks group membership, not user activity status. UseinactiveUsers()to find suspended or deactivated users.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
* Additional Notes:
* The query can be tested inIssues > Search for issuesand saved as a filter if needed.
* inactiveUsers()is specific to Jira Cloud and includes users who are deactivated or removed from the organization.
* Ensure the user running the query hasBrowse Projectspermission for the relevantprojects.
:
Atlassian Support Documentation:Advanced searching - functions reference Atlassian Support Documentation:Advanced searching - fields reference Atlassian Support Documentation:Advanced searching - operators reference Atlassian Support Documentation:Search for issues using JQL
NEW QUESTION # 28
ALPHA team handles alerts in the ALPHA project in alpha.atlassian.net. They often view and comment on bugs in the BETA project on beta.atlassian.net. The team can link ALPHA issues to other ALPHA issues but not to BETA issues. What needs to be configured?
- A. Application access
- B. Approved domains
- C. Global permissions
- D. Application links
Answer: D
Explanation:
The ALPHA team can view and comment on bugs in the BETA project (beta.atlassian.net) but cannot link ALPHA issues (alpha.atlassian.net) to BETA issues. This indicates a cross-site interaction issue, specifically with issue linking between two Jira Cloud sites. The solution is to configureapplication links(Option A) to enable linking between the ALPHA and BETA projects across the two sites.
* Explanation of the Correct Answer (Option A):
* Application linksallow Jira Cloud sites to communicate with each other, enabling features like issue linking between projects on different sites (e.g., alpha.atlassian.net and beta.atlassian.net).
Without an application link between the two sites, users cannot create links from ALPHA issues to BETA issues, even if they have access to view and comment on BETA issues. Configuring an application link between the two sites will enable cross-site issue linking.
* Exact Extract from Documentation:
Configure application links in Jira Cloud
Application links connect Jira Cloud sites or other Atlassian products, enabling features like cross-site issue linking.
To create an application link:
* Go toSettings > Products > Application links.
* Enter the URL of the target site (e.g., beta.atlassian.net).
* Follow the prompts to authenticate and configure the link.Impact:
* Allows linking issues between projects on different Jira Cloud sites.
* Requires permissions to view issues in the target project.Note: Requires Jira administrator permissions on both sites.(Source: Atlassian Support Documentation, "Configure application links in Jira Cloud")
* Why This Fits: The inability to link ALPHA issues to BETA issues is due to the lack of an application link between alpha.atlassian.net and beta.atlassian.net. Configuring an application link resolves this, making Option A the correct answer.
* Why Other Options Are Incorrect:
* Global permissions (Option B):
* Global permissions(e.g., Administer Jira, Browse Users) control system-wide actions within a single Jira site. They do not govern cross-site interactions like issue linking between two separate Jira Cloud sites.
* Extract from Documentation:
Global permissions manage actions within a single Jira site, not cross-site features like issue linking.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Application access (Option C):
* Application accessrefers to granting users access to specific Atlassian products (e.g., Jira Software, Confluence) within an organization. The ALPHA team can already view and comment on BETA issues, indicating they have access to beta.atlassian.net. Application access does not control issue linking between sites.
* Extract from Documentation:
Application access grants users product access but does not enable cross-site features like issuelinking.
(Source: Atlassian Support Documentation, "Manage product access")
* Approved domains (Option D):
* Approved domainsare used to manage cross-site authentication and security for Atlassian organizations, ensuring users from approved domains can access linked sites. While this might be relevant for user authentication, the team's ability to view and comment on BETA issues suggests authentication is not the issue. The specific problem is issue linking, which requires an application link.
* Extract from Documentation:
Approved domains manage cross-site authentication, not specific features like issue linking. Use application links for cross-site interactions.
(Source: Atlassian Support Documentation, "Manage approved domains")
* Additional Notes:
* Steps to configure:
* On alpha.atlassian.net, go toSettings > Products > Application links.
* Add a link to beta.atlassian.net and authenticate as needed.
* Repeat on beta.atlassian.net to link to alpha.atlassian.net (bidirectional link).
* Configuring application links requiresJira administratorprivileges on both sites.
* Ensure the ALPHA team has permissions to create links (Link Issuespermission) in the ALPHA project and view issues in the BETA project.
:
Atlassian Support Documentation:Configure application links in Jira Cloud Atlassian Support Documentation:Manage global permissions Atlassian Support Documentation:Manage product access Atlassian Support Documentation:Manage approved domains
NEW QUESTION # 29
The configuration details of an SMTP Mail Server of a Jira instance are shown below.
The configuration hasn't been changed in the last 24 months.
Currently emails are no longer being sent and the failed notifications can be seen in the Mail Error Queue.
What is the likely cause of the failure?
- A. The user jira has no valid Jira license.
- B. Email volume has increased and the Timeout is too low.
- C. The Jira license has expired.
- D. The database and/or server disk is full.
- E. The SMTP password has expired.
Answer: C
NEW QUESTION # 30
You want to create a new link type that looks identical in linked issues. How can you achieve this?
- A. Disable bidirectional linking globally.
- B. Create the link type with no inward link description.
- C. Choose the same name for the inward and outward link descriptions.
- D. Create the link type with no outward link description.
Answer: C
Explanation:
To create a new link type in Jira Software Cloud that looks identical in linked issues (i.e., the link description is the same regardless of the direction of the link), you shouldchoose the same name for the inward and outward link descriptions(Option C). This ensures that the link type appears with the same description in both the source and target issues.
* Explanation of the Correct Answer (Option C):
* In Jira,issue link typesdefine relationships between issues, with anoutwarddescription(for the source issue) and aninward description(for the target issue). For example, a "Blocks" link type might have "blocks" as the outward description and "is blocked by" as the inward description. To make the link type look identical in both linked issues, you set the same description for both the inward and outward links (e.g., "relates to" for both). This results in the link appearing as "relates to" in both issues, regardless of which issue is the source or target.
* Exact Extract from Documentation:
Manage issue link types
Issue link types define relationships between issues, with separateoutwardandinwarddescriptions.
To create a link type:
* Go toSettings > Issues > Issue linking.
* Add a new link type.
* Enter aName(e.g., Relates), and set theOutward descriptionandInward description(e.g., both as "relates to").Impact: If the inward and outward descriptions are the same, the link appears identical in both linked issues.Note: Requires Jira administrator permissions.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Why This Fits: Setting the same name for the inward and outward link descriptions ensures the link type looks identical in linked issues, meeting the requirement and making Option C the correct answer.
* Why Other Options Are Incorrect:
* Create the link type with no inward link description (Option A):
* Jira requires both aninwardandoutwarddescription when creating a link type. Leaving the inward description blank is not allowed, and even if possible, it would not make the link look identical in both issues-it would result in an empty or default description in the target issue.
* Extract from Documentation:
Bothinwardandoutwarddescriptions are required when creating a link type. Blank descriptions are not supported.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Disable bidirectional linking globally (Option B):
* There is no concept ofbidirectional linkingin Jira's issue linking system, and no global setting exists to disable it. Issue links are inherently bidirectional (a link from issue A to B implies a reverse link from B to A), and the descriptions control how they appear.
Disabling linking is not an option.
* Extract from Documentation:
Issue links are bidirectional, with inward and outward descriptions defining the relationship. No global setting exists to disable bidirectionality.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Create the link type with no outward link description (Option D):
* Similar to Option A, Jira requires anoutwarddescription when creating a link type.
Leaving it blank is not allowed, and it would not achieve identical appearance in both issues, as the source issue would lack a description.
* Extract from Documentation:
Bothoutwardandinwarddescriptions are mandatory for issue link types.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
* Additional Notes:
* Steps to configure:
* Go toSettings > Issues > Issue linking.
* ClickAdd link type.
* Enter aName(e.g., "Relates") and set bothOutward descriptionandInward descriptionto the same value (e.g., "relates to").
* Save the link type.
* Configuring issue link types requiresJira administratorprivileges.
* The new link type will appear identically in both linked issues (e.g., "Issue A relates to Issue B" and "Issue B relates to Issue A").
:
Atlassian Support Documentation:Configure issue linking in Jira Cloud
NEW QUESTION # 31
Users complain that they can see a particular custom field in all company-managed projects except one.
Identify two possible reasons. (Choose two.)
- A. Step property
- B. Screen
- C. Project roles
- D. Issue layout
- E. Security levels
- F. Groups
- G. Validator
Answer: B,D
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 # 32
George is the project lead of several projects. Now, he needs to create projects but should not have Jira administrator privileges. What does George need?
- A. Project role
- B. Product role
- C. Project permission
- D. Global permission
- E. Product access
Answer: D
NEW QUESTION # 33
You are setting up Jira Software Cloud for an organization of 250 employees. Product access is already configured to grant new users access to Jira Software by default You now need to configure site access so that it meets these 3 conditions
1. Minimum administration overhead is required
2. Access is granted to the entire organization at the same time
3. Access is restricted only to your organization
Which solution meets these requirements? (Choose one)
- A. Enable existing users to send invitations to all current and future employees
- B. Create an invite link and share it with all current and future employees
- C. Approve any domain in the site access settings
- D. Add all your company's domains as approved domains
- E. Set the global mode to public and enable CAPTCHA on sign up
Answer: D
NEW QUESTION # 34
You inherited a mature Jira instance with hundreds of projects and associated schemes. You are trying to optimize the administration of the instance.
You need to create a new project and determine which schemes to apply.
Select the two best approaches. (Choose two.)
- A. Evaluate existing shared schemes based on common project category or other criteria.
- B. Create a project using the Jira Default Schemes and then create new schemes to avoid sharing conflicts.
- C. Use one of the project templates other than Jira Default Schemes.
- D. Attempt to generalize existing schemes with project roles and share those.
- E. Use the Scheme Helper admin tool to see which combinations of schemes are compatible.
- F. Create a custom project template that uses the most common shared schemes.
Answer: A,E
NEW QUESTION # 35
Jenni wants to populate several custom fields of type User Picker (single user). But she does not see any users to select when she starts typing a name. What is Jenni missing?
- A. Project permission
- B. Project role
- C. Product role
- D. Global permission
- E. Product access
Answer: A
Explanation:
The issue described indicates that Jenni is unable to see users when trying to populate aUser Picker (single user)custom field, suggesting she lacks the necessary permission to browse or select users. In Jira Software Cloud, the ability to select users in a User Picker field is controlled by theBrowse Users and Groupsglobal permission or theUser Pickerfield's configuration, but the most relevant factor here is aproject permission (Option B), specifically theBrowse Projectspermission, which determines whether Jenni can see users associated with the project.
* Explanation of the Correct Answer (Option B):
* TheUser Picker (single user)custom field allows users to select a single Jira user from a dropdown or autocomplete list. To see users in this field, Jenni must have permissions to view users in the context of the project, which is typically governed by theBrowse Projectspermission in the project's permission scheme. If Jenni lacks this permission for the project where the field is used, she may not see any users when typing in the field.
* Additionally, the User Picker field can be configured with auser filter(e.g., restricting selectable users to those in a specific role or group). If Jenni does not have access to the relevant project or the users are filtered out, she will not see any users.
* Exact Extract from Documentation:
Configure User Picker fields
The User Picker (single user) field allows selecting a single Jira user. To populate the field:
* The user must have theBrowse Projectspermission for the project to view and select users associated with the project.
* The field can be configured with a user filter (e.g., only users in a specific role or group). If a filter is applied, only users matching the filter are shown.Note: If no users appear in the User Picker, check the user's project permissions and the field's configuration.(Source:
Atlassian Support Documentation, "Configure custom fields")
* Why This Fits: The most likely reason Jenni cannot see users is that she lacks theBrowse Projectspermission for the project, which prevents her from accessing the user list in the User Picker field. Alternatively, a restrictive user filter in the field configuration could be the cause, but this is still tied to project-level access.
* Why Other Options Are Incorrect:
* Product access (Option A):
* Product access (e.g., access to Jira Software or Jira Service Management) determines whether a user can log in to Jira and use its features. However,Jenni is already interacting with the User Picker field, indicating she has product access. Product access does not control the visibility of users in a User Picker field.
* Extract from Documentation:
Manage product access
Product access grants users the ability to use Jira products. It does not control specific permissions like viewing users in fields, which are managed by global and project permissions.
(Source: Atlassian Support Documentation, "Manage product access")
* Global permission (Option C):
* TheBrowse Users and Groupsglobal permission allows users to see other users and groups across Jira (e.g., in user pickers or sharing dialogs). While this permission is relevant for user visibility, it is less likely the issue here, as Jenni's problem is specific to a project's User Picker field, suggesting a project-level restriction rather than a global one.
* Extract from Documentation:
Global permissions
TheBrowse Users and Groupspermission allows users to select users in fields like User Picker. If this permission is missing, users may not see any users in pickers. However, project-specific permissions like Browse Projectsalso affect user visibility in project contexts.
(Source: Atlassian Support Documentation, "Manage global permissions")
* Product role (Option D):
* Product roles (e.g., Jira Software User, Jira Service Management Agent) define access to specific products but do not control permissions for selecting users in fields. This is not relevant to Jenni's issue.
* Extract from Documentation:
Product roles define access to Jira products and are not related to project-specific permissions or field behaviors.
(Source: Atlassian Support Documentation, "Manage product roles")
* Project role (Option E):
* Project roles (e.g., Administrator, Developer) are used in permission schemes to grant permissions. While Jenni might need a project role to have theBrowse Projectspermission, the role itself is not the missing element-rather, it's the permission granted by the role.
Option B (project permission) is more precise.
* Extract from Documentation:
Project roles are used in permission schemes to grant permissions likeBrowse Projects. The permission, not the role, determines whether a user can select users in a User Picker field.
(Source: Atlassian Support Documentation, "Manage project roles")
* Additional Notes:
* If a user filter is applied to the User Picker field (e.g., limiting selectable users to a specific group or role), Jenni might not see users if she or the users are not in the filtered set. This should be checked in the field's configuration (Settings > Issues > Custom fields).
* To resolve the issue, verify Jenni'sBrowse Projectspermission inProject settings > Permissions and check the User Picker field's configuration for restrictive filters.
:
Atlassian Support Documentation:Configure custom fields
Atlassian Support Documentation:Manage project permissions
Atlassian Support Documentation:Manage global permissions
Atlassian Support Documentation:Manage product access
Atlassian Support Documentation:Manage project roles
NEW QUESTION # 36
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. Project permissions
- B. Issue security scheme
- C. Project roles
- D. Custom field context
- E. Field configurations
Answer: A,D,E
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 # 37
DEV and ENG projects share the same permission scheme. Users of both projects also work in a single board that shows both DEV and ENG issues.
However some users cannot move issues across the board or move issues between the two projects.
Identify the configuration related to this problem. (Choose one)
- A. Project permissions
- B. Global permissions
- C. Product access
- D. Security levels
- E. Board permissions
Answer: A
NEW QUESTION # 38
In a company-managed project, a limited set of users should be notified when issues transition to Pending status, and the project admin must be able to manage the list of users. What two items must be configured?
(Choose two.)
- A. Workflow validator
- B. Group
- C. Project role
- D. Custom event
- E. Workflow condition
Answer: C,D
Explanation:
To address the requirement of notifying a limited set of users when issues transition to a "Pending" status in a company-managed project, and allowing the project admin to manage the list of users, two key configurations are necessary: aproject roleand acustom event. Below is the detailed explanation based on official Jira Software Cloud documentation.
* Project Role (Option A):
* Purpose: Project roles allow project administrators to define and manage a group of users who can be assigned specific permissions or notification responsibilities within a project. This is critical for the requirement that the project admin must manage the list of users to be notified.
* How It Works: In Jira, project roles (e.g., "Developers," "Administrators," or a custom role like
"Pending Status Notifiers") are created and managed at the project level. The project admin can add or remove users from these roles without needing global admin permissions, which aligns with the requirement for the project admin to manage the user list.
* Configuration Steps:
* Navigate toProject Settings > Peoplein the company-managed project.
* Create a new project role or use an existing one (e.g., "Pending Notifiers").
* Add users to this role as needed. The project admin can update this list at any time.
* In the notification scheme, associate the project role with the custom event (explained below) to ensure that users in this role receive notifications when the event is triggered.
* Why This Is Necessary: Using a project role ensures scalability and flexibility. Instead of hardcoding individual users or groups in the notification scheme, a project role allows the admin to dynamically manage who receives notifications without modifying the underlying configuration.
* Custom Event (Option C):
* Purpose: A custom event is required to trigger notifications specifically for thetransition to the
"Pending" status. Jira's notification system relies on events to determine when and to whom notifications are sent. By creating a custom event, you can link it to the specific workflow transition (e.g., moving to "Pending") and configure the notification scheme to notify the project role.
* How It Works: In Jira, events are fired during workflow transitions via post functions. A custom event (e.g., "Issue Moved to Pending") can be created and associated with the transition to the
"Pending" status. The notification scheme is then configured to send notifications to the designated project role when this event occurs.
* Configuration Steps:
* Navigate toSettings > System > Events(requires Jira admin permissions).
* Create a new custom event, such as "Issue Moved to Pending," with a description and an appropriate notification template (e.g., "Issue Updated").
* In the workflow used by the project, edit the transition to the "Pending" status:
* Add a post function to the transition, such as"Fire a Generic Event"or a custom event, and select the custom event ("Issue Moved to Pending").
* Update the project'snotification scheme(found inProject Settings > Notificationsor Settings > Issues > Notification Schemes):
* Map the custom event to the project role (e.g., "Pending Notifiers") to ensure that users in this role receive notifications when the event is fired.
* Why This Is Necessary: A custom event is essential because Jira's default events (e.g., "Issue Updated," "Issue Created") may not be specific enough to target only the "Pending" status transition. A custom event ensures that notifications are sent only when the issue transitions to
"Pending," meeting the requirement for targeted notifications.
* Why Other Options Are Incorrect:
* Workflow Condition (Option B):
* A workflow condition controls whether a user can execute a transition (e.g., restricting who can move an issue to "Pending"). It does not influence notifications or manage lists of users to be notified. Therefore, it is irrelevant to the requirement of notifying users and allowing the project admin to manage the user list.
* Workflow Validator (Option D):
* A workflow validator checks whether certain criteria are met before allowing a transition to proceed (e.g., ensuring a field is filled). Like conditions, validators do not handle notifications or user management for notifications, making this option incorrect.
* Group (Option E):
* While groups can be used in notification schemes to define who receives notifications, they are managed by Jira admins at the global level (viaSettings > User Management > Groups ), not by project admins. The requirement specifies that theproject adminmust manage the list of users, which is not feasible with groups since project admins lack permission to edit global groups. Project roles, however, can be managed by project admins, making them the correct choice over groups.
* Additional Notes:
* The configuration assumes a company-managed project, as team-managed projects have simpler permission and notification settings that do not support custom events or complex workflow configurations to the same extent.
* If the project admin lacks permission to edit workflows or notification schemes (which require Jira admin access), they would need to collaborate with a Jira admin to set up the custom event and initial notification scheme. However, once configured, the project admin can manage the project role's membership independently.
* The use of a custom event ensures that notifications are specific to the "Pending" status transition, avoiding unnecessary notifications for other transitions or actions.
NEW QUESTION # 39
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 has the role of site admin
- C. Ashley does not have a managed account
- D. You are not an organization admin
Answer: C
NEW QUESTION # 40
You are configuring an issue type screen in a team-managed project. Which statement is true?
- A. You can reorder custom fields within all sections of the screen.
- B. You can reuse a custom field from another team-managed project.
- C. You can add any field type to the Context fields section.
- D. You can edit the name of any field on the screen.
- E. You can add any field type to the Description fields section.
Answer: A
Explanation:
In a team-managed project, theissue type screen(configured inProject settings > Issue types) determines which fields are displayed for an issue type and how they are organized (e.g., in sections like Description or Context fields). The true statement is thatyou can reorder custom fields within all sections of the screen (Option E), as team-managed projects allow flexible reordering of fields within their designated sections.
* Explanation of the Correct Answer (Option E):
* In team-managed projects, the issue type screen is configured per issue type, and fields (including custom fields) are organized into sections (e.g., Description fields, Context fields). Users with appropriate permissions (e.g., project admins) can reorder custom fields within any section of the screen to customize the layout, ensuring fields appear in the desired order for creation, editing, or viewing.
* Exact Extract from Documentation:
Configure issue types in team-managed projects
Each issue type in a team-managed project has its own screen configuration, defining which fields are displayed and their order.
To reorder fields:
* Go toProject settings > Issue types.
* Select the issue type and edit its screen.
* Drag and drop fields (including custom fields) within sections (e.g., Description fields, Context fields) to reorder them.Note: Custom fields can be reordered within any section of the screen, but some system fields have fixed positions.(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* Why This Fits: The ability to reorder custom fields within all sections of the issue type screen is a standard feature in team-managed projects, making Option E the true statement.
* Why Other Options Are Incorrect:
* You can edit the name of any field on the screen (Option A):
* In team-managed projects, you cannot edit the name of fields directly on the screen configuration. Custom field names are set when the field is created (Project settings > Project fields), and system field names (e.g., Summary, Description) are fixed. The screen configuration only allows adding, removing, or reordering fields, not renaming them.
* Extract from Documentation:
Field names are set inProject settings > Project fieldsfor custom fields or are fixed for system fields. Screen configurations do not allow renaming fields.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
* You can reuse a custom field from another team-managed project (Option B):
* Custom fields in team-managed projects are project-specific and cannot be reused across projects, unlike company-managed projects where global custom fields are shared. To use a similar field, you must create a new custom field in the project.
* Extract from Documentation:
Custom fields in team-managed projects are unique to the project and cannot be reused from other team- managed projects.
(Source: Atlassian Support Documentation, "Manage fields in team-managed projects")
* You can add any field type to the Context fields section (Option C):
* TheContext fieldssection (right panel in the issue view) has restrictions on which field types can be added. System fields likeSummary,Description, and certain others are fixed in the main section and cannot be moved to the Context fields section. Only eligible fields (e.g., custom fields, Labels, Components) can be added to this section.
* Extract from Documentation:
TheContext fieldssection is limited to certain field types (e.g., custom fields, Labels). Core fields like Summary and Description cannot be moved to Context fields.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* You can add any field type to the Description fields section (Option D):
* TheDescription fieldssection (main section below the Summary) also has restrictions.
Fields likeSummary,Issue Type, andStatusare fixed in their positions, and not all field types can be added to the Description fields section. Only certain fields (e.g., Description, custom text fields) are eligible.
* Extract from Documentation:
TheDescription fieldssection is for fields like Description or custom text fields. Some system fields have fixed positions and cannot be moved.
(Source: Atlassian Support Documentation, "Configure issue types in team-managed projects")
* Additional Notes:
* Configuring issue type screens requiresproject adminprivileges in a team-managed project ( Project settings > Issue types).
* Reordering fields enhances usability by prioritizing important fields in each section.
* System fields may have limited reordering options compared to custom fields.
:
Atlassian Support Documentation:Configure issue types in team-managed projects Atlassian Support Documentation:Manage fields in team-managed projects
NEW QUESTION # 41
Currently, the 'Affects Version/s' field is populated on issues in a particular company-managed project. Now, you want to hide it when viewing issues and to hide its values when viewing filter results. Where would you go to make the change?
- A. Field configuration
- B. Custom field context
- C. Issue layout
- D. Issue detail view
- E. Screen
Answer: C
Explanation:
To hide theAffects Version/sfield when viewing issues and in filter results in a company-managed project, you need to configure theissue layout(Option E). The issue layout determines which fields are displayed or hidden in the issue view and affects how fields appear in filter results.
* Explanation of the Correct Answer (Option E):
* Theissue layoutin a company-managed project controls the visibility and arrangement of fields in the issue view (when viewing an issue) and influences how fields are displayed in filter results (e.
g., in issue navigator or boards). To hide theAffects Version/sfield, you can move it to the Hidden fieldssection in the issue layout. This ensures the field is not shown in the issue view or filter results, even if it contains values.
* Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts define which fields are displayed, hidden, or placed in the context panel when viewing issues.
They also influence field visibility in filter results.
To hide a field:
* Go toProject settings > Issue layout.
* Select the issue type or screen to configure.
* Move the field (e.g., Affects Version/s) to theHidden fieldssection.Note: Hiding a field in the issue layout does not remove it from screens used for Create or Edit operations, but it prevents it from appearing in the issue view and filter results.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Why This Fits: Theissue layoutdirectly controls field visibility in the issue viewand filter results, making it the correct place to hide theAffects Version/sfield, satisfying both requirements.
* Why Other Options Are Incorrect:
* Issue detail view (Option A):
* Theissue detail viewis part of the issue view interface and is not a configuration setting. It is affected by the issue layout but cannot be directly modified to hide fields.
* Extract from Documentation:
The issue detail view displays fields based on the issue layout configuration. To hide fields, configure the issue layout inProject settings > Issue layout.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
* Field configuration (Option B):
* Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. Hiding a field in a field configuration removes it from all operations (Create, Edit, View), which would preventAffects Version/sfrom being populated at all. The requirement is to hide the field only when viewing and in filter results, not to remove it entirely, so field configuration is not suitable.
* Extract from Documentation:
Hiding a field in a field configuration removes it from all screens and operations. Use issue layouts to hide fields in the issue view and filter results.
(Source: Atlassian Support Documentation, "Configure field settings")
* Custom field context (Option C):
* Custom field contextsdefine the options and default values for a custom field across projects or issue types. TheAffects Version/sfield is a system field, not a custom field, and contexts do not control field visibility in the issue view or filter results.
* Extract from Documentation:
Custom field contexts apply to custom fields and manage options, not visibility. System fields likeAffects Version/sare not affected by contexts.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
* Screen (Option D):
* Screensdetermine which fields appear during issue operations (Create, Edit, View).
RemovingAffects Version/sfrom a screen would affect Create or Edit operations, not just viewing, and would not specifically hide the field in filter results. The issue layout is the correct place for view-specific changes.
* Extract from Documentation:
Screens control fields for Create, Edit, and View operations. To hide fields in the issue view and filter results, use the issue layout.
(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
* Additional Notes:
* Configuring the issue layout requiresproject adminprivileges and is done inProject settings > Issue layout.
* HidingAffects Version/sin the issue layout does not remove its values from the database; it only prevents display in the issue view and filter results.
* Ensure the field remains on relevant screens for Create/Edit if it needs to continue being populated.
:
Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Atlassian Support Documentation:Configure field settings
Atlassian Support Documentation:Manage custom fields in Jira Cloud
Atlassian Support Documentation:Configure screens in Jira Cloud
NEW QUESTION # 42
......
Ultimate Guide to Prepare ACP-120 Certification Exam for Jira Administrator: https://www.pass4sures.top/Jira-Administrator/ACP-120-testking-braindumps.html
ACP-120 Ultimate Study Guide: https://drive.google.com/open?id=1q_AMxvfnM8C-ky4wvplAkMhJFi9rxF1x