Support policies
Bitbucket Server FAQ
- Bitbucket rebrand FAQ
- How do I change the external database password
- Bitbucket Server home directory
- Raising a request with Atlassian Support
- Support policies
- Building Bitbucket Server from source
- Contributing to the Bitbucket Server documentation
- Collecting analytics for Bitbucket Server
- Bitbucket Server EAP - How to update your add-on
On this page
In this section
Related content
- Automation For Jira - Troubleshooting the most common errors reported in the rule audit logs
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira rule fails "java.lang.StringIndexOutOfBoundsException: begin 12, end 3, length 3" error
- The Jira application throws a 500 error in the UI when any Automation For Jira page is accessed
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- "An unknown error occurred" when enabling or saving Jira Automation rules after upgrade
- Automation rule fails with the error "you do not have the permission to associate a worklog to this issue"
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- An automation rule shows the error "Could not find configured field '[object Object]'. It may have been deleted" in its configuration
- Automation for Jira cannot publish an Automation rule with an error: "additional fields contains invalid field(s) in ‘update’ or ‘fields’ section: <Field_Name>"
Welcome to the support policies index page. Here, you'll find information about how Atlassian Support can help you and how to get in touch with our helpful support engineers. Please choose the relevant page below to find out more.
- Bug fixing policy
- New features policy
- Security Bugfix Policy
- Finding Your Bitbucket Server Support Entitlement Number (SEN)
To request support from Atlassian, please raise a support issue in our online support system. To do this, visit support.atlassian.com, log in (creating an account if need be) and create an issue. Our friendly support engineers will get right back to you with an answer.
Last modified on Feb 25, 2021
In this section
Related content
- Automation For Jira - Troubleshooting the most common errors reported in the rule audit logs
- Automation For Jira (A4J) Data Center - The ultimate troubleshooting guide
- Automation for Jira rule fails "java.lang.StringIndexOutOfBoundsException: begin 12, end 3, length 3" error
- The Jira application throws a 500 error in the UI when any Automation For Jira page is accessed
- Automation for Jira - Troubleshooting guide for situations where automation rules are not triggered
- "An unknown error occurred" when enabling or saving Jira Automation rules after upgrade
- Automation rule fails with the error "you do not have the permission to associate a worklog to this issue"
- Automation rule| Rule audit logs indicate an error upon execution even though the operation was performed successfully
- An automation rule shows the error "Could not find configured field '[object Object]'. It may have been deleted" in its configuration
- Automation for Jira cannot publish an Automation rule with an error: "additional fields contains invalid field(s) in ‘update’ or ‘fields’ section: <Field_Name>"
Powered by Confluence and Scroll Viewport.