JIRA Studio contains fully functional versions of JIRA, Confluence, FishEye, Crucible, and Subversion. However, in order to securely integrate these applications in a hosted environment, some of the functions that are available in the installable versions of the products are restricted in JIRA Studio. This means,
- The function is pre-configured and cannot be altered by anyone, or,
- The function can only be configured by JIRA Studio Technical Support — changes can be requested by filing a ticket at https://support.atlassian.com in the 'JIRA Studio' project.
The functions that are restricted in JIRA Studio are listed below.
On this page:
JIRA Studio General
- Imports — Imports of existing data are available upon request, by filing a ticket at https://support.atlassian.com in the 'JIRA Studio' project. The following imports are supported upon request:
- JIRA issues import from existing JIRA installations.
- Subversion data import from existing Subversion repositories.
- Themes — Custom themes, look & feel, etc, are currently not supported.
- Plugins — JIRA Studio contains a number of popular plugins. Please read the JIRA Studio Plugin Policy for the list of supported plugins. Requests for new plugins should be filed at https://studio.atlassian.com under the JIRA Studio project.
FishEye and Crucible
The FishEye/Crucible administration console is unavailable to JIRA Studio customers. The administration options for these applications have been configured to offer the greatest flexibility and security for our customers. To request changes to the default FishEye/Crucible configuration, please file a feature request at https://studio.atlassian.com under the JIRA Studio project.
JIRA
The following table lists all of the functions that are restricted in JIRA Studio, even to users with administrator permissions. The table also lists whether the function can be configured by JIRA Studio Technical Support on request (if not, then it is unavailable for configuration in JIRA Studio).
| Restricted Function |
Configurable on Request? |
Notes |
| SMTP Mail server |
YES |
By default Studio delivers mail to localhost, and from there to your SMTP server. In some circumstances you may prefer for Studio to deliver it directly to your SMTP server. We can configure this for you, but keep in mind that we would need to know a username/password for your SMTP server.
The [JIRA Studio] prefix is not configurable, as we need its presence to identify email replies to notifications (see JST-539). |
| POP/IMAP Mail servers |
NO |
|
Configure a CVS source code repository
|
NO |
Studio comes with Subversion hosting, and no external repositories are supported.
|
| Configure listeners |
NO |
|
| Configure services |
NO |
|
| Change the index path |
NO
|
|
| Run the integrity checker |
NO
|
|
| Configure logging and profiling information |
NO
|
|
| Access the scheduler |
NO
|
|
| Export/backup JIRA data to XML |
YES |
JIRA exports can be requested by filing at ticket at https://studio.atlassian.com.
|
| Import/restore JIRA data from XML |
NO
|
|
Import data from external systems
(Bugzilla, Mantis, FogBugz, Excel/CSV) |
NO
|
|
| Import XML workflows into JIRA |
NO
|
|
Disable attachments,
Set the attachment path or size limit
|
NO |
Attachments enabled by default, maximum size set to 100MB. |
| Enable trackbacks |
NO
|
|
| Run Jelly scripts |
NO
|
|
| Configure LDAP integration |
NO
|
|
| Configure trusted applications |
NO
|
|
| Access license details |
NO
|
|
Modify SysAdmin users & attributes
|
NO
|
|
Confluence
The following table lists all of the functions that are restricted in JIRA Studio, even to users with administrator permissions. The table also lists whether the function can be configured by JIRA Studio Technical Support on request (if not, then it is unavailable for configuration in JIRA Studio).
| Restricted Function |
Configurable on Request? |
Notes |
General Configuration
- Server Base URL
- Remote API plugin
- External user management
- Public Signup
|
NO
|
Public signup is managed via JIRA.
All APIs are disabled.
|
| Daily Backup Admin |
NO
|
Backups are managed globally. |
| Plugins |
NO
|
Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins. |
| Plugin Repository |
NO
|
Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins. |
| Mail Servers |
NO |
JIRA Studio comes with an internal SMTP server configured to send notifications. |
| User Macros |
NO
|
|
| Attachment Storage |
NO
|
Attachments enabled by default, maximum size set to 10MB. |
| Layouts |
NO
|
|
| Custom HTML |
NO
|
|
| Backup & Restore |
Backup - YES
Restore - NO
|
Confluence exports can be requested by filing at ticket at https://studio.atlassian.com.
|
| SnipSnap Import |
NO
|
|
| Logging and Profiling |
NO
|
|
| Cluster Configuration |
NO
|
|
Subversion
While you can access many of the Subversion functions via the command line client, access to the administration console in Subversion is unavailable, meaning that functions like svnadmin dump and svnadmin load cannot be used.
Enabling/Disabling anonymous access to Subversion is restricted in JIRA Studio, and is disabled by default. You can request for anonymous access to be enabled by filing at ticket at https://studio.atlassian.com.
