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?
Correct Answer: E
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
Question 2
In your organization, a cobbler leads a Jira project with two issue types: - Shoe Order - Repair The cobbler has given you the following requirements: 1. All screens should use the Summary, Description, Due Date, and Components fields. 2. Both issue types need to use a new custom field called Shoe Type on all screens. 3. The Priority field should appear on all screens for Repair issues. 4. Users should not be able to set the Priority for Shoe Orders during creation, but the Priority field still needs to be editable and viewable after creation. Identify the minimum number of screens and screen schemes that will meet the requirements.
Correct Answer: F
Question 3
You are tidying up a Jira project and find that the following two issue types are being used. - Task - Assignment They seem very similar. If both are not needed, you could convert all existing Assignment issues in the project into Task issues and remove the Assignment issue type from the project. Which project configurations would you check to see if it is necessary to keep the two as separate issue types instead? (Choose three.)
Correct Answer: A,B,F
Question 4
Jan asked you to create a new Select List custom field called Department for his project MCAS. You created the field in the morning. In the afternoon, Jan notes that his Jira dashboard is not showing the field correctly. He asks to help him troubleshoot. View the Exhibit to see Jan's entire dashboard. - The first gadget shows 26 issues in the project by Status. - The second gadget shows that there are three issues that have the new Department field set. - The last gadget shows "No Data Available". The filter query for that gadget is "project=MCAS and Department is empty." Why does Jan's gadget say "No Data Available"?
Correct Answer: A
Question 5
Two users have access to the same filter and see the same issues in a company-managed project. One of them can perform a bulk operation to watch issues in the filter, but the other user cannot. What should you investigate?
Correct Answer: A
The scenario describes two users who can view the same issues in a filter (indicating they have theBrowse Projectspermission), but only one can perform a bulk operation towatchissues. The ability to watch issues is controlled by theView Issue WatchersandManage Watcher Listpermissions in the project's permission scheme. Therefore, you should investigateproject permissions(Option A). * Explanation of the Correct Answer (Option A): * Performing a bulk operation to watch issues requires theManage Watcher Listpermission, which allows users to add themselves or others as watchers to an issue. Since both users can see the issues (via the filter), they likely have theBrowse Projectspermission, but the user who cannot perform the bulk operation may lack theManage Watcher Listpermission. * Exact Extract from Documentation: Manage Watcher List permission TheManage Watcher Listpermission allows users to add or remove watchers from an issue, including via bulk operations. This permission is granted via the project's permission scheme. Note: To view the watcher list, users also need theView Issue Watcherspermission. Both permissions are required to perform actions like bulk watching issues. To check permissions: * Go toProject settings > Permissions. * Review theManage Watcher ListandView Issue Watcherspermissions to see which users, groups, or roles have them.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud") * Why This Fits: The difference in the users' ability to perform the bulk watch operation is most likely due to a difference in theirManage Watcher Listpermission, which is defined in the project's permission scheme. Investigating project permissions will reveal whether the second user lacks this permission. * Why Other Options Are Incorrect: * Product access (Option B): * Product access determines whether users can use Jira Software. Both users can view the filter and issues, indicating they have product access. Product access does not control specific permissions like managing watchers. * Extract from Documentation: Manage product access Product access grants users the ability to use Jira products. Specific actions, like managing watchers, are controlled by project or global permissions, not product access. (Source: Atlassian Support Documentation, "Manage product access") * Groups (Option C): * Groups may be used in permission schemes to grant permissions, but the root cause is the permission itself, not the group membership. Investigating groups might be a secondary step after checking project permissions, butproject permissionsis the more direct answer. * Extract from Documentation: Groups are used in permission schemes to grant permissions to multiple users. To determine why a user lacks a permission, check the permission scheme first, then verify group membership if relevant. (Source: Atlassian Support Documentation, "Manage groups") * Default user preferences (Option D): * Default user preferences (e.g., notification settings) control whether a user receives notifications for watched issues, not their ability to watch issues.The issue is about performing a bulk operation, not receiving notifications. * Extract from Documentation: Manage user preferences Users can manage their notification preferences inPersonal settings > Email notifications. These settings affect notification delivery, not the ability to perform actions like watching issues. (Source: Atlassian Support Documentation, "Manage your Jira notification emails") * Project roles (Option E): * Project roles are used in permission schemes to grant permissions. Like groups, roles are a means to assign permissions, but the issue lies in the permission itself (Manage Watcher List). Investigating project permissions directly addresses the root cause. * Extract from Documentation: Project roles are used in permission schemes to grant permissions likeManage Watcher List. Check the permission scheme to identify the root cause of permission differences. (Source: Atlassian Support Documentation, "Manage project roles") * Additional Notes: * Both users can see the filter and issues, so they likely have theBrowse Projectspermission. The difference in their ability to perform the bulk watch operation points to theManage Watcher List permission, which should be checked inProject settings > Permissions. * If the permission is granted to a group or role, verify the users' membership in those groups or roles as a follow-up step. : Atlassian Support Documentation:Manage permissions in Jira Cloud Atlassian Support Documentation:Manage product access Atlassian Support Documentation:Manage groups Atlassian Support Documentation:Manage your Jira notification emails Atlassian Support Documentation:Manage project roles
