Three team members have left the company and their issues need to be re-assigned to various - users. All of their issues are in the Marketing project which uses the Default Notification Scheme. The scheme has never been updated. How do you inform the new assignees about their re-assigned issues?
Correct Answer: A
Question 17
Peter is building a workflow in his team-managed project. He can add several rules to his workflow except for one rule. Identify that rule.
Correct Answer: B
In team-managed projects, workflows are simplified and configured withinProject settings > Workflow. Users (typically project admins) can add rules to transitions, such as clearing fields, restricting transitions, or setting field values. However, team-managed workflows do not support complex automation-like rules, such as automatically reopening Sub-tasks when a Story is reopened, as this requires interacting with related issues (Sub-tasks), which is not supported out-of-box in team-managed workflow rules. * Explanation of the Correct Answer (Option B): * The rule toreopen Sub-tasks when reopening Storiesrequires a workflow rule to detect the transition of a Story to an open status and then automatically transition its Sub-tasks to an open status. Team-managed workflows do not support rules that affect related issues (e.g., Sub-tasks) during a transition. This functionality requires Jira automation or a company-managed project workflow with custom post functions, which are not available in team-managed projects. * Exact Extract from Documentation: Configure workflows in team-managed projects Team-managed projects use simplified workflows that allow adding rules to transitions, such as: * Restricting transitions to specific users or roles. * Setting or clearing field values (e.g., Assignee, Description). * Requiring fields to be filled.Rules are limited to the issue being transitioned and cannot affect related issues (e.g., Sub-tasks, Epics). To automate actions on related issues, use Jira automation rules.Note: Team-managed workflows are project-specific and edited inProject settings > Workflow.(Source: Atlassian Support Documentation, "Configure workflows in team-managed projects") * Why This Fits: The rule to reopen Sub-tasks requires interacting with related issues (Sub-tasks), which is beyond the capabilities of team-managed workflow rules, making Option B the correct answer. * Why Other Options Are Incorrect: * Rule to clear the Assignee when closing (Option A): * Team-managed workflows support rules to clear fields during a transition. A rule can be added to the transition to theClosedstatus to clear theAssigneefield. * Extract from Documentation: You can add a rule to a transition to clear a field, such as Assignee, when moving to a status like Closed. (Source: Atlassian Support Documentation, "Configure workflows in team-managed projects") * Rule to ensure only Peter can approve Stories (Option C): * Team-managed workflows allow restricting transitions to specific users or roles. A rule can be added to the transition to anApprovedstatus to allow only Peter to perform it. * Extract from Documentation: Add a rule to restrict a transition to a specific user (e.g., Peter) or role, ensuring only they can move issues to a status like Approved. (Source: Atlassian Support Documentation, "Configure workflows in team-managed projects") * Rule to clear the Description when reopening (Option D): * Team-managed workflows support clearing fields during transitions. A rule can be added to the transition to anOpenstatus to clear theDescriptionfield. * Extract from Documentation: Rules can clear fields like Description during a transition, such as when reopening an issue. (Source: Atlassian Support Documentation, "Configure workflows in team-managed projects") * Rule to ensure only the Reporter can close bugs (Option E): * Team-managed workflows allow restricting transitions to specific users, including the Reporter. A rule can be added to the transition to theClosedstatus for bugs to allow only the Reporter to perform it. * Extract from Documentation: Restrict a transition to the Reporter to ensure only they can move issues to a status like Closed. (Source: Atlassian Support Documentation, "Configure workflows in team-managed projects") * Additional Notes: * Team-managed workflows are designed for simplicity, with rules limited to the issue being transitioned. Complex logic, such as affecting Sub-tasks (Option B), requires Jira automation rules, which are separate from workflow rules. * Peter, as a project admin in a team-managed project, can edit the workflow inProject settings > Workflow. : Atlassian Support Documentation:Configure workflows in team-managed projects Atlassian Support Documentation:Automate your Jira Cloud instance
Question 18
Your team currently only uses a single issue type but wants to add a second one. Which configuration requires a separate project for the second issue type?
Correct Answer: E
In a company-managed project, adding a second issue type can often be accommodated within the same project by configuring issue type-specific settings (e.g., fields, layouts). However, if the second issue type requires adifferent workflow, a separate project may be necessary unless the project'sworkflow schemeis modified to support multiple workflows. Since the question implies a configuration thatrequiresa separate project,different workflows per issue type(Option E) is the most likely to necessitate this, as it involves complex workflow management that is often easier to handle in separate projects. * Explanation of the Correct Answer (Option E): * In a company-managed project, aworkflow schememaps workflows to issue types. It is possible to assign different workflows to different issue types within the same project by configuring the workflow scheme. However, managing multiple workflows within a single project can become complex, especially if the workflows have significantly different statuses, transitions, or rules. Creating a separate project for the second issue type simplifies workflow management by isolating the workflows, as each project can have its own workflow scheme. The question's phrasing suggests a scenario where a separate project is required, likely due to the complexity or isolation needed for distinct workflows. * Exact Extract from Documentation: Configure workflow schemes A workflow scheme maps workflows to issue types in a company-managed project. To use different workflows: * Go toSettings > Issues > Workflow schemes. * Create or edit a scheme and assign different workflows to issue types (e.g., one for Issue Type A, another for Issue Type B). * Apply the scheme to the project inProject settings > Workflows.Note: For complex or conflicting workflows, separate projects may be preferred to simplify management and avoid configuration conflicts.(Source: Atlassian Support Documentation, "Configure workflow schemes") * Why This Fits: While different workflows can technically be managed within one project via a workflow scheme, the complexity or need for isolation (e.g., different teams, permissions, or configurations) often necessitates a separate project for the second issue type's workflow, making Option E the correct answer. * Why Other Options Are Incorrect: * Different custom fields per issue type (Option A): * Different custom fields can be configured for eachCustom field contextsorscreen schemes allow different fields to be shown or hidden for specific issue types within the same project. A separate project is not required. * Extract from Documentation: Custom field contexts or screen schemes can restrict fields to specific issue types within a single project. Separate projects are not needed. (Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud") * Different card colors per issue type (Option B): * Card colors on boards (e.g., Kanban, Scrum) are configured per issue type usingboard settings(e.g., based on issue type or priority). This is managed within a single project and does not require a separate project. * Extract from Documentation: Card colors are configured inBoard settings > Card colorsand can vary by issue type within the same project. (Source: Atlassian Support Documentation, "Configure boards in Jira Cloud") * Different components per issue type (Option C): * Componentsare project-specific, not issue type-specific. While components can be assigned to issues, they are not tied to issue types, and different components can be used within the same project without needing a separate project. * Extract from Documentation: Components are project-specific and can be assigned to any issue type within the same project. (Source: Atlassian Support Documentation, "Manage components in Jira Cloud") * Different issue layouts per issue type (Option D): * Issue layoutscan be configured per issue type within a single project inProject settings > Issue layout. Different layouts for each issue type do not require a separate project. * Extract from Documentation: Issue layouts can be customized for each issue type inProject settings > Issue layoutwithin the same project. (Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") * Additional Notes: * Steps to configure different workflows: * Create a new workflow for the second issue type inSettings > Issues > Workflows. * Update the project's workflow scheme inProject settings > Workflowsto map the new workflow to the second issue type. * Alternatively, create a new project with its own workflow scheme for simplicity. * Configuring workflows and schemes requiresJira administratorprivileges. * A separate project may be preferred for organizational reasons (e.g., different teams, permissions), but technically, a single project can handle different workflows. The question's emphasis onrequiringa separate project points to workflows due to their complexity. : Atlassian Support Documentation:Configure workflow schemes Atlassian Support Documentation:Manage custom fields in Jira Cloud Atlassian Support Documentation:Configure boards in Jira Cloud Atlassian Support Documentation:Manage components in Jira Cloud Atlassian Support Documentation:Configure issue layouts in Jira Cloud
Question 19
Which statement is true about changing a project's key?
You are configuring an issue layout in a company-managed project. Which statement is true?
Correct Answer: B
In a company-managed project, theissue layoutdetermines how fields are displayed in the issue view (e.g., which fields are visible, hidden, or in the context panel). The true statement is thatyou can copy a layout to another project using the same screen(Option B), as Jira allows copying issue layouts to streamline configuration across projects. * Explanation of the Correct Answer (Option B): * Theissue layoutin a company-managed project is configured inProject settings > Issue layout and is tied to a screen (via the screen scheme). Jira allows copying an issue layout to another project that uses the same screen, ensuring consistent field arrangements across projects. * Exact Extract from Documentation: Configure issue layouts in company-managed projects Issue layouts define which fields are displayed, hidden, or placed in the context panel in the issue view. To copy a layout: * Go toProject settings > Issue layout. * SelectCopy layoutand choose another project that uses the same screen.Note: The target project must use the same screen (via its screen scheme) for the layout to be compatible. (Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") * Why This Fits: Copying an issue layout to another project using the same screen is a supported feature, making Option B the correct answer. * Why Other Options Are Incorrect: * You can reuse fields from a team-managed project (Option A): * Fields in team-managed projects are project-specific and cannot be reused in company- managed projects. Company-managed projects use global custom fields or system fields, managed inSettings > Issues > Custom fields. Fields from team-managed projects are isolated and not accessible. * Extract from Documentation: Custom fields in team-managed projects are project-specific and cannot be reused in company-managed projects. Company-managed projects use global custom fields. (Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud") * You can move any field to the Hidden fields section (Option C): * Not all fields can be moved to theHidden fieldssection. System fields likeSummary,Issue Type, andStatusare required and cannot be hidden. Only non-mandatory fields (e.g., custom fields, non-required system fields) can be hidden. * Extract from Documentation: In the issue layout, you can hide non-mandatory fields by moving them to theHidden fieldssection. Required fields like Summary, Issue Type, and Status cannot be hidden. (Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") * You can move any field to the Context fields section (Option D): * TheContext fieldssection (right panel in the issue view) has restrictions on which fields can be placed there. Fields likeSummary,Description, and certain system fields cannot be moved to the context panel, as they are designed for the main issue view. Only eligible fields (e.g., custom fields, Labels, Components) can be moved to theContext fieldssection. * Extract from Documentation: TheContext fieldssection is for fields like Labels, Components, or custom fields. Core fields like Summary and Description cannot be moved to the context panel. (Source: Atlassian Support Documentation, "Configure issue layouts in Jira Cloud") * Additional Notes: * Configuring issue layouts requiresproject adminprivileges for the project (Project settings > Issue layout). * Copying layouts is useful for maintaining consistency across projects with similar configurations. : Atlassian Support Documentation:Configure issue layouts in Jira Cloud Atlassian Support Documentation:Manage custom fields in Jira Cloud
