| OnDemand | Download |
|---|---|
Düzgün, kontrollü ve istikrarlı bir ortam. | Her türlü konfigürasyona açık olduğundan, sistemin yapısı size bağlıdır. |
| Sistem yükseltme ve bakımı otomatik gerçekleştirilir. | Sistemin yükseltemesinden, bakımından, eklenti yüklemelerinden siz sorumlusunuz. |
| Özelleştirmelerde kısıtlamalar (Bakınız Kısıtlama Tablosu). | İstediğiniz gibi özelleştirin. |
https://<accouny_name>.atlassian.net üzerinden sunucunuza erişim. | Kendi alan adınızı kullanın. |
| İngilizce dışındaki alternatif diller için tam destek vermemektedir. | Birden çok dil desteği bulunmaktadır. |
| Veritabanına direk erişim izni yoktur. | Veritabanına erişebilirsiniz. |
Kısıtlama Tablosu
Restricted Function | Configurable on Request? | Notes |
|---|---|---|
General Configuration
| NO | General Configuration options are available in JIRA OnDemand but Advanced Settings are not. External user management is also not available. |
System Administrator Permissions | NO | The JIRA 'System Administrator' global permission is not available in Atlassian OnDemand. 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 OnDemand comes with an internal SMTP server configured to send notifications. |
Incoming Mail Servers
| NO | POP/IMAP Mail Servers are configurable in JIRA OnDemand 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-6015 - Authenticate to see issue details for the status of this functionality request. |
Configuring services | NO |
|
Customising source files | NO |
|
Customising email content | NO | The procedure for customising email content sent in notification messages requires editing Velocity files within the JIRA webapp. This makes it a special case of "customising source files". See JST-1791 and JRA-7266 for feature requests to allow customisation of email contents through the web UI. |
Changing the index path | NO |
|
Running the integrity checker | NO |
|
Configuring logging and profiling information | NO |
|
Accessing the scheduler | NO |
|
Importing data | YES | Please read Importing Data for information on supported imports for Atlassian OnDemand. Imports from certain non-Atlassian products or single project imports can be performed using a local evaluation copy of JIRA to create a compatible backup that can be imported into OnDemand. |
Importing XML workflows into JIRA | NO |
|
| Importing JIRA projects | NO | The information on Restoring a Project from Backup does not apply to Atlassian OnDemand. |
Plugins | NO | Only default plugins are allowed. Please see Add-ons in OnDemand for the list of supported plugins. |
Plugin Repository | NO | Only default plugins are allowed. Please see Add-ons in OnDemand for the list of supported plugins. |
Disabling attachments, or setting the attachment path | NO | Attachments enabled by default |
Running Jelly scripts | NO | Please see JST-1439 on the status. |
Configuring LDAP integration | NO |
|
Configuring trusted applications | NO |
|
| Configuring application links | YES | |
| Connecting local Bamboo installations | NO | |
| Configuring issue links | NO | |
Accessing license details | NO |
|
Modifying SysAdmin users & attributes | NO |
|
| Deactivating users | NO | It is not possible to 'deactivate' a JIRA user in JIRA OnDemand. Instead use Atlassian OnDemand's application access features to restrict a user's access to one or more applications in Atlassian OnDemand. |
Remote API (XML-RPC, SOAP, REST) | YES | This is already enabled by default. For more information, see JIRA Remote API. |
| Installing intermediate SSL certificates | NO | It is not possible to install intermediate certificates in OnDemand. 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 in issue fields | NO | This feature creates an XSS vulnerability that could allow malicious users to gain system administrator permissions and use the OnDemand infrastructure for nefarious purposes. Wiki markup is still available. |
| Uploading custom icons for issue type and priority | NO | This is tracked at JRA-21246. |
| External gadgets | NO | |
| Change number of workflow transition buttons | YES | Create a support request at https://support.atlassian.com 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). |