The Atlassian Design System components and foundations (features) have three release phases and two deprecation phases.
This page provides guidance on what you can expect at each phase and who can use them.
You can get help with our features and report bugs by contacting us.
There’s more guidance for Atlassian teams about the release phase changes (Atlassians only).
Release phases for components and foundations
| Phase | Definition |
|---|---|
| Early Access | New experimental feature. There may be breaking changes in minor releases at versions 0.x. We don't recommend using this unless you are part of an early access pilot group, as support is otherwise not available. |
| Beta | New and ready to use. The feature is supported and stable at versions 1.0+. We are working on improvements based on customer feedback. This may include expanding feature sets, and evolving tooling, guidance, and self-service. Breaking changes will only be made in major releases, and should be infrequent. |
| General Availability | Fully stable and ready to use. |
Deprecation phases
| Phase | Definition |
|---|---|
| Intent to Deprecate (Caution) | This feature is being considered for deprecation. There may be some issues with this feature that need to be resolved. If you are not already using the feature, use the recommended alternative instead. |
| Deprecated | This feature is no longer supported and will be removed after the deprecation period ends. We have provided a recommended solution to replace it and communicated how to move to it. |
No General Availability feature will be removed from the system without a clearly announced deprecation period.