ATLASSIAN Jira Administrator ACP-120 Question # 2 Topic 1 Discussion

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.