Restricted functions in JIRA Cloud applications
Generally speaking, all functions performed by the JIRA System administrator in JIRA server applications are restricted in JIRA Cloud applications. The following table lists all of the functions that are restricted in JIRA Cloud applications, even to users with administrator permissions. The table below also lists whether the function can be configured by Atlassian Technical Support on request. If not, then it is unavailable for your configuration in JIRA Cloud applications.
Restricted function | Configurable on request? | Notes |
---|---|---|
General Configuration
| NO | A limited number of specific General Configuration and Advanced Settings options are available in JIRA Cloud applications. External user management is not available. |
System Administrator Permissions | NO | The JIRA 'System Administrator' global permission is not available in JIRA Cloud applications. The 'JIRA administrators' permission is still available. You can see a list of differences between the two administration types here. |
Configuring an outgoing (SMTP) Mail server | NO | Atlassian Cloud comes with an internal SMTP server configured to send notifications. |
Incoming Mail Servers
| NO | POP/IMAP Mail Servers are configurable in JIRA Cloud applications but File system messages are not. Note that you can create issues via email using those POP/IMAP servers. |
Changing project key pattern | NO | |
Configuring listeners | NO | Please see - AOD-6015Getting issue details... STATUS for the status of this functionality request. |
Configuring services | NO |
|
Customizing source files | NO |
|
Customizing email content | NO | The procedure for customizing email content sent in notification messages requires editing Velocity files within the JIRA web app. This makes it a special case of "customizing source files". See - AOD-1791Getting issue details... STATUS and - JRA-7266Getting issue details... STATUS for suggestions to allow customization of email contents through the web UI. |
Changing the index path | NO |
|
Running the integrity checker | NO |
|
Configuring logging and profiling information | NO | In Labs we have an Audit feature available. The feature can be enabled at the following location: |
Accessing the scheduler | NO |
|
Importing data | YES | Please read Import and export data for information on supported imports for JIRA Cloud. Imports from certain non-Atlassian products (e.g. Bugzilla FogBugz for Your Server) or single project imports can be performed using a local evaluation copy of JIRA to create a compatible backup that can be imported into JIRA Cloud. |
Importing XML workflows into JIRA | NO | It is possible to Import Workflow from Marketplace only. |
Importing JIRA projects | NO | Restoring a project from backup does not apply to JIRA Cloud. Please see - JRA-31806Getting issue details... STATUS for the related feature request status, and Project Import From JIRA Server to JIRA Cloud for workaround. |
Add-ons | YES | Please see Add-ons and plugins for the list of supported add-ons. |
Disabling attachments, or setting the attachment path | NO | Attachments enabled by default |
Running Jelly scripts | NO | Please see - CLOUD-1439Getting issue details... STATUS for the related feature request status. |
Configuring LDAP integration | NO |
|
Configuring trusted applications | NO |
|
Configuring application links | YES | |
Connecting local Bamboo installations | YES | |
Accessing license details | NO |
|
Modifying SysAdmin users & attributes | NO |
|
Deactivating users | NO | It is not possible to 'deactivate' a user in JIRA Cloud applications. See Manage application access for information on how restrict a user's access to one or more applications in Atlassian Cloud. |
Renaming users | YES | It is possible to rename a JIRA application and/or Confluence user in Cloud User Management. |
Remote API (REST) | YES | For more information, see JIRA REST APIs. |
Installing intermediate SSL certificates | NO | It is not possible to install intermediate certificates in JIRA Cloud applications. The potential impact might be that you will run into problems when adding 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). The full list is here. |
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. Wiki markup is still available. |
Text Gadget | NO | This gadget creates an XSS vulnerability as it can contain arbitrary HTML. Please see - JRA-29848Getting issue details... STATUS . |
Uploading custom icons for issue type and priority | NO | This is tracked at - JRA-21246Getting issue details... STATUS . |
Default session timeout | NO | This is tracked at - JRA-34258Getting issue details... STATUS . |
External gadgets | NO | |
Change number of workflow transition buttons | YES | Create a support request with the number of transition buttons you want, and a 15-minute maintenance window (with 24 hours of notice) and Atlassian Support will configure it for you. (We'll be working from Advanced workflow configuration). |
Configuring OAuth authentication | NO | You need the 'JIRA System Administrators' global permission to do that. 3 Legged OAuth is automatically configured for Application Links. |
Configuring Secure Administrator Sessions | NO |