Atlassian Data Center Bug Fix Policy

Atlassian Data Center Bug Fix Policy

Atlassian Support Offerings

• Atlassian Cloud Bug Fix Policy

• Atlassian Support Attachment Retention Policy

• Atlassian End of Support Policy

• Atlassian Data Center Bug Fix Policy

• Supported Platforms

• Implementation of New Features Policy

• Atlassian Cloud Update Policy

• Atlassian Cloud Security Update Policy

• Premier Support Offering Details

• Troubleshooting and Support Tools

• Priority Support Offering Details

• Eligibility for Support Tickets for Atlassian Cloud

• Atlassian Support Locations

• Atlassian Support AI chat

• FastShift Terms

• Atlassian FastShift Data Processing Addendum

• Third-Party FastShift Sub-processors

• FastShift Security Measures

On this page

Related content

• No related content found

Still need help?

The Atlassian Community is here for you.

Ask the community

Summary

This policy outlines the procedures for managing functional bugs. For further information regarding security vulnerabilities, visit Security Bug Fix Policy.

• Our Support team helps with workarounds and bug reporting

• As a general rule, we'll fix critical functional and security bugs in all currently supported releases: the latest feature release and supported LTS releases. To check which releases are supported, check the Atlassian End of Support Policy.

• We schedule fixing non-critical bugs according to a variety of considerations.

• We support releases for two years after the initial feature or Long Term Support (LTS) release.

Example:

We provide technical support for Jira Software 10.2.x for two years after Jira 10.2.0 was released. After that, Jira Software Data Center 10.2 will no longer receive security and functionality bug fixes.

Report a bug

If you're working on an app for an Atlassian product or using our APIs, we encourage you to report any bugs through the Ecosystem Jira.

Shared responsibility model

While Atlassian is committed to delivering secure products out of the box, we also rely on a shared responsibility model. This model requires customers to implement practices that continue beyond deployment and extend into operational phases. Some of these responsibilities include:

• Operating Atlassian software on private networks.

• Ensuring timely implementation of security fixes once they're released.

• Configuring Web Application Firewalls (WAF), VPNs, multi-factor authentication, and single sign-on capabilities.

• Implementing encryption and access controls.

• Performing regular backups.

• Conducting regular security audits.

This guide defines the roles and responsibilities for both Atlassian and Datta Ceter admins that are required for the most secure product environment.

On this page:

Bug reports

Atlassian Support is eager and happy to help verify bugs—we take pride in it!

Create an issue in our support system, providing as much information as you can about how to replicate the problem you're experiencing. We'll replicate the bug to verify and then lodge the report for you. We'll also try to construct workarounds, if possible.

Search existing bug reports

Use our public issue tracker to search for existing bugs. Report new issues, watch and vote for the ones that are important to you. If you watch an issue, we'll email you a notification when it's updated.

How we approach bug fixing

Evaluating bugs by their symptom severity allows us to focus on the fixes that matter most. We prioritize security issues, in line with our Security Bug Fix Policy.