An automation rule is configured as shown: * When: Rule is triggered on All comments * If: Initiator is in Developers * Then: Transition the issue to DEVELOPMENT If: Initiator is in Reviewers * Then: Transition the issue to REVIEWYou are only in the Reviewers project role. What happens when you comment on an issue?
Correct Answer: B
The automation rule is triggered when any comment is added to an issue and checks the initiator's project role to determine the action. Since you are only in theReviewersproject role, commenting on an issue will trigger the rule, and the issue will transition toREVIEWbased on the rule's logic. * Explanation of the Correct Answer (Option B): * The rule is triggered byAll comments, meaning any comment on an issue activates the rule. * The rule has twoIfconditions: * If the initiator (the user who commented) is in theDevelopersproject role, the issue transitions toDEVELOPMENT. * If the initiator is in theReviewersproject role, the issue transitions toREVIEW. * Since you are only in theReviewersproject role, the secondIfcondition is met when you comment, and theThenaction transitions the issue toREVIEW. * Exact Extract from Documentation: Configure automation rules Automation rules consist of triggers, conditions, and actions. * Trigger: Defines when the rule runs (e.g., Comment Added). * Condition: Checks criteria like user roles (e.g., Initiator is in Reviewers). * Action: Performs tasks like transitioning an issue.Conditions are evaluated sequentially, and the corresponding action is executed if the condition is met. If multiple conditions apply, each matching condition's action is executed unless restricted by rule logic.Note: The initiator is the user who triggers the rule (e.g., the commenter).(Source: Atlassian Support Documentation, "Automate your Jira Cloud instance") * Why This Fits: As a member of theReviewersproject role, your comment satisfies theIf: Initiator is in Reviewerscondition, triggering theTransition the issue to REVIEWaction, making Option B the correct answer. * Why Other Options Are Incorrect: * The rule does not execute (Option A): * The rule is triggered byAll comments, so any comment, including yours, will execute the rule. The issue is not whether the rule executes but what action it performs. * Extract from Documentation: AComment Addedtrigger activates the rule whenever a comment is added to an issue, regardless of the user' s role. (Source: Atlassian Support Documentation, "Jira automation triggers") * The rule executes but does not perform any actions (Option C): * The rule executes and performs theTransition the issue to REVIEWaction because you are in theReviewersproject role, which satisfies the secondIfcondition. The rule will not skip actions if a condition is met. * Extract from Documentation: If a condition in an automation rule is met, the associated action is executed unless restricted by additional logic. (Source: Atlassian Support Documentation, "Automate your Jira Cloud instance") * The issue transitions to DEVELOPMENT (Option D): * TheDEVELOPMENTtransition is only triggered if the initiator is in theDevelopersproject role. Since you are only in theReviewersrole, this condition is not met, and the issue will not transition toDEVELOPMENT. * Extract from Documentation: Conditions likeInitiator is in [Role]check the user's project role membership. Only the actions for matching conditions are executed. (Source: Atlassian Support Documentation, "Jira automation conditions") * Additional Notes: * The rule assumes theDEVELOPMENTandREVIEWstatuses exist in the project's workflow and that transitions to these statuses are valid from the issue's current status. * If you were in bothDevelopersandReviewersroles, both actions could execute sequentially, but the question specifies you are only inReviewers, so only theREVIEWtransition applies. : Atlassian Support Documentation:Automate your Jira Cloud instance Atlassian Support Documentation:Jira automation triggers Atlassian Support Documentation:Jira automation conditions
Question 42
A company-managed project uses a single issue type. When must a second issue type be added to the project?
Correct Answer: B
In a company-managed project with a single issue type, adding a second issue type is necessary when a configuration requires issue type-specific behavior that cannot be applied to the existing issue type. The requirement that necessitates a second issue type iswhen adding a new workflow(Option B), as different workflows for different issue types require separate issue types to be mapped in the project's workflow scheme. * Explanation of the Correct Answer (Option B): * In a company-managed project, aworkflow schememaps workflows to issue types. If the project currently uses a single issue type with one workflow, adding a new workflow (e.g., for a different process) requires a second issue type to associate with the new workflow. Without a second issue type, the new workflow cannot be applied, as a single issue type can only be mapped to one workflow in a given scheme. Adding a second issue type allows the project to use both the existing workflow (for the current issue type) and the new workflow (for the new issue type). * Exact Extract from Documentation: Configure workflow schemes A workflow scheme maps workflows to issue types in a company-managed project. To use a new workflow: * Create or select a new workflow inSettings > Issues > Workflows. * Update the project's workflow scheme inProject settings > Workflowsto assign the new workflow to a specific issue type.Note: To use multiple workflows in a project, you must have multiple issue types, as each issue type can only be associated with one workflow in a scheme.(Source: Atlassian Support Documentation, "Configure workflow schemes") * Why This Fits: Adding a new workflow requires a second issue type to map the new workflow in the workflow scheme, as a single issue type cannot use multiple workflows, making Option B the correct answer. * Why Other Options Are Incorrect: * When adding a new resolution (Option A): * Resolutionsare global settings (Settings > Issues > Resolutions) that apply to all issues in a project, regardless of issue type. Adding a new resolution does not require a new issue type, as resolutions are managed at the workflow level and can be used by the existing issue type. * Extract from Documentation: Resolutions are global and apply to all issue types. Adding a new resolution does not require new issue types. (Source: Atlassian Support Documentation, "Manage resolutions in Jira Cloud") * When adding a new status (Option C): * A newstatuscan be added to the existing workflow for the single issue type without needing a new issue type. Statuses are part of a workflow, and the existing issue type can use the updated workflow with the new status. * Extract from Documentation: Statuses are added to workflows, not issue types. A new status can be used by the existing issue type's workflow. (Source: Atlassian Support Documentation, "Configure advanced work item workflows") * When adding a new custom field (Option D): * A newcustom fieldcan be applied to the existing issue type via itscustom field contextor screen configuration. It does not require a new issue type, as fields can be shared across or restricted to specific issue types within the same project. * Extract from Documentation: Custom fields can be added to existing issue types via contexts or screens. New issue types are not required. (Source: Atlassian Support Documentation, "Manage custom fields in Jira Cloud") * When adding a new security level (Option E): * A newsecurity levelin the issue security scheme applies to all issues in the project, regardless of issue type. It does not require a new issue type, as security levels are project- wide and not tied to specific issue types. * Extract from Documentation: Security levels apply to all issues in a project and are not issue type-specific. Adding a new level does not require new issue types. (Source: Atlassian Support Documentation, "Configure issue security schemes") * Additional Notes: * Steps to add a second issue type for a new workflow: * Add a new issue type to the project's issue type scheme inProject settings > Issue types. * Create or select a new workflow inSettings > Issues > Workflows. * Update the workflow scheme inProject settings > Workflowsto map the new workflow to the new issue type. * These changes requireJira administratorprivileges. * The need for a second issue type arises specifically from the workflow scheme's one-to-one mapping of workflows to issue types. : Atlassian Support Documentation:Configure workflow schemes Atlassian Support Documentation:Manage resolutions in Jira Cloud Atlassian Support Documentation:Configure advanced work item workflows Atlassian Support Documentation:Manage custom fields in Jira Cloud Atlassian Support Documentation:Configure issue security schemes
Question 43
You want to rename an issue type. What might be impacted by this change?
Correct Answer: D
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 administrator privileges. * 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. : Atlassian Support Documentation:Configure boards in Jira Cloud Atlassian Support Documentation:Manage issue types in Jira Cloud Atlassian Support Documentation:Configure screen schemes in Jira Cloud Atlassian Support Documentation:Configure workflow schemes Atlassian Support Documentation:Manage custom fields in Jira Cloud
Question 44
You are designing a complex new workflow. Two of the requirements are listed below: 1. Any user should be able to trigger the Put On Hold transition from any status in the workflow. 2. Only users with the Close Issues permission should be able to Close the issue at any point in the flow. Based only on these requirements, which two workflow elements should you use? (Choose two.)
Currently, several groups and project robs are listed in every system event of the DEV Notification Scheme and should remain that way. A new requirement states that when DEV issues move from the status Open to status Assigned, only Project Rob (Managers) should be notified. DEV project does not share any of its schemes. Identify the event that needs to be configured.
