Pass the ATLASSIAN Jira Administrator ACP-120 Questions and answers with ExamsMirror

To ensure that newly created issues in a company-managed project’s Kanban board are not left unassigned, you must configure theDefault Assigneesetting in the project’s settings. TheProject lead(Option B) is a valid and appropriate choice, as it assigns new issues to the project’s designated lead by default.

Explanation of the Correct Answer (Option B):

In a company-managed project, theDefault Assigneesetting determines who is automatically assigned to new issues when no assignee is specified during creation (e.g., when creating issues directly on a Kanban board). TheProject leadis a predefined user set in the project’s settings and can be selected as the default assignee to ensure issues are not left unassigned.

By selectingProject leadin theDefault Assigneedropdown, all new issues created in the project, including those created on the Kanban board, will be automatically assigned to the project lead, meeting the requirement.

Exact Extract from Documentation:

Configure the default assignee

TheDefault Assigneesetting in a company-managed project determines who is assigned to new issues when no assignee is specified.

Options include:

Project lead: Assigns issues to the user designated as the project lead.

Unassigned: Leaves issues unassigned (if allowed by the project’s permission scheme).To configure:

Go toProject settings > Details.

SelectProject leadin theDefault Assigneedropdown.Note: Ensure the project lead has theAssignable Userpermission in the project’s permission scheme.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Why This Fits: SelectingProject leadensures that all newly created issues are automatically assigned to the project lead, preventing them from being unassigned, making Option B the correct answer.

Why Other Options Are Incorrect:

Board administrator (Option A):

There is noBoard administratoroption in theDefault Assigneedropdown. Board administrators manage Kanban or Scrum boards but are not a predefined assignee role for issues.

Extract from Documentation:

TheDefault Assigneedropdown includesProject lead,Unassigned, or specific users, but notBoard administrator.

(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Component lead (Option C):

TheComponent leadis not an option in theDefault Assigneedropdown. Component leads are assigned to specific components, and issues are only assigned to them if a component with a default assignee is selected during issue creation, which is not guaranteed for Kanban board creations.

Extract from Documentation:

Component leads are assigned to issues only when a component with a default assignee is selected. They are not part of theDefault Assigneesetting.

(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")

Project admin (Option D):

There is noProject adminoption in theDefault Assigneedropdown. Project administrators have theAdminister Projectspermission but are not a predefined assignee role. TheProject leadis the designated user for default assignments.

Extract from Documentation:

TheDefault Assigneesetting does not includeProject admin. UseProject leadorUnassigned.

(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Reporter (Option E):

TheReporteris the user who creates the issue and is not an option in theDefault Assigneedropdown for company-managed projects. Assigning issues to the reporter would require a custom automation rule or manual assignment, not a default setting.

Extract from Documentation:

TheReporteris not a valid option forDefault Assignee. UseProject leadorUnassignedfor automatic assignments.

(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Additional Notes:

TheDefault Assigneesetting is configured inProject settings > Details, requiringproject adminprivileges.

Ensure the project lead has theAssignable Userpermission in the project’s permission scheme to be eligible as an assignee.

IfUnassignedis selected, issues could remain unassigned, which violates the requirement.

Changing the name of a project in Jira Software Cloud affects how the project is displayed and referenced in certain contexts, but it does not have significant system-wide impacts like reindexing or changing URLs. The primary impact is thatissue filters may need to be updated(Option E), as filters often reference the project name.

Explanation of the Correct Answer (Option E):

In Jira, issue filters (created using JQL, Jira Query Language) can include the project name to scope the search (e.g., project = "Old Project Name"). If the project name changes, any filters that explicitly reference the old project name will no longer return the correct results and must be updated to use the new project name.

Exact Extract from Documentation:

Change a project’s name

To change the name of a project:

Go toProject settings > Details.

Update theNamefield and save changes.Impact: Changing the project name does not affect the project key, issue keys, or URLs. However, JQL queries, filters, or dashboards that reference the project by name (e.g., project = "Old Name") may need to be updated to reflect the new name.Note: Use the project key in JQL queries to avoid issues with name changes, as the key remains constant.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Why This Fits: The documentation explicitly states that changing a project’s name impacts JQL-based filters and dashboards that reference the project name, making Option E the correct choice.

Why Other Options Are Incorrect:

Jira will need to be reindexed (Option A):

Changing a project name is a metadata update that does not affect the search index. Reindexing is required for changes like modifying field configurations or schemes, but not for renaming a project.

Extract from Documentation:

Reindexing is required when you make changes to field configurations, schemes, or indexing settings. Changing a project’s name or key does not trigger a reindex.

(Source: Atlassian Support Documentation, "Reindex Jira Cloud")

The URL for issues will change (Option B):

Issue URLs in Jira are based on the project key and issue key (e.g., https:// .atlassian.net/browse/KEY-123), not the project name. Changing the project name does not affect URLs.

Extract from Documentation:

Issue URLs are constructed using the project key and issue key, which remain unchanged when the project name is updated.

(Source: Atlassian Support Documentation, "Manage projects in Jira Cloud")

The old name can no longer be reused (Option C):

There is no restriction in Jira preventing the reuse of a previous project name. Project names are not required to be unique, and the old name can be reused for another project or reverted if needed.

Extract from Documentation:

Project names can be reused across projects, as they are not required to be unique. The project key, however, must be unique.

(Source: Atlassian Support Documentation, "Create and configure projects")

The project key will also change (Option D):

The project key is a separate attribute from the project name and remains unchanged when the name is updated. Changing the project key is a distinct operation that requires admin permissions and affects issue keys and URLs.

Extract from Documentation:

The project key is a unique identifier for the project and does not change when you update theproject name. To change the project key, use theChange project keyoption, which updates all issue keys and URLs.

(Source: Atlassian Support Documentation, "Edit a project key")

Additional Notes:

To minimize the impact of project name changes, it’s recommended to use the project key in JQL queries (e.g., project = KEY) instead of the project name, as the key is immutable unless explicitly changed.

Changing the project name requires project admin permissions and is done inProject settings > Details.

To meet the requirements of restricting visibility of some BRAVO issues to managers, others to supervisors, and keeping the remaining issues visible to all users, you need to configure anissue security schemeto define security levels and theSet Issue Securitypermission to allow users to apply these levels. These two elements are critical for implementing issue-level security in a company-managed project.

Explanation of the Correct Answers:

Issue security scheme (Option A):

Anissue security schemedefines security levels that restrict who can view issues based on criteria such as users, groups, or roles. To meet the requirements, you need to create at least three security levels: one for managers, one for supervisors, and one (or none, for default visibility) for all users. The scheme is then applied to the BRAVO project to enforce these visibility rules.

Exact Extract from Documentation:

Configure issue security schemes

Issue security schemes define security levels to restrict who can view issues. Each level specifies users, groups, or roles (e.g., managers, supervisors) who can see issues assigned to that level.

To create a scheme:

Go toSettings > Issues > Issue security schemes.

Create a new scheme and add security levels (e.g., “Managers Only,” “Supervisors Only,” “All Users”).

Assign the scheme to a project inProject settings > Issue security.Note: Security levels override theBrowse Projectspermission for restricted issues.(Source: Atlassian Support Documentation, "Configure issue security schemes")

Why This Fits: The issue security scheme is necessary to create security levels that restrict visibility to managers, supervisors, or all users, addressing all three requirements.

Set Issue Security permission (Option B):

TheSet Issue Securitypermission allows users to select a security level for an issue (via theSecurity Levelfield). Without this permission, users cannot assign issues to the “Managers Only” or “Supervisors Only” security levels,which is necessary to implement the restricted visibility requirements. This permission must be granted to appropriate users (e.g., project admins or specific roles) in the project’s permission scheme.

Exact Extract from Documentation:

Set Issue Security permission

TheSet Issue Securitypermission allows users to set or change the security level of an issue, determining who can view it. This permission is granted via the project’s permission scheme.

To configure:

Go toProject settings > Permissions.

Add users, groups, or roles (e.g., Administrators) to theSet Issue Securitypermission.Note: Without this permission, users cannot assign issues to specific security levels, even if a scheme is configured.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Why This Fits: TheSet Issue Securitypermission is required to enable users to apply the security levels defined in the issue security scheme, ensuring that issues can be restricted to managers or supervisors as needed.

Why Other Options Are Incorrect:

Global permissions (Option C):

Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific visibility. Issue visibility is managed by project-level permissions and security schemes, not global permissions.

Extract from Documentation:

Global permissions control system-wide actions, such as administering Jira or sharing filters. Issue visibility is managed by project permissions and issue security schemes.

(Source: Atlassian Support Documentation, "Manage global permissions")

Browse Projects permission (Option D):

TheBrowse Projectspermission allows users to view issues in a project. While all users currently have this permission (since they can see all BRAVO issues), modifying it does not address the need to restrict specific issues to managers or supervisors. Issue security schemes overrideBrowse Projectsfor restricted issues.

Extract from Documentation:

TheBrowse Projectspermission allows users to view issues in a project, but issue security levels can further restrict visibility for specific issues.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Administer Projects permission (Option E):

TheAdminister Projectspermission allows users to manage project settings, such as components or permission schemes. While it may be needed to configure the issue security scheme or permissions, it is not directly required to meet the visibility requirements.

Extract from Documentation:

TheAdminister Projectspermission allows managing project settings but is not required to set issue security levels or view restricted issues.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Additional Notes:

To implement the requirements, create an issue security scheme with three levels:

“Managers Only” (e.g., restricted to a “Managers” group).

“Supervisors Only” (e.g., restricted to a “Supervisors” group).

“All Users” (or no security level, allowingBrowse Projectsto apply).

Assign the scheme to the BRAVO project and grant theSet Issue Securitypermission to users who need to assign these levels (e.g., project admins).

The configuration requires Jira administrator privileges to create the scheme, but project admins can manage security levels within the project.

In Jira Software Cloud, automation rules usesmart valuesto reference issue fields, such as the issue key, in actions like sending emails. The correct syntax for referencing the issue key in theSend Emailaction’s subject line is{{issue.key}}(Option B).

Explanation of the Correct Answer (Option B):

The{{issue.key}}smart value retrieves the issue key (e.g., PROJ-123) of the issue that triggers or is processed by the automation rule. This can be used in the subject line of theSend Emailaction to include the issue key dynamically.

Exact Extract from Documentation:

Use smart values in automation rules

Smart values allow you to access issue fields and other data in automation actions. To reference the issue key:

Use{{issue.key}}to insert the issue key (e.g., PROJ-123) in fields like email subjects or bodies.Examples:

Email subject: Issue {{issue.key}} Updated

Output: Issue PROJ-123 UpdatedNote: Smart values are enclosed in double curly braces ({{}}). Use dotnotation to access fields (e.g., {{issue.key}}, {{issue.summary}}).(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

Why This Fits: The{{issue.key}}syntax is the standard way to reference the issue key in Jira automation, making it the correct choice for theSend Emailaction’s subject line.

Why Other Options Are Incorrect:

{{triggerIssue.issuekey}} (Option A):

The{{triggerIssue}}smart value refers to the issue that triggers the rule, but the field iskey, notissuekey. The correct syntax is{{triggerIssue.key}}, not{{triggerIssue.issuekey}}. Additionally,{{issue.key}}is sufficient for most rules unless specifically targeting the trigger issue in a branched rule.

Extract from Documentation:

Use{{triggerIssue.key}}to reference the key of the issue that triggers the rule.{{issue.key}}is used for the current issue in the rule’s context.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

{{issueKey}} (Option C):

Smart values require dot notation for field access (e.g.,{{issue.key}}).{{issueKey}}is not a valid smart value, as it does not reference a specific field.

Extract from Documentation:

Smart values must reference valid fields using dot notation (e.g., {{issue.key}}, {{issue.summary}}). Single variables like {{issueKey}} are not supported.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

{issue.issuekey} (Option D):

The syntax uses single curly braces andissuekeyinstead ofkey, which is incorrect. Smart values require double curly braces ({{}}) and the correct field name (key).

Extract from Documentation:

Smart values use double curly braces ({{}}) and standard field names (e.g., {{issue.key}}). Incorrect formats like {issue.issuekey} will not work.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

issue.key (Option E):

Without curly braces,issue.keyis treated as plain text, not a smart value. It will not resolve to the issue key and will appear literally in the email subject.

Extract from Documentation:

Smart values must be enclosed in {{}} to be evaluated. Plain text like issue.key will not resolve to a field value.

(Source: Atlassian Support Documentation, "Use smart values in Jira automation")

Additional Notes:

TheSend Emailaction in Jira automation allows smart values in the subject and body to dynamically include issue data.

If the rule involves branching or multiple issues,{{issue.key}}refers to the current issue in the rule’s context, while{{triggerIssue.key}}refers to the triggering issue. For a simple email rule,{{issue.key}}is typically sufficient.

TheAdminister Projectspermission in Jira Software Cloud grants users the ability to manage project settings, such as components, versions, and roles. Among the listed actions,modifying component leads(Option C) requires theAdminister Projectspermission, as it involves updating project-specific configurations.

Explanation of the Correct Answer (Option C):

Modifying component leads involves changing the user assigned as the lead for acomponent inProject settings > Components. This action requires theAdminister Projectspermission, as it is a project administration task.

Exact Extract from Documentation:

Administer Projects permission

TheAdminister Projectspermission allows users to manage project settings, including:

Creating, editing, or deleting components and their leads.

Updating project details, roles, and permissions.

Configuring notification schemes, issue security, and other project-level settings.To modify component leads:

Go toProject settings > Components.

Edit the component and update the lead.Note: Only users withAdminister Projectspermission can perform this action.(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")

Why This Fits: Modifying component leads is a project administration task that directly requires theAdminister Projectspermission, making Option C the correct choice.

Why Other Options Are Incorrect:

Reopen bugs (Option A):

Reopening bugs involves transitioning an issue back to an open status, which requires theTransition Issuespermission and possiblyEdit Issuespermission, depending on the workflow. It does not requireAdminister Projects.

Extract from Documentation:

Transition Issues permission

Allows users to move issues through workflow transitions, such as reopening a bug. This does not requireAdminister Projects.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Assign issues to themselves (Option B):

Assigning issues to oneself requires theAssignable Userpermission (to be eligible as an assignee) and theAssign Issuespermission (to change the assignee). These are not administrative tasks.

Extract from Documentation:

Assign Issues permission

Allows users to assign issues to other users or themselves, provided they have theAssignable Userpermission. This does not requireAdminister Projects.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Edit due dates (Option D):

Editing due dates requires theEdit Issuespermission, as it involves modifying an issue’sDue Datefield. This is not an administrative task.

Extract from Documentation:

Edit Issues permission

Allows users to modify issue fields, such as Due Date, Summary, or Description. This does not requireAdminister Projects.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Set fix versions (Option E):

Setting fix versions requires theEdit Issuespermission to modify theFix Versionsfield. In some cases, theResolve Issuespermission may also be needed if the field is restricted to resolution workflows, butAdminister Projectsis not required.

Extract from Documentation:

Edit Issues permission

Allows users to update fields like Fix Versions. TheAdminister Projectspermission is required to manage versions, not set them on issues.

(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Additional Notes:

TheAdminister Projectspermission is typically granted to project administrators or leads via the project’s permission scheme. It is checked inProject settings > Permissions.

Other actions listed (A, B, D, E) are issue-level operations that do not require administrative privileges.

The changes toUser Default Settingsaffect the default behavior for new filters, dashboards, and issue watching. The two statements that are definitely true areonly newly created dashboards will reflect the new default setting(Option A) andonly newly created saved filters will reflect the new default setting(Option C), as these settings apply to new creations only.

Explanation of the Correct Answers:

Only newly created dashboards will reflect the new default setting (Option A):

Changing theDefault sharing for filters and dashboardstoPublicin User Default Settings sets the default sharing option for newly created dashboards toPublic. Existing dashboards retain their original sharing settings (e.g., Private, Group) and are not affected by the change. Only dashboards created after the setting is updated will default toPublic.

Exact Extract from Documentation:

Manage user default settings

TheDefault sharing for filters and dashboardssetting determines the default sharing option for new filters and dashboards.

To configure:

Go toSettings > System > User default settings.

SetDefault sharingtoPublic,Private, or another option.Impact:

Only newly created filters and dashboards use the new default setting.

Existing filters and dashboards retain their original sharing settings.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Why This Fits: The change toPublicsharing applies only to newly created dashboards, making Option A definitely true.

Only newly created saved filters will reflect the new default setting (Option C):

Similarly, theDefault sharingsetting affects the default sharing option for newly created saved filters. Filters created after the change will default toPublic, but existing filters keep their original sharing settings (e.g., Private, Group).

Exact Extract from Documentation:

Manage user default settings

Changing theDefault sharing for filters and dashboardstoPublicapplies to new filters and dashboards only.

Impact:

Existing saved filters are not updated to the new default sharing setting.

New filters created after the change will default toPublic.(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Why This Fits: The change toPublicsharing applies only to newly created saved filters, making Option C definitely true.

Why Other Options Are Incorrect:

Saved filters using the old default setting will reflect the new default setting (Option B):

Existing saved filters do not automatically update to the new default sharing setting (Public). They retain their original sharing configuration (e.g., Private, Group) set at creation, so this statement is false.

Extract from Documentation:

Existing filters and dashboards are unaffected by changes to theDefault sharingsetting. Only new creations use the updated default.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

All users will become watchers of issues they have created in the past (Option D):

SettingAutowatch own issuestoYesenables autowatching for issues createdafterthe setting is changed. It does not retroactively add users as watchers to issues they created in the past. For past issues, users must be manually added as watchers or an automation rule must be created, so this statement is not definitely true.

Extract from Documentation:

TheAutowatch own issuessetting applies to issues created after the setting is enabled. It does not affect previously created issues.

(Source: Atlassian Support Documentation, "Manage user default settings in Jira Cloud")

Additional Notes:

ConfiguringUser Default SettingsrequiresJira administratorprivileges and is done inSettings > System > User default settings.

Users can override the default sharing setting when creating filters or dashboards (e.g., choosing Private instead of Public).

To retroactively apply autowatching to past issues, a bulk operation or automation rule would be needed, but this is not automatic.

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 Issuespermission for all relevant projects.

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 Listpermission, 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.

The JQL query project IN projectsWhereUserHasRole("Sales") filters for issues in projects wherethe user running the query has theSalesproject role. Since Leila is a member of theSales groupand receives the filter subscription, the issues she receives are those from projects whereLeila is in the Sales role(Option A).

Explanation of the Correct Answer (Option A):

The JQL functionprojectsWhereUserHasRole("Sales")returns a list of projects where the user executing the query is a member of theSalesproject role. The query project IN projectsWhereUserHasRole("Sales") selects all issues from those projects.

Leila, as a member of theSales group, receives the filter subscription. When the subscription runs for Leila, the JQL query is evaluated in her context, meaning it returns issues from projects whereLeilahas theSalesproject role.

Exact Extract from Documentation:

Advanced searching - functions reference

TheprojectsWhereUserHasRole("role")function returns projects where the user running the query is a member of the specified project role.

Example:

project IN projectsWhereUserHasRole("Sales") returns issues from projects where the user has theSalesproject role.Note: For filter subscriptions, the query is executed in the context of each recipient, so results depend on the recipient’s role membership.(Source: Atlassian Support Documentation, "Advanced searching - functions reference")

Why This Fits: The filter subscription runs the JQL query for Leila, returning issues from projects whereLeila is in the Sales role, making Option A the correct answer.

Why Other Options Are Incorrect:

Issues assigned to anyone in the Sales group (Option B):

The JQL query does not filter byassigneeor group membership. It only selects issues based on the projects where the user has theSalesrole, regardless of who the issues are assigned to.

Extract from Documentation:

To filter by assignee, use assignee in membersOf("group"). TheprojectsWhereUserHasRolefunction filters by project, not assignee.

(Source: Atlassian Support Documentation, "Advanced searching - fields reference")

Issues from projects where Leila is in the Sales group (Option C):

The query usesprojectsWhereUserHasRole("Sales"), which checks for theSalesproject role, not a group. Project roles and groups are distinct, and the query does not reference group membership.

Extract from Documentation:

Project roles are project-specific and distinct from groups. UseprojectsWhereUserHasRolefor roles, notmembersOffor groups.

(Source: Atlassian Support Documentation, "Advanced searching - functions reference")

Issues assigned to anyone in the Sales role (Option D):

The query does not filter byassigneeor role membership of the assignee. It selects issues from projects where the user (Leila) has theSalesrole, not issues assigned to users in that role.

Extract from Documentation:

To filter by assignees in a role, additional JQL or scripting is needed.projectsWhereUserHasRoleonly filters by project.

(Source: Atlassian Support Documentation, "Advanced searching - fields reference")

Additional Notes:

TheSalesproject role must exist in the relevant projects, and Leila must be added to it inProject settings > Peoplefor those projects.

The subscription sends emails to theSales group, and each recipient (like Leila) seesissues based on their own role membership in the JQL query’s context.

Leila must haveBrowse Projectspermission for the projects returned by the query to see the issues.

The question pertains to configuring a"Create a new issue or add a comment to an existing issue" mail handlerin Jira Software Cloud. Mail handlers process incoming emails to create issues or add comments, and certain fields can be specifically configured to control how the handler behaves. According to Jira Cloud documentation, the two fields with specific settings in this type of mail handler areReporterandPriority.

Explanation of the Correct Answers:

Reporter (Option C):

TheReporterfield specifies the user who is set as the reporter of the issue created by the mail handler. In the mail handler configuration, you can define whether the reporter is set to a default user, derived from the email’s "From" address (if the email address matches a Jira user), or another specified user.

Exact Extract from Documentation:

Configuring an email handler

When setting up a mail handler like "Create a new issue or add a comment to an existing issue," you can configure the following settings:

Reporter: Specify the user who will be set as the reporter for new issues. Options include:

The user associated with the email’s "From" address (if they have a Jira account).

A default user (e.g., a project lead or a specific user account).

If no valid user is found, the handler can be configured to reject the email or use a fallback user.This setting ensures that the issue is attributed to the correct user as the reporter.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")

Why This Fits: The Reporter field is a critical setting in the mail handler, as it determines who is recorded as creating the issue, which affects permissions, notifications, and reporting.

Priority (Option D):

ThePriorityfield allows you to set a default priority for issues created by the mail handler if the email does not explicitly specify a priority. This ensures that new issues have a consistent priority unless overridden by the email content.

Exact Extract from Documentation:

Field settings for mail handlers

For the "Create a new issue or add a comment to an existing issue" handler, you can specify default values for certain fields, including:

Priority: Set a default priority for new issues (e.g., Medium, High). If the email contains a specific priority value (e.g., via a keyword or mapping), it can override the default.These settings allow you to control the behavior of issue creation and ensure consistency in field values.(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")

Why This Fits: The Priority field is explicitly configurable in the mail handler to ensure that new issues are assigned an appropriate priority, making it one of the two fields with specific settings.

Why Other Options Are Incorrect:

Epic Link (Option A):

TheEpic Linkfield is not specifically configurable in the mail handler settings. While you can map email content to fields like Epic Link using advanced configurations (e.g., regex or scripting in Automation), it is not a standard field with specific settings in the mail handler configuration interface.

Extract from Documentation:

Mail handlers allow mapping of email content to standard fields like Summary, Description, or Priority. Advanced field mappings, such as Epic Link, require custom automation rules or third-party apps.

(Source: Atlassian Support Documentation, "Automate email processing with Jira Automation")

Custom Field (Option B):

While custom fields can sometimes be populated via email content (e.g., through regex or automation), the mail handler’s standard configuration does not provide specific settings for custom fields. The handler focuses on system fields like Reporter and Priority.

Extract from Documentation:

Custom fields are not directly supported in the default mail handler settings. To populate custom fields, you may need to use Jira Automation or a third-party mail handler app.

(Source: Atlassian Support Documentation, "Configure email handlers in Jira Cloud")

Watchers (Option E):

TheWatchersfield is not a configurable setting in the mail handler. You cannot specify default watchers or automatically add watchers based on email content in the standard mail handler configuration. Watchers are typically managed manually or via automation rules.

Extract from Documentation:

Watchers are not a configurable field in mail handlers. To add watchers automatically, use JiraAutomation or a workflow post function.

(Source: Atlassian Support Documentation, "Configure notifications and watchers")

Additional Notes:

The"Create a new issue or add a comment to an existing issue" mail handleris one of several mail handler types in Jira Cloud. Its configuration focuses on ensuring that issues are created with the correct metadata (e.g., Reporter, Priority) and that comments are added to existing issues based on issue keys in the email subject.

Configuring the Reporter and Priority fields ensures that issues created via email align with project workflows and notification schemes.