Summary
Raise the maximum character limit for service account names in Atlassian organisation administration from the current 30 characters to a higher limit (suggested: 64 characters, with 50 as a minimum acceptable increase).

Problem statement
The current 30-character limit on service account names is too restrictive for organizations that need to follow structured, descriptive naming conventions. Customers responsible for setting up and managing service accounts at scale are finding it very difficult to design a naming convention that:

• Uniquely identifies the service account across the organization

• Indicates the owning team, environment, and purpose/integration

• Remains human-readable and auditable

• Fits within 30 characters

As a result, admins are forced to use cryptic abbreviations or hashes, which reduces clarity, increases the risk of naming collisions, and makes ongoing administration, auditing, and access reviews significantly harder.

Customer impact

• Org admins cannot apply a consistent naming standard across all service accounts.

• Increased operational overhead — admins spend time inventing and documenting abbreviations.

• Reduced auditability and traceability of service accounts to their owning team/integration.

• Higher risk of misconfiguration when multiple accounts have similar shortened names.

• Friction when onboarding new integrations, especially in larger organizations with many teams and tools.

Example naming convention (currently blocked)
A typical desired convention such as:
svc-<team><product><environment>-<purpose>
e.g. svc-platform-jira-prod-automation (33 chars) — already exceeds the current limit.