In Confluence Cloud, the space name field is limited to 200 characters when creating a space, but the same field accepts longer values (at least 255 characters in our tests) when renaming an existing space. This inconsistency is not documented (UI or REST API), and there is no officially published maximum length for space names.

This behaviour impacts customers who automate space creation from Jira issues, where the issue summary can be up to 255 characters. When the Jira summary exceeds 200 characters, automations that use it directly as the space name may fail during creation, even though longer values are accepted later by the rename flow.

We request that Confluence:

1. Align the character limits between space creation and rename (UI and API), using a single, well‑defined maximum, and

1. Clearly document the effective maximum supported length and provide an official recommendation for integrators (e.g. what limit they should enforce in Jira → Confluence automations), which is especially important for large Data Center → Cloud migrations.