On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What does Taylor definitely need?
Correct Answer: D
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
Question 7
One of the HR managers created a filter and shared the subscription with members of the hr- managers group. The filter contains the following valid JQL query: Manager = currentUser() AND Manager in membersOf("hr-managers") Which issues will be included in the subscription?
Correct Answer: A
Question 8
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.)
Correct Answer: B,C,F
Question 9
Until now, two teams have been working together in a single company-managed Software project. Now, they want to split their work into two distinct projects. For each of their requirements, you must decide whether you can use shared schemes for the two projects or whether a unique scheme must be created. Which requirement necessitates the use of a unique scheme?
Correct Answer: D
When splitting a single company-managed project into two, you must determine whether the new projects can share configuration schemes (e.g., issue type scheme, workflow scheme, notification scheme) or require unique schemes to meet specific requirements. The requirement that necessitates a unique scheme isthe Fix Versions field must be mandatory for one of the projects(Option D), as this requires a distinct field configuration scheme. * Explanation of the Correct Answer (Option D): * Making theFix Versionsfield mandatory for one project but not the other requires a uniquefield configuration scheme. In Jira, field configurations control whether fields are required, hidden, or optional. A field configuration scheme maps field configurations to issue types, and each project can have its own field configuration scheme. To make Fix Versions mandatory for one project, a new field configuration must be created and associated with that project's scheme. * Exact Extract from Documentation: Configure field settings for a project Field configurations define the behavior of fields (e.g., required, optional, hidden) for specific issue types. Each project can have its own field configuration scheme, which maps field configurations to issue types. To make a field required: * Create or edit a field configuration (inSettings > Issues > Field configurations). * Find the field (e.g., Fix Versions) and mark it asRequired. * Associate the field configuration with a field configuration scheme. * Assign the field configuration scheme to the project inProject settings > Fields.If two projects need different field behaviors (e.g., Fix Versions required in one but not the other), they must use separate field configuration schemes.(Source: Atlassian Support Documentation, "Configure field settings") * Why This Fits: The requirement to make the Fix Versions field mandatory for one project but not the other cannot be achieved with a shared field configuration scheme, as field configurations apply uniformly to all projects using the same scheme. A unique field configuration scheme is necessary. * Why Other Options Are Incorrect: * Each project must use a different set of components and component leads (Option A): * Components and component leads are configured at the project level, not through a scheme. Each project can have its own components and leads without requiring a unique scheme, so this requirement does not necessitate a new scheme. * Extract from Documentation: Manage components Components are project-specific and configured inProject settings > Components. Each project can have its own set of components and component leads, independent of schemes. (Source: Atlassian Support Documentation, "Manage components in Jira Cloud") * Each project must send notifications from a different email address (Option B): * Notifications in company-managed projects are controlled by thenotification scheme, which defines who receives notifications for specific events. However, the email address used for sending notifications is configured at the system level (viaSettings > System > Outgoing email) or per project for custom sender addresses (if supported by the Jira instance). This does not inherently require a unique notification scheme, as the sender address is not tied to the scheme itself. * Extract from Documentation: Configure outgoing email The sender email address for notifications is set globally or per project inSettings > System > Outgoing email . Notification schemes define recipients, not the sender address. (Source: Atlassian Support Documentation, "Configure email in Jira Cloud") * Sprints must be managed by a different set of users in each project (Option C): * Sprint management is controlled by permissions in thepermission scheme, specifically the Manage Sprintspermission. Both projects can share the same permission scheme, as permissions can be granted to project-specific roles, groups, or users. For example, different project roles can be assigned the Manage Sprints permission in each project, allowing different users to manage sprints without requiring a unique scheme. * Extract from Documentation: Manage sprints TheManage Sprintspermission is granted in the permission scheme to specific roles, groups, or users. Projects can share a permission scheme, with permissions scoped to project-specific roles (e.g., Project A's Administrators vs. Project B's Administrators). (Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud") * Additional Notes: * The need for a unique field configuration scheme for Option D arises because field configurations are applied at the scheme level, and a single scheme cannot have different rules (e.g., required vs. optional) for the same field across projects. * For other requirements (A, B, C), project-level settings or shared schemes with role-based scoping can accommodate the differences, making unique schemes unnecessary. : Atlassian Support Documentation:Configure field settings Atlassian Support Documentation:Manage components in Jira Cloud Atlassian Support Documentation:Configure email in Jira Cloud Atlassian Support Documentation:Manage permissions in Jira Cloud
Question 10
The OPS team will start using Jira to track and approve Change Requests in the OPS project. They have these workflow requirements: - Requests can be approved by two individuals only. - The approvers will change weekly. Jira is connected to your corporate LDAP with Read-Only permissions. What is the best way to structure permissions for the OPS project to support these workflow requirements?
