What is the impact of changing the name of a project?

Changing the name of a project in Jira Software Cloud affects how the project is displayed and referenced in certain contexts, but it does not have significant system-wide impacts like reindexing or changing URLs. The primary impact is thatissue filters may need to be updated(Option E), as filters often reference the project name.

Explanation of the Correct Answer (Option E):

In Jira, issue filters (created using JQL, Jira Query Language) can include the project name to scope the search (e.g., project = "Old Project Name"). If the project name changes, any filters that explicitly reference the old project name will no longer return the correct results and must be updated to use the new project name.

Exact Extract from Documentation:

Change a project’s name

To change the name of a project:

Go toProject settings > Details.

Update theNamefield and save changes.Impact: Changing the project name does not affect the project key, issue keys, or URLs. However, JQL queries, filters, or dashboards that reference the project by name (e.g., project = "Old Name") may need to be updated to reflect the new name.Note: Use the project key in JQL queries to avoid issues with name changes, as the key remains constant.(Source: Atlassian Support Documentation, "Manage project settings in Jira Cloud")

Why This Fits: The documentation explicitly states that changing a project’s name impacts JQL-based filters and dashboards that reference the project name, making Option E the correct choice.

Why Other Options Are Incorrect:

Jira will need to be reindexed (Option A):

Changing a project name is a metadata update that does not affect the search index. Reindexing is required for changes like modifying field configurations or schemes, but not for renaming a project.

Extract from Documentation:

Reindexing is required when you make changes to field configurations, schemes, or indexing settings. Changing a project’s name or key does not trigger a reindex.

(Source: Atlassian Support Documentation, "Reindex Jira Cloud")

The URL for issues will change (Option B):

Issue URLs in Jira are based on the project key and issue key (e.g., https:// .atlassian.net/browse/KEY-123), not the project name. Changing the project name does not affect URLs.

Extract from Documentation:

Issue URLs are constructed using the project key and issue key, which remain unchanged when the project name is updated.

(Source: Atlassian Support Documentation, "Manage projects in Jira Cloud")

The old name can no longer be reused (Option C):

There is no restriction in Jira preventing the reuse of a previous project name. Project names are not required to be unique, and the old name can be reused for another project or reverted if needed.

Extract from Documentation:

Project names can be reused across projects, as they are not required to be unique. The project key, however, must be unique.

(Source: Atlassian Support Documentation, "Create and configure projects")

The project key will also change (Option D):

The project key is a separate attribute from the project name and remains unchanged when the name is updated. Changing the project key is a distinct operation that requires admin permissions and affects issue keys and URLs.

Extract from Documentation:

The project key is a unique identifier for the project and does not change when you update theproject name. To change the project key, use theChange project keyoption, which updates all issue keys and URLs.

(Source: Atlassian Support Documentation, "Edit a project key")

Additional Notes:

To minimize the impact of project name changes, it’s recommended to use the project key in JQL queries (e.g., project = KEY) instead of the project name, as the key is immutable unless explicitly changed.

Changing the project name requires project admin permissions and is done inProject settings > Details.