The Atlassian Design System components and foundations (features) go through a cycle of three phases of release and two phases of deprecation.
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).
| Phase | Definition | Availability |
|---|---|---|
| Early Access | An experimental feature piloted internally to improve, create, and adopt for a broader audience. Component APIs are still being iterated, so expect breaking changes. We communicate this with a version numbering of 0.x. | Invited internal Atlassian teams — code and some design files will be available publicly, but we only recommend invited Atlassians use them. |
| Beta | New and ready to use. Base experience or technical implementation is complete and will not change, expect new versions to improve the functionality. Code will be at version 1.0 or above. | Internal Atlassian teams — code and some design files will be available publicly, but we only recommend Atlassians use them. |
| General Availability | The feature is stable. Code will be at version 1.0 or above. | Everyone |
| Phase | Definition | Who can use it |
|---|---|---|
| Intent to Deprecate | The feature will be removed soon — usually replaced by a better feature. | Anyone currently using the feature — we provide documentation on what to use instead. |
| Deprecated | The feature is no longer supported. The feature documentation will remain for a short period to support migration. | No one — follow the documentation on what to use instead. |