OnDemand Documentation

Index

Skip to end of metadata
Go to start of metadata

JIRA Studio customers will be migrated to the Atlassian OnDemand service starting from the end of January 2012. This page summarises the changes you will see after the migration of your JIRA Studio service.

Wondering about the migration process? Please see our Migration FAQ.

On this page:

Access level changes for your users

What are the changes?

With Atlassian OnDemand, the Developer and Collaborator terminology is no longer valid. Application access replaces the concept of access level. The access level settings for your existing users will be mapped to access to certain applications, as shown in the following table.

Table 1. How access level is mapped to application access

Access level for Studio usersOnDemand application access
Developer

JIRA + Confluence + FishEye/Crucible + Bamboo + GreenHopper

CollaboratorJIRA + Confluence + GreenHopper
Settings for the default access level
  • non-Google Apps: JIRA  + Confluence
  • Google Apps: Your default access level preference for new Google Apps users will be preserved and mapped to OnDemand.
    e.g. If you configured new Google Apps users to be granted Collaborator access in JIRA Studio, then new Google Apps users in OnDemand will be granted access to JIRA + Confluence + GreenHopper

What does this mean in terms of licensing if you continue with the Studio pricing?

If you continue with your Studio pricing, for every Developer license you purchase, you get a user with access to all applications; for every Collaborator license, you get a new user for JIRA and Confluence. For example, you have 20 Developer license and 10 Collaborator license, you can have up to 30 users for JIRA, GreenHopper and Confluence each, up to 20 users for FishEye/Crucible and GreenHopper each, and unlimited users for Bamboo.

What next?

After your service is migrated to Atlassian OnDemand, you can

  • change the default access level, or the default application access as it is called in OnDemand
  • configure the access for your users so that they only see the applications they are interested in

For instructions on how to do these, refer to the Managing application access page.

Bamboo is enabled

If you continue with your Studio pricing and your JIRA Studio service did not have Bamboo enabled, you will notice an extra tab called Builds in Atlassian OnDemand.

Confluence 4.1 - a new text editor

You'll notice that your site now has Confluence 4.1. The first thing you'll notice is a new XHTML-based editor, which was introduced in Confluence 4, and this new editor has replaced the Wiki Markup editor. 

What are the changes?

The editing experience is quite different now. 

The following two pages show you how to use the new editor to do the things you have always done:

Please also check out the following Release Notes to find out the new features.