Confluence admins will be getting the ability to rename space keys. This EAP is to allow for early access and testing of 3rd party apps as well as any other interested parties.
The ability to change a Space key has garnered significant interest from numerous customers. Customers frequently request the capability to rename space keys due to organizational changes such as modifications in team or project names, acquisitions by other companies, organizational restructuring, or alterations in user names. Furthermore, unchangeable space keys creates obstacles when attempting to migrate spaces between Confluence instances with identical space keys.
This functionality addresses one of the most requested features in Confluence: allowing users to rename space keys.
To address this, we created the concept of Space Aliases. When you go to Space Settings, Space details, and Edit Space Details, you will see the “Space key:” field is editable. Note that, like the original space keys, these space aliases need to be unique across all spaces.
In places where you see space keys, you will see the new alias, and the alias can be used anyplace a space key currently can be used.
For developers, we kindly request that you refrain from scanning URLs to parse space keys. If this is currently being done, we strongly recommend transitioning to AP.context.getContext() or utilizing our V2 Space API to obtain the correct space key from its response.
Since the alias field is subject to change, it is recommended to avoid using aliases to store your application data. Instead, opt for using the Space ID whenever feasible.
We want to ensure app developers have access to this change early so they can identify any issues this causes to their apps. To get access to this change, please fill out the following form. For additional context about this EAP, please refer to our RFC-54 Introducing Space Alias in the Confluence URL
To sign up, please complete this form.
By signing up for this Early Access Program (“EAP ”), you acknowledge the Atlassian Privacy Policy and that:
- Early access to Space Aliases is governed by the Atlassian Customer Agreement (“ACA”). This feature is considered a “Free or Beta Product”, as set forth in Section 17 of the ACA and is subject to applicable terms, conditions, and disclaimers.
- Early access to updated Space APIs is governed by the Atlassian Developer Terms. These APIs are considered “Early Access Materials”, as set forth in Section 10 of the Atlassian Developer Terms and are subject to applicable terms, conditions, and disclaimers.