What happens to WBS Gantt-Chart for Jira when changing a project key?

Question

What is the impact on WBS Gantt-Chart for Jira if I change a project key (for example, during a migration or to resolve a duplicate key)? Do I need to update anything manually or in the database?

Answer

WBS Gantt-Chart for Jira identifies issues by their issue keys, which always include the project key as a prefix (e.g., PROJ-123). When you change a project key in Jira (such as from OLDPROJ to NEWPROJ), Jira automatically updates all issue keys to use the new prefix (e.g., NEWPROJ-123).

What does this mean for WBS Gantt-Chart?

The chart will continue to function normally as long as the issue keys are updated by Jira.
You do not need to make any direct changes in the database for WBS Gantt-Chart to recognize the new project key.

Important Considerations

However, there are a few things to watch out for:

Hardcoded References:
If you have saved Gantt charts or templates containing hardcoded references to the old issue keys, such as dependencies or links pointing to OLDPROJ-123, you will need to update those references manually.
JQL Filters:
If you use JQL filters in your Gantt charts or elsewhere that explicitly mention the old project key (e.g., issuekey = OLDPROJ-123), those filters will become invalid after the project key change. Update your filters to use the new project key.

Need More Help?

If you have further questions or need additional assistance, feel free to reach out to the Ricksoft Support Team. We're here to help!