Get started with Jira
New to Jira? Check out our guides for new administrators and users.
We have a number of help resources available. You can get your problem resolved faster by using the appropriate resource(s).
Search the Atlassian Community.
Raise a support request*.
Check the Jira knowledge base.
Search the Atlassian Community.
Raise a support request*.
If you've identified a bug but don't need further assistance, raise a bug report.
Raise a suggestion*.
If you need help with something else, raise a support request*.
* Include as much information as possible to help our support team resolve your issue faster.
Our support team handles support requests that are raised in our support system. You need to log in using your Atlassian account before you can raise support requests.
For information on our general support policies, including support availability, SLAs, bugfixes, and more, see Atlassian Support Offerings. Note, you'll find anything security-related at Security @ Atlassian.
Atlassian Community is our official application forum. Atlassian staff and Atlassian users contribute questions and answers to this site.
You may be able to find an answer immediately on the Atlassian Community, instead of having to raise a support request. This is also your best avenue for help if:
you are using an unsupported Jira instance or an unsupported Jira platform,
you are trying to perform an unsupported operation, or
you are developing an add-on for business projects.
You can also have a look at the most popular Jira answers and most popular business projects answers.
If there are known issues with a version after it has been released, the problems will be documented as articles in our knowledge base.
Our official issue tracker records our backlog of bugs, suggestions, and other changes. This is open for the public to see. If you log in with your Atlassian account, you will be able to create issues, comment on issues, vote on issues, watch issues, and more.
Before you create an issue, search the existing issues to see if a similar issue has already been created.
Was this helpful?