Functional differences in Atlassian Cloud
The features listed below either function differently or are not applicable in Atlassian Cloud.
- Imports & Exports — Importing and exporting issues in Jira Cloud or spaces in Confluence Cloud varies from completing the process in our Server products. Read Import and export data for information on the supported processes for imports and exports on Atlassian Cloud.
- Templates — External, custom Confluence templates are not supported, and the current layout cannot be altered using custom HTML or CSS. You can create your own templates within Confluence, or you can also download pre-defined templates from the Atlassian Marketplace in the form of a template bundle. You need to be a site admin to install template bundles into your Confluence site. You need Confluence Administrator permissions to manage the existing template bundles. See Global Permissions Overview for more information on roles in Confluence Cloud.
- Apps — Some apps are only supported in self-hosted instances of Jira products and Confluence; however, Atlassian Cloud contains a number of popular apps (and the list just keeps on growing). Refer to the Marketplace apps for the list of supported apps.
- Alternative languages — Atlassian Cloud products and apps are currently available in 22 languages. See our Languages page for a complete list of the languages that are currently available. Note: We are always working to provide more languages across our software products and apps.
- Backups — To create a backup of your Atlassian Cloud data, you will need to create an offline backup. For details on how to create a backup of your data on Jira and Confluence Cloud, refer to Jira - Exporting issues or Confluence - Create a site backup. Note: Atlassian Cloud data is backed up on a daily and weekly basis and can be recovered in the event of a natural disaster.
- Custom domain(s) — Atlassian provides cloud subscribers with a secure, authenticated domain name. Your cloud site is accessible at
https://<domain_name>.atlassian.net, where <domain_name> is a unique word that you specify when signing up for Atlassian Cloud. Note: Choose wisely, because your Atlassian Cloud domain name cannot be changed after your cloud site is created. For more information or to vote on the status of this feature, view updates on or follow CLOUD-6999.
- IP whitelisting (restricting access by source IP range) — IP whitelisting is currently not available on Atlassian Cloud. For more information or to vote on the status of this feature, view updates on or follow AOD-2636. At this time, it is only possible to restrict access by managing project permission or configuring issue-level security. For more information, refer to the Managing project permissions and Configuring issue-level securitydocuments.
- Direct access to the database — If you are moving from a self-hosted server environment to Atlassian Cloud, be aware that you will not have direct access to change the database structure, file system, or other server infrastructure as you did when using our Server products.
- Available ports for connecting to external applications — If you set up application links to an external application, the external application may use either an HTTP protocol (on port 80) or HTTPS protocol (on port 443) or ports 7990, 8060, 8080, 8085, 8090, 8443 (HTTP and HTTPS, standard ports for Bitbucket, Jira and Confluence Server. Read Changing port that your Atlassian application listens on for more.)
- Cloud site redirects — DNS redirection is currently not available on Atlassian Cloud. For more information or to vote on the status of this feature, view updates on or follow CLOUD-5790.
Jira Cloud products