ACP-120 Jira Administration for Cloud Questions and Answers

The Import Jira Cloud feature allows migration of data between Jira Cloud sites, including projects, issues, configurations, and attachments. However, deleted issues (Option C) cannot be imported, as they are not included in standard Jira Cloud backups or export data.

Explanation of the Correct Answer (Option C) :

Deleted issues are permanently removed from Jira Cloud and are not included in backups or export files created for migration. The Import Jira Cloud feature only imports data that exists in the source site’s backup, which excludes issues that have been deleted.

Exact Extract from Documentation :

Import Jira Cloud data

The Import Jira Cloud feature allows migration of data between Jira Cloud sites, including:

Projects (company-managed and team-managed).

Issues, comments, and attachments.

Configurations (e.g., custom fields, workflows, automation rules). Limitations :

Deleted issues are not included in backups or exports and cannot be imported. To import:

Create a backup from the source site in Settings > System > Backup manager .

Use Settings > System > Import Jira Cloud on the target site. Note : Requires Jira administrator permissions and may involve Atlassian support for full migrations. (Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Why This Fits : Deleted issues are not part of the data exported from the source site, making them impossible to import, so Option C is the correct answer.

Why Other Options Are Incorrect :

Automation rules (Option A) :

Automation rules are included in Jira Cloud backups and can be imported to the target site using the Import Jira Cloud feature, provided they are compatible with the target site’s configuration.

Extract from Documentation :

Automation rules are included in Jira Cloud backups and can be imported, though some rules may require reconfiguration if dependencies (e.g., custom fields) differ.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Custom fields (Option B) :

Custom fields are part of the configuration data in a Jira Cloud backup and are imported to the target site. Their contexts and options are preserved during migration.

Extract from Documentation :

Custom fields, including their configurations and contexts, are included in backups and imported to the target site.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Team-managed projects (Option D) :

Team-managed projects are fully supported in Jira Cloud backups and can be imported to the target site, including their issues, configurations, and settings.

Extract from Documentation :

Both company-managed and team-managed projects are included in Jira Cloud backups and can be imported to another site.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Attachments (Option E) :

Attachments (media files) are included in Jira Cloud backups and can be imported to the target site, provided the backup includes media data.

Extract from Documentation :

Attachments are included in Jira Cloud backups and imported to the target site if media import is enabled.

(Source: Atlassian Support Documentation, "Import data to Jira Cloud")

Additional Notes :

The Import Jira Cloud feature is accessed via Settings > System > Import Jira Cloud and typically requires Jira administrator privileges, with possible Atlassian support for full migrations.

Deleted issues are permanently removed and cannot be recovered unless a backup from before deletion is available, but even then, they are not part of standard exports.

Other data (e.g., automation rules, custom fields) may require post-import reconfiguration if there are incompatibilities between sites.

In a team-managed project in Jira Software Cloud, notifications can be configured to alert specific users or roles when certain events occur, such as a change to a custom field. The question specifies a custom field called "Reviewer" with a field type of People, and asks who can be notified when this field changes. Based on Jira Cloud documentation for team-managed projects, the Reviewer (the user selected in the People field) can be notified (Option A).

Explanation of the Correct Answer (Option A):

In team-managed projects, notification schemes are simplified compared to company-managed projects. Project admins can configure notifications for specific events, such as changes to fields, through the Notifications settings in the project.

For a custom field of type People (e.g., "Reviewer"), Jira allows notifications to be sent to the user selected in that field when the field’s value changes. This is because the People field type stores a reference to a Jira user, and Jira’s notification system can dynamically resolve this user for notifications.

Exact Extract from Documentation:

Create and configure notifications in team-managed projects

In team-managed projects, you can set up notifications to inform specific people or roles about issue activity, like when an issue is updated or a field changes.

To configure notifications:

From your project’s sidebar, select Project settings > Notifications.

Select Add notification.

Choose an event, such as Issue updated or Field changed.

Select who to notify, such as:

A specific role, like Assignee or Reporter.

A user selected in a People field (e.g., a custom field like Reviewer).

Other options like watchers or specific users, depending on the event.

Note: Notifications in team-managed projects are simpler and don’t rely on notification schemes or custom events like company-managed projects.

(Source: Atlassian Support Documentation, "Configure notifications in team-managed projects")

Why This Fits: The documentation confirms that a user selected in a People field (such as the "Reviewer" field) can be notified when that field changes. This makes Reviewer the correct choice, as it directly corresponds to the user selected in the custom field.

Why Other Options Are Incorrect:

Current User (Option B):

The Current User refers to the user who performs the action (e.g., the person who changes the Reviewer field). While it’s possible to notify the Current User for some events in team-managed projects, the question asks specifically about notifying someone when the Reviewer field changes, and the most relevant recipient is the user selected in the Reviewer field, not the person making the change.

Extract from Documentation:

Notify the current user

You can choose to notify the user who triggers the event, like the person who updates an issue. This is available for most events in team-managed projects.

(Source: Atlassian Support Documentation, "Configure notifications in team-managed projects")

Single specified email address (Option C):

Team-managed projects do not support sending notifications to a single specified email address that is not associated with a Jira user account. Notifications must be sent to users or roles within the Jira system (e.g., Assignee, Reporter, or a user in a People field).

Extract from Documentation:

Notifications in team-managed projects are sent to users or roles associated with the issue, such as the assignee, reporter, or a user in a custom field. External email addresses are not supported.

(Source: Atlassian Support Documentation, "Configure notifications in team-managed projects")

Single selected user (Option D):

While team-managed projects allow notifications to be sent to a specific user (e.g., a hardcoded user selected during notification configuration), this is not dynamic and does not align with the question’s focus on the Reviewer field changing. Notifying a single selected user would mean the same user is notified every time, regardless of who is set as the Reviewer, which is less relevant than notifying the actual Reviewer.

Extract from Documentation:

You can choose a specific user to notify, but this is a static selection and not tied to dynamic field values like a People field.

(Source: Atlassian Support Documentation, "Configure notifications in team-managed projects")

Group (Option E):

Team-managed projects do not support sending notifications to entire groups of users. Notifications are limited to individual users, roles, or users selected in fields like People fields. This restriction simplifies the notification system in team-managed projects compared to company-managed projects.

Extract from Documentation:

Unlike company-managed projects, team-managed projects don’t support notifying groups or project roles. Notifications are limited to individual users, roles like Assignee, or users in People fields.

(Source: Atlassian Support Documentation, "Configure notifications in team-managed projects")

Additional Notes:

The People field type in Jira is specifically designed to store a single user (or multiple users, depending on configuration), and it integrates with the notification system to allow dynamic notifications based on the selected user(s).

In team-managed projects, the notification configuration is more user-friendly and does not require complex setups like custom events or notification schemes, which are exclusive to company-managed projects.

The question’s focus on the Reviewer field changing makes the user in that field (the Reviewer) the most logical recipient of the notification.

To find issues where Tom set the priority to Highest during the current month, regardless of the current priority value, the JQL query must use the WAS operator to check the historical priority value and the BY clause to specify the user (Tom), along with a time range for the current month. The correct query is priority was Highest by tom after startOfMonth() (Option B).

Explanation of the Correct Answer (Option B) :

The condition Tom set the priority value to “Highest” sometime this month requires checking the issue’s change history for the priority field. The WAS operator checks if a field had a specific value at some point, and the BY clause filters for changes made by a specific user (Tom). The after startOfMonth() clause ensures the change occurred within the current month (from the first day of the month to the present).

The condition the priority value may or may not be “Highest” now means the query should not filter based on the current priority value, which Option B correctly avoids by not including a current-state condition (e.g., priority = Highest ).

The query priority was Highest by tom after startOfMonth() returns issues where Tom changed the priority to Highest after the start of the current month, satisfying both conditions.

Exact Extract from Documentation :

Advanced searching - operators reference

The WAS operator checks if a field had a specific value at some point in the issue’s history.

priority was Highest by tom after startOfMonth() returns issues where the priority field was set to Highest by the user tom after the start of the current month. Note : The WAS operator does not check the current field value, only historical values. Use after to specify a time range. (Source: Atlassian Support Documentation, "Advanced searching - operators reference")

Why This Fits : The query uses WAS to check historical priority changes by Tom to Highest within the current month, without restricting the current priority, making Option B the correct answer.

Why Other Options Are Incorrect :

priority changed to Highest by tom before endOfMonth() (Option A) :

The CHANGED operator checks for transitions in field values, but before endOfMonth() includes all changes up to the end of the current month, including past months, which is too broad. The query needs to limit changes to the current month (e.g., after startOfMonth() ).

Extract from Documentation :

The CHANGED operator requires FROM and TO clauses for specific transitions. before endOfMonth() includes all prior changes, not just the current month.

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

priority was Highest by tom during (startOfMonth(), endOfMonth()) and priority = Highest or priority != Highest (Option C) :

The during (startOfMonth(), endOfMonth()) clause is valid for time ranges, but the additional condition priority = Highest or priority != Highest is redundant and always true (it includes all issues). However, during is less precise than after startOfMonth() , as it may exclude changes on the last day of the month depending on timezone handling. This makes the query less optimal.

Extract from Documentation :

The during clause defines a time range but may have edge cases with end dates. after startOfMonth() is simpler for current-month filtering.

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

priority was Highest by tom and (priority = Highest by tom after startOfMonth() or priority != Highest) (Option D) :

The clause priority = Highest by tom after startOfMonth() is invalid, as the BY clause cannot be used with current-state conditions like priority = Highest . The WAS operator already covers the historical change, and the additional or priority != Highest is unnecessary and complicates the query.

Extract from Documentation :

The BY clause is used with WAS or CHANGED , not with current-state conditions like priority = Highest .

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

Additional Notes :

The query assumes Highest is a valid priority value (check in Settings > Issues > Priorities ).

The query can be tested in Issues > Search for issues and saved as a filter.

Ensure Tom’s user account is correctly referenced (e.g., username or user ID) and that the user running the query has Browse Projects permission.

Creating groups and managing group membership in Jira Software Cloud are system-level tasks that require the Jira administrator privilege. This privilege allows Jon to access user management settings and perform group-related actions.

Explanation of the Correct Answer (Option D) :

The Jira administrator privilege 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 to Settings > 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 : The Jira administrator privilege 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 requires Jira administrator privileges 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) :

The Product Admin role 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 requires Jira administrator privileges.

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 term system administrator is not a standard role in Jira Cloud. In some contexts, it may refer to Jira administrators or organization 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 to Settings > User management > Groups , which is restricted to Jira administrators .

If Jon is also an organization admin, he might have overlapping permissions, but the Jira administrator role is the most direct for group management in Jira.

In a company-managed project, workflows define the statuses and transitions for issues. Modifying a workflow using out-of-box functionality involves adding conditions , validators , post functions , or properties to transitions. The two requirements that can be satisfied using only out-of-box functionality are automatically clear Assignee when transitioning to Pending (Option C) and only members of Testers project role can transition to Passed (Option E).

Explanation of the Correct Answers :

Automatically clear Assignee when transitioning to Pending (Option C) :

This requirement can be met by adding a post function to the workflow transition to the Pending status. The out-of-box Clear Field Value post function can be used to clear the Assignee field during the transition.

Exact Extract from Documentation :

Configure workflow post functions

Post functions are executed after a transition is completed and can update issue fields or perform other actions. Out-of-box post functions include:

Clear Field Value : Clears the value of a specified field (e.g., Assignee). To add a post function:

Go to Settings > Issues > Workflows .

Edit the workflow and select the transition to Pending.

Add the Clear Field Value post function and choose Assignee . Note : Post functions are executed automatically during the transition, requiring no additional configuration. (Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Why This Fits : The Clear Field Value post function is an out-of-box feature that directly clears the Assignee field during the transition to Pending , satisfying the requirement without custom scripting or apps.

Only members of Testers project role can transition to Passed (Option E) :

This requirement can be met by adding a condition to the workflow transition to the Passed status. The out-of-box User Is In Project Role condition can restrict the transition to members of the Testers project role.

Exact Extract from Documentation :

Configure workflow conditions

Conditions restrict who can execute a workflow transition. Out-of-box conditions include:

User Is In Project Role : Allows only users in a specified project role (e.g., Testers) to perform the transition. To add a condition:

Go to Settings > Issues > Workflows .

Edit the workflow and select the transition to Passed.

Add the User Is In Project Role condition and select the Testers role. Note : Conditions are evaluated before the transition is displayed, ensuring only authorized users see the option. (Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Why This Fits : The User Is In Project Role condition is an out-of-box feature that restricts the Passed transition to the Testers project role, satisfying the requirement without custom scripting or apps.

Why Other Options Are Incorrect :

Automatically set Due Date based on the issue type (Option A) :

Out-of-box post functions allow setting a field to a specific value (e.g., Update Issue Field ) but do not support conditional logic based on issue type (e.g., setting different due dates for different issue types). This requirement would require a scripted post function or an automation rule, which goes beyond out-of-box workflow functionality.

Extract from Documentation :

Out-of-box post functions can update fields with static values (e.g., set Due Date to a specific date). Conditional logic based on issue type requires automation rules or third-party apps.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Only a subset of project users should be able to create epics (Option B) :

Creating epics is controlled by the Create Issues permission in the project’s permission scheme, not by workflow settings. While permissions can be restricted to a subset of users (e.g., a group or role), this is not a workflow modification. Additionally, restricting epic creation specifically (versus other issue types) requires issue type-specific permissions, which are not supported out-of-box without advanced configuration or apps.

Extract from Documentation :

The Create Issues permission controls who can create issues, including epics. Issue type-specific restrictions require advanced permission schemes or apps, not workflow changes.

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

Automatically reassign an issue when Priority is edited (Option D) :

Reassigning an issue when the Priority field is edited is not possible with out-of-box workflow post functions, as post functions are tied to transitions, not field edits. This requirement would require a Jira automation rule or a scripted listener, which goes beyond out-of-box workflow functionality.

Extract from Documentation :

Post functions are executed during workflow transitions, not field edits. To react to field changes like Priority, use Jira automation or third-party apps.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")

Additional Notes :

Modifying workflows requires Jira administrator privileges, as workflows are managed at the system level ( Settings > Issues > Workflows ).

Out-of-box functionality refers to native Jira features without scripting, third-party apps, or automation rules. Options C and E leverage standard post functions and conditions, while A, B, and D require additional logic or non-workflow configurations.

In a company-managed project, a single workflow can be shared across multiple issue types (e.g., Blogs and Ideas) via a workflow scheme that maps workflows to issue types. To satisfy a requirement that necessitates a second workflow, the requirement must involve workflow-specific differences that cannot be handled within a single workflow. The requirement that Blogs should allow reopening after they are closed, but not Ideas (Option D) requires a second workflow, as reopening involves a transition that must be present for Blogs but absent for Ideas.

Explanation of the Correct Answer (Option D) :

The requirement to allow Blogs to be reopened after being closed, but not Ideas , means the workflow for Blogs must include a transition from the Closed status to an open status (e.g., Open or Reopened ), while the workflow for Ideas must not include this transition. In a single workflow, transitions apply to all issue types using that workflow, so it is impossible to have a transition for Blogs but not Ideas. Therefore, a second workflow is needed: one for Blogs (with a reopen transition) and one for Ideas (without a reopen transition). These workflows can be assigned to the respective issue types via the project’s workflow scheme .

Exact Extract from Documentation :

Configure workflows in company-managed projects

Workflows define statuses and transitions for issues. A workflow scheme maps workflows to issue types in a project.

To use different workflows for different issue types:

Create separate workflows (e.g., one for Blogs with a reopen transition, one for Ideas without).

Go to Settings > Issues > Workflow schemes .

Edit the project’s workflow scheme to assign the appropriate workflow to each issue type (e.g., Blogs to Workflow A, Ideas to Workflow B). Note : A single workflow applies the same transitions to all issue types it governs. To have different transitions (e.g., reopening for Blogs but not Ideas), use separate workflows. (Source: Atlassian Support Documentation, "Configure workflow schemes")

Why This Fits : The need for a reopen transition for Blogs but not Ideas requires distinct workflows, as a single workflow cannot differentiate transitions by issue type, making Option D the correct answer.

Why Other Options Are Incorrect :

Blogs should be auto-closed after 3 days, but not Ideas (Option A) :

Auto-closing issues after 3 days can be achieved using a Jira automation rule (e.g., a scheduled rule that transitions Blogs to Closed based on a time condition). This does not require a workflow change, as the transition to Closed can exist in a shared workflow, and the automation rule can filter by issue type (Blogs).

Extract from Documentation :

Use Jira automation to transition issues based on time conditions (e.g., close Blogs after 3 days). Filter by issue type to exclude Ideas. This does not require separate workflows.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")

Blogs should be editable after they are closed, but not Ideas (Option B) :

Editability after closing is controlled by the Edit Issues permission and workflow properties (e.g., jira.issue.editable). A workflow property can be set on the Closed status to allow editing for Blogs but not Ideas, or a separate field configuration scheme can make fields read-only for Ideas. This can be managed without a second workflow.

Extract from Documentation :

Use workflow properties (e.g., jira.issue.editable=true) or field configuration schemes to control editability by issue type. Separate workflows are not required.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Blogs should be sent to the project lead each Friday, but not Ideas (Option C) :

Sending issues to the project lead each Friday can be handled with a Jira automation rule (e.g., a scheduled rule that sends an email or creates a task for Blogs). This is independent of the workflow, as it involves notifications or actions, not status transitions.

Extract from Documentation :

Use Jira automation to send notifications or tasks for specific issue types (e.g., Blogs) on a schedule (e.g., every Friday). This does not require workflow changes.

(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance")

Additional Notes :

Creating a second workflow requires Jira administrator privileges to modify workflows ( Settings > Issues > Workflows ) and update the workflow scheme ( Project settings > Workflows ).

The workflow scheme can assign different workflows to Blogs and Ideas, ensuring the reopen transition is only available for Blogs.

Options A, B, and C can be addressed with automation or other configurations, but Option D fundamentally requires distinct workflows due to the transition difference.

Since all company-managed projects share a single configuration (including permission schemes), permissions are applied uniformly across projects. A project role is necessary when a requirement involves project-specific differences in user permissions, as roles allow membership to vary by project. The requirement that only some Compliance users can delete issues and they differ in each project (Option A) necessitates a project role, as it requires project-specific user assignments for the Delete Issues permission.

Explanation of the Correct Answer (Option A) :

The requirement states that only some Compliance users can delete issues , and the specific users differ in each project . In a shared permission scheme, permissions like Delete Issues are granted to users, groups, or project roles. Using a group would apply the same users across all projects, which does not allow for different users per project. A project role (e.g., “Compliance Deleters”) can be added to the Delete Issues permission in the shared permission scheme, and different Compliance users can be added to this role in each project’s Project settings > People , accommodating the project-specific variation.

Exact Extract from Documentation :

Manage project roles

Project roles allow permissions to be granted to different users in each project, even with a shared permission scheme.

To configure:

Create a new project role in Settings > System > Project roles (e.g., “Compliance Deleters”).

Add the role to a permission (e.g., Delete Issues ) in the permission scheme ( Settings > Issues > Permission schemes ).

Add users to the role in each project’s Project settings > People . Example : Grant Delete Issues to the “Compliance Deleters” role, then assign different users to the role in each project. Note : Project roles are ideal for permissions that vary by project while maintaining a shared scheme. (Source: Atlassian Support Documentation, "Manage project roles")

Why This Fits : A project role allows different Compliance users to have the Delete Issues permission in each project, satisfying the requirement for project-specific variation while keeping the shared configuration, making Option A the correct answer.

Why Other Options Are Incorrect :

All members need to be able to move issues (Option B) :

The Move Issues permission can be granted to all Compliance users via a group (e.g., “Compliance Team”) in the shared permission scheme. Since the requirement applies uniformly to all members across all projects, a project role is not necessary, as there is no project-specific variation.

Extract from Documentation :

Permissions like Move Issues can be granted to a group in a shared permission scheme, applying to all projects without needing project-specific roles.

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

Only two Compliance users should be able to see secured issues (Option C) :

Secured issues are managed by an issue security scheme , where security levels define who can view issues (e.g., specific users, groups, or roles). To allow only two Compliance users to see secured issues, you can create a security level listing those two users explicitly or a group containing only them. This does not require a project role, as the same two users apply across all projects, and security levels are part of the shared configuration.

Extract from Documentation :

Issue security levels can specify individual users or groups to restrict visibility. Project roles are not required unless visibility varies by project.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

Only some Compliance users need to create shared dashboards (Option D) :

Creating shared dashboards requires the Share dashboards and filters global permission, not a project-level permission. This can be granted to a group containing the relevant Compliance users in Settings > System > Global permissions . Since this is a global permission, it does not vary by project and does not require a project role.

Extract from Documentation :

The Share dashboards and filters global permission allows users to share dashboards. It is granted globally, not via project roles.

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

Additional Notes :

Steps to configure Option A :

Create a “Compliance Deleters” project role in Settings > System > Project roles .

Add the role to the Delete Issues permission in the shared permission scheme ( Settings > Issues > Permission schemes ).

For each project, add the appropriate Compliance users to the “Compliance Deleters” role in Project settings > People .

This configuration requires Jira administrator privileges to create the role and modify the permission scheme, but project admins can manage role membership.

The shared configuration (permission scheme, etc.) is preserved, as the project role integrates seamlessly.

The issue is that users cannot see the Browser Type field 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 are field 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 configurations determine whether a field is required, optional, or hidden for specific issue types in a project. If the Browser Type field is marked as Hidden in 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 to Project settings > Fields .

Review the field configuration for the issue type (e.g., Bug).

Ensure the field (e.g., Browser Type) is not marked as Hidden . Note : Hidden fields are completely removed from issue operations. (Source: Atlassian Support Documentation, "Configure field settings")

Why This Fits : If Browser Type is 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) :

The custom field context defines which projects and issue types a custom field applies to. If the Browser Type field’s context does not include the DEV project or the Bug issue 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 in Settings > 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 the Browser Type field’s context excludes the DEV project or Bug issue type, it will not be available, making this a possible root cause.

Project permissions (Option D) :

The Edit Issues permission in the project’s permission scheme determines whether users can edit issues, including fields like Browser 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

The Edit Issues permission allows users to modify issue fields, including custom fields.

If users cannot edit a field:

Check Project settings > Permissions .

Ensure the user, group, or role has the Edit Issues permission. 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 the Edit Issues permission, they may not be able to edit or see the Browser Type field 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 affecting Edit 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 like Edit Issues for editability issues.

(Source: Atlassian Support Documentation, "Manage project roles")

Issue security scheme (Option E) :

An issue security scheme restricts which issues a user can view based on security levels. If users can see the bug issues but not the Browser Type field, the issue is not about issue visibility but field visibility or editability, so the 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:

Check Project settings > Fields to ensure Browser Type is not hidden in the field configuration for bugs.

Verify the field’s context in Settings > Issues > Custom fields includes the DEV project and Bug issue type.

Confirm users have the Edit Issues permission in Project settings > Permissions .

Other potential causes (not listed) include the field not being on the Edit screen (screen configuration) or being hidden in the issue layout , but these are covered by field configurations and permissions broadly.

Resolving these issues may require Jira administrator (for field configurations, contexts) or project admin (for permissions) privileges.

Restoring a Jira Cloud instance with a backup involves importing data, users, and media from the backup file. Valid options include importing data, merging or overwriting users, and importing media. However, importing apps (Option B) is not a valid option, as apps are not included in Jira Cloud backups and must be reinstalled separately.

Explanation of the Correct Answer (Option B) :

Jira Cloud backups include issues, configurations, users, and media (e.g., attachments) but do not include installed apps or their data. Restoring a backup does not involve importing apps, as apps must be reinstalled from the Atlassian Marketplace and configured separately.

Exact Extract from Documentation :

Restore Jira Cloud from a backup

A Jira Cloud backup includes:

Issues and their history.

Configurations (e.g., workflows, schemes).

Users and groups.

Media (e.g., attachments). When restoring:

Import data : Restore issues and configurations.

Merge with existing Cloud users : Add users from the backup without overwriting existing users.

Overwrite existing Cloud users : Replace existing users with those from the backup.

Import media : Restore attachments and other media. Note : Apps and their data are not included in backups. Reinstall apps from the Atlassian Marketplace after restoring. (Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")

Why This Fits : Importing apps is not a valid option for restoring a Jira Cloud backup, as apps are excluded from backups, making Option B the correct answer.

Why Other Options Are Incorrect :

Import data (Option A) :

Importing data is a valid option, as it restores issues, configurations, and other Jira data from the backup.

Extract from Documentation :

Import data to restore issues, projects, and configurations from a Jira Cloud backup.

(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")

Merge with existing Cloud users (Option C) :

Merging users is a valid option, allowing users from the backup to be added to the existing Cloud instance without overwriting current users.

Extract from Documentation :

Choose Merge with existing Cloud users to add users from the backup while preserving existing user accounts.

(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")

Overwrite existing Cloud users (Option D) :

Overwriting users is a valid option, replacing existing users with those from the backup.

Extract from Documentation :

Choose Overwrite existing Cloud users to replace current users with those from the backup.

(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")

Import media (Option E) :

Importing media is a valid option, restoring attachments and other media files from the backup.

Extract from Documentation :

Import media to restore attachments and other files included in the backup.

(Source: Atlassian Support Documentation, "Restore your Jira Cloud site from a backup")

Additional Notes :

Restoring a Jira Cloud backup requires Jira administrator or organization admin privileges and is done via Settings > System > Restore .

After restoring, apps must be reinstalled, and their data may need to be reimported if the app supports it.

Managing product subscriptions and billing for a Jira site is a task handled at the Atlassian organization level, not within the Jira product itself. The organization admin role is required to perform these actions, as it grants access to billing and subscription management.

Explanation of the Correct Answer (Option A) :

The organization admin role allows users to manage the Atlassian organization, including product subscriptions, billing, and user access across all products (e.g., Jira Software, Confluence). Francis needs this role to manage subscriptions and billing for the Jira site.

Exact Extract from Documentation :

Organization admin role

Organization administrators manage the Atlassian organization, including:

Managing product subscriptions and billing.

Adding or removing users from the organization.

Configuring organization-wide settings like security policies. To manage billing:

Go to admin.atlassian.com .

Select Billing to view and update subscription details. Note : Only organization admins can manage subscriptions and billing. Product admins or Jira admins cannot access these settings. (Source: Atlassian Support Documentation, "Manage your Atlassian organization")

Why This Fits : The organization admin role is the only role that grants access to billing and subscription management, making Option A the correct choice.

Why Other Options Are Incorrect :

Product admin role for Jira Software (Option B) :

The product admin role for Jira Software allows users to manage user access and settings specific to Jira Software (e.g., adding users to the product). It does not include access to billing or subscription management, which is handled at the organization level.

Extract from Documentation :

Product admins for Jira Software manage user access and product-specific settings but cannot manage subscriptions or billing.

(Source: Atlassian Support Documentation, "Manage product access")

Administer Jira global permission (Option C) :

The Administer Jira global permission (Jira administrator role) allows users to manage Jira-specific settings, such as schemes, workflows, and user groups. It does not grant access to organization-level billing or subscription management.

Extract from Documentation :

The Administer Jira permission allows managing Jira settings, such as schemes and permissions, but does not include billing or subscription management, which is handled by organization admins.

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

Product admin role for Jira Administration (Option D) :

There is no distinct product admin role for Jira Administration in Jira Cloud. The term may be confused with the Jira administrator role or product admin role for Jira Software, neither of which grants billing access.

Extract from Documentation :

Jira Cloud uses roles like Jira administrator and product admin for Jira Software. Billing and subscriptions are managed by organization admins, not product-specific roles.

(Source: Atlassian Support Documentation, "Manage your Atlassian organization")

Additional Notes :

Francis must access admin.atlassian.com to manage subscriptions and billing, which requires the organization admin role .

Other roles (e.g., Jira administrator) may be involved in configuring Jira settings but are irrelevant for billing tasks.

To create an automation rule that triggers when a Story is updated, checks if it is unestimated (i.e., has no Story Points), and comments on its Sub-tasks, the rule requires a Branch rule on Sub-tasks to target the Sub-tasks and an Issue fields condition on whether Story Points is empty to check the unestimated status. These two elements are essential to meet the rule’s requirements.

Explanation of the Correct Answers :

Branch rule on Sub-tasks (Option A) :

The rule needs to comment on the Sub-tasks of the updated Story. A Branch rule is used in Jira automation to perform actions on related issues, such as Sub-tasks. The Branch rule on Sub-tasks allows the rule to iterate over each Sub-task of the Story and execute the comment action.

Exact Extract from Documentation :

Branch rule / related issues

A branch rule allows actions to be performed on issues related to the trigger issue, such as Sub-tasks, Epics, or linked issues.

To comment on Sub-tasks:

Add a Branch rule / related issues component.

Select Sub-tasks as the related issue type.

Add a Comment on issue action within the branch to comment on each Sub-task. Note : The branch rule processes each related issue individually. (Source: Atlassian Support Documentation, "Jira automation actions")

Why This Fits : The Branch rule on Sub-tasks is necessary to target the Sub-tasks of the Story and apply the comment action, satisfying the requirement to comment on Sub-tasks.

Issue fields condition on whether Story Points is empty (Option B) :

The rule must check if the Story is unestimated, meaning the Story Points field is empty (null or not set). The Issue fields condition allows checking the value of a field, such as Story Points , to ensure it meets a condition (e.g., is empty).

Exact Extract from Documentation :

Issue fields condition

The Issue fields condition checks the value of an issue field against a specified criterion.

To check if Story Points is empty:

Add an Issue fields condition .

Select Story Points as the field.

Set the condition to is empty . Note : This condition ensures the rule only proceeds if the field has no value. (Source: Atlassian Support Documentation, "Jira automation conditions")

Why This Fits : The Issue fields condition on whether Story Points is empty ensures the rule only comments on Sub-tasks if the Story is unestimated, satisfying the condition requirement.

Why Other Options Are Incorrect :

Related issues condition on Issues in the sprint (Option C) :

A Related issues condition checks if related issues (e.g., Sub-tasks, Epics) meet certain criteria. The requirement does not involve checking the sprint status of issues, only that the Story is unestimated and comments are added to Sub-tasks. This condition is irrelevant to the rule.

Extract from Documentation :

The Related issues condition checks if related issues meet a condition (e.g., all Sub-tasks are resolved). It is not needed for commenting on Sub-tasks without additional criteria.

(Source: Atlassian Support Documentation, "Jira automation conditions")

Branch rule on Stories (Option D) :

A Branch rule on Stories would target Stories, not Sub-tasks. Since the rule needs to comment on the Sub-tasks of the updated Story, a branch on Sub-tasks (Option A) is required, not Stories.

Extract from Documentation :

A Branch rule targets specific related issues (e.g., Sub-tasks, Epics). Choose the correct issue type to match the action (e.g., Sub-tasks for commenting on Sub-tasks).

(Source: Atlassian Support Documentation, "Jira automation actions")

Additional Notes :

The complete rule would look like this:

Trigger : Issue Updated (filter to Story issue type).

Condition : Issue fields condition (Story Points is empty).

Action : Branch rule on Sub-tasks.

Action : Comment on issue (add the desired comment).

The rule assumes the Story Points field is available and Sub-tasks exist for the Story.

The rule can be configured in Project settings > Automation (for project-level rules) or Settings > System > Automation rules (for global rules).

To move issues from the backlog to a planned sprint in a Jira Software Cloud project, Boris needs permissions to modify the issue’s sprint field and edit the issue itself. The two permissions required are Schedule Issues (Option B) and Edit Issues (Option D).

Explanation of the Correct Answers :

Schedule Issues (Option B) :

The Schedule Issues permission allows a user to add issues to a sprint, remove issues from a sprint, or move issues between sprints. This permission is necessary to move issues from the backlog (which is not part of a sprint) into a planned sprint.

Exact Extract from Documentation :

Schedule Issues permission

The Schedule Issues permission allows users to:

Add issues to a sprint.

Remove issues from a sprint.

Move issues between sprints or to the backlog. This permission is required to manage the sprint field in issues, such as moving an issue from the backlog to a planned sprint. Note : This permission is granted via the project’s permission scheme. (Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")

Why This Fits : Moving an issue to a planned sprint involves updating the Sprint field, which requires the Schedule Issues permission.

Edit Issues (Option D) :

The Edit Issues permission allows a user to modify issue fields, including the Sprint field. Without this permission, Boris cannot edit the issue to set its sprint, even if he has the Schedule Issues permission.

Exact Extract from Documentation :

Edit Issues permission

The Edit Issues permission allows users to modify issue fields, such as Summary, Description, or Sprint. This permission is required to update an issue’s details, including moving it to a sprint if combined with the Schedule Issues permission.

Note : This permission is granted via the project’s permission scheme.

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

Why This Fits : Editing the Sprint field to move an issue into a planned sprint requires the Edit Issues permission, as it involves modifying the issue’s metadata.

Why Other Options Are Incorrect :

Work On Issues (Option A) :

The Work On Issues permission allows users to log work on issues (e.g., record time spent). It is not related to moving issues to a sprint or editing issue fields.

Extract from Documentation :

Work On Issues permission

Allows users to log work on issues using the time tracking feature. This does not include editing issue fields or managing sprints.

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

Move Issues (Option C) :

The Move Issues permission allows users to move issues between projects or change their issue type within the same project. Moving an issue to a sprint does not involve changing its project or issue type, so this permission is not required.

Extract from Documentation :

Move Issues permission

Allows users to move issues to a different project or change their issue type. This is not required for moving issues to a sprint within the same project.

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

Manage Sprints (Option E) :

The Manage Sprints permission allows users to create, start, complete, or delete sprints. While this permission is necessary for managing the sprint itself, it is not required to move issues into a planned sprint, as Boris is not creating or modifying the sprint.

Extract from Documentation :

Manage Sprints permission

Allows users to create, start, complete, or delete sprints. Moving issues to an existing sprint requires the Schedule Issues and Edit Issues permissions, not Manage Sprints .

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

Assignable User (Option F) :

The Assignable User permission allows a user to be assigned to issues (i.e., set as the Assignee). It does not affect the ability to move issues to a sprint.

Extract from Documentation :

Assignable User permission

Allows users to be set as the assignee of an issue. This does not include editing other fields like the Sprint field.

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

Additional Notes :

Boris likely already has the Browse Projects permission, as he can review his assigned issues. The Schedule Issues and Edit Issues permissions are specifically required for the action of moving issues to a sprint.

These permissions are granted via the project’s permission scheme, which can be checked in Project settings > Permissions .

When moving stories from a company-managed project to a team-managed project using a bulk operation, certain issue attributes are preserved, while others may change or be lost due to differences in project configurations. The definite outcome is that their comments will remain the same (Option A), as comments are retained during issue moves.

Explanation of the Correct Answer (Option A) :

Comments are part of an issue’s data and are preserved when moving issues between projects, whether from a company-managed to a team-managed project or vice versa. The bulk move operation retains all comments attached to the stories, ensuring they remain visible in the target team-managed project.

Exact Extract from Documentation :

Move issues in Jira Cloud

When moving issues between projects:

Comments : All comments are retained, including their content, author, and timestamps. To move issues:

Select issues and choose Bulk change > Move issues .

Choose the target project and issue type.

Map fields and statuses as needed. Note : Comments are preserved regardless of the source or target project type (company-managed or team-managed). (Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Why This Fits : The bulk move operation ensures that comments are transferred with the stories, making their comments will remain the same a definite outcome.

Why Other Options Are Incorrect :

Their keys will remain the same (Option B) :

Issue keys (e.g., PROJ-123) are project-specific, consisting of the project key and an issue number. When moving issues to a different project (from a company-managed to a team-managed project), the issues are assigned new keys based on the target project’s key (e.g., NEWPROJ-456). The original keys do not remain the same.

Extract from Documentation :

When moving issues to a different project, the issue keys change to reflect the target project’s key. The original key is preserved in the issue history as a reference.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Their issue links will be lost (Option C) :

Issue links (e.g., “blocks,” “is related to”) are generally preserved during a move, provided the linked issues remain accessible in the target project and the link types are supported. While there could be rare cases where links to restricted issues are affected, it is not a definite outcome that links will be lost.

Extract from Documentation :

Issue links are retained during a move unless the linked issues are inaccessible in the target project due to permissions or restrictions.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Their issue history will be lost (Option D) :

The issue history (e.g., status changes, field updates) is preserved during a move. The history is transferred to the target project, maintaining a record of all changes, including those from the source project.

Extract from Documentation :

The issue history, including all changes and updates, is retained when moving issues between projects.

(Source: Atlassian Support Documentation, "Move issues in Jira Cloud")

Additional Notes :

Steps for the bulk move :

Run a filter to select the stories in Issues > Search for issues .

Choose Bulk change > Move issues .

Select the team-managed project and map statuses or fields as needed.

The operation requires the Move Issues permission in the source project and Create Issues permission in the target project.

Other attributes (e.g., status , custom fields ) may need mapping due to differences between company-managed and team-managed projects, but comments are always preserved.

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

Explanation of the Correct Answer (Option A) :

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

Leila, as a member of the Sales 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 where Leila has the Sales project role.

Exact Extract from Documentation :

Advanced searching - functions reference

The projectsWhereUserHasRole("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 the Sales project 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 where Leila 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 by assignee or group membership. It only selects issues based on the projects where the user has the Sales role, regardless of who the issues are assigned to.

Extract from Documentation :

To filter by assignee, use assignee in membersOf("group"). The projectsWhereUserHasRole function 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 uses projectsWhereUserHasRole("Sales") , which checks for the Sales project 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. Use projectsWhereUserHasRole for roles, not membersOf for groups.

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

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

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

Extract from Documentation :

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

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

Additional Notes :

The Sales project role must exist in the relevant projects, and Leila must be added to it in Project settings > People for those projects.

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

Leila must have Browse Projects permission for the projects returned by the query to see the issues.

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 that issue 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 to Project settings > Details .

Update the Name field 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:// < site > .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 the project name. To change the project key, use the Change project key option, 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 in Project settings > Details .

The scenario indicates that a filter returns 120 issues, but Sven can only see the 5 issues assigned to him. This suggests that issue-level security is restricting Sven’s visibility to only those issues where he is the assignee. The root cause is that “Current Assignee” is listed in the security level (Option A), limiting visibility of other issues.

Explanation of the Correct Answer (Option A) :

In a company-managed project with issue-level security, security levels define who can view an issue based on criteria like users, groups, roles, or fields (e.g., Current Assignee ). If a security level includes Current Assignee , only the user assigned to the issue can view it (along with others specified in the level, if any). Since Sven can only see the 5 issues assigned to him, the security level for the other 115 issues likely includes Current Assignee , and Sven is not the assignee for those issues, nor does he meet other criteria in the security level.

Exact Extract from Documentation :

Configure issue security schemes

Issue security levels restrict who can view issues based on criteria like users, groups, project roles, or fields (e.g., Reporter, Assignee).

For example, if a security level includes Current Assignee , only the user assigned to the issue (and others specified in the level) can view it.

To check security levels:

Go to Project settings > Issue security .

Review the security levels and their criteria. Note : Users must have the Browse Projects permission to view issues, but security levels further restrict visibility. (Source: Atlassian Support Documentation, "Configure issue security schemes")

Why This Fits : The security level restricting visibility to Current Assignee explains why Sven can only see the 5 issues assigned to him, as he does not meet the criteria for viewing the other 115 issues.

Why Other Options Are Incorrect :

Sven lacks “Set Issue Security” permission (Option B) :

The Set Issue Security permission allows users to set or change the security level of an issue. It does not affect a user’s ability to view issues. Sven’s issue is about visibility, not setting security levels.

Extract from Documentation :

The Set Issue Security permission controls who can set the Security Level field. Viewing issues is controlled by the Browse Projects permission and security levels.

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

The filter is private (Option C) :

If the filter were private, Sven would not be able to access it at all. Since he can see the filter and 5 issues, the filter is accessible to him, and privacy is not the issue. The problem lies in issue visibility.

Extract from Documentation :

Private filters are only accessible to their owner or shared users. If a user can view a filter, visibility of issues is determined by permissions and security levels.

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

Sven lacks “Assign Issues” permission (Option D) :

The Assign Issues permission allows users to assign issues to others or themselves. It does not affect the ability to view issues. Sven’s issue is about seeing issues, not assigning them.

Extract from Documentation :

The Assign Issues permission allows users to change the assignee of an issue. Viewing issues requires the Browse Projects permission and appropriate security level access.

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

The other issues are unassigned (Option E) :

If the other issues were unassigned, they might not be visible if the security level only allows Current Assignee to view issues. However, this does not fully explain why Sven cannot see all 115 issues, as some could be assigned to others. The root cause is the security level’s restriction, not the assignment status.

Extract from Documentation :

Unassigned issues can be restricted by security levels if the level does not include criteria like Current Assignee or other roles Sven belongs to.

(Source: Atlassian Support Documentation, "Configure issue security schemes")

Additional Notes :

Sven likely has the Browse Projects permission, as he can see the filter and 5 issues. The issue-level security is the limiting factor, with Current Assignee in the security level restricting his visibility.

To resolve the issue, check the issue security scheme in Project settings > Issue security and verify the criteria for each security level.

To fire a custom notification event during a workflow transition in a company-managed project, a post function must be configured in the workflow. Post functions are used to perform actions, such as firing events, after a transition is executed. The Fire a Generic Event post function (or a specific event post function) is used to trigger the custom notification event.

Explanation of the Correct Answer (Option D) :

A post function is a workflow element that executes actions after a transition is completed. To fire a custom notification event, the Fire a Generic Event post function (or a similar event-specific post function) is added to the transition, specifying the custom event. This event is then mapped to recipients in the project’s notification scheme to send notifications.

Exact Extract from Documentation :

Configure workflow post functions

Post functions are executed after a transition is completed and can perform actions like firing events for notifications. Out-of-box post functions include:

Fire a Generic Event : Fires a specified event (e.g., a custom event) to trigger notifications defined in the notification scheme. To configure:

Go to Settings > Issues > Workflows .

Edit the workflow and select the desired transition.

Add the Fire a Generic Event post function and select the custom event. Note : The event must be defined in Settings > System > Events and mapped to recipients in the project’s notification scheme. (Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Why This Fits : The post function is the workflow element responsible for firing a custom notification event during a transition, making Option D the correct choice.

Why Other Options Are Incorrect :

Validator (Option A) :

Validators check conditions before a transition is executed (e.g., ensuring a field is filled). They do not trigger events or send notifications.

Extract from Documentation :

Validators ensure that conditions are met before a transition can proceed. They do not perform actions like firing events.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Transition property (Option B) :

Transition properties are used to customize transition behavior (e.g., restricting who can see a transition button). They do not trigger events or send notifications.

Extract from Documentation :

Transition properties customize transition behavior, such as visibility or restrictions, but do not fire events or trigger notifications.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Condition (Option C) :

Conditions determine whether a user can see or execute a transition (e.g., restricting to a role). They do not trigger events or send notifications.

Extract from Documentation :

Conditions restrict who can perform a transition. They do not execute actions like firing events.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Trigger (Option E) :

Triggers in workflows (not to be confused with automation rule triggers) are used to automatically execute transitions based on external events (e.g., a commit in a linked repository). They do not fire notification events.

Extract from Documentation :

Triggers automatically execute transitions based on external events (e.g., code commits). They do not fire notification events.

(Source: Atlassian Support Documentation, "Configure advanced work item workflows")

Additional Notes :

Before configuring the post function, the custom event must be created in Settings > System > Events by a Jira administrator.

The project’s notification scheme must map the custom event to the desired recipients (e.g., users, roles, or groups).

Configuring the post function requires Jira administrator privileges, as workflows are managed at the system level.

To use a newly added custom field in a company-managed project, you must ensure it appears on the appropriate screens (e.g., Create, Edit, View) for the project’s issue types. The configuration that must be modified is the screen (Option B), as the field needs to be added to the screen(s) used by the project.

Explanation of the Correct Answer (Option B) :

The custom field is already available to all issue types and projects, meaning its context is configured globally. To make the field usable in your company-managed project, it must be added to the screen associated with the project’s issue types (via the screen scheme ). Screens determine which fields are displayed during issue operations (Create, Edit, View), and adding the custom field to the relevant screen ensures users can interact with it.

Exact Extract from Documentation :

Add a custom field to a screen

To use a custom field in a project, it must be added to the screens used for Create, Edit, or View operations.

To add a field:

Go to Settings > Issues > Screens .

Select the screen associated with the project’s issue types.

Add the custom field to the screen. Note : Ensure the screen is part of the project’s screen scheme ( Project settings > Screens ). If the field is not on the screen, it will not appear during issue operations. (Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")

Why This Fits : Adding the custom field to the project’s screen is a necessary configuration to make it usable, as it ensures the field is visible and editable, meeting the requirement to use the field in the project.

Why Other Options Are Incorrect :

Field configuration (Option A) :

Field configurations control whether a field is required, optional, or hidden. While you might later adjust the field’s behavior (e.g., make it required), the field is already available and does not require field configuration changes to be used initially. Adding it to a screen is the primary step.

Extract from Documentation :

Field configurations manage field behavior (e.g., required, hidden). Adding a field to a screen is required before configuring its behavior.

(Source: Atlassian Support Documentation, "Configure field settings")

Custom field context (Option C) :

The custom field’s context is already configured to include all issue types and projects, so no changes are needed here. Contexts define the projects and issue types a field applies to, and this is already set correctly.

Extract from Documentation :

Custom field contexts define where a field is available. If a field is already available to all projects and issue types, no context changes are needed.

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

Issue layout (Option D) :

The issue layout controls which fields are displayed or hidden in the issue view and filter results. While you might later adjust the issue layout to show the field in the issue view, the initial step to use the field is adding it to the screen for Create/Edit operations. The screen configuration is more fundamental.

Extract from Documentation :

Issue layouts control field visibility in the issue view. Fields must first be added to screens for Create/Edit operations before appearing in the issue layout.

(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")

Additional Notes :

Steps to configure :

Identify the screen(s) used by the project’s issue types in Project settings > Screens .

Go to Settings > Issues > Screens , select the relevant screen, and add the custom field.

Configuring screens requires Jira administrator privileges.

After adding the field to the screen, you may also configure the issue layout or field configuration for additional control, but the screen is the first required step.

In Jira Software Cloud, the Assignee field for a new issue can be set to Automatic , in which case Jira determines the assignee based on the project’s Default Assignee setting and any component-specific Default Assignee settings. The issue in the ENG project has all four components selected (Activation, Bin, Cart, Database), and the Assignee is left as Automatic . The issue will be assigned to the Project Lead (Option E) due to the rules for handling multiple components with conflicting default assignees.

Explanation of the Correct Answer (Option E) :

Project Default Assignee : The project ENG has its Default Assignee set to the Project Lead , meaning that if no component-specific assignee is determined, the issue will be assigned to the Project Lead.

Component Default Assignees :

Activation : Default Assignee is Component lead (User 1).

Bin : Default Assignee is Project default (Project Lead).

Cart : Default Assignee is Component lead (User 3).

Database : Default Assignee is Unassigned .

Automatic Assignment Logic with Multiple Components : When an issue has multiple components selected, Jira evaluates the Default Assignee for each component:

If all components have the same default assignee, that user is assigned.

If components have different default assignees (or some are unassigned), Jira falls back to the project’s Default Assignee (Project Lead in this case).

In this scenario:

Activation assigns to User 1.

Bin assigns to the Project Lead (via project default).

Cart assigns to User 3.

Database assigns to Unassigned.

Since the components have conflicting default assignees (User 1, Project Lead, User 3, Unassigned), Jira cannot resolve to a single assignee and uses the project’s Default Assignee , which is the Project Lead .

Exact Extract from Documentation :

Configure default assignees

The Default Assignee for a project or component determines who is assigned to new issues when the Assignee field is set to Automatic .

Multiple components :

If an issue has multiple components with different default assignees, Jira assigns the issue to the project’s Default Assignee . To configure:

Go to Project settings > Components to set component default assignees.

Go to Project settings > Details to set the project’s Default Assignee . Note : The project’s Default Assignee is used when component assignees conflict. (Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Why This Fits : With conflicting default assignees across the four components, Jira assigns the issue to the project’s Default Assignee , which is the Project Lead , making Option E the correct answer.

Why Other Options Are Incorrect :

User 1 (Option A) :

User 1 is the default assignee for the Activation component (as the Component lead). However, with multiple components selected and different assignees (User 1, Project Lead, User 3, Unassigned), Jira falls back to the project’s Default Assignee (Project Lead), not User 1.

Extract from Documentation :

If multiple components have different default assignees, the project’s Default Assignee is used, not a component-specific assignee.

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

User 2 (Option B) :

User 2 is the Component lead for Bin , but the default assignee for Bin is set to Project default (Project Lead), not the Component lead. Even if it were User 2, the conflicting assignees across components would result in the Project Lead being assigned.

Extract from Documentation :

The Project default setting for a component assigns issues to the project’s Default Assignee , not the Component lead.

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

User 3 (Option C) :

User 3 is the default assignee for the Cart component (as the Component lead). However, the conflicting assignees across components (User 1, Project Lead, User 3, Unassigned) result in the Project Lead being assigned, not User 3.

Extract from Documentation :

Conflicting component assignees result in the project’s Default Assignee being used.

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

User 4 (Option D) :

User 4 is the Component lead for Database , but the default assignee for Database is Unassigned , not User 4. Even if it were User 4, the conflicting assignees would result in the Project Lead being assigned.

Extract from Documentation :

The Unassigned default assignee for a component does not override the project’s Default Assignee in conflicts.

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

Unassigned (Option F) :

While the Database component has a default assignee of Unassigned , the presence of other components with different assignees (User 1, Project Lead, User 3) creates a conflict, and Jira assigns the issue to the Project Lead, not Unassigned .

Extract from Documentation :

Unassigned as a default assignee is overridden by the project’s Default Assignee in cases of conflict.

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

Additional Notes :

The Default Assignee for the project is set in Project settings > Details , and component-specific default assignees are set in Project settings > Components .

The user creating the issue must have the Assign Issues permission, and the Project Lead must have the Assignable User permission to be assigned.

If only one component were selected (e.g., Activation), the issue would be assigned to User 1, but selecting all four components triggers the conflict resolution to the Project Lead.