In a company-managed project, a limited set of users should be notified when issues transition to Pending status, and the project admin must be able to manage the list of users. What two items must be configured? (Choose two.)
Project role
Workflow condition
Custom event
Workflow validator
Group
The Answer Is:
A, CExplanation:
To address the requirement of notifying a limited set of users when issues transition to a "Pending" status in a company-managed project, and allowing the project admin to manage the list of users, two key configurations are necessary: aproject roleand acustom event. Below is the detailed explanation based on official Jira Software Cloud documentation.
Project Role (Option A):
Purpose: Project roles allow project administrators to define and manage a group of users who can be assigned specific permissions or notification responsibilities within a project. This is critical for the requirement that the project admin must manage the list of users to be notified.
How It Works: In Jira, project roles (e.g., "Developers," "Administrators," or a custom role like "Pending Status Notifiers") are created and managed at the project level. The project admin can add or remove users from these roles without needing global admin permissions, which aligns with the requirement for the project admin to manage the user list.
Configuration Steps:
Navigate toProject Settings > Peoplein the company-managed project.
Create a new project role or use an existing one (e.g., "Pending Notifiers").
Add users to this role as needed. The project admin can update this list at any time.
In the notification scheme, associate the project role with the custom event (explained below) to ensure that users in this role receive notifications when the event is triggered.
Why This Is Necessary: Using a project role ensures scalability and flexibility. Instead of hardcoding individual users or groups in the notification scheme, a project role allows the admin to dynamically manage who receives notifications without modifying the underlying configuration.
Custom Event (Option C):
Purpose: A custom event is required to trigger notifications specifically for thetransition to the "Pending" status. Jira’s notification system relies on events to determine when and to whom notifications are sent. By creating a custom event, you can link it to the specific workflow transition (e.g., moving to "Pending") and configure the notification scheme to notify the project role.
How It Works: In Jira, events are fired during workflow transitions via post functions. A custom event (e.g., "Issue Moved to Pending") can be created and associated with the transition to the "Pending" status. The notification scheme is then configured to send notifications to the designated project role when this event occurs.
Configuration Steps:
Navigate toSettings > System > Events(requires Jira admin permissions).
Create a new custom event, such as "Issue Moved to Pending," with a description and an appropriate notification template (e.g., "Issue Updated").
In the workflow used by the project, edit the transition to the "Pending" status:
Add a post function to the transition, such as"Fire a Generic Event"or a custom event, and select the custom event ("Issue Moved to Pending").
Update the project’snotification scheme(found inProject Settings > NotificationsorSettings > Issues > Notification Schemes):
Map the custom event to the project role (e.g., "Pending Notifiers") to ensure that users in this role receive notifications when the event is fired.
Why This Is Necessary: A custom event is essential because Jira’s default events (e.g., "Issue Updated," "Issue Created") may not be specific enough to target only the "Pending" status transition. A custom event ensures that notifications are sent only when the issue transitions to "Pending," meeting the requirement for targeted notifications.
Why Other Options Are Incorrect:
Workflow Condition (Option B):
A workflow condition controls whether a user can execute a transition (e.g., restricting who can move an issue to "Pending"). It does not influence notifications or manage lists of users to be notified. Therefore, it is irrelevant to the requirement of notifying users and allowing the project admin to manage the user list.
Workflow Validator (Option D):
A workflow validator checks whether certain criteria are met before allowing a transition to proceed (e.g., ensuring a field is filled). Like conditions, validators do not handle notifications or user management for notifications, making this option incorrect.
Group (Option E):
While groups can be used in notification schemes to define who receives notifications, they are managed by Jira admins at the global level (viaSettings > User Management > Groups), not by project admins. The requirement specifies that theproject adminmust manage the list of users, which is not feasible with groups since project admins lack permission to edit global groups. Project roles, however, can be managed by project admins, making them the correct choice over groups.
Additional Notes:
The configuration assumes a company-managed project, as team-managed projects have simpler permission and notification settings that do not support custom events or complex workflow configurations to the same extent.
If the project admin lacks permission to edit workflows or notification schemes (which require Jira admin access), they would need to collaborate with a Jira admin to set up the custom event and initial notification scheme. However, once configured, the project admin can manage the project role’s membership independently.
The use of a custom event ensures that notifications are specific to the "Pending" status transition, avoiding unnecessary notifications for other transitions or actions.
Currently, users log time and enter a comment on a transition screen when closing issues. Now, they want the comment to be copied automatically to the work log description. Identify the configuration area that needs to be modified.
Field configuration
Global time tracking settings
Issue layout
Workflow condition
Global permissions
The Answer Is:
DExplanation:
The requirement involves automating an action during a workflow transition (copying a comment entered on a transition screen to the work log description when closing issues). As correctly noted, this type of automation is typically handled by aworkflow post function, which executes actions after a transition is completed. However, the provided options do not include "workflow post function." Among the options,Workflow condition(Option D) is the closest, as it points to the general area of workflow configuration where post functions are also managed, despite being technically inaccurate since conditions and post functions serve different purposes. Let’s analyze this in detail.
Explanation of the Correct Approach (Workflow Post Function):
Aworkflow post functionis the appropriate mechanism to copy the comment entered on the transition screen to the work log description during theClose Issuetransition. Post functions are executed automatically after a transition completes, and they can manipulate issue data, such as copying field values. However, Jira’s out-of-the-box post functions (e.g.,Copy Value From Other Field) may not directly support copying a transition screen comment to a work log description, as the comment field on a transition screen is transient and not stored as a standard issuefield until the transition is complete. This may require a custom post function or a third-party app (e.g., ScriptRunner) to script the behavior.
Alternatively, aJira automation rulecould achieve this by triggering on theIssue Transitionedevent (to the Closed status) and copying the latest comment to the work log description, but automation rules are configured separately and not part of the workflow editor.
Exact Extract from Documentation:
Configure workflow post functions
Post functions are executed after a transition is completed and can perform actions like updating fields or copying data.
To configure:
Go toSettings > Issues > Workflows.
Edit the workflow and select theClose Issuetransition.
Add a post function (e.g.,Copy Value From Other Fieldor a scripted post function via an app).Note: Copying a transition screen comment to a work log description may require a custom script or third-party app, as standard post functions do not directly support this.(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Why This Fits the Requirement: A post function on theClose Issuetransition can automate the copying of the comment to the work log description, aligning with the requirement for an action during a workflow transition.
Analysis of the Options and Selection of Option D:
The options provided do not include "workflow post function," which is the precise configuration area. However, let’s evaluate each option:
Field configuration (Option A):
Field configurationscontrol whether fields are required, optional, or hidden for specific issue types. They do not handle automation or copying data between fields during transitions.
Extract from Documentation:
Field configurations manage field behavior (required, hidden), not field value copying or automation.
(Source: Atlassian Support Documentation, "Configure field settings")
Global time tracking settings (Option B):
Global time tracking settingsconfigure time tracking formats, permissions, and defaults (e.g., enabling time logging, setting time units). They do not control copying data between fields like comments and work log descriptions.
Extract from Documentation:
Global time tracking settings manage time tracking behavior, not field interactions or automation.
(Source: Atlassian Support Documentation, "Configure time tracking in Jira Cloud")
Issue layout (Option C):
Issue layoutsdetermine field visibility and arrangement in the issue view (e.g., which fields are shown or hidden). They do not manage automation or data copying during transitions.
Extract from Documentation:
Issue layouts control field display in the issue view, not field value copying or automation.
(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
Workflow condition (Option D):
Workflow conditionsrestrict who can perform a transition (e.g., only users in a specific group). They do not execute actions like copyingdata between fields, which is the role of apost function. However, both conditions and post functions are configured within the same workflow editor (under the transition settings), makingWorkflow conditionthe closest option to the general area of workflow configuration where post functions reside. The question’s options may reflect a terminology error, intending "workflow post function" but listing "workflow condition" instead. Given the context of a workflow transition action, Option D is the most plausible choice despite the inaccuracy.
Extract from Documentation:
Conditions restrict transition access, while post functions perform actions like updating fields. Both are configured in the workflow editor under the transition settings.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Global permissions (Option E):
Global permissionscontrol system-wide actions (e.g., Administer Jira, Work On Issues). They do not manage field interactions or automation during transitions.
Extract from Documentation:
Global permissions manage system access, not field automation or workflow actions.
(Source: Atlassian Support Documentation, "Manage global permissions")
Why Option D is Selected: WhileWorkflow conditionis technically incorrect (as conditions do not copy data), it points to the workflow configuration area where the correct solution—apost function—is implemented. In the absence of a "workflow post function" option, Option D is the closest match, likely due to a wording error in the question. The user’s analysis aligns with this interpretation, recognizing that the solution lies within the workflow editor, specifically with post functions.
Additional Notes:
Steps to Configure a Post Function:
Go toSettings > Issues > Workflows(requires Jira administrator privileges).
Edit the workflow used by the project and select theClose Issuetransition.
Add a post function to copy the transition screen comment to the work log description (this may require a custom script or third-party app like ScriptRunner, as standard post functions do not directly support this).
Alternative with Automation Rule:
Go toProject settings > Automation(orSettings > System > Automation rulesfor global rules).
Create a rule with the triggerIssue Transitioned(to Closed status).
Add a condition to check for a new comment (if needed).
Add an action to edit the work log and copy the latest comment to the work log description (may require scripting or app support).
The question’s options suggest a possible oversight in not including "workflow post function." However, interpretingWorkflow conditionas a reference to the broader workflow configuration area (where post functions are managed) makes it the most reasonable choice.
Until now, two teams have been working together in a single company-managed Software project. Now, they want to split their work into two distinct projects. For each of their requirements, you must decide whether you can use shared schemes for the two projects or whether a unique scheme must be created. Which requirement necessitates the use of a unique scheme?
Each project must use a different set of components and component leads.
Each project must send notifications from a different email address.
Sprints must be managed by a different set of users in each project.
The Fix Versions field must be mandatory for one of the projects.
The Answer Is:
DExplanation:
When splitting a single company-managed project into two, you must determine whether the new projects can share configuration schemes (e.g., issue type scheme, workflow scheme, notification scheme) or require unique schemes to meet specific requirements. The requirement that necessitates a unique scheme isthe Fix Versions field must be mandatory for one of the projects(Option D), as this requires a distinct field configuration scheme.
Explanation of the Correct Answer (Option D):
Making theFix Versionsfield mandatory for one project but not the other requires a uniquefield configuration scheme. In Jira, field configurations control whether fields are required, hidden, or optional. A field configuration scheme maps field configurations to issue types, and each project can have its own field configuration scheme. To make Fix Versions mandatory for one project, a new field configuration must be created and associated with that project’s scheme.
Exact Extract from Documentation:
Configure field settings for a project
Field configurations define the behavior of fields (e.g., required, optional, hidden) for specific issue types. Each project can have its own field configuration scheme, which maps field configurations to issue types.
To make a field required:
Create or edit a field configuration (inSettings > Issues > Field configurations).
Find the field (e.g., Fix Versions) and mark it asRequired.
Associate the field configuration with a field configuration scheme.
Assign the field configuration scheme to the project inProject settings > Fields.If two projects need different field behaviors (e.g., Fix Versions required in one but not the other), they must use separate field configuration schemes.(Source: Atlassian Support Documentation, "Configure field settings")
Why This Fits: The requirement to make the Fix Versions field mandatory for one project but not the other cannot be achieved with a shared field configuration scheme, as field configurations apply uniformly to all projects using the same scheme. A unique field configuration scheme is necessary.
Why Other Options Are Incorrect:
Each project must use a different set of components and component leads (Option A):
Components and component leads are configured at the project level, not through a scheme. Each project can have its own components and leads without requiring a unique scheme, so this requirement does not necessitate a new scheme.
Extract from Documentation:
Manage components
Components are project-specific and configured inProject settings > Components. Each project can have its own set of components and component leads, independent of schemes.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
Each project must send notifications from a different email address (Option B):
Notifications in company-managed projects are controlled by thenotification scheme, which defines who receives notifications for specific events. However, the email address used for sending notifications is configured at the system level (viaSettings > System > Outgoing email) or per project for custom sender addresses (if supported by the Jira instance). This does not inherently require a unique notification scheme, as the sender address is not tied to the scheme itself.
Extract from Documentation:
Configure outgoing email
The sender email address for notifications is set globally or per project inSettings > System > Outgoing email. Notification schemes define recipients, not the sender address.
(Source: Atlassian Support Documentation, "Configure email in Jira Cloud")
Sprints must be managed by a different set of users in each project (Option C):
Sprint management is controlled by permissions in thepermission scheme, specifically theManage Sprintspermission. Both projects can share the same permission scheme, as permissions can be granted to project-specific roles, groups, or users. For example, different project roles can be assigned the Manage Sprints permission in each project, allowing different users to manage sprints without requiring a unique scheme.
Extract from Documentation:
Manage sprints
TheManage Sprintspermission is granted in the permission scheme to specific roles, groups, or users. Projects can share a permission scheme, with permissions scoped to project-specific roles (e.g., Project A’s Administrators vs. Project B’s Administrators).
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Additional Notes:
The need for a unique field configuration scheme for Option D arises because field configurations are applied at the scheme level, and a single scheme cannot have different rules (e.g., required vs. optional) for the same field across projects.
For other requirements (A, B, C), project-level settings or shared schemes with role-based scoping can accommodate the differences, making unique schemes unnecessary.
You want to rename an issue type. What might be impacted by this change?
Issue type schemes
Issue type screen schemes
Workflow schemes
Swimlanes by queries
Custom field contexts
The Answer Is:
DExplanation:
Renaming an issue type in Jira Software Cloud changes its display name, which can impact configurations or features that reference the issue type by name, particularly in JQL queries or user-defined settings. The element most likely to be impacted isswimlanes by queries(Option D), as swimlanes often use JQL queries that include issue type names.
Explanation of the Correct Answer (Option D):
Swimlaneson Jira boards (e.g., Kanban or Scrum) can be configured to use JQL queries to group issues (e.g., issuetype = Bug). If a swimlane’s JQL query references the issue type being renamed (e.g., issuetype = Task), renaming the issue type (e.g., toStory) will cause the query to no longer match issues of the renamed type, breaking the swimlane’s functionality. These queries must be updated to reflect the new issue type name.
Exact Extract from Documentation:
Configure board swimlanes
Swimlanes on Jira boards can be based on JQL queries (e.g., issuetype = Bug).
Impact of renaming issue types:
JQL queries referencing the issue type name (e.g., issuetype = Task) will no longer match issues if the issue type is renamed (e.g., to Story).To update:
Go toBoard settings > Swimlanes.
Update the JQL query to use the new issue type name.Note: Renaming an issue type can affect any JQL-based feature, including swimlanes, filters, and dashboards.(Source: Atlassian Support Documentation, "Configure boards in Jira Cloud")
Why This Fits: Renaming an issue type impactsswimlanes by queriesbecause JQL queries in swimlane configurations may reference the issue type name, requiring updates to maintain functionality, making Option D the correct answer.
Why Other Options Are Incorrect:
Issue type schemes (Option A):
Issue type schemesdefine which issue types are available in a project. Renaming an issue type changes its display name globally but does not alter the scheme’s structure or associations, as issue types are referenced by their internal IDs in schemes.
Extract from Documentation:
Renaming an issue type updates its display name but does not affect issue type schemes, which use internal IDs.
(Source: Atlassian Support Documentation, "Manage issue types in Jira Cloud")
Issue type screen schemes (Option B):
Issue type screen schemesmap screens to issue types for operations (Create, Edit, View). These schemes reference issue types by their internal IDs, so renaming an issue type does not impact the scheme’s configuration.
Extract from Documentation:
Issue type screen schemes use issue type IDs, not names. Renaming an issue type does not require changes to screen schemes.
(Source: Atlassian Support Documentation, "Configure screen schemes in Jira Cloud")
Workflow schemes (Option C):
Workflow schemesmap workflows to issue types. Like other schemes, they use issue type IDs, so renaming an issue type does not affect workflow assignments or configurations.
Extract from Documentation:
Workflow schemes reference issue types by ID. Renaming an issue type has no impact on workflow schemes.
(Source: Atlassian Support Documentation, "Configure workflow schemes")
Custom field contexts (Option E):
Custom field contextsdefine the projects and issue types where a custom field is available. Contexts also use issue type IDs, so renaming an issue type does not require changes to the context configuration.
Extract from Documentation:
Custom field contexts use issue type IDs. Renaming an issue type does not affect field contexts.
(Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud")
Additional Notes:
Renaming an issue type is done inSettings > Issues > Issue typesand requiresJira administratorprivileges.
Other JQL-based features (e.g., filters, dashboards, automation rules) may also be impacted if they reference the issue type name, butswimlanes by queriesis the most directly affected among the options.
To minimize impacts, use issue type IDs in JQL queries (e.g., issuetype = 10001), though this is less common.
version in a company-managed project:
• Move all issues in version 1.1 to version 1.2.
• Remove version 1.1 as an available option from the Fix Versions system field.
Which two operations will both meet the requirements? (Choose two.)
Delete
Archive
Build and release
Merge
The Answer Is:
B, DExplanation:
The question involves managing versions in a company-managed project in Jira Software Cloud. Maia wants to move all issues from version 1.1 to version 1.2 and remove version 1.1 as an available option in theFix Versionsfield. The two operations that meet both requirements areArchiveandMerge.
Explanation of the Correct Answers:
Archive (Option B):
Archiving a version removes it from theFix Versionsfield as an available option for new issues, while preserving the version’s association with existing issues. Additionally, archiving allows you to move issues to another version (e.g., version 1.2) during the process, meeting both requirements.
Exact Extract from Documentation:
Archive a version
Archiving a version removes it from the list of available versions in fields like Fix Versions, so it can’t be selected for new issues. You can also move issues to another version during the archiving process.
To archive a version:
Go to your project’sReleasespage.
Find the version (e.g., version 1.1) and selectArchive.
Optionally, choose to move issues to another version (e.g., version 1.2).Archived versions are still visible in reports and issue details but are no longer selectable in fields.Note: You need project admin permissions to archive versions.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Why This Fits: Archiving version 1.1 removes it from the Fix Versions field, preventing it from being selected for new issues, and allows Maia to move all issues to version 1.2 during the archiving process, fulfilling both requirements.
Merge (Option D):
Merging a version moves all issues from one version (e.g., version 1.1) to another (e.g., version 1.2) and deletes the source version, effectively removing it from the Fix Versions field. This meets both requirements, as it reassigns issues and eliminates version 1.1 as an available option.
Exact Extract from Documentation:
Merge versions
Merging versions allows you to combine two versions by moving all issues from one version to another. The source version is deleted after the merge.
To merge versions:
Go to your project’sReleasespage.
Find the version to merge (e.g., version 1.1) and selectMerge.
Choose the target version (e.g., version 1.2) to move issues to.After merging, the source version (version 1.1) is removed from the Fix Versions field and is no longer available for selection.Note: Merging is permanent and cannot be undone, so ensure the target version is correct.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Why This Fits: Merging version 1.1 into version 1.2 moves all issues to version 1.2 and deletes version 1.1, ensuring it is no longer an option in the Fix Versions field, thus meeting both requirements.
Why Other Options Are Incorrect:
Delete (Option A):
Deleting a version removes it from the Fix Versions field, but it also removes the version from all issues associated with it without reassigning them to another version. This does not meet the requirement to move issues to version 1.2.
Extract from Documentation:
Delete a version
Deleting a version removes it from the project and clears it from the Fix Versions field of all associated issues. Issues are not reassigned to another version automatically.
Note: Use caution, as this action cannot be undone, and issues lose their version association.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Build and release (Option C):
Building and releasing a version marks it as complete and moves unresolved issues to another version, but it does not remove the version from the Fix Versions field. Released versions remain selectable unless archived or deleted.
Extract from Documentation:
Release a version
Releasing a version marks it as complete and optionally moves unresolved issues to another version. The released version remains available in the Fix Versions field unless archived.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Additional Notes:
BothArchiveandMergeare suitable, but they have different implications:
Archiving preserves version 1.1 in reports and issue histories, making it ideal if historical data needs to be retained.
Merging permanently deletes version 1.1, which may be preferred if the version is no longer relevant.
The operations require project admin permissions in a company-managed project, and theReleasespage is accessed viaProject Settings > Releases.
In your company-managed project, you are in the process of releasing a version that contains unresolved issues. You opt to ignore these issues and proceed to release the version. What happens to the unresolved issues?
They are moved to the next version.
They are transitioned to Done.
They are left unresolved.
They are moved to the top of the backlog.
The Answer Is:
CExplanation:
When releasing a version in a company-managed project that contains unresolved issues, you can choose to ignore these issues and proceed with the release. The unresolved issuesare left unresolved(Option C), meaning they retain their current status and resolution state without being automatically moved or transitioned.
Explanation of the Correct Answer (Option C):
In Jira, releasing a version marks it as complete and updates theRelease DateandReleasedstatus for the version. If unresolved issues (issues without a resolution, e.g., not in a Done status) are included, you can choose to ignore them during the release process. Ignoring unresolved issues means they remain in their current state—unresolved, with no changes to their status, resolution, or version association. They are not automatically moved to another version, transitioned, or reordered in the backlog.
Exact Extract from Documentation:
Release a version in company-managed projects
When releasing a version:
You can choose to ignore unresolved issues (issues without a resolution).
Ignored unresolved issues: Remain in their current status and resolution state, with no automatic changes.To release:
Go toProject settings > Releases.
Select the version and clickRelease.
Choose to ignore unresolved issues if prompted.Note: Unresolved issues are not moved to another version or transitioned unless explicitly configured.(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Why This Fits: Ignoring unresolved issues during a version release leaves them unchanged in their current unresolved state, making Option C the correct answer.
Why Other Options Are Incorrect:
They are moved to the next version (Option A):
Moving unresolved issues to the next version is an option during the release process, but it is not the default or required action when choosing toignoreunresolved issues. Ignoring them explicitly avoids moving them to another version.
Extract from Documentation:
When releasing, you can move unresolved issues to another version or leave them unchanged. Ignoring unresolved issues keeps them in their current version.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
They are transitioned to Done (Option B):
Transitioning issues toDone(or setting a resolution) requires a workflow transition and is not automatic when releasing a version. Ignoring unresolved issues means no status or resolution changes occur.
Extract from Documentation:
Releasing a version does not transition issues or set resolutions unless explicitly configured via a workflow post function.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
They are moved to the top of the backlog (Option D):
Releasing a version does not affect the backlog order or automatically reorder issues. The backlog is managed separately, and ignoring unresolved issues leaves them in their current position.
Extract from Documentation:
Releasing a version does not modify the backlog order. Unresolved issues remain in their current position unless manually reordered.
(Source: Atlassian Support Documentation, "Manage versions in company-managed projects")
Additional Notes:
Releasing a version requiresproject adminprivileges and is done inProject settings > Releases.
If you choose to move unresolved issues to another version instead of ignoring them, Option A would apply, but the question specifiesignoringthe issues.
Unresolved issues may still be associated with the released version unless manually updated.
Which action requires that users have the "Administer Projects" permission?
Reopen bugs
Assign issues to themselves
Modify component leads
Edit due dates
Set fix versions
The Answer Is:
CExplanation:
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.
Users complain that they can see a particular custom field in all company-managed projects except one. Identify two possible reasons. (Choose two.)
Groups
Project roles
Security levels
Screen
Issue layout
Validator
Step property
The Answer Is:
D, EExplanation:
The issue is that a custom field is visible in all company-managed projects except one, indicating a project-specific configuration is preventing the field from being displayed. The two possible reasons areScreen(Option D) andIssue layout(Option E), as these configurations control whether a field appears in a project’s issue operations or view.
Explanation of the Correct Answers:
Screen (Option D):
In company-managed projects,screensdetermine which fields are displayed during issue operations (Create, Edit, View) for specific issue types, as defined by thescreen scheme. If the custom field is not included on the screen(s) used by the problematic project’s issue types, users will not see the field when creating, editing, or viewing issues in that project. This could explain why the field is missing in one project but visible in others.
Exact Extract from Documentation:
Configure screens in company-managed projects
Screens define which fields are available during issue operations (Create, Edit, View). Each project uses a screen scheme to map screens to issue types and operations.
If a field is not on a project’s screen:
Users cannot see or interact with the field in that project.To check:
Go toProject settings > Screens.
Verify if the custom field is included on the relevant screens.Note: A field must be on the screen to be visible during issue operations.(Source: Atlassian Support Documentation, "Configure screens in Jira Cloud")
Why This Fits: If the custom field is not on the screen(s) used by the project, it will not be visible, makingScreena possible reason for the issue.
Issue layout (Option E):
Theissue layoutin a company-managed project controls which fields are displayed, hidden, or placed in the context panel in the issue view. If the custom field is moved to theHidden fieldssection in the issue layout for the problematic project, users will not see it when viewing issues, even if the field is on the screen and contains data. This could explain the field’s absence in one project.
Exact Extract from Documentation:
Configure issue layouts in company-managed projects
Issue layouts determine which fields are displayed or hidden in the issue view.
To hide a field:
Go toProject settings > Issue layout.
Move the field to theHidden fieldssection.Impact: Hidden fields are not shown in the issue view, even if they areon the screen and have values.Note: Issue layouts are project-specific and can differ between projects.(Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud")
Why This Fits: If the custom field is hidden in the issue layout for the problematic project, it will not be visible in the issue view, makingIssue layouta possible reason.
Why Other Options Are Incorrect:
Groups (Option A):
Groups are used in permission schemes or field configurations to control access or behavior, but they do not directly determine field visibility. If the field is visible in other projects, the issue is not group-related, as groups apply globally or via schemes shared across projects.
Extract from Documentation:
Groups are used for permissions or field restrictions, not for controlling field visibility on screens or layouts.
(Source: Atlassian Support Documentation, "Manage groups in Jira Cloud")
Project roles (Option B):
Project roles are used in permission schemes to grant permissions (e.g.,Edit Issues). They do not control whether a field is displayed on a screen or in the issue layout. The issue is about visibility, not permissions.
Extract from Documentation:
Project roles manage permissions, not field visibility. Check screens or issue layouts for display issues.
(Source: Atlassian Support Documentation, "Manage project roles")
Security levels (Option C):
Security levels (part of an issue security scheme) restrict which issues a user can view, not which fields are displayed within an issue. If users can see issues but not the field, security levels are not the cause.
Extract from Documentation:
Issue security levels control issue visibility, not field visibility within an issue.
(Source: Atlassian Support Documentation, "Configure issue security schemes")
Validator (Option F):
Validators ensure conditions are met before a workflow transition (e.g., a field is filled). They do not affect whether a field is visible in the issue view or during operations.
Extract from Documentation:
Validators enforce conditions during transitions, not field visibility.
(Source: Atlassian Support Documentation, "Configure advanced work item workflows")
Step property (Option G):
Step properties (workflow properties) control behaviors like editability in a status (e.g.,jira.issue.editable). They do not directly control field visibility on screens or in the issue view.
Extract from Documentation:
Workflow properties manage status behaviors, not field visibility. Use screens or issue layouts for display issues.
(Source: Atlassian Support Documentation, "Use workflow properties")
Additional Notes:
To resolve the issue, check:
Project settings > Screens: Ensure the custom field is on the relevant screen(s) for the project’s issue types.
Project settings > Issue layout: Verify the field is not in theHidden fieldssection.
These configurations requireproject admin(for issue layout) orJira administrator(for screens) privileges.
Other potential causes (not listed) includefield configurations(if the field is hidden for all issue types in the project), but screens and issue layouts are the most direct reasons.
You want to create a new link type that looks identical in linked issues. How can you achieve this?
Create the link type with no inward link description.
Disable bidirectional linking globally.
Choose the same name for the inward and outward link descriptions.
Create the link type with no outward link description.
The Answer Is:
CExplanation:
To create a new link type in Jira Software Cloud that looks identical in linked issues (i.e., the link description is the same regardless of the direction of the link), you shouldchoose the same name for the inward and outward link descriptions(Option C). This ensures that the link type appears with the same description in both the source and target issues.
Explanation of the Correct Answer (Option C):
In Jira,issue link typesdefine relationships between issues, with anoutwarddescription(for the source issue) and aninward description(for the target issue). For example, a “Blocks” link type might have “blocks” as the outward description and “is blocked by” as the inward description. To make the link type look identical in both linked issues, you set the same description for both the inward and outward links (e.g., “relates to” for both). This results in the link appearing as “relates to” in both issues, regardless of which issue is the source or target.
Exact Extract from Documentation:
Manage issue link types
Issue link types define relationships between issues, with separateoutwardandinwarddescriptions.
To create a link type:
Go toSettings > Issues > Issue linking.
Add a new link type.
Enter aName(e.g., Relates), and set theOutward descriptionandInward description(e.g., both as “relates to”).Impact: If the inward and outward descriptions are the same, the link appears identical in both linked issues.Note: Requires Jira administrator permissions.(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Why This Fits: Setting the same name for the inward and outward link descriptions ensures the link type looks identical in linked issues, meeting the requirement and making Option C the correct answer.
Why Other Options Are Incorrect:
Create the link type with no inward link description (Option A):
Jira requires both aninwardandoutwarddescription when creating a link type. Leaving the inward description blank is not allowed, and even if possible, it would not make the link look identical in both issues—it would result in an empty or default description in the target issue.
Extract from Documentation:
Bothinwardandoutwarddescriptions are required when creating a link type. Blank descriptions are not supported.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Disable bidirectional linking globally (Option B):
There is no concept ofbidirectional linkingin Jira’s issue linking system, and no global setting exists to disable it. Issue links are inherently bidirectional (a link from issue A to B implies a reverse link from B to A), and the descriptions control how they appear. Disabling linking is not an option.
Extract from Documentation:
Issue links are bidirectional, with inward and outward descriptions defining the relationship. No global setting exists to disable bidirectionality.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Create the link type with no outward link description (Option D):
Similar to Option A, Jira requires anoutwarddescription when creating a link type. Leaving it blank is not allowed, and it would not achieve identical appearance in both issues, as the source issue would lack a description.
Extract from Documentation:
Bothoutwardandinwarddescriptions are mandatory for issue link types.
(Source: Atlassian Support Documentation, "Configure issue linking in Jira Cloud")
Additional Notes:
Steps to configure:
Go toSettings > Issues > Issue linking.
ClickAdd link type.
Enter aName(e.g., “Relates”) and set bothOutward descriptionandInward descriptionto the same value (e.g., “relates to”).
Save the link type.
Configuring issue link types requiresJira administratorprivileges.
The new link type will appear identically in both linked issues (e.g., “Issue A relates to Issue B” and “Issue B relates to Issue A”).
Gary is no longer receiving notifications when his colleagues modify issues that he is watching. You already verified that watchers should be notified. Which personal setting did Gary update?
Watch your issues
You make changes to the issue
Email notifications format
Notifications for relevant issues
The Answer Is:
DExplanation:
The scenario indicates that Gary is no longer receiving notifications for issues he is watching, despite the notification scheme being correctly configured to notify watchers. This suggests that Gary has modified a personal setting that controls whether he receives notifications for watched issues. Based on Jira Software Cloud documentation, the relevant personal setting is "Notifications for relevant issues" (Option D).
Explanation of the Correct Answer (Option D):
In Jira Cloud, users can control their notification preferences through their personal settings in the user profile. The setting "Notifications for relevant issues" determines whether a user receives email notifications for events they are associated with, such as being a watcher of an issue.
If Gary disabled this setting (i.e., turned off notifications for relevant issues), he would stop receiving notifications for issues he is watching, even if the project’s notification scheme is configured to notify watchers.
Exact Extract from Documentation:
Manage your Jira notification emails
You can choose whether you want to receive email notifications about activity in your Jira products. For example, you can choose to receive emails when you’re added as a watcher to an issue, or when an issue you’re working on is updated.
To manage your notification preferences:
From your Jira site, select your profile picture in the top right and select Personal settings.
Under Email notifications, select whether you’d like to receive notifications for relevant issue activity.
On: Receive emails for issue activity you’re associated with, like when you’re a watcher, assignee,or reporter.
Off: Don’t receive emails for issue activity, even if you’re associated with the issue.
Note: This setting doesn’t affect emails about your account, like password resets. To manage those, update your Atlassian account preferences.
(Source: Atlassian Support Documentation, "Manage your Jira notification emails")
Why This Fits: The documentation explicitly states that turning off the "Notifications for relevant issues" setting prevents a user from receiving emails for issue activity they are associated with, including as a watcher. Since Gary is no longer receiving notifications for watched issues, this is the most likely setting he updated.
Why Other Options Are Incorrect:
Watch your issues (Option A):
This option refers to a setting that automatically adds a user as a watcher to issues they create or are assigned to. However, the question states that Gary is already watching the issues (since he was receiving notifications previously), so this setting is not relevant. Disabling this setting would only prevent Gary from being automatically added as a watcher to new issues, not stop notifications for issues he is already watching.
Extract from Documentation:
Watching issues
You can watch an issue to receive email notifications whenever it’s updated. By default, you may automatically watch issues you create or are assigned to, depending on your notification settings.
To change your auto-watch settings:
Select your profile picture and then select Settings.
Under Jira settings, select whether to automatically watch issues you create or are assigned to.
(Source: Atlassian Support Documentation, "Watch issues and manage your watchlist")
You make changes to the issue (Option B):
This option is not a standard personal setting in Jira Cloud. There is no user-level setting that specifically toggles notifications based on whether the user themselves makes changes to an issue. Notifications are controlled by the notification scheme and the user’s email notification preferences, not by a setting tied to the user’s own changes.
Email notifications format (Option C):
This setting allows users to choose the format of email notifications (e.g., HTML or text). Changing this setting affects how notifications are displayed, not whether they are sent. Therefore, it would not cause Gary to stop receiving notifications entirely.
Extract from Documentation:
Email format
You can choose whether notifications are sent in HTML or text format. This is managed in your Atlassian account settings, under email preferences.
(Source: Atlassian Support Documentation, "Manage your Atlassian account")
Additional Notes:
The question specifies that the notification scheme is correctly configured to notify watchers, so the issue lies with Gary’s personal settings, not the project or system configuration.
The "Notifications for relevant issues" setting is a global toggle that affects all notifications for issue activity a user is associated with, making it the most direct cause of Gary’s issue.
