No one should be allowed to edit issues in a particular workflow status of a company-managedproject. Which element must be configured?
Condition
Post function
Trigger
Status Property
Okay, let's analyze this question again with the revised options.
The requirement is to preventanyonefromeditingan issue when it resides in aspecific workflow status.
As established previously:
Conditions (A):Control whether atransitionout of or into a status can occur. They check criteriabeforea transition starts. They don't prevent editingwhilean issue is sitting in a status.
Post Functions (Implied by B & C):Actions that executeaftera transition is successfully completed (e.g., updating a field, sending a notification). They don't affect editability within the status itself.
Triggers (D):Automatically initiate a workflow transition based on external events (like code commits). Not relevant to editing permissions within a status.
The correct way to achieve this in Jira is by setting aStatus Property:
Navigate to Workflow configuration.
Select the relevant status.
Go to its 'Properties'.
Add a property: jira.issue.editable with the value false.
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.
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.
On the Bulk Operation screen, Taylor is unable to choose the Delete Issues bulk action. What does Taylor definitely need?
Organization admin privileges
Jira administration privileges
Global permissions
Project permissions
Project administration privileges
The inability to choose theDelete Issuesbulk action on the Bulk Operation screen indicates that Taylor lacks the necessary permission to delete issues in the project. TheDelete Issuespermission, which is a project-level permission defined in the project’s permission scheme, is required for this action. Therefore, Taylor definitely needsproject permissions(Option D).
Explanation of the Correct Answer (Option D):
TheDelete Issuespermission allows users to delete issues, including via bulk operations. This permission is granted through the project’s permission scheme and is specific to the project containing the issues. If Taylor cannot select theDelete Issuesbulk action, she lacks this permission for the project.
Exact Extract from Documentation:
Delete Issues permission
TheDelete Issuespermission allows users to delete issues, either individually or via bulk operations. This permission is granted via the project’s permission scheme.
To perform bulk operations:
Run a filter to select issues.
On the Bulk Operation screen, choose an action (e.g., Delete Issues).Note: Users must have the relevant permission (e.g.,Delete Issues) for allselected issues to see the action in the bulk operation wizard.To check permissions:
Go toProject settings > Permissions.
Verify which users, groups, or roles have theDelete Issuespermission.(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Why This Fits: TheDelete Issuespermission is a project-level permission, and granting it to Taylor will enable her to choose theDelete Issuesbulk action, makingproject permissions(Option D) the correct answer.
Why Other Options Are Incorrect:
Organization admin privileges (Option A):
Organization admins manage Atlassian organization settings, such as user access and billing. They do not directly control project-level permissions likeDelete Issues.
Extract from Documentation:
Organization admins manage user access and organization settings. Project-specific actions, like deleting issues, are controlled by project permissions.
(Source: Atlassian Support Documentation, "Manage your Atlassian organization")
Jira administration privileges (Option B):
Jira administrators manage global settings, such as schemes and user management. While they can modify permission schemes, theDelete Issuespermission is project-specific and does not require Jira admin privileges to grant or use.
Extract from Documentation:
Jira administrators can modify permission schemes, but theDelete Issuespermission is applied at the project level and does not require admin privileges to use.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Global permissions (Option C):
Global permissions (e.g.,Administer Jira,Create Projects) control system-wide actions, not project-specific actions like deleting issues. TheDelete Issuespermission is project-level, not global.
Extract from Documentation:
Global permissions control system-wide actions, such as administering Jira or sharing filters. Project permissions, likeDelete Issues, are specific to projects.
(Source: Atlassian Support Documentation, "Manage global permissions")
Project administration privileges (Option E):
Project administration privileges (via theAdminister Projectspermission) allow users to manage project settings, such as components and permission schemes. However, deleting issues is an issue-level action that requires theDelete Issuespermission, not administrative privileges.
Extract from Documentation:
TheAdminister Projectspermission allows managing project settings. Deleting issues requires theDelete Issuespermission, which is separate.
(Source: Atlassian Support Documentation, "Manage permissions in Jira Cloud")
Additional Notes:
To resolve the issue, check Taylor’s permissions inProject settings > Permissionsand ensure she has theDelete Issuespermission, either directly, via a group, or via a project role.
If the issues in the bulk operation span multiple projects, Taylor needs theDelete Issuespermission for all relevant projects.
Your team creates issues directly in the Kanban board of a company-managed project. You must ensure that all their newly created issues are not left unassigned. Which entry must you select in the project’s Default Assignee dropdown?
Board administrator
Project lead
Component lead
Project admin
Reporter
To ensure that newly created issues in a company-managed project’s Kanban board are not left unassigned, you must configure theDefault Assigneesetting in the project’s settings. TheProject lead(Option B) is a valid and appropriate choice, as it assigns new issues to the project’s designated lead by default.
Explanation of the Correct Answer (Option B):
In a company-managed project, theDefault Assigneesetting determines who is automatically assigned to new issues when no assignee is specified during creation (e.g., when creating issues directly on a Kanban board). TheProject leadis a predefined user set in the project’s settings and can be selected as the default assignee to ensure issues are not left unassigned.
By selectingProject leadin theDefault Assigneedropdown, all new issues created in the project, including those created on the Kanban board, will be automatically assigned to the project lead, meeting the requirement.
Exact Extract from Documentation:
Configure the default assignee
TheDefault Assigneesetting in a company-managed project determines who is assigned to new issues when no assignee is specified.
Options include:
Project lead: Assigns issues to the user designated as the project lead.
Unassigned: Leaves issues unassigned (if allowed by the project’s permission scheme).To configure:
Go toProject settings > Details.
SelectProject leadin theDefault Assigneedropdown.Note: Ensure the project lead has theAssignable Userpermission in the project’s permission scheme.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Why This Fits: SelectingProject leadensures that all newly created issues are automatically assigned to the project lead, preventing them from being unassigned, making Option B the correct answer.
Why Other Options Are Incorrect:
Board administrator (Option A):
There is noBoard administratoroption in theDefault Assigneedropdown. Board administrators manage Kanban or Scrum boards but are not a predefined assignee role for issues.
Extract from Documentation:
TheDefault Assigneedropdown includesProject lead,Unassigned, or specific users, but notBoard administrator.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Component lead (Option C):
TheComponent leadis not an option in theDefault Assigneedropdown. Component leads are assigned to specific components, and issues are only assigned to them if a component with a default assignee is selected during issue creation, which is not guaranteed for Kanban board creations.
Extract from Documentation:
Component leads are assigned to issues only when a component with a default assignee is selected. They are not part of theDefault Assigneesetting.
(Source: Atlassian Support Documentation, "Manage components in Jira Cloud")
Project admin (Option D):
There is noProject adminoption in theDefault Assigneedropdown. Project administrators have theAdminister Projectspermission but are not a predefined assignee role. TheProject leadis the designated user for default assignments.
Extract from Documentation:
TheDefault Assigneesetting does not includeProject admin. UseProject leadorUnassigned.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Reporter (Option E):
TheReporteris the user who creates the issue and is not an option in theDefault Assigneedropdown for company-managed projects. Assigning issues to the reporter would require a custom automation rule or manual assignment, not a default setting.
Extract from Documentation:
TheReporteris not a valid option forDefault Assignee. UseProject leadorUnassignedfor automatic assignments.
(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")
Additional Notes:
TheDefault Assigneesetting is configured inProject settings > Details, requiringproject adminprivileges.
Ensure the project lead has theAssignable Userpermission in the project’s permission scheme to be eligible as an assignee.
IfUnassignedis selected, issues could remain unassigned, which violates the requirement.
Two projects were created as follows:
OPS1: Created from the Procurement project template.
OPS2: Created from the Process Control project template.You need to create project OPS3. You want it to have the same components as OPS1 but the same schemes as OPS2. How should OPS3 be created?
With a shared configuration with OPS1 from the Process Control project template
With a shared configuration with OPS2 from the Procurement project template
Requirements for OPS3:
Same Components as OPS1:Components are configurationswithina project, not typically part of the shared scheme setup during creation.
Same Schemes as OPS2:Schemes (Workflow Scheme, Issue Type Scheme, Screen Schemes, Field Configuration Scheme, Permission Scheme, etc.) define the core configuration and behavior of a project.
How Project Creation Options Work:
Creating from a Template:Sets up a project with anew setof schemes and configurations based on the chosen template. The new project doesnotinitially share schemes with any other project.
Creating with Shared Configuration:When you create a project and choose "Share settings with an existing project" (e.g., share with OPS2), the new project (OPS3) uses theexact same scheme objectsas the existing project (OPS2). Changes to these schemes will affect both projects. This is the mechanism to ensure OPS3 has the same schemes as OPS2.
Analyzing the Options:
with a shared configuration with OPS1 from the Process Control project template
Shared configuration with OPS1: This would give OPS3 the sameschemesas OPS1. This contradicts Requirement 2 (needs schemes from OPS2).
from the Process Control project template: Choosing a template is generally an alternative to sharing configuration. If you share configuration, the template choice is irrelevant for the schemes. This part makes the option confusing, but the core action (sharing with OPS1) is incorrect based on the scheme requirement.
with a shared configuration with OPS2 from the Procurement project template
Shared configuration with OPS2: This would give OPS3 the sameschemesas OPS2. Thissatisfies Requirement 2.
from the Procurement project template: As above, the template choice is confusing when sharing configuration. However, the critical action (sharing schemes with OPS2) aligns with the requirement.
Addressing the Component Requirement:
Neither "creating from a template" nor "creating with shared configuration" will automatically copy theComponentsfrom OPS1 to OPS3. Components need to be set up manually within the OPS3 project after it has been created.
Conclusion:
To meet the requirement of having the sameschemesas OPS2, youmustcreate OPS3 using the "Share settings with an existing project" option and select OPS2. Option B correctly specifies sharing the configuration with OPS2.
The mention of the template in Option B is likely extraneous or indicates a slightly flawed understanding in the question's options, but the core part "shared configuration with OPS2" is thecorrect action to satisfy the scheme requirement. The component requirement must be handled separately after project creation.
Therefore, the correct approach described in the options is:
with a shared configuration with OPS2 from the Procurement project template
You need to find unresolved issues assigned to suspended users. Identify the correct JQL query.
resolution is EMPTY AND assignee in inactiveUsers()
statusCategory != Done AND assignee not in organizationMembers()
resolution = Unresolved AND assignee changed to inactive
statusCategory = Done AND assignee not in activeUsers()
resolution = EMPTY AND assignee not in membersOf("jira-software-users")
To find unresolved issues assigned to suspended users in Jira Software Cloud, the JQL query must check for issues with no resolution (unresolved) and an assignee who is inactive (suspended). The correct query isresolution is EMPTY AND assignee in inactiveUsers()(Option A), as it uses the appropriate field (resolution) and function (inactiveUsers()) to identify these issues.
Explanation of the Correct Answer (Option A):
Unresolved issues: In Jira, an issue is considered unresolved if itsresolutionfield is empty (i.e., not set to Resolved, Done, or similar). The JQL clauseresolution is EMPTYidentifies unresolved issues.
Suspended users: Suspended users are those whose accounts are inactive (e.g., deactivated or removed from the organization). TheinactiveUsers()function returns all inactive users in the Jira instance. The clauseassignee in inactiveUsers()filters for issues assigned to these users.
Combined query:resolution is EMPTY AND assignee in inactiveUsers()returns all unresolved issues assigned to inactive users.
Exact Extract from Documentation:
Search for issues using JQL
resolution is EMPTY: Finds issues with no resolution set (unresolved issues).
assignee in inactiveUsers(): Finds issues assigned to users who are inactive (e.g., deactivated or suspended).Example:
resolution is EMPTY AND assignee in inactiveUsers() returns unresolved issues assigned to inactive users.Note: TheinactiveUsers()function is specific to Jira Cloud and includes users who are no longer active in the instance.(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
Why This Fits: The query correctly usesresolution is EMPTYfor unresolved issues andinactiveUsers()for suspended users, making Option A the correct answer.
Why Other Options Are Incorrect:
statusCategory != Done AND assignee not in organizationMembers() (Option B):
statusCategory != Donechecks the status category (e.g., To Do, In Progress) but is less precise thanresolution is EMPTY, as some statuses in non-Done categories may still be resolved.assignee not in organizationMembers()is incorrect, asorganizationMembers()is not a valid JQL function in Jira Cloud, and it would not specifically target inactive users.
Extract from Documentation:
statusCategory != Doneis broader thanresolution is EMPTYand may include resolved issues. NoorganizationMembers()function exists in JQL.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
resolution = Unresolved AND assignee changed to inactive (Option C):
resolution = Unresolvedis incorrect, asUnresolvedis not a valid resolution value; useresolution is EMPTYinstead.assignee changed to inactiveis invalid, aschanged to inactiveis not a supported JQL operator for theassigneefield.
Extract from Documentation:
Useresolution is EMPTYfor unresolved issues. Thechangedoperator does not supportinactiveas a value forassignee.
(Source: Atlassian Support Documentation, "Advanced searching - operators reference")
statusCategory = Done AND assignee not in activeUsers() (Option D):
statusCategory = Doneis the opposite of what is needed, as it selects resolved or completed issues, not unresolved ones.assignee not in activeUsers()might include inactive users but is less precise thaninactiveUsers(), and thestatusCategoryclause makes the query incorrect.
Extract from Documentation:
statusCategory = Doneselects issues in completed statuses, not unresolved issues. UseinactiveUsers()for precise inactive user filtering.
(Source: Atlassian Support Documentation, "Advanced searching - fields reference")
resolution = EMPTY AND assignee not in membersOf("jira-software-users") (Option E):
resolution = EMPTYis correct, butassignee not in membersOf("jira-software-users")is incorrect, asjira-software-usersis a default group for active users with Jira Software access, not a reliable indicator of suspended users. This would exclude active users in the group, not specifically target inactive ones.
Extract from Documentation:
ThemembersOf()function checks group membership, not user activity status. UseinactiveUsers()to find suspended or deactivated users.
(Source: Atlassian Support Documentation, "Advanced searching - functions reference")
Additional Notes:
The query can be tested inIssues > Search for issuesand saved as a filter if needed.
inactiveUsers()is specific to Jira Cloud and includes users who are deactivated or removed from the organization.
Ensure the user running the query hasBrowse Projectspermission for the relevantprojects.
Christian has a saved filter showing bugs that have not been updated in the past two weeks. He plans to run a bulk operation to change the priority to Highest on all the issues in the filter. Identify one definite outcome of this action.
The saved filter will display no issues.
Filter subscriptions based on the filter will stop sending emails.
Christian will be added as a watcher on all the edited issues.
Email notifications will be sent during the bulk operation.
Christian’s saved filter shows bugs that have not been updated in the past two weeks, likely using a JQL query like issuetype = Bug AND updated <= -2w. Running a bulk operation to change the priority toHigheston all issues in the filter will update the issues, affecting theirupdatedtimestamp. The definite outcome is thatthe saved filter will display no issues(Option A), as the issues will no longer meet the filter’s criteria after being updated.
Explanation of the Correct Answer (Option A):
The saved filter likely uses a JQL query such as issuetype = Bug AND updated <= -2w, which returns bugs not updated in the past two weeks (i.e., updated timestamp is older than two weeks). When Christian performs a bulk operation to change the priority toHighest, each issue’supdatedtimestamp is set to the current time, as any edit (including priority changes) updates this field. After the operation, all issues in the filter will have a recentupdatedtimestamp (e.g., within the last few minutes), causing them to no longer satisfy the updated <= -2w condition. As a result, the filter will return no issues.
Exact Extract from Documentation:
Bulk change issues
Bulk operations (e.g., changing priority) update issue fields and metadata, including theupdatedtimestamp.
Impact on filters:
If a filter uses a condition like updated <= -2w, updating issues will change theirupdatedtimestamp, potentially excluding them from the filter.To perform a bulk change:
Run a filter inIssues > Search for issues.
SelectBulk changeand choose an action (e.g., Edit Issues).
Update fields (e.g., Priority to Highest).Note: Bulk changes trigger theIssue Updatedevent, updating theupdatedfield.(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")
Why This Fits: The bulk operation updates theupdatedtimestamp of all issues, causing them to no longer meet the filter’s updated <= -2w condition, resulting in the filter displaying no issues, making Option A the definite outcome.
Why Other Options Are Incorrect:
Filter subscriptions based on the filter will stop sending emails (Option B):
Filter subscriptions send emails based on the filter’s results and schedule (e.g., daily, weekly). The bulk operation does not disable the subscription or change its configuration; it only affects the filter’s results. If the filter returns no issues after the operation, the subscription will send an email with no results, but it will not stop sending emails entirely.
Extract from Documentation:
Filter subscriptions send emails based on the filter’s results and schedule. Empty results do not stop the subscription; they result in an empty email.
(Source: Atlassian Support Documentation, "Manage filters in Jira Cloud")
Christian will be added as a watcher on all the edited issues (Option C):
Adding a watcher during a bulk operation is not automatic. Users are not added as watchers unless explicitly included in the bulk operation (e.g., via anAdd Watcheraction, which is not part of changing priority). Christian’s user settings or automation rules could theoretically add him as a watcher, but this is not a definite outcome of the priority change.
Extract from Documentation:
Bulk operations do not automatically add the user as a watcher. Use theAdd Watcheraction in abulk operation to add watchers explicitly.
(Source: Atlassian Support Documentation, "Bulk change issues in Jira Cloud")
Email notifications will be sent during the bulk operation (Option D):
Email notifications for theIssue Updatedevent (triggered by the priority change) depend on the project’snotification schemeand the recipients configured for the event (e.g., watchers, assignee). Notifications are not guaranteed, as they may be disabled or limited to specific users. Thus, this is not a definite outcome.
Extract from Documentation:
Bulk operations trigger theIssue Updatedevent, but notifications depend on the notification scheme and may not be sent if not configured.
(Source: Atlassian Support Documentation, "Configure notification schemes")
Additional Notes:
The bulk operation requires Christian to have theEdit Issuespermission for the issues in the filter.
The filter’s JQL query (e.g., issuetype = Bug AND updated <= -2w) can be verified inIssues > Manage filters.
To avoid impacting the filter, Christian could modify the JQL to exclude recently updated issues or create a temporary filter for the bulk operation.
You renamed a status in the workflow of a team-managed project. Which statement is true?
The status will be renamed in all team-managed workflows.
Workflow rules that reference the status must be updated.
Transitions coming into that status must be updated.
Saved filters that reference the status must be updated.
The status will be renamed on the Status page in Jira administration.
Renaming a status in a team-managed project’s workflow affects only that project’s workflow, as statuses in team-managed projects are project-specific. The primary impact is thatsaved filters that reference the status must be updated(Option D), as JQL queries in filters use status names and will no longer return correct results if the status name changes.
Explanation of the Correct Answer (Option D):
In Jira, saved filters often use JQL queries that reference status names (e.g., status = "In Progress"). If a status is renamed in a team-managed project’s workflow (e.g., from “In Progress” to “Active”), any filters referencing the old status name will no longer include issues in the renamed status. These filters must be updated to use the new status name.
Exact Extract from Documentation:
Manage statuses in team-managed projects
Statuses in team-managed projects are project-specific and edited inProject settings > Workflow. Renaming a status changes its name for that project’s issues.
Impact: JQL queries in filters, boards, or dashboards that reference the status name (e.g., status = "In Progress") will no longer match issues in the renamed status. Update these queries to use the new status name.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Why This Fits: Renaming a status affects JQL-based filters that explicitly reference the status, requiring updates to reflect the new name, making Option D the correct answer.
Why Other Options Are Incorrect:
The status will be renamed in all team-managed workflows (Option A):
Statuses in team-managed projects are project-specific, not shared across projects. Renaming a status in one project’s workflow does not affect other team-managed projects.
Extract from Documentation:
Each team-managed project has its own workflow and statuses, independent of other projects. Changes to a status in one project do not affect others.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Workflow rules that reference the status must be updated (Option B):
Workflow rules in team-managed projects (e.g., transition restrictions, fieldupdates) reference statuses by their internal IDs or context, not their display names. Renaming a status does not break these rules, so they do not need updating.
Extract from Documentation:
Workflow rules in team-managed projects are tied to status IDs, not names. Renaming a status does not require updating rules.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
Transitions coming into that status must be updated (Option C):
Transitions in a workflow reference statuses by their internal IDs or context, not their display names. Renaming a status does not affect the transitions pointing to it, so no updates are needed.
Extract from Documentation:
Transitions are linked to statuses by internal IDs. Renaming a Bedrock status does not affect transition configurations.
(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects")
The status will be renamed on the Status page in Jira administration (Option E):
TheStatus pagein Jira administration (Settings > Issues > Statuses) manages global statuses used in company-managed projects. Team-managed project statuses are project-specific and do not appear on or affect the global Status page.
Extract from Documentation:
Statuses in team-managed projects are project-specific and not listed inSettings > Issues > Statuses, which is for company-managed projects.
(Source: Atlassian Support Documentation, "Manage statuses in Jira Cloud")
Additional Notes:
Renaming a status in a team-managed project is done inProject settings > Workflowand requires project admin privileges.
To minimize filter issues, use status IDs in JQL queries (e.g., status = 10001), but this is less common than using names.
George is the project lead of several projects. Now, he needs to create projects but should not have Jira administrator privileges. What does George need?
Project role
Product access
Project permission
Global permission
Product role
To create projects in Jira Software Cloud without having full Jira administrator privileges, George needs a specificglobal permission, namely theCreate Projectspermission. This permission allows users to create new projects without granting them broader administrative access.
Explanation of the Correct Answer (Option D):
TheCreate Projectsglobal permission enables a user to create new projects in Jira. This permission is distinct from Jira administrator privileges, which include managing global settings like schemes, users, and workflows. By granting George this permission, he can create projects while maintaining a limited scope of authority.
Exact Extract from Documentation:
Global permissions
Global permissions control access to system-wide actions in Jira. TheCreate Projectspermissionallows users to create new projects without requiring full Jira administrator privileges.
To grant this permission:
Go toSettings > System > Global permissions.
Add a user, group, or role to theCreate Projectspermission.Note: Users with this permission can create projects but cannot modify global configurations like schemes or user management unless they have additional permissions.(Source: Atlassian Support Documentation, "Manage global permissions")
Why This Fits: TheCreate Projectsglobal permission directly addresses the requirement for George to create projects without needing Jira administrator privileges, making Option D the correct choice.
Why Other Options Are Incorrect:
Project role (Option A):
Project roles (e.g., Administrator, Developer) are used within a project’s permission scheme to grant project-specific permissions, such asAdminister ProjectsorBrowse Projects. They do not control the ability to create new projects, which is a system-level action.
Extract from Documentation:
Project roles are used in permission schemes to grant permissions within a specific project. They do not apply to global actions like creating projects.
(Source: Atlassian Support Documentation, "Manage project roles")
Product access (Option B):
Product access determines whether a user can use Jira Software or other Atlassian products. While George needs product access to use Jira, this does not grant the specific ability to create projects.
Extract from Documentation:
Product access allows users to log in and use Jira products. Specific actions, like creating projects, require global or project permissions.
(Source: Atlassian Support Documentation, "Manage product access")
Project permission (Option C):
Project permissions (e.g.,Administer Projects,Browse Projects) are defined in a project’s permission scheme and apply to actions within a specific project. Creating a project is a global action, not tied to any existing project’s permission scheme.
Extract from Documentation:
Project permissions control actions within a project, such as editing issues or managing components. Global permissions control system-wide actions like creating projects.
(Source: Atlassian Support Documentation, "Manage project permissions")
Product role (Option E):
Product roles (e.g., Jira Software User, Jira Service Management Agent) define access to specific Atlassian products but do not grant permissions for actions like creating projects. This is not relevant to the requirement.
Extract from Documentation:
Product roles determine access to Atlassian products and are not related to specific permissions like creating projects.
(Source: Atlassian Support Documentation, "Manage product roles")
Additional Notes:
TheCreate Projectspermission can be granted to George via a group or directly to his user account inSettings > System > Global permissions.
As a project lead, George likely already has project-level permissions (e.g.,Administer Projectsfor his projects), but these do not extend to creating new projects.
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.
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.
