Restricted functions in Jira Cloud applications

Still need help?

The Atlassian Community is here for you.

Ask the community

In Jira Cloud applications, unlike in Jira Server applications, there's no Jira System administrator role. The closest equivalent to a Jira System administrator is an Atlassian Cloud site admin, who has all the rights of a Jira admin plus extra user management and site admin rights (like managing billing details). Some functions of the Jira Server system admin can't be performed in Jira Cloud, or must be performed by Atlassian Technical Support by request.

This table describes functions that are restricted in Jira Cloud applications, and whether they can be configured by Atlassian Technical Support:

Restricted function

Configurable on request?

Notes

External user management

Yes

This can be configured using G Suite. To allow single sign-on (SSO), you can use SAML.

Jira as a user server

No You can't link Cloud applications to another Cloud or Server site for user management. Instead, link Cloud applications to G Suite or SAML for user management and access.
LDAP for user management No
See ID-79 - Getting issue details... STATUS for the status of this functionality request.

Configure an outgoing (SMTP) mail server

No

Atlassian Cloud comes with an internal SMTP server configured to send notifications. The prefix is not configurable.

Incoming mail servers

  •  Configuring file system messages

No

You can configure POP/IMAP mail servers but not file system messages.

To create issues in Jira and Jira Service Desk via email using POP/IMAP servers, make sure they are configured to the standard ports: IMAP: 143; IMAPS: 993; POP3: 110; POP3S: 995.

Change project key pattern No

Configure listeners

No

See  AOD-6015 - Getting issue details... STATUS for the status of this functionality request.

Configure services

No


Customize source files

No


Customize Jira notifications

No

To customize Jira notifications, one must edit Velocity files within the Jira web app. This makes it a special case of "customizing source files". See AOD-1791 - Getting issue details... STATUS and JRA-7266 - Getting issue details... STATUS for suggestions to allow customizing email content via the web UI.

Change the index path

No


Run the integrity checker

No


Configure logging and profiling information

No

We have an auditing feature available in labs. To turn it on, go to http://<your_site_name>/auditing/settings.

Access the scheduler

No


Import data

Yes

Check out Import and export data to learn about supported imports for Jira Cloud. To migrate to Jira Cloud, you can use an evaluation copy of Jira hosted on your own server to import from non-Atlassian products or individual projects.

Import XML workflows into Jira

No

You can only import workflows from Marketplace.

Import Jira projects No

You can't restore projects from a backup in Jira Cloud.

See JRA-31806 - Getting issue details... STATUS for the related feature request status, and How to import a project from a JIRA Server application to a JIRA Cloud application for workaround.

Install custom add-ons

No

For a list of supported add-ons, see Marketplace apps. Some add-ons are only available for Server applications and are not compatible with Cloud.

Disable attachments, or set the attachment path

No

Attachments are enabled by default

Run Jelly scripts

No

See CLOUD-1439 - Getting issue details... STATUS for the related feature request status.

Configure trusted applications

No


Modify SysAdmin users & attributes

No


Install intermediate SSL certificates No

It's not possible to install intermediate certificates in Jira Cloud applications. Intermediate certificates could cause problems when you add secure POP/IMAP mail servers that have certificates signed by non-root CAs.

The workaround is to obtain a certificate signed by a trusted root Certification Authority (CA). For a full list of these certificates, see this list.

HTML and JavaScript in issue fields No This feature creates an XSS vulnerability that could allow malicious users to gain system administrator permissions and use the Cloud infrastructure for nefarious purposes. Instead, use wiki markup.
Text Gadget No
This gadget creates an XSS vulnerability as it can contain arbitrary HTML. See the related issue at JRA-29848 - Getting issue details... STATUS .
Upload custom icons for issue type and priority No
This is tracked at  JRA-21246 - Getting issue details... STATUS .
Default session timeout No
This is tracked at JRA-34258 - Getting issue details... STATUS .
External gadgets No
Configure OAuth authentication No
  • 3-legged OAuth is automatically configured for application links.
  • 2 Legged OAuth without impersonation is supported and required for the Development Panel. Use this type to connect to Bitbucket Server and Bamboo Server.
  • 2-legged OAuth with impersonation is not supported.
Configure secure administrator sessions No
Custom database configuration No Changing the database can negatively impact performance.
Last modified on May 30, 2018

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.