1. Atlassian OnDemand Documentation Home

1. Atlassian OnDemand Documentation Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.2 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.3 Choosing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4 Getting started administering Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4.1 Getting started with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4.2 Getting started with Bamboo OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4.3 Getting started with Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4.4 Getting started with Confluence OnDemand only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.4.5 Getting started with Source and Review Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.5 Getting started using Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1.6 Getting started for evaluators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2 Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1 Administering Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1 Administering Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.1 Creating new projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.2 Deleting a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.3 Setting project permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.4 Associating a JIRA project with multiple FishEye repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.5 Associating a JIRA project with a Confluence space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.6 Customising Application Tabs for your Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.7 Linking activities from bitbucket or GitHub to JIRA Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.1.8 Configuring cross-application linking in JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.2 Managing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.2.1 Importing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.2.2 Uploading Data via WebDAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3 Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3.1 Managing users and groups for sites with multiple OnDemand applications . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3.2 Managing users and groups for sites integrated with Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3.3 Managing users and groups for JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.3.4 Managing users and groups for Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4 Administering your Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.1 Changing your OnDemand 'From' Email Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.2 Changing your Account Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.3 Requesting support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.4 Changing your Account Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.5 Enabling Public Signup and CAPTCHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.6 Viewing your user count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.7 Changing your Welcome Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.4.8 Integrating OnDemand with Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.5 Managing permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4
5
5
6
7
8
9
12
14
16
18
20
23
24
24
25
25
26
27
27
27
29
30
33
33
33
41
43
44
50
55
56
57
57
58
58
58
59
60
60
61
62
1.2.1.5.1 Managing project visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.6 Configuring the look and feel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.6.1 Changing the Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.6.2 Configuring Global and Default Application Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.6.3 Editing the Date and Time Formats for 'Issues' (JIRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.6.4 Editing the colour scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.1.7 OnDemand Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2 Using Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.1 Creating Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.2 Creating your own dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.3 Managing your profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.3.1 Changing Your Password in Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.4 Working with Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.5 Working with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.5.1 Logging In and Out With Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.5.2 Using Google Docs with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.5.3 Using Google Calendar with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2.2.5.4 Using the Activity Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3 JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1 Administering Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.1 Administration console differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.2 JIRA Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.3 Enabling sub-tasks for a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.4 Configuring JIRA Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.4.1 Disabling or Enabling a JIRA Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.4.2 Viewing your JIRA Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.4.3 Viewing the JIRA Plugin Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.5 Linking a bitbucket or GitHub repository with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.6 Integrating Flowdock with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.7 Connecting Zephyr with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.1.8 Configuring Cloud Connectors in JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2 Working with Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2.1 JIRA User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2.2 Creating an issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2.2.1 Copy of Creating an issue - page structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2.3 Managing agile projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3.2.4 Creating issue comments via emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4 Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1 Administering the Wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.1 Configuring Default Space Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.2 Configuring Confluence Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.2.1 Configuring a Confluence Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.2.2 Disabling or Enabling a Confluence Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.2.3 Viewing the Confluence Plugin Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.2.4 Viewing your Confluence Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.3 Applying a Theme to a Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.4 Creating Confluence templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.1.5 Confluence Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2 Working with the Wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2.1 Confluence User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.4.2.2 Viewing drafts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5 Source and Review Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.1 Administering Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2 Administering Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2.1 Configuring commits to require a JIRA issue key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2.2 Configuring repository permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2.2.1 Configuring repository permissions for a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2.2.2 Configuring default repository permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.2.2.3 Enabling Anonymous Access to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3 Working with Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.3.1 Crucible User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.4 Working with Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.4.1 FishEye User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.4.2 Checking changesets committed against an issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.5.5 Working with the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6 Bamboo OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1 Administering Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.1 Integrating Builds with your Issues Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.1.2 Bamboo Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2 Working with Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.1 Bamboo User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.6.2.2 Actioning Issues via Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.1 changelog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.2 changeset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.3 external user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.4 issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.5 JIRA project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.6 page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.7 project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
63
63
64
65
65
66
66
67
67
69
70
70
71
72
72
74
76
77
81
82
85
86
88
88
89
90
91
91
94
94
94
95
96
98
99
99
101
101
102
104
105
105
106
109
109
112
113
114
115
116
120
120
121
122
123
123
124
126
127
128
128
129
129
130
130
131
132
133
137
138
139
140
141
142
142
142
142
142
142
142
1.7.8 repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.9 review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.10 source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.11 space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.12 user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.7.13 wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8 Atlassian OnDemand release summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.1 February 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.1.1 February 2012 - FishEye Crucible 2.7 upgrade notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.2 January 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.3 December 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.4 November 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.5 The launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.8.6 Known Issues and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.1 Restricted Functions in Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.2 Supported browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.2.1 End of Support Announcements for Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.3 Atlassian OnDemand Application Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.4 Atlassian OnDemand licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5 Support Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.1 Bug Fixing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.2 How to Report a Security Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.3 New Features Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.4 Security Advisory Publishing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.5 Security Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.6 Severity Levels for Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.5.7 Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.6 Atlassian OnDemand Plugin Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.6.1 Third-Party Plugin Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.7 About Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.9.8 Maintenance windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10 Atlassian OnDemand FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1 Usage FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.1 How can I edit or reassign closed issues? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.2 How can I prevent certain users seeing certain content? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.3 How do I access my Subversion repository? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.4 How do I file bugs or log feature requests? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.5 How do I update JIRA issues via subversion commit messages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.6 How should OnDemand be configured for a shared code module? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.7 What is the server base URL for my wiki in Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.8 What is the URL for my installation of Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.1.9 What happens to my existing projects if I purchase new applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2 Configuration and Administration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.1 Can I use a custom Elastic Bamboo image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.2 Subversion is constantly asking users to re-authenticate and failing with the correct credentials . . . . . . . . . . . .
1.10.2.3 Can I change the look and feel of Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.4 Can I install my own plugins? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.5 Are alternative languages available for Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.6 What remote APIs are supported in Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.7 Can I use EBS volumes with Elastic Bamboo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.8 How do I create a backup copy of my Subversion repository? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.9 How do I add Google Apps to Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.10 Can I use Clover with Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.11 How do I import Subversion data for a single project? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.12 How do I migrate from Visual SourceSafe to Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.13 How are we notified of system maintenance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.14 When will my Atlassian OnDemand applications be upgraded? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.15 Where do I set the region used for maintenance windows? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.16 Users are locked out of FishEye and Crucible REST APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.17 I cannot log in using my Google Apps account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.18 I cannot find my applications after adding them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.2.19 Do you support SSL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3 Subscription and Account FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.1 Can I disable a user without deleting them? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.2 How do I add a technical contact to my account? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.3 How do I get started with the Tempo Plugin? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.4 How do I upgrade my account, renew my license, change credit card details, etc? . . . . . . . . . . . . . . . . . . . . . .
1.10.3.5 How is the user count of my account calculated? How do I reduce my user count? . . . . . . . . . . . . . . . . . . . . . .
1.10.3.6 What are the storage and bandwidth limits? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.7 What database does the Atlassian OnDemand instance use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.8 What domain name will my OnDemand service be on? Can I use my own domain name? . . . . . . . . . . . . . . . .
1.10.3.9 What happens to my OnDemand instance when my account is cancelled? . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.10 What is the minimum number of users allowable in an upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.3.11 What is the minimum term of service? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.10.4 Google Apps Integration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11 Contributing to the Atlassian OnDemand Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.11.1 Atlassian OnDemand Documentation in Other Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12 Migrating from JIRA Studio to Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.12.1 Migration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
143
143
143
143
143
143
143
147
148
150
151
152
152
153
154
154
159
159
159
160
161
161
162
162
163
163
163
164
165
166
166
167
168
169
170
170
170
170
170
171
171
171
171
171
172
172
173
173
173
173
173
173
174
175
175
175
175
176
176
176
176
177
177
177
177
178
178
178
178
178
178
179
179
179
179
179
180
181
181
183
Atlassian OnDemand October 2011 Documentation
Atlassian OnDemand Documentation Home
Atlassian OnDemand is a flexible development and collaboration platform for teams of any size. With no downloads and easy administration,
your team can securely develop from wherever they have access to the Internet.
Choose the full suite of applications; or, start with JIRA, Confluence or both, and then expand your platform in an a-la-carte fashion by adding
more applications.
Getting Started
Quick Start Guide for users
Quick Start Guide for administrators
Importing Data
Overview
Choosing applications
FAQ
Domain name
Storage and bandwidth limits
Adding Google Apps to Atlassian OnDemand
See more
JIRA Studio customers
Migrating from JIRA Studio to Atlassian OnDemand
Administering AOD
Creating users and groups
Granting application access to users
Creating new projects
Configuring the look and feel
Using AOD
Overview of the workspace
Creating an issue
Creating links
Resources
Answers from the community
OnDemand on Twitter
Atlassian Training
for Evaluators
Free Trial
Release Summary
Atlassian OnDemand release summary
Support
Atlassian Support
Support Policies
Atlassian OnDemand Plugin Policy
Feedback and Feature Requests
4
Atlassian OnDemand October 2011 Documentation
We'd love to hear any feedback and feature requests from you! Please add an issue under the OnDemand project in our issue tracker here:
Issue Tracker and Feature Requests for OnDemand
Alternatively, you may submit feedback via email to sales@atlassian.com.
Getting started
Getting to know your site
Overview of applications
Workspace
Start using Atlassian OnDemand
Getting started using Atlassian OnDemand, e.g.:
JIRA:
Creating and assigning issues
Viewing your issues with gadgets
FishEye/Crucible/Subversion:
Viewing changesets
Creating code reviews
Confluence:
Creating a page
Bamboo:
Creating a build plan
Start administering Atlassian OnDemand
Getting started with JIRA OnDemand
Getting started with Bamboo OnDemand
Getting started with Confluence OnDemand
Getting started with Confluence OnDemand only
Getting started with Source and Review Bundle
Personalisation
Creating your own dashboard
Managing your profile
Overview
Atlassian OnDemand (AOD) is a collaboration platform for software development teams of any size. This platform is a set of Atlassian
applications integrated as a service. Choose the full suite or pick a subset of it, and as the business processes and requirements change,
you can add or reduce applications as needed with your my.atlassian.com account.
Atlassian OnDemand applications
The Atlassian OnDemand applications are based on downloadable versions of Atlassian products.
JIRA OnDemand — to manage projects and track issues. Based on JIRA.
Confluence OnDemand — to share information among the team, for example creating documents, sharing and discussing ideas,
specs, mockups, and diagrams. Based on Confluence.
Source and Review Bundle — to search, view and review code. Based on FishEye and Crucible. The bundle includes the
integrated Subversion (SVN) as well.
Bamboo OnDemand — to build and deploy software. Based on Bamboo. Bamboo OnDemand runs builds on elastic agents using
Elastic Bamboo, and Elastic Bamboo utilises computing resources from the Amazon Elastic Compute Cloud (EC2).
Add-Ons
GreenHopper: to manage JIRA projects in the agile way. More on GreenHopper
5
Atlassian OnDemand October 2011 Documentation
Balsamiq: to create and edit UI mockups in JIRA issues or Confluence pages. More on Balsamiq
Gliffy: to create online diagrams such as flow charts and organisation charts in Confluence pages. More on Gliffy.
Team Calendars: to manage team leaves and mark project milestones and events, and display them in Confluence pages.
People can subscribe to Confluence calendars in Outlook and iCal to keep up to date as well. More on Team Calendars.
Refer to the Choosing applications page to decide what applications to use and Atlassian OnDemand Plugin Policy for information about
available plugins.
The Application Versions page shows the current version running in OnDemand.
Atlassian OnDemand compared with downloadable Atlassian products
The hosted Atlassian OnDemand sites offer most of the functions available in the corresponding downloadable products, but some
differences exist as well due to the distinction between hosted environments and on-premises environments.
In the Atlassian OnDemand documentation, we might refer to the names of the Atlassian OnDemand applications in the short form, for
example, JIRA for JIRA OnDemand, and Confluence for Confluence OnDemand. In circumstances where a functionality is different between
OnDemand and the downloadable product, we will mark the relevant information as such accordingly.
Related topics
Getting started administering Atlassian OnDemand
Getting started using Atlassian OnDemand
Workspace
Default workspace
After logging in to Atlassian OnDemand for the first time, you will see a workspace similar to the following example, which uses the default
look and feel and layout. The navigation bar shows the enabled Atlassian OnDemand applications for your site. In this example, all Atlassian
OnDemand applications are enabled, that is JIRA, Confluence, FishEye, Crucible and Bamboo.
Figure 1: Default Atlassian OnDemand workspace
Control or
menu
6
Description
Atlassian OnDemand October 2011 Documentation
Project
drop-down
menu
This menu displays the project you are currently viewing. Use it to select a project to work on.
Tabs
The tabs are the area where you can switch between applications. You will only see the applications you have access to.
You might see a different set of tabs depending on how your administrator has set up the project.
Application
menus
The menus are context-sensitive and you will see different options depending on what application you are working with.
User
drop-down
menu
This menu displays your username (e.g. 'Joseph Smith'). Use it to access your own access your user profile and (if you
are an administrator) administration functions.
History
drop-down
menu
This menu displays up to twenty pages that you navigated.
Quick
Search
Build information (e.g. build plans, build results) is currently not searchable. Build information is available in the Builds
application, and is also captured in the History drop-down menu and the activity stream.
Customised workspace
Your workspace might look different from the default depending on:
your team's application selection
your administrator's setup for your site
what applications you can access
You can also create your own dashboard and customise the information displayed on it.
Figure 2: Customised workspace (Click to enlarge)
Choosing applications
Atlassian OnDemand comes in two flavours: the Confluence family and the JIRA family. Confluence and JIRA are the base products in the
two families respectively. Based on your business requirements, you can choose to run any of the following application combinations.
For example:
Use Confluence OnDemand for intranets, knowledge bases and documentation
Use JIRA OnDemand together with Source and Review Bundle if you need issue management and code review.
On top of these applications, you can enable add-ons for additional functionality. For instance if your team follow the agile methodology, add
GreenHopper on top of JIRA to manage your project in the agile way.
7
Atlassian OnDemand October 2011 Documentation
Family / Base
product
Application combinations
Included products
Confluence
Confluence OnDemand
Confluence only
Add-ons
Gliffy
Team
Calendars
JIRA OnDemand
JIRA
JIRA only
JIRA OnDemand + Confluence OnDemand
JIRA + Confluence
JIRA OnDemand + Source and Review Bundle
JIRA + FishEye/Crucible/SVN
JIRA OnDemand + Confluence OnDemand +
Source and Review Bundle
JIRA + Confluence +
FishEye/Crucible/SVN
JIRA OnDemand + Source and Review Bundle +
Bamboo OnDemand
JIRA + FishEye/Crucible/SVN +
Bamboo
The complete suite
JIRA + Confluence +
FishEye/Crucible/SVN + Bamboo
Bonfire
Gliffy
GreenHopper
Google Apps
Google Apps integration is available with the JIRA family.
How to add and remove applications
As your business requirements change, you can add or remove applications any time you need to. To add or remove applications, just
enable and disable them in your my.atlassian.com account, and the products will be automatically installed or uninstalled for your site. The
only exception to this rule is the expansion to multiple applications from Confluence OnDemand only. If you want to add other applications on
top of Confluence OnDemand, our support staff will complete the process for you.
How to add and remove user licenses
Atlassian OnDemand is licensed on a user basis for each application. When you sign up, you specify the number of user license you want to
purchase for an application, e.g. 500 users for Confluence and 50 users for JIRA. When the number of users that needs access to an
application changes, you can change your license accordingly.
For more information, see the Order FAQ on www.atlassian.com.
For information about licensing and application permissions, refer to the Managing permissions page.
Related topics
Restricted Functions in Atlassian OnDemand
Supported Browsers
Ordering FAQ on www.atlassian.com
Getting started administering Atlassian OnDemand
JIRA
Getting started with JIRA OnDemand
Source and Review Bundle
i.e. FishEye + Crucible + Subversion
Getting started with Source and Review Bundle
8
Atlassian OnDemand October 2011 Documentation
Confluence
Getting started with Confluence OnDemand
Getting started with Confluence OnDemand only
Bamboo
Getting started with Bamboo OnDemand
Where
The administration console is the central place for carrying out administration tasks and configuring your site. Log in as an administrator, click
the menu labelled with your user name in the header, and select Administration. The administration console appears with the General tab
active.
The administration console uses a tab layout for most of the service combinations except Confluence On Demand. Use the General tab for
the settings that apply across your site, and use the individual tab for applications for application-specific settings.
Screenshot: Administration console for a site that has the complete OnDemand suite (click to enlarge the image)
Related topics
Overview
Getting started using Atlassian OnDemand
Restricted Functions in Atlassian OnDemand
Getting started with JIRA OnDemand
This guide is intended for JIRA OnDemand administrators. The instructions on this page will help you get started using JIRA OnDemand
yourself, show you how to configure JIRA to let your team get involved and finally preview a few advanced features of JIRA OnDemand.
What is Atlassian OnDemand? Read the Overview page for a brief introduction.
Audience: Administrators
The administration consoles are different between the sites that have JIRA OnDemand only and those with multiple
applications.
See Administration console differences for more information and screenshots.
9
Atlassian OnDemand October 2011 Documentation
(optional) Step 1. Import existing data
If you have existing JIRA data, you can import it into your JIRA OnDemand site. Follow the instructions on the Importing Data page.
Congratulations! You have imported existing data into JIRA OnDemand. Next, try creating a JIRA project.
Step 2. Create a project
1. Log in as an administrator. Click your user name (top right corner) and then the Administration link. The administration console will
appear with the Projects page displayed.
2. Click Add Project. Enter the project details, as follows:
In the Name field, type a descriptive name for your project, typically two or three words, e.g. 'Online Banking'. You can
change the project name later.
In the Key field, type a prefix for issues in your project, typically three or four characters, e.g.'EBNK'. You cannot change the
key after the project is created.
In the Project Lead field, select the user to whom issues should be assigned by default. You can set this to yourself at this
stage and change the setting later.
3. Click the Add button.
For more information on creating projects, see Creating new projects.
When you create a project:
If Confluence is enabled, a wiki space for the project is automatically created.
If Source and Review Bundle is enabled, a Subversion source repository for the project is automatically created.
If Bamboo is enabled, a build project for the project is automatically created.
Congratulations! You have created a JIRA project. Try creating an issue and resolving it, or setting up project versions/components, or
customising the dashboard. Once you've tried out JIRA for yourself, get your team involved by creating some users.
Step 3. Create users
The process for adding users depends on whether you have Google Apps integration enabled for your OnDemand instance. When you
create new users, they are automatically added to the users group by default and can log in to your site.
Add OnDemand (non-Google Apps) users:
1. In the administration console, go to General > User Management > Users.
2. Click the Add User link, and fill out the fields on the displayed form.
Further instructions can be found here: Managing Users and Groups.
Add Google Apps users:
1. Google users are created in Google Apps. Log in to your Google domain as an administrator, and on the Google Apps toolbar, click
Organization & Users.
2. Create Google users as needed.
3. Anywhere in Atlassian OnDemand, type g + g to bring up the Administration Search box, and search for Google Management.
4. On the displayed page, locate the Start Synchronization button and click it to transfer the users from Google Apps to Atlassian
OnDemand.
5. Grant users with access to applications. Type g + g and search for Application Access (or General > User Management >
Application Access). Configure the desired access to Atlassian applications and click Update.
Further instructions can be found here: Managing users and groups for sites integrated with Google Apps.
Interested in Google Apps integration for your OnDemand instance? It's free!
See the Google Apps Integration FAQ for more information.
Congratulations! You have created new users. Next, try creating a custom workflow for your team to use.
Step 4. Customise a workflow
10
Atlassian OnDemand October 2011 Documentation
A JIRA workflow is the set of steps (or statuses) and transitions that an issue goes through during its lifecycle. A read-only default workflow is
pre-configured for JIRA. The instructions below will show you how to copy this workflow to create your own custom workflow.
1.
2.
3.
4.
In the administration console, go to Issues > Workflows.
Click Copy for the 'jira' default workflow.
Enter a name and description for the workflow and click Copy.
Click Design for your new workflow. The workflow designer will open. Try modifying your workflow, then saving your changes.
You have now created your own custom workflow. To use it with a project, you'll need to activate it. See Activating Workflow for further
instructions.
Congratulations! You have created created a custom workflow. Next, try modifying the permissions for your project.
Step 5. Configure security
You can configure JIRA by using different levels of security settings according to your business requirements. You can configure who can
access JIRA, and what they can do/see within JIRA. The instructions below will show you how to add a new group, and then give the group
the access to a project.
1.
2.
3.
4.
5.
Type g + g to bring up the Administration Search box, and search for Groups (or General > Groups).
At the bottom of the displayed page, add a new group.
Navigate to Issues > Projects in the administration console and click the project that you want to grant your group permission to.
In the People section, click View Project Roles.
Find the row for the 'Users' project role and click the groups. Enter the name of your group and click Update.
You have now given your new group the permission to access your project. For further information on configuring security, see the following
topics:
Managing permissions
Managing project visibility
Configure security (JIRA documentation)
Congratulations! You have now set up JIRA for use by your team. Try assigning issues to different people, or watching another person's
issue for updates, or restricting an issue to a group. Once you've gotten your team involved, try configuring some advanced features.
Next steps
Now that you've got JIRA OnDemand set up for your team, try out some of the advanced JIRA features. Extend the base JIRA functionality
via plugins, create links to and from other OnDemand applications and try transition issues via commit commands.
Managing plugins
Click here to expand...
JIRA OnDemand has pre-installed plugins that you can enable to extend the base JIRA functionality. Read our plugin policy for more
information. The instructions below describe how to enable one of the non-commercial plugins, the JIRA Suite Utilities plugin.
1. Type g + g and search for Plugins (or Issues > Plugins in the administration console).
2. Click the 'JIRA Suite Utilities' row in the 'User-installed Plugins' table.
3. Click 'Enable'.
You have now enabled a plugin. Check out some of the commercial plugins on offer, such as GreenHopper for agile project management
and Bonfire for agile testing. Once you've configured your add-ons, try creating links to other OnDemand applications.
Creating links to and from JIRA OnDemand
Click here to expand...
If you are using JIRA OnDemand with other OnDemand applications, you can create links to and from the other applications. The instructions
below will describe how to create a link to a wiki page from an issue.
1. Navigate to Confluence OnDemand and create a new page titled Feature Specification.
2. Navigate to JIRA OnDemand and create a new issue.
3. In the issue description, enter the following text:
[Feature Specification]
4.
11
Atlassian OnDemand October 2011 Documentation
4. Save your issue. The text 'Feature Specification' will be rendered as a link. Clicking the link will take you to your wiki page.
You have now created a link between your OnDemand applications. For more information on creating links, see Creating Links. Once you've
finished creating links, try configuring commit commands for JIRA.
Configuring commit commands
Click here to expand...
If you have the Source and Review Bundle, then you can configure commit commands for JIRA. This feature allows users to action JIRA
issues via commands in commit messages. The instructions below will show you how to use one of these commands.
1. Create an issue. Note down the issue key for the issue, e.g. EBNK-123.
2. Commit some code to your Subversion repository. In your commit message, include the following text:
EBNK-123 #comment This commit fixes this issue #resolve
where EBNK-123 is the issue key for your issue.
3. View your issue again. You'll notice that your issue is now resolved with the comment "This commit fixes this issue".
You have now resolved an issue via a commit message. For more information, see Using Smart Commits (FishEye documentation).
Congratulations! You have now set up some of the advanced features of JIRA OnDemand. For more information on JIRA OnDemand, see
the JIRA OnDemand documentation.
Getting started with Bamboo OnDemand
Using this guide, you will complete the required build configuration and be able to run a test build on one of your repositories.
Audience: Administrators
Before you begin
Bamboo OnDemand runs builds on elastic agents using Elastic Bamboo, and Elastic Bamboo utilises computing resources from the Amazon
Elastic Compute Cloud (EC2). You will be charged by Amazon for your EC2 compute usage. These charges are separate to your Atlassian
license cost and will be billed to your Amazon Web Services (AWS) account.
Make sure that you have at least one project. If not, refer to the steps in the Getting started with JIRA OnDemand page to create a
project. A project must exist before you can create a build plan.
Make sure that you have an AWS account. If you do not have one, register for one on the AWS registration page.
Upload your AWS private key file and certificate file by opening a support ticket and attaching the files to the support ticket. Our
support staff will configure the file location setting for you. You can't upload the files in Bamboo OnDemand at the moment.
More on Amazon EC2
For details on Amazon EC2 pricing, refer to the Amazon EC2 pricing page page.
You can track your EC2 usage on the AWS Account page.
Your Elastic Bamboo compute usage will not be distinguishable from your non-Bamboo EC2 compute usage in your
AWS billing.
(optional) Step 1. Import Subversion source code
If you use the integrated Subversion, import your existing source code by following these instructions.
Importing Unversioned Data into Subversion
Importing Versioned Data into Subversion
12
Atlassian OnDemand October 2011 Documentation
Congratulations! You have imported your existing source code. Next, try configuring Elastic Bamboo to run your builds.
Step 2. Configure Elastic Bamboo
1.
2.
3.
4.
5.
Log in as an administrator, and go to Administration > Builds > Elastic Bamboo. The 'Configuration Details' page will appear.
Read and accept the Atlassian Hosted Services Terms of Use. The 'Elastic Bamboo Configuration' page will refresh.
Click the Enable button to enable Elastic Bamboo. You will then see the fields to enter the Elastic Bamboo configuration details.
In the Configuration Details section, enter the AWS Access Key ID and AWS Secret Access Key.
In the Elastic Bamboo Global Settings section, modify the Maximum Number of Elastic Instance field to be 1. As a start, we will
create only 1 plan at this stage, and therefore one instance is enough. You can change this setting later as needed.
6. Leave all the other settings as default, and click the Save button.
Screenshot: Elastic Bamboo Configuration settings
Show me more about AWS Access Key ID and Secret Access key.
To upload the AWS private key file and certificate file, open a support ticket and attach the files to the support ticket.
Congratulations! You have enabled and configured Elastic Bamboo. Next, try starting an elastic instance.
Step 3. Start an elastic instance
1. In the Builds the administration console, click Elastic Bamboo > Instances. The 'Manage Elastic Instances' page will appear.
2. Click the 'Start New Elastic Instances' link. The 'Start New Elastic Instances' screen will appear.
In the 'Number of instances' field, enter 1 .
Leave the 'Elastic Image Configuration Name' field as 'Default'.
3. Click the 'Submit' button. The 'Manage Elastic Instances' page will appear, showing the startup process of your new instances.
default image: If the default image does not contain the capabilities that meet your build requirements, you can use an EBS
volume with the default image to extend the build resource.
Congratulations! You have started an elastic instance to run your build on. Next, try creating a plan for your build.
Step 4. Create a build plan
1.
2.
3.
4.
5.
6.
Go to Builds > Create Plan.
In the Plan Details section, select your project, enter the name and key for the plan.
In the Source Repository section, select the repository type and specify the repository URL.
Leave the Build Strategy settings as default for now.
In the Build Configuration section, specify the builder and other settings as needed.
Leave the rest of the settings as default and select the check box in the Enable this Plan section so that the build will start running
after the plan is created.
7. Click the Create button. You will see the new plan displayed in the 'All Projects' tab on the 'Builds' dashboard. A build will start
running and the progress is displayed along the process.
13
Atlassian OnDemand October 2011 Documentation
What are plans and what do the settings for a plan mean?
plans and the settings for a plan
Congratulations! You have created a build plan and run a build for it. Next, try configuring some of the advanced features of Bamboo
OnDemand.
Next steps
Grant permissions
Grant permissions to your users so that they can work with Bamboo: Granting Global Permissions to Users or Groups
Save costs
After your build completes, it is recommended that you shut down your elastic instances if the elastic instances are not in use. The reason is
that a large portion of the Elastic Bamboo cost is from the instance running time.
To shut down elastic instances:
1. Navigate to 'Administration' > 'Builds' > 'Elastic Bamboo' > 'Instances'
2. Click the 'Shut Down' link in the 'Operations' column, next to the instance that you wish to shut down. The 'Shut Down Instance'
screen will display.
3. Click the 'Confirm' button to shut down the elastic instance. The elastic instance that you have shut down will display a 'Shutting
down' status for a few minutes, before it shuts down and disappears from this screen.
Configure builds
The following topics contain instructions on how to configure a number of other settings for your build plans:
Configuring a Plan's Notifications
Configuring Concurrent Builds
Using Elastic Block Store (EBS) to improve the build time: Configuring Elastic Instances to use the EBS
Learn more
Can I use a custom Elastic Bamboo image?
If you are interested adopting the Continuous Integration (CI), the blog post Pipelining the build for fun and profit talks about how the
Atlassian JIRA developers use Bamboo to reduce the build time while practising CI.
Getting started with Confluence OnDemand
Use this guide if you are using OnDemand aplications in the JIRA family together with Confluence OnDemand. If your site uses Confluence
OnDemand only, refer to Getting started with Confluence OnDemand only instead. The instructions on this page will help you create a space
to share information, give your team access to the site via users and groups and permissions, and try some advanced features to
customise your site.
What is Atlassian OnDemand? Read the Overview page.
Audience: Administrators
14
Atlassian OnDemand October 2011 Documentation
On this page:
Step 1. Create a space
Step 2. Create users and groups
Step3. Set permissions
Next steps
Step 1. Create a space
Skip to the next step if you have already created a JIRA project. Otherwise, use the following instructions to create a space:
1. Click the Wiki tab to go to the Confluence dashboard and click the 'Add Space' link.
2. The 'Create Space' screen appears. Enter a space name and a short, unique space key.
3. Leave all the other settings as default, and click 'OK' to add your space to your site.
If you have created a JIRA project, a space for the project has been automatically created for you at the same time.
Congratulations! You have created a space for your team to share information. Try creating a page or a blog post. Once you have tried
creating content yourself, give your team access to the space by creating users and groups, and setting permissions.
Step 2. Create users and groups
The process for adding users depends on whether you have Google Apps integration enabled for your OnDemand instance. When you
create new users, they are automatically added to the users group by default and can log in to your site.
Add OnDemand (non-Google Apps) users:
1. In the administration console, go to 'General' > 'User Management' > 'Users'.
2. Click the 'Add User' link, and fill out the fields on the displayed form.
Further instructions on managing OnDemand users can be found here: Managing Users and Groups.
Add Google Apps users:
1. Google users are created in Google Apps. Log in to your Google domain as administrator, and on the Google Apps toolbar, click
Organization & Users.
2. Create Google users.
3. In the Atlassian OnDemand administration console, synchnronise the users from Google Apps to OnDemand. To do this, navigate to
General > Google Management, and click Start Synchronization.
4. Grant users with access to applications. Go to General > User Management > Application Access and configure the desired
access to Atlassian applications and click Update.
Further instructions on managing Google Apps users can be found here: Managing users and groups for sites integrated with Google
Apps.
If your site has multiple On Demand applications, user management is centralised in JIRA OnDemand. You configure
application-specific permissions in the individual applications.
Interested in Google Apps integration for your OnDemand instance? It's free!
See the Google Apps Integration FAQ for more information.
Congratulations! You have created new users and groups. Next, try setting permissions on the space.
Step3. Set permissions
You can control who can do what in spaces with global permissions and space permissions. For example, set which groups can create
spaces at the global level and specify which groups can remove pages at the space level.
To set permissions:
1. Log in as an administrator, and go to the 'Administration Console' by clicking your username > Administration.
2. Click Wiki. In the left-hand panel, click Permissions
3.
15
Atlassian OnDemand October 2011 Documentation
3. Click Global Permissions or Space Permissions as needed.
If you selected global permissions, click Edit Permissions to enable the editable mode, and set permissions as needed.
If you selected space permissions, click the Manage Permissions link to navigate to the settings page. Click Edit
Permissions, and then set permissions as needed.
4. Click Save All to save changes.
You can change permission settings at any time.
Global permissions apply to all spaces.
Space permissions apply to a specific space. More on space permissions.
Anonymous users do not contribute to the user number allocated by your license. Anonymous access is available only if
enabled for the entire Confluence site, i.e. enabled at the global permission level.
Congratulations! Your team can now access the site and spaces based on the permissions you've set up. Try adding comments to pages,
sharing content and watching changes. Once you've gotten your team involved, try configuring some advanced features.
Next steps
Now that you've gotten Confluence OnDemand set up for your team, try out some of the advanced Confluence features. Add your personal
touch by customising the site and space, import templates to standardise content format and extend Confluence's base functionality via
plugins.
Customising the look and feel
Click here to expand...
With themes, colour schemes and logos, you can adapt your site or specific spaces as needed.
1. In your space, go to Browse > Space Admin.
2. In the "Look and Feel" section, choose the option as needed and customise the settings.
Custom themes are not supported.
If you choose a non-default theme, when users navigate to a Confluence space with that theme applied from other applications, they will lose
the OnDemand context, that is they will not see the other tabs. Please ensure that your Confluence space has links back into the OnDemand
site.
Themes: screen layout. Themes can be applied at the site level or the space level.
Setting up templates
Click here to expand...
To get started, import the global templates that Confluence comes with and then customise them as needed.
1. Go to the Wiki tab of the 'Administration Console'.
2. In the left-hand panel, select Configuration > Import Templates. You will the list of default templates. To preview a template, click
the template name.
3. Select the templates you want to use and the space to import them into, and then click Import. The templates are imported.
4. Follow the instructions on the page to edit the templates as needed.
Templates: Confluence pages with predefined content.
Global templates are available in every space across the site.
Space templates are only available in the space in which they are defined.
Managing plugins
Click here to expand...
1. Go to Browse > Confluence Admin. The administration console appears.
2. Under the Configuration section of the left-hand panel, click Plugins. You will see a list of user-installed plugins.
3. Click the plugins to view their details. Then enable and disable them as needed.
You can not install or remove plugins in OnDemand.
Getting started with Confluence OnDemand only
16
Atlassian OnDemand October 2011 Documentation
If you site contains Confluence OnDemand only, use this guide to create a space for your team to start sharing information. If your site
contains more applications in addition to Confluence OnDemand, refer to Getting started with Confluence OnDemand.
You will also learn how to control the access to your site with the use of permissions and how to personalise your site to your style.
What is Atlassian OnDemand? Read the Overview page.
Audience: Administrators
On this page:
Step 1. Create a space
Step 2. Create users
Step 3. Set permissions
Next steps
Step 1. Create a space
1. Go to the Confluence dashboard by clicking the Dashboard link at the top left of your screen, and then click the Add Space link that
is below the welcome message.
2. The 'Create Space' screen appears. Enter a space name and a unique space key.
3. Leave all the other settings as default, and click OK to add the space to your site.
Your site comes with a Demonstration space that contains a tutorial. Use the tutorial to learn the basics of using Confluence,
such as using the Dashboard, creating spaces pages and publishing blog posts. You can find the Demonstration space on the
dashboard.
Congratulations! You have created a space for your team to share information. Try creating a page or a blog post. Once you have tried
creating content yourself, give your team access to the space by creating users and groups, and setting permissions.
Step 2. Create users
1.
2.
3.
4.
Log in as an administrator, and go to the Confluence 'Administration Console' by clicking Browse > Confluence Admin.
Under the Security section, select Manage Users. At the top of the page, click Add User.
Enter the user's details.
Send the username and password to your users.
Tip: If applicable, you can use one universal password for all users and ask the users to change the password after their first login.
Congratulations! You have created new users. Next, try setting permissions on the space and globally.
Step 3. Set permissions
You can control who can do what in your site and space with global permissions and space permissions respectively. For example, set which
17
Atlassian OnDemand October 2011 Documentation
groups can create spaces at the global level and specify which groups can remove pages at the space level.
To set global permissions:
1. Under the Security section of the administration console, click Global Permissions. The global permission page will appear.
2. Click Edit Permissions to enable the editable mode, and set permissions as needed. Click Save All to save changes.
To set space permissions:
1. In your space, click Browse > Space Admin at the top of the page. The space administration page appears.
2. Under the Security section in the left-hand panel, click Permissions.
3. Click Edit Permissions to enable the editable mode, and set the permissions as needed. Click Save All to save changes.
You can change permission settings at any time.
Global permissions apply to all spaces.
Space permissions apply to a specific space. More on space permissions.
Anonymous users do not contribute to the user number allocated by your license. Anonymous access is available only if
enabled for the entire Confluence site, i.e. enabled at the global permission level.
Congratulations! Your team can now access the site and spaces based on the permissions you've set up. Try adding comments to pages,
sharing content and watching changes. Once you've gotten your team involved, try configuring some advanced features.
Next steps
Now that you've gotten Confluence OnDemand set up for your team, try out some of the advanced Confluence features. Add your personal
touch by customising the site and space, import templates to standardise content creation and extend Confluence's base functionality via
plugins.
Customising the look and feel
Click here to expand...
With themes, colour schemes and logos, you can adapt your site or specific spaces as needed.
1. In your space, go to Browse > Space Admin.
2. In the "Look and Feel" section, choose the option as needed and customise the settings.
Themes: screen layout. Themes can be applied at the site level or the space level.
Custom themes are not supported.
Setting up templates
Click here to expand...
To get started, import the global templates that Confluence comes with and then customise them as needed.
1. Under the Configuration section, select Import Templates. You will the list of default templates. To preview a template, click the
template name.
2. Select the templates you want to use and the space to import them into, and then click Import. The templates are imported.
3. Follow the instructions on the page to edit the templates as needed.
Templates: Confluence pages with predefined content.
Global templates are available in every space across the site.
Space templates are only available in the space in which they are defined.
Managing plugins
Click here to expand...
1. Go to Browse > Confluence Admin. The administration console appears.
2. Under the Configuration section of the left-hand panel, click Plugins. You will see a list of user-installed plugins.
3. Click the plugins to view their details. Then enable and disable them as needed.
You cannot install your own plugins. See the plugin policy.
18
Atlassian OnDemand October 2011 Documentation
Getting started with Source and Review Bundle
For your team to start using the Source and Review Bundle, there is no additional required configuration on the part of administrators as long
a project has been created. Using this guide, you will learn the basics about managing source code repository permissions and review
permissions.
What is Atlassian OnDemand? Read the Overview page for a brief introduction.
Audience: Administrators
On this page:
(optional) Step 1. Create a project
(optional) Step 2. Import Subversion data
Step 3. Try browsing your repository
Step 4. Try creating a review
Next steps
(optional) Step 1. Create a project
Follow the instructions in the Getting started with JIRA OnDemand page to create a project. A Subversion source repository is created
automatically when a project is being created, and then your team can start browsing the source code with FishEye or reviewing the source
code by using Crucible for the project.
(optional) Step 2. Import Subversion data
If you have existing Subversion data, use the following instructions to import the data.
Import SVN source code
Importing Unversioned Data into Subversion
Importing Versioned Data into Subversion
Congratulations! After the SVN data is imported, there is no further configuration required. You and your team can now start using the
Source and Review Bundle.
Step 3. Try browsing your repository
1. Log in as a administrator or user and select your project.
2. Navigate to 'Source' > 'Browse'. Your repository will be shown in the 'Repositories' tab.
3. Click the repository to view it. You can navigate around your repository via the navigation tree on the left. For more information on
browsing your code, see Browsing through a Repository.
4. You also can check out the code by using the command shown on the page. It will look something like the command below:
svn checkout https://myinstance.com/svn/MYPROJECT/trunk MYPROJECT --username myusername
Congratulations! You have browsed your repository. Try using the search and viewing a file. Once you have explored your repository, try
creating a review.
Step 4. Try creating a review
1. Log in as a administrator or user and select your project.
2.
19
Atlassian OnDemand October 2011 Documentation
2. Navigate to 'Reviews' > 'Create new review'. The create review wizard will open.
3. Add content to your review. For example, you may browse and add a changeset.
4. Click 'Start review' to create the review.
Congratulations! You have created a review. Try adding reviewers, selecting more files for review and performing the review. Once you
have created and performed a review, try some advanced features.
Next steps
Controlling access to source code and reviews
Click here to expand...
If you plan to create multiple projects, you might want to apply access control to the source code and reviews on a project basis. Set the read
permission and commit permission for a project's source code at the group level in FishEye, and then Crucible will inherit the same
permissions for the reviews in the project.
Set the default permissions for all new projects
Set the permissions for a particular project: Project-specific permissions overwrite the default permissions.
Manage anonymous access to your repository
Trying advanced configurations
Click here to expand...
The following advanced configuration settings can extend the base FishEye/Crucible/Subversion functionality to help your team work with
code more efficiently.
Configure commits to require a JIRA issue key
Action issues via commit messages
Create a review for a changeset from the Source tab
Click here to expand...
1. In the header, select a project from the project drop-down menu and click the Source tab.
2. Click Activity to open the source-related activity stream, and then click the Commits button to display commits only.
3. Hover your mouse over any commit activity. You will see a cog icon displayed at the right end of it. Click the cog and then select
Create Review. Follow the instructions to complete the review setting.
Screenshot: Creating a review from the Source tab
Getting started using Atlassian OnDemand
The information on this page will help you get started using Atlassian OnDemand. Depending on what applications you have access to, you
can get started by trying out the functionality in the relevant sections below.
On this page:
JIRA
Confluence
FishEye/Crucible/Subversion
Bamboo
JIRA
20
Atlassian OnDemand October 2011 Documentation
Create an issue
Add gadgets to view the information that you need on the dashboard, e.g.:
The Assigned To Me Gadget
The Watched Issues Gadget
Search for issues and save the search criteria for future use:
Create filters (i.e. saved search criteria)
Show filter results on the dashboard: Adding the Filter Results Gadget
Manage agile projects: plan tasks and track progress (if you use GreenHopper)
Useful keyboard shortcuts in Issues
Action
Keyboard Shortcut
Create issue
'c'
Edit issue
'e'
Next issue
'j'
Previous issue
'k'
Assign issue
'a'
Comment on issue
'm'
See also:
JIRA Keyboard Shortcuts
More info: Working with Issues
Confluence
21
Atlassian OnDemand October 2011 Documentation
Create a page by going to the Wiki tab and using the Add button in the top right corner.
If your site has Gliffy, try adding a Gliffy diagram. It has a number of built-in templates to get you started.
If you use Balsamiq, try adding a UI mockup.
Attach documents to pages.
Watch pages so that changes are sent to your inbox. To do this:
Go to the Tools menu in the top right corner and click Watch.
More info: Working with the wiki
FishEye/Crucible/Subversion
View changesets by going to the Source tab. Browse and drill down to branches in the left navigation.
Create and participate in code reviews.
1. Go to the Review tab and click Create new review.
2. Set up the review by following the instructions.
View all the code changes committed against an issue by going to the Source tab of the issue in JIRA.
Check out Getting started with Source and Review Bundle
More info: Working with the Repository, Getting Started with Crucible and Working with source
Bamboo
22
Atlassian OnDemand October 2011 Documentation
Create a Plan
More info: Getting started with Bamboo OnDemand and working with builds
Getting started for evaluators
This page is a draft in progress and visible to atlassian-staff only.
After getting your Atlassian On Demand instance up and running, follow these essential steps to configure your site and start using it.
Want to sign up for free evaluation?
Go to link to WAC page.
test project --> create some issues --> customise workflow to match process
Importing data
import SVN data
integrate with external repos (GH, BB)
Create an account. (link to WAC FAQ)
Importing data
link to importing users
link to importing issues
Setting up accounts for team members
link to create users
Creating a project
(link to create projects)
call out the diff for agile ones
Create and assign an issue
link to create issues
assignment is taken care of during issue creation via the Assignee field
Checking in and checking out code
changes reflected in activity streams
Create Confluence pages
Useful for creating and sharing specs, UI mockups, digramming
reporting and graphs
Developer
Access my JIRA Studio Issues
I can tackle my task.
JIRA Studio/Issues
Developer
23
Atlassian OnDemand October 2011 Documentation
Commit some code
it can be reviewed and built.
Source (FE/CRU)
Lead Developer/Developer
Review the code
I know how the code has been written.
Review (FE/CRU)
Related topics
Create an Atlassian On Demand account (link to WAC FAQ)
Atlassian OnDemand
Administering Atlassian OnDemand
Administering Projects
Managing data
Managing Users and Groups
Administering your Account
Managing permissions
Configuring the look and feel
OnDemand Cookies
Using Atlassian OnDemand
Creating Links
Creating your own dashboard
Managing your profile
Working with Activities
Working with Google Apps Integration
Administering Atlassian OnDemand
There are two types of administrative tasks in Atlassian OnDemand.
Global settings that affect your whole site and all applications, e.g. managing user groups, creating projects, and configuring the look
and feel for your site.
Application-specific settings that apply for an application only.
Global settings
This section covers the global administration tasks in Atlassian OnDemand:
Administering Projects
Managing data
Managing Users and Groups
Administering your Account
24
Atlassian OnDemand October 2011 Documentation
Managing permissions
Configuring the look and feel
OnDemand Cookies
Application-specific administration
Please find the information on application-specific administration using the links below:
Administering Issues
Administering the Wiki
Administering Reviews
Administering Source
Administering Builds
Accessing the administration console
Administration tasks are carried out in the administration console. To access the menus you want to work with faster, type 'g' + 'g' from
anywhere in your Atlassian OnDemand site. This brings up the Administration Search box, in which you can search for menus.
Screenshot: Searching for permissions when viewing an issue
Administering Projects
Creating new projects
Deleting a project
Setting project permissions
Associating a JIRA project with multiple FishEye repositories
Associating a JIRA project with a Confluence space
Customising Application Tabs for your Project
Linking activities from bitbucket or GitHub to JIRA Issues
Configuring cross-application linking in JIRA OnDemand
Creating new projects
In Atlassian OnDemand, a project is like a container and includes the following objects if the corresponding application is available in your
site:
a JIRA project
a wiki space
a build project
a source repository
Audience: Administrators
25
Atlassian OnDemand October 2011 Documentation
Before you begin
To be able to create projects, you must have access to all available applications in your site. For information on how to set application
access, see Managing application access.
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.You will see the existing projects if any.
2. Click Add Project. The 'Add A New Project' page will appear.
3. In the Name field, type the name of the new project (e.g. 'Timesheet Mobile App'). The project name is displayed on the Dashboard.
You can change the project name at any time.
4. In the Key field, type the unique key for the new project (e.g. 'TS'). The key will be used as the prefix of this project's issue keys (e.g.
'TST-1'). You cannot change the project key later after the project is created.
5. In the Project Lead field, type the name of the user to be assigned as the project lead for the project.
6. Click the Add button to add the new project.
Result: Depending on what applications are available in your site, a JIRA project, a Confluence space, a Subversion repository, a FishEye
repository and a Bamboo project will be created automatically.
Next: After the project is created, you will see the global settings for the project and can continue to configure application-specific settings for
the project as needed. .
Screenshot: Adding a new project
Related topics
Managing application permissions
Getting started administering Atlassian OnDemand
Deleting a project
Deleting a project will delete the project from JIRA, Confluence, FishEye, Crucible, Bamboo and Subversion. Hence, the issues, wiki
documents, source files, changesets, code reviews, build plans and build results associated with the project will all be deleted.
The deletion of Bamboo data only applies if you are using Bamboo OnDemand. If you use your own hosted Bamboo instance with
Atlassian OnDemand, your Bamboo project will not be deleted.
Before you begin
To be able to delete projects, you must have access to all available applications in your site. Otherwise, you will not see the Delete option.
For information on how to set application access, see Managing application access.
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active. The 'Administration' page appears, listing all of the projects currently set
up in OnDemand.
2. Locate the project you want to delete. In the Operations column, click the Delete link. The 'Delete Atlassian OnDemand project'
page appears.
3. Click the Delete button to delete the project.
26
Atlassian OnDemand October 2011 Documentation
Result: The results of the project deletion are displayed, listing the status for each application as shown in the second screenshot below.
Notes:
The project key will be displayed for the Subversion repository rather than the project name, as the project key is the
primary identifier in Subversion.
FishEye and Crucible are treated as one application, hence if your FishEye repository is successfully deleted then your
Crucible reviews will also be deleted.
Screenshot 1: The Delete Project link
Screenshot 2: Delete Project Confirmation
Setting project permissions
Depending on how many applications your site has, your project could include multiple components, e.g. a JIRA project and a wiki space. In
order to set the permissions for a project, you will need to configure each component (i.e. application) separately.
The Managing project visibility page shows you how to configure your project with an example.
On the Managing application permissions page, you will find links to the documentation on those settings in each application.
Associating a JIRA project with multiple FishEye repositories
By default, a JIRA issue will display the changeset from Subversion in the Source tab if the commit message references the JIRA issue in
question and the source is committed within the same project.
If you have source code that is committed in repositories outside the project that you'd also like referenced, you can associate the
repositories with the project:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the list of projects, click the project you wish to modify, e.g. Online banking.
3. In the Settings section, locate FishEye Repository, and click the Select link. You will see the page where you can associate
repositories with the project.
4. In the FishEye repository key field, enter the repository key for the repository that you want displayed in issues' source tab.
5. Click Associate.
Associating a JIRA project with a Confluence space
If your Atlassian OnDemand site has JIRA and Confluence, you can associate JIRA projects and Confluence spaces easily.
27
Atlassian OnDemand October 2011 Documentation
On this page:
Associating a space with a JIRA project via General settings
Associating a space with a JIRA project via Wiki setting
Associating a space with a JIRA project via General settings
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the list of projects, click the project you wish to modify, e.g. Online banking.
3. In the Settings section, locate Confluence Space, and click the Select link.
4. Enter the Confluence space key you want to link with the project, and click Associate.
Associating a space with a JIRA project via Wiki setting
1. Go to a page in the space and choose Browse > Space Admin.
2. In the left-hand menu, click XML Export in the Application Links section.
3. Enter the JIRA project key you want to link with the Confluence space, and click Associate.
28
Atlassian OnDemand October 2011 Documentation
Customising Application Tabs for your Project
If your site has multiple applications, you can hide, display or move the application tabs. You can also add your own custom tabs to display
an external URL.
Audience: Administrators
On this page:
Configuring application tabs for your project
Adding an application tab to your project
Renaming default application tabs
Configuring application tabs for your project
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active. You will see the list of projects currently set up.
2. Click the name of the project that you want to customise. The global settings for the project will appear.
3. At the bottom of the Tabs section, click 'More'. The 'Tab Administration' page will display.
To hide or show an application tab, click the 'Hide' or 'Show' links in the 'Actions' column for the tab respectively.
To move an application tab, click the up ( ) and down ( ) arrows in the 'Actions' column for the tab.
To reset the display to the default tab configuration, click the 'Reset Default Tab Configuration' link. Note that this will
remove any custom tabs that you have added.
To edit the default tab configuration for all projects, click the 'Edit Default Tab Configuration' link. Read more about default
application tabs in Configuring Global and Default Application Tabs.
Adding an application tab to your project
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active. You will see the list of projects currently set up.
2. Click the name of the project that you want to customise. The global settings for the project will appear.
3. At the bottom of the Tabs section, click 'More'. The 'Tab Administration' page will display.
4. Click the 'Add Custom Tab' link, and then specify the tab name in the Display Name field and and the URL.
5. Click the Save button to add the tab.
29
Atlassian OnDemand October 2011 Documentation
Using an external URL for a tab
Please note that if you specify an URL for your home page which is external to your Atlassian OnDemand site (e.g.
http://www.youtube.com), the entire external page will be loaded without any OnDemand context when you click the 'Home'
tab. Please ensure that your external page has links back into OnDemand; otherwise the user will only be able to navigate
back by using the back button of their browser.
Renaming default application tabs
You cannot rename the default tabs in OnDemand. However, you can create custom tabs and point the custom tabs to specific applications'
URL, and then hide the default tabs.
To find out the URL of an application for your project, click the application in the header to go to that application and copy the URL from the
address bar.
Linking activities from bitbucket or GitHub to JIRA Issues
JIRA OnDemand includes a bitbucket & GitHub Connector plugin. This system plugin allows you to link bitbucket or GitHub repositories
(repos) with their corresponding JIRA project. You can use the connector to connect to public or private repositories. Once linked, the plugin
identifies DVCS commit messages that reference a specific JIRA issue key and records the commit in JIRA. The information appears in the
issue's Activity and Commits section. The plugin records the commit message, the list of changed files, and provides links to view the
change set.
JIRA requires that a connected repository provide a POST service. The POST service allows JIRA to hook into a source code commit and
obtain the proper data. You can enable this service through your hosted repository or you can enable this service through the bitbucket &
GitHub plugin on JIRA. If you want to enable the service through JIRA, you must provide JIRA with the username/password of a user with
administrative access to the repository.
On this page:
Prequisite for GitHub private repositories
Procedures
Example of how commit information appears in a project
Using with Force Sync operations to troubleshoot
Prequisite for GitHub private repositories
If you are planning on connecting to GitHub private repositories, you must configure OAuth settings for GitHub before connecting to your
repos. To configure the OAuth settings, do the following:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3. Open the Issues tab and click Source Control > GitHub OAuth Settings.
4. Follow the instructions on the page.
Procedures
To display a list of hosted projects linked to JIRA, open your JIRA instance in your browser and do the following:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3. Open the Issues tab and click Source Control > Bitbucket and and GitHub Repositories.
The Bulk Configure Repositories page appears. The page lists Existing Linked Repositories. Each repository entry includes the
repository URL and its corresponding project key.
To add a repository to this list, scroll down past the list to the blue form.
1. Click Choose project and select the JIRA project you want to link the repository to.
2. Enter the URL of the hosted repository.
JIRA uses the HTTPS protocol to connect to the repository.
3. Click the Add Repository button.
JIRA verifies it can connect to the repository.
4. If the repository you specified is private, JIRA prompts you for a valid username/password to connect to the repository.
5. Check Install postcommit service.
6. Then, depending on which hosting service you are using, do the following:
30
Atlassian OnDemand October 2011 Documentation
6.
For bitbucket repositories
For GitHub repositories
Enter the credentials of a repository administrator.
Click the Add Repository button.
The system informs prompts you to authorize the connection:
If you do not enable the postcommit service
at this point, you
must ensure that the service is enabled
through the
hosted service. For information on enabling
a post service on
bitbucket, see Setting Up the bitbucket
POST Service.
Click the Add Repository button.
Press Allow.
Your repository appears in the the Bulk Configure Repositories page.
Ensure your project users have the correct permissions
Project users must all have View Version Control permissions. Without the proper permissions, users can not see the
Bitbucket tab even on linked projects.
Automatic synchronisation
After you link a repository, JIRA automatically starts looking for commits that reference issue keys for the associated JIRA project. The
summary shows the sync results and errors if any. A synchronisation of commit data from the DVCS repository to JIRA can take some time.
As the synchronisation progresses, the commits appear in related issues.
Example of how commit information appears in a project
Commit code as follows, and you will see this commit in the activity section of the JIRA issue PONE-1.
hg commit -m "DVCS-2 add a README file to the project."
hg push
Screenshot: Bitbucket commits on the Activity tab of the DVCS-2 issue
31
Atlassian OnDemand October 2011 Documentation
Screenshot: Bitbucket commits on the Commits tab of the DVCS-2 issue
Using with Force Sync operations to troubleshoot
If you see inconsistencies between the displayed commits in JIRA and the actual activity in your repository, you should run a Force Sync
operation. The Force Sync operation compares the existing commit data in JIRA with that in the linked repository. The system restores any
missing commit data to JIRA. A forced synchronization does not affect the commits in hosted DVCS. You should run Force Sync operations
when:
There are missing commit activities in JIRA.
You haven't seen commits appearing in JIRA for a longer period of time than usual.
The hosted DVCS system is back online after an offline period and you want to retrieve the commit data immediately. Otherwise, you
must wait for service to send the data.
To run a Force Sync operation:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3.
32
Atlassian OnDemand October 2011 Documentation
3. Open the Issues tab and click Source Control > Bitbucket and and GitHub Repositories.
The Bulk Configure Repositories page appears. The page lists Existing Linked Repositories.
4. Locate the repository that you want to synchronise.
5. Click the Force Sync link.
A synchronisation starts. After the synchronisation is complete, a summary for the synchronisation displays under the repository
listing in JIRA.
Related topics
Setting Up the bitbucket POST Service
Post-Receive Hooks
Configuring cross-application linking in JIRA OnDemand
In order to create links in JIRA OnDemand to point to other applications, the fields where links are created must use the Wiki Style Renderer,
e.g. the Comment and Description fields of your project's JIRA issues.
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active..
2. Go to the JIRA project configuration page. To do this, click your project name, and in the Settings area, find the JIRA caption and
click Configure.
3. On the JIRA project configuration page, go to the Fields section.
4. Click your project's field configuration and configure the Renderers to be Wiki Style Renderer.
If the field configuration applies to multiple projects and you don't want other projects to be affected by the change, you can copy the
referenced Field Configuration Scheme and associate your project with the new field configuration before changing the settings.
Configuring renderes in JIRA OnDemand
Related topics
Creating Links
Configuring Renderers
Managing data
Atlassian OnDemand provides mechanisms for handling data outside of the application user interface. You may need to use these to import
data into OnDemand or provide us with large amounts of data for a support case.
Read more about managing data in the topics below:
Importing Data
Uploading Data via WebDAV
Importing Data
Use the information on this page to learn how to import data into Atlassian OnDemand.
Audience: Administrators
33
Atlassian OnDemand October 2011 Documentation
Importing data from issue trackers
You can import issue data into JIRA OnDemand from other issue trackers such as JIRA, JIRA Hosted or third-party issue
trackers (e.g. Bugzilla).
Importing Issues
The JIRA importer has been designed to overwrite the existing JIRA data in your Atlassian OnDemand service. Please be
aware that if you choose to import data after you have used JIRA OnDemand for a while, you will lose all the data input in the
interim.
Importing Confluence data
You can import content to Confluence OnDemand from both Confluence and other Confluence OnDemand instances.
Importing wiki data
Importing source code
If your Atlassian OnDemand site has the Source and Review Bundle, i.e. FishEye, Crucible and Subversion, you can import
your source code to Subversion in Atlassian OnDemand.
To import versioned Subversion data (preserving full history): see Import versioned data using the Subversion importer
.
If you have not previously used Subversion, you can import your content directly: see Import unversioned data.
Importing users
Import users
Related topics
Atlassian OnDemand Application Versions
Restricted Functions in Atlassian OnDemand
Importing Issues
With the JIRA Import Wizard, you can import issues into JIRA OnDemand from JIRA instances, JIRA Hosted instances or third-party issue
trackers such as Bugzilla.
On this page:
Before you begin
Procedure
1. Get the data
2. Import the data
After the import
Granting application access to new users
Setting permissions
Related topics
Figure 1: The import process for JIRA instances and third-party issue trackers
Figure 2: The import process for JIRA Hosted instances
34
Atlassian OnDemand October 2011 Documentation
Before you begin
The import process overwrites all the existing data and configuration in JIRA OnDemand and cross-application settings. For
example, issues and their attachments, and look and feel configuration.
Restrictions:
Character encoding — Atlassian OnDemand uses UTF-8 encoding. If your JIRA instance uses other character encoding
methods, you cannot import data to JIRA OnDemand.
JIRA versions — You cannot import issues from JIRA to JIRA OnDemand if your JIRA version is newer than the current
JIRA OnDemand version. For example, if JIRA OnDemand runs JIRA 4.4, then the import from JIRA 4.4.1 to JIRA
OnDemand will not work. If you use JIRA Hosted and its version is newer than JIRA OnDemand, importing data is not
possible and you will have to wait until JIRA OnDemand is upgraded to a version the same as or higher than your JIRA
Hosted version.
Third-party issue trackers only: If you do not have a local JIRA instance, download the same version or an earlier version of JIRA
from the JIRA Archive Downloads and obtain an evaluation license for it from my.atlassian.com.
Procedure
1. Get the data
1. Third-party issue trackers only: Import data from your existing third-party issue trackers to a local JIRA instance. Find the instructions
on the Migrating from Other Issue Trackers page.
2. Log in to Atlassian OnDemand as an administrator, and go to Administration > JIRA Import. The JIRA Import Wizard appears.
Read the prerequisites to view the supported formats for the data to be imported.
3. In your JIRA instance, create an XML backup of the issue data with the JIRA XML backup utility and then compress the attachments.
For instructions, refer to the Backing up data (JIRA documentation) page.
For JIRA Hosted users, skip the attachment compression step and proceed to the following step.
4. Optional: If you want to import avatars or logos, back them up as well. To do this, compress the /data/avatars and
/data/logos directories individually. Make sure that the /avatars and /logos directories are at the top level.
5. JIRA Hosted only: To obtain the XML backup you just created and the attachments, open an issue at https://support.atlassian.com in
the 'OnDemand' project and our support staff will provide you with the files.
Supported file formats for the backup data:
Issues: XML, Zip containing XML file (.zip), GZipped XML file (.xml.gz), BZip2 XML file (.xml.bz2)
Attachments, avatars and logos: .zip, .tar.gz/.tgz, .tar.bz2
2. Import the data
1. Upload the files to Atlassian OnDemand by using WebDAV.
2. Log in to Atlassian OnDemand as an administrator, and go to Administration > General > JIRA Import. The JIRA Import Wizard
appears.
3. Click the Next button and follow the instructions on the wizard to finish the import process.
The wizard checks URLs in the specified XML backup, and will let you choose whether or not to update URLs to point to the new
JIRA in Atlassian OnDemand.
The import process renames default JIRA group names to OnDemand groups as follows.
Original JIRA groups
OnDemand groups
jira-administrators
administrators
jira-developers
developers
jira-user
users
After the import
Granting application access to new users
35
Atlassian OnDemand October 2011 Documentation
The import process does not honour the default application access settings and does not give access to any applications to new users. You
must grant application access to these users for them to be able to log in.
For information on how to assign application access, see Managing application access.
Setting permissions
JIRA permissions
In your old JIRA instance, if you have made changes to the default 'JIRA Administrators' and 'JIRA Users' global permissions, for example
you added a group called managers to the 'JIRA Users' global permission, you must configure the JIRA global permission settings in
OnDemand after the import.
This is because the import process does not import the settings of the 'JIRA System Administrators', 'JIRA Administrators' and 'JIRA
Users' global permissions. The other global permission settings such as 'Browse Users' are imported.
'JIRA System Administrators': As Atlassian OnDemand is a hosted product, you do not have the JIRA System Administrators
permission. Hence, there is no configuration required for this permission.
JIRA Administrators' and 'JIRA Users' global permissions: configure these two permissions by adding groups and users to them
as needed.
Permissions for other applications
Application permissions are managed in each application individually. If your site has other OnDemand applications, e.g. Confluence or
Bamboo, refer to Managing application permissions for information on how to configure permission for these applications
Related topics
Wiki permissions
Source permissions
Build permissions
Managing Users and Groups
Importing wiki data
You can import content to Confluence OnDemand from both Confluence and other Confluence OnDemand instances. The import works at
the space level. If you want to import the entire content of a Confluence site into Confluence OnDemand, you can do it by importing the
spaces one at a time.
Audience: Administrators
On this page:
Before you begin
Importing Confluence spaces to Confluence OnDemand
1. Export space data from source Confluence instance
2. Import the data into Confluence OnDemand
Before you begin
Confluence versions — Confluence OnDemand can only import spaces that are exported from a Confluence instance of the same
major version. For example, if the current version of Confluence OnDemand is 4.1.3, only space exports from Confluence 4.1.x can
be imported. To find out the version of Confluence OnDemand, please refer to Atlassian OnDemand Application Versions.
Linking spaces to JIRA projects — If your OnDemand site also has JIRA, you can link a Confluence space to a JIRA project when
importing a space. This will change the space's key to match the key of the JIRA project, but will not modify the space's name. If
another space with the JIRA project key is already associated with the JIRA project, you can use one of the following methods to
work around the issue:
If you want to retain the existing space's content, import your space with its original key, i.e. without linking it to a JIRA
project, and then associate this space with the JIRA project after the import. For instructions, see Associating a JIRA project
with a Confluence space.
If you do not need the existing space's content any more, remove that space before the import. The space importer does not
overwrite an existing space.
Renaming spaces — Renaming Confluence spaces is not supported. Confluence spaces can be linked to JIRA projects as
described above, but they will not have matching names. Alternatively, spaces can be renamed using a locally installed evaluation
copy of Confluence and then imported. See the following instructions for renaming Confluence spaces: Copy Or Rename A Space
(Confluence documentation).
Importing personal spaces — It is a known issue that personal spaces will become global after being imported. The issue is being
tracked as JST-5760. Creating a new personal space and moving the imported content to it page by page is the only workaround at
this time.
36
Atlassian OnDemand October 2011 Documentation
Importing Confluence spaces to Confluence OnDemand
1. Export space data from source Confluence instance
Export the space you want to import as XML. To do this:
1. Log in to the source Confluence or Atlassian OnDemand site.
2. Navigate to any page in the space you wish to export and choose Browse > Space Admin.
3. Click on the Advanced tab.
4. In the left-hand menu, click XML Export. This will create a zipped archive of XML files and attachments.
For detailed instructions, please refer to Exporting Confluence Pages and Spaces to XML.
2. Import the data into Confluence OnDemand
1. If your exported archive is larger than 100 MB, upload the file to Atlassian OnDemand via WebDAV. For archives smaller than 100
MB, you do not have to use WebDAV to upload data.
2. Log in as an administrator to Atlassian OnDemand.
3. Go to the import screen to import the XML archive. To do this:
If your site only has Confluence OnDemand, go to Browse > Confluence Admin > Import spaces.
If you site has multiple OnDemand applications, go to (Your username) > Administration. Then click the Wiki tab, and in
the left-hand menu, click Configuration > Import Spaces.
4. Select the XML archive you want to import.
If you didn't upload the archive via WebDAV, specify your file by using the Choose File button.
If you uploaded the archive via WebDAV, click the file in the WebDAV Files field.
5. Optional: For sites with multiple OnDemand applications, specify the JIRA project you would like to link this space to.
6. Click the Import button to import your Confluence space.
This will not import user accounts. Please see Importing Users if you would like to do this.
Related topics
Importing Issues
Importing Users
Importing Users
If you have a list of users and groups that you'd like us to bulk populate, you may provide us with a user listing in CSV format. The examples
of the appropriate CSV format are available on the Crowd CSV Import page.
There are some OnDemand-specific groups to be aware of:
Users must be in the users group in order to log in (by default).
If you would like to specify application access, subject to your licence, you can include the following group memberships for users in
the CSV file as necessary:
_licensed-jira (for JIRA access)
_licensed-confluence (for Confluence access)
_licensed-fecru (for FishEye/Crucible access)
_licensed-bamboo (for Bamboo access)
To import users:
Upload the CSV files to us via WebDAV and submit a support request so that the support staff can import the users for you.
Automated Example with PostgreSQL
If you have a large instance with many users, you may want to generate the CSV data automatically. If you are using Postgres as your
database with JIRA or Confluence, you can generate the required CSV files with the following queries:
This assumes you do not have any external directories configured. If you do, you will probably need to refine the queries
further.
37
Atlassian OnDemand October 2011 Documentation
users.sql
copy (SELECT user_name AS username, first_name AS first, last_name AS last, email_address AS
mail, credential AS password_hash FROM cwd_user) to '/tmp/users.csv' csv header
group_memberships.sql
copy (SELECT DISTINCT child_name AS username, parent_name AS group FROM cwd_membership) to
'/tmp/group_memberships.csv' csv header;
These two queries will generate a users.csv and group_memberships.csv file in /tmp that can be sent to Support. You can read more
about Postgres's COPY command for more options.
The Import Process - What to expect?
Purpose
Create a page to guide users as they prepare for their imports.
These folks often feel that their jobs are on the line, and can get quite stressed if they don't know what we need from them
and what to expect from us in advance.
Let's hold their hands, and call out any potential complications in advance.
The better we can set their expectations here, the less time we'll have to spend with them on the phone reassuring them
that everything be okay, and the less likely they'll be upset when their import takes 7 hours. Initial upfront investment here
=> saves time and poor cSAT scores later.
What we're going to do:
1.
Create a private page
2.
Brainstorm topics to cover
Melanie
Jeff Curry
Azwandi
Maleko
Dylan Hansen
Anyone else?
3.
Fill in content
Fill in while brainstorming
Mel to follow up on remainder with experts
4.
Get approval from Douglas
5.
Publish page
Brainstorm
Can use Tim's experience as a motivator/persona inspiration: JST-21737
Some initial thoughts:
Be clear that while it may be as quick as an hour, it can take up to 8 hours. Plan for this accordingly, communicate with your team in
advance!
Try to schedule a time when the customer will be offline, or let them choose.
Identify what kind of interactions the support engineers will need with the customers during migration - can we cover any of that in
advance?
Outline steps the customer is going to need to take on their side.
Paint a picture of the process:
How to export
When to provide the exports, relative to the scheduled time slot
Will there be room in the WebDAV for their exports?
Do they need to be available during the import? If so, will it be via Skype or other?
"I've logged in, and ___ is wrong!"
How will they be notified when they're done?
What finishing touches will the customer and/or their users be expected to handle themselves?
Space templates?
Avatars?
38
Atlassian OnDemand October 2011 Documentation
Resetting passwords?
What are risk factors that may cause things to go awry?
Custom plugins
...
Crowd connected to LDAP
Anything we can be aware of up-front would be helpful in ensuring the support engineer will have the resources they need at
Go Time.
Draft Page Content
Importing Versioned Data into Subversion
You can import a full Subversion (SVN) repository from a dump file. Importing the full repository preserves all historical information, whereas
an svn import (see Importing Unversioned Data into Subversion) only stores the most recent state. Please note, the import process
described below will overwrite any existing Subversion data for all projects in your OnDemand repository. If you want to import Subversion
data for a single project, see this FAQ: How do I import Subversion data for a single project?.
On this page:
1. Creating an SVN dump file
2. Altering the structure of your Subversion repository
3. Testing the Integrity of the Dump File
4. Importing the SVN Dump File to Atlassian OnDemand
Troubleshooting
Related topics
1. Creating an SVN dump file
You can generate a Subversion dump file from the SVN host by using the svnadmin dump command, e.g.
$ svnadmin dump /path/to/svn/ > svn.dump
Ensure that the Subversion content in your dump file conforms to the Subversion layout used in OnDemand. Some functions in OnDemand
assume that the content follows the standard layout (e.g. project creation/deletion). Atlassian OnDemand does not provide enough control to
manage arbitrary mappings.
The standard Subversion layout in Atlassian OnDemand is described below:
Your OnDemand site has a single Subversion repository, at https://<account_name>.atlassian.net/svn/.
The convention is to have a top-level directory per project, whose name is the same as the project key. Please note, all Subversion
content in your dump file must be associated with a OnDemand project. If a project does not yet exist, you need to create it before
you import. See Adding New Projects for instructions.
For example, given two projects, "Plugins" (project key "PL") and "Plugins for Eclipse" (project "PLE"), Subversion may look
like this:
/
/PL
/PL/trunk
/PL/tags
/PL/branches
/PLE
/PLE/trunk
/PLE/tags
/PLE/branches
...
If your existing Subversion repository does not match this layout, you will need modify your repository or dump file as follows:
If you have projects that do not have corresponding top-level directories in your existing Subversion repository, create the top-level
directories in the repository. For example,
$ svn mkdir --parents -m "Created place-holder directories for MYPROJ project."
file:///path/to/svn/MYPROJ/{trunk,tags,branches}
If the directories in your existing Subversion repository do not match your project names, do one the following:
rename each top-level directory via Subversion, e.g. svn rename Plugins PL. However, only new commits made after
the rename will appear in Source application.
- OR alter the structure (including history) of the repository using Subversion tools (see below).
- OR -
39
Atlassian OnDemand October 2011 Documentation
work with our Premium Hosted Services Partner, or another partner, to get your repository into the format required by
Atlassian OnDemand prior to importing.
2. Altering the structure of your Subversion repository
If the structure of the Subversion content in your dump file does not conform to the Subversion layout used in OnDemand (described above),
you can alter it yourself.
First, export a subset of your repository while creating an SVN dump file using the svndumpfilter tool. In the following example, the resulting
dump file will only contain the data under the 'PL' top-level directory. This rewrites the history, so 'PLE' and other top-level directories will not
exist in this dump.
$ svnadmin dump /path/to/svn/ | svndumpfilter include --drop-empty-revs --renumber-revs PL/ >
PL.dump
Next, download the third-party Perl script: svn-dump-reloc. Run the script to rename directories through the entire repository history. For
example, to change all occurrences of the file/directory paths starting with 'Plugins/' to 'PL/' use the following command:
$ svnadmin dump /path/to/svn/ | svn-dump-reloc Plugins/ PL/ > svn.dump
3. Testing the Integrity of the Dump File
You must test the integrity of your SVN dump file, particularly if you have altered the structure of the repository. To do this, create a new,
blank repository and attempt to load the dump file into it. For example:
1. Create a test repository:
$ svnadmin create /tmp/test_repo
2. Load in the dump file using svnadmin load:
$ cat svn.dump | svnadmin load /tmp/test_repo
3. Verify the contents of your SVN repo by inspecting its directory hierarchy:
$ svn ls file:///tmp/test_repo/PL/trunk
You can also verify the history by checking the recent logs:
$ svn log -l5 file:///tmp/test_repo/
If the load completes without errors and the contents of the repository look as expected, you can proceed to the next step.
4. Importing the SVN Dump File to Atlassian OnDemand
Once you have created and verified your SVN dump file, follow the instructions below to import it into the Subversion repository of your
Atlassian OnDemand instance.
Procedure:
1. Log in to Atlassian OnDemand as an administrator.
2. Compress your Subversion dump file and upload it to the dump_files sub-directory in the WebDAV directory share. See Uploading
Data via WebDAV for instructions. To compress the dump file, you can use gzip or bzip2. The importer can import the zipped files.
3. Click your username, select 'Administration' from the dropdown. The administration console will be displayed.
4. In the Source tab, go to 'Import SVN Repository'.
5. The SVN dump files that you have uploaded to dump-files will be displayed. Click 'Import' next to the file you want to import. The
importer will make the following checks:
If you have an existing SVN repository that is not empty (i.e. it contains files apart from the base "skeleton" structure), you
will be asked to confirm whether you want to overwrite it.
40
5.
Atlassian OnDemand October 2011 Documentation
If you have users in the dump file that do not exist in OnDemand instance, you will be asked to confirm whether you still
want to do the import. You can still import your file, however, if you want to match all committers to users, you will need to
create the missing users before doing the import. Unmapped committers will remain in the SVN history, and will simply not
have a JIRA/FishEye user associated with them.
6. The importer will back up your existing OnDemand repository as a SVN dump file in your WebDAV dump-files sub-directory. The
import will then be completed.
7. If your import is successful, a confirmation message will be displayed.
8. Optional: You can delete the SVN dump files (the imported file or the backup of your old data) from your WebDAV directory after the
import.
Please note: your Subversion users will need to check out a new copy of Subversion content after your repository is moved to OnDemand.
See Working with the Repository for guidance.
Troubleshooting
The files in your existing OnDemand repository may be associated with entities like code reviews. If you overwrite these files on
import, you might experience errors when trying to access the files (e.g. via the code review). Raise a support request for assistance.
Related topics
How do I import Subversion data for a single project?
Importing Unversioned Data into Subversion
Importing Unversioned Data into Subversion
If you have not previously used Subversion, you can import your content directly into OnDemand's Subversion with the svn import
command in a Subversion Client. This command allows you to import a directory, which may contain further levels of directories and files,
into a Subversion repository. However, the svn import command will only import an unversioned tree of files into Subversion, that is e.g.
no history will be retained.
Access to the Subversion Administration Console is restricted, and as a result you will not be able to import full directories and history into
Subversion. If you would like to import data into your Subversion repository with the full history preserved, see Importing Versioned Data into
Subversion.
The domain name for sites created before Nov 8, 2011 is https://<account_name>.jira.com.
Please replace atlassian.net with jira.com as needed.
To import unversioned data into Subversion:
1. Open a Subversion console.
2. If you have already created your project in OnDemand, enter the following command to import your local directory into your project's
Subversion directory:
svn import <local_directory> https://<account_name>.atlassian.net/svn/<project_key>/trunk
where,
<local_directory> is the path to the directory that you wish to import into Subversion,
<account> is the account name that you provided at signup, and
<project_key> is the key that you defined for the project at project creation.
You can create directories in Subversion by using the svn create command. However, we strongly recommend that
you create your <project_key>/trunk by creating a project in the OnDemand application.
3. You will see a commit message on your console at the completion of a successful import (e.g. 'Committed revision 1').
4. Check that your files have been correctly imported by using the svn list command to display the files in your target directory. For
example, svn list https://<account_name>.atlassian.net/svn/<project_key>/trunk
If you now want to work with your imported files, check out a working version of the directory from Subversion first. Read more about working
with your Repository.
Uploading Data via WebDAV
Your Atlassian OnDemand instance includes a WebDAV (Web-based Distributed Authoring and Versioning) directory share, and you can use
this directory to send us large amounts of data related to your initial setup or a support case. The directory has a 4 GB limit. You must belong
to the administrators group.
Please note that this directory share is not intended to be used for general file storage. It is also different from the Confluence WebDAV
interface accessible at https://<account_name>.atlassian.net/wiki/plugins/servlet/confluence/default.
On this page:
41
Atlassian OnDemand October 2011 Documentation
Supported WebDAV clients
Accessing your WebDAV directory
Accessing your WebDAV directory in OS X
Accessing your WebDAV directory in Windows XP
Accessing your WebDAV directory in Windows Vista
Accessing your WebDAV directory in Linux
Accessing your WebDAV directory using a client
Troubleshooting
Audience: Administrators
The domain name for sites created before Nov 8, 2011 is https://<account_name>.jira.com.
Please replace atlassian.net with jira.com as needed.
Supported WebDAV clients
Depending on your operating system, you may need to install a client to access your web directory. Please refer to the matrix below for
details:
Operating
System
OnDemand WebDAV Directory compatibility
Recommended Alternative Clients
OS X
All versions of OS X should be compatible.
We highly recommend Transmit, if you don't want to
use the OS X WebDAV functionality. A free, open
source alternative is Cyberduck.
Windows
XP
Windows XP may not work with the WebDAV directory, as
compatibility is highly dependent on the service packs and
hotfixes that are installed.
The BitKinex WebDAV Client is a free time-limited DAV
client. Please note that this client has not been tested
thoroughly with the OnDemandWebDAV directory.
Windows
Vista
Windows Vista has a working redirector for DAV over HTTPS.
Please note that this has not been tested thoroughly with the
OnDemand WebDAV directory.
The BitKinex WebDAV Client is a free time-limited DAV
client. Please note that this client has not been tested
thoroughly with the OnDemand WebDAV directory.
Linux
Cadaver is known to work well.
Accessing your WebDAV directory
Google Marketplace Users: If you signed up for OnDemand via Google Marketplace, you should have been prompted to
provide a password for Subversion access the first time you logged into Atlassian OnDemand. Use that password to
access WebDAV, not your Google Apps password.
Accessing your WebDAV directory in OS X
1. Activate the Finder in OS X and select Connect to Server from the Go menu.
2. Enter the following URL:
https://<account_name>.atlassian.net/webdav where <account_name> is the account name that your administrator
provided at signup.
You must use https, not http.
3. You will be prompted for a username and password. Enter the username and password that you use to log into Atlassian
OnDemand.
If you have trouble using WebDAV through Finder, please try using an alternative WebDAV client.
Accessing your WebDAV directory in Windows XP
There are a number of ways to set up WebDAV access in Windows XP. The method below will allow you to access your WebDAV directory
from My Network Places.
1. Navigate to My Network Places and click Add a network place.
2.
42
Atlassian OnDemand October 2011 Documentation
2. The 'Add Network Place Wizard' will display. Click Next. A list of service providers will be displayed.
3. Select Choose another network location > Next.
4. You will be prompted to enter a URL in the 'Internet or network address' field on the next page. Enter the following URL and click
Next:
https://<account_name>.atlassian.net/webdav where <account_name> is the account name that your administrator
provided at signup.
You must use https, not http.
5. You will be prompted for a username and password. Enter the username and password that you use to log into Atlassian
OnDemand and click OK.
6. Enter a name that will used to reference the WebDAV directory on your computer.
7. Click Next > Finish.
Accessing your WebDAV directory in Windows Vista
This method is one of the ways to set up WebDAV access in Windows Vista.
1. Open My Computer and click Map Network Drive.
2. The 'Map Network Drive' screen will display. Click Connect to a Web site that you can use to store your documents and
pictures > Next.
3. Click Choose a custom network location > Next.
4. You will be prompted to enter a URL in the 'Internet or network address' field on the next page. Enter the following URL and click
Next:
https://<account_name>.atlassian.net/webdav where <account_name> is the account name that your administrator
provided at signup.
You must use https, not http.
5. You will be prompted for a username and password. Enter the username and password that you use to log into Atlassian
OnDemand and click OK.
If you are getting the following error message when trying to map the web folder, 'The folder you entered does not appear
to be valid', you may need to download and install the following Vista update — KB907306
Accessing your WebDAV directory in Linux
This method is one of the ways to set up WebDAV access in Linux.
1. Install a WebDAV client. For example, to install Cadaver on Debian/Ubuntu, run sudo apt-get install cadaver.
2. Connect to https://<account_name>.atlassian.net/webdav, using your Atlassian OnDemand username and password,
and use the putcommand to upload a file.
$ cadaver https://<account_name>.atlassian.net/webdav
Authentication required for WebDAV on server `*.atlassian.net':
Username: jsmith
Password:
dav:/webdav/> put .Wink
Uploading .Wink to `/webdav/.Wink':
Progress: [=============================>] 100.0% of 1933 bytes succeeded.
Accessing your WebDAV directory using a client
Please refer to the documentation for your client application for instructions on connecting to a WebDAV directory.
Please note:
The URL of the WebDAV directory is:
https://<account_name>.atlassian.net/webdav, where <account_name> is the account name that your administrator
provided at signup.
You must use https, not http.
The authentication credentials required to access the WebDAV directory are the username and password that you use to log into
Atlassian OnDemand.
Troubleshooting
Some users might have trouble logging in to WebDAV. The issue might be due to the following bug:
https://studio.atlassian.com/browse/JST-5660.
Managing Users and Groups
43
Atlassian OnDemand October 2011 Documentation
A user is the account for an individual who accesses your Atlassian OnDemand site.
If multiple users in your orgnisation share the same application permissions, you can use groups for easier permission setup and
maintenance.
Audience: Administrators
If you have JIRA, or JIRA plus more:
For example JIRA + Confluence, or JIRA + Bamboo, user administration is centralised in JIRA, i.e. the Issues application.
Managing users and groups for sites with multiple OnDemand applications
If your site is integrated with Google Apps:
Most of the user management tasks are performed in JIRA.
Managing users and groups for sites integrated with Google Apps.
If you have Confluence only:
Users and groups are managed in Confluence.
Managing users and groups for Confluence OnDemand
Managing users and groups for sites with multiple OnDemand applications
For sites that use multiple Atlassian OnDemand applications, there are three aspects to consider in terms of user management:
Users
Application access
Application permissions
Users must be granted application access to a given application in order to be able to log in to a particular application. Once they log in to an
application, what they can see and do is determined by the permissions they have for that application.
Audience: Administrators
If your site has
Confluence OnDemand only, refer to Managing users and groups for Confluence OnDemand.
JIRA OnDemand only, refer to Managing users and groups for JIRA OnDemand.
44
Atlassian OnDemand October 2011 Documentation
A bit more about application access and application permissions
Application access controls if a user has access to a given application, i.e. the ability to log in. Application access is different from application
permissions in that application access is the first layer of security and only determines if a user has the license entitlement to an application.
application access manages licensing and authentication, i.e. which applications a user can log in. Access to a given application is
the prerequisite for a user to be able to use the application. Giving a user access to an application means that the user will count
towards that application's license.
application permissions manage authorisation, i.e. what actions users can perform within a particular application.
Managing users
For Atlassian OnDemand sites that have JIRA OnDemand and/or more OnDemand applications, all the user-related administration tasks
such as creating and deleting users and resetting user passwords are managed centrally in JIRA.
The only exception is creating Google users for sites that are integrated with Google Apps, which needs to be done in Google Apps.
Audience: Administrators
If your site has
JIRA OnDemand only: refer to Managing users and groups for JIRA OnDemand.
Confluence OnDemand only: Managing users and groups for Confluence OnDemand.
Adding a new user and granting application access
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Users. Then in the top right area of the page, click Add User. The 'Create New
User' page appears.
3. Enter the details for the new user, for example:
Username: jsmith
Password and Confirm Password: 1234
Full Name: Joseph Smith
Email: jsmith@example.com
4. To send the username and password to the user automatically in an email after the account is created, select the Send Notification
Email check box.
After receiving the email, the user can follow the link in the email to set their password. The link is valid for 24 hours.
5. If you plan to use the default groups of OnDemand and the new user needs to work on issues, e.g. editing issues, select the Add to
developers group check box.
6. Grant the required application access to your user by selecting the check box under each application.
Note that a user must have access to all applications to be able to create projects.
7. Click the Create button.
When users are created, they are automatically added to any groups that are granted with the JIRA Users global permission. The
default group that has this global permission is the users group.
When you set application access for a new user in step 6, access to certain applications might be already selected for you. What
applications are selected at this stage is set by the default application access.
If your site is integrated with Google Apps, use these instructions to create non-Google users, i.e. external users.
The only difference is step 2: instead of the Add User control, you will see Add External (non-Google) user.
Related topics
Managing groups
Managing application permissions
Managing application access: Learn how to set default application access.
Default groups and permissions
external user
Managing groups
45
Atlassian OnDemand October 2011 Documentation
When multiple users in your site need the same application permissions, you can add them to a group for easier permission setup.
When users are created, they are automatically added to any groups that are granted with the 'JIRA Users' global permission. The default
group that has this global permission is the 'users' group.
Audience: Administrators
If your site has Confluence OnDemand only, refer to Managing groups in Confluence OnDemand.
Adding groups
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Groups. The 'Groups' administration page appears.
3. Locate the Add Group caption. In the Name field, enter the new group name and click the Add Group button. The group is added.
Editing group membership
1. On the 'Groups' administration page, you can edit group members by clicking the Edit Members link.
2. Specify user names in the Leave or Join column and click the corresponding button.
Related topics
Managing application permissions
Default groups and permissions in Atlassian OnDemand
Managing application access
Application access controls what applications users can log in.
You can configure application access for a user when creating the user account.
You can switch on and off applications for existing users.
You can also grant application access to multiple users at the same time.
Application access is for license management and giving a user access to an application counts towards that application's license.
For an overview of user management, see Managing users and groups for sites with multiple OnDemand applications.
Audience: Administrators
On this page:
Setting default applications for new users
Granting application access to a new user
Viewing a user's application access
Granting and revoking application access for an existing user
Granting application access to multiple users
Setting default applications for new users
By setting default applications for your Atlassian OnDemand site, when new users are created, they are granted access to these applications
automatically. If your site is integrated with Google Apps, access to the default applications will be granted to Google users at their initial
login.
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Default Application Access. The 'Set Default Application Access' page appears.
3. Use the check boxes under the applications to set default applications, and then click the Save button.
Granting application access to a new user
When creating a user, you can specify what applications the user can access in the administration console.
For detailed instructions, see the Managing users page.
46
Atlassian OnDemand October 2011 Documentation
Viewing a user's application access
To view the applications a user has access to, the easiest way is through the Application Access page.
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Application Access. The 'Application Access' page appears.
3. Locate the user. To do this, enter the full username (e.g. kwatson) or part of it (e.g. kt) in the search box and then click the Search
button. The user will be displayed and you will see the application access settings for the user.
Granting and revoking application access for an existing user
You can grant access to or revoke access from a user as needed in either one of the following places:
The Application Access page
The User Details page in Users administration page
Procedure via the Application Access page:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Application Access. The 'Application Access' page appears.
3. Locate the user. To do this, enter the full username (e.g. kwatson) or part of it (e.g. kt) in the search box and then click the Search
button. The user will be displayed.
4. Use the check boxes under the applications to change the user's application access, and then click the Update button to save
changes.
Procedure via the User Details page:
1.
2.
3.
4.
On the General tab of the administration console, click User Management > Users.
Search for the the user with the filter, and then click the username to display the User Details page.
Find the Applications item and click the pencil icon next to it. The application access settings become editable.
Edit the check boxes as needed and then click the Done button to save the changes.
To remove a user's access to Subversion, you have to remove that user's FishEye/Crucible access. The removal of FishEye/Crucible
access happens immediately, but the removal of Subversion access might need a few minutes to take effect.
Granting application access to multiple users
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click User Management > Bulk Add Application Access.
3. Select the check box under the application for which you want to grant access.
4. In the user entry box, enter the usernames and separate them by commas, or click the Users icon to search for users.
5. After usernames are entered, click the Submit button to save the changes.
Managing application permissions
Application permissions control what users can do and what data they can see within a particular application. Each application's permissions
are configured separately and define the level of access to a given application only.
Audience: Administrators
The permission for logging in
For Atlassian OnDemand sites that have multiple applications, users are centrally managed in JIRA. To be able to log in, a user must have
the 'JIRA Users' global permission or belong to groups that have this permission. Even for users that only need to access Confluence, they
still need the 'JIRA Users' global permission; otherwise, they cannot log in to Confluence.
JIRA permissions - Issues
Configuring Security (JIRA documentation) – the information covers the various aspects of security within JIRA.
Note that the information on system administrators does not apply to Atlassian OnDemand.
Confluence permissions - Wiki
Global permissions (Confluence documentation)
Atlassian OnDemand.
47
Note that the information on system administrators does not apply to
Atlassian OnDemand October 2011 Documentation
Configuring default space permissions
Space Administrators and their Permissions (Confluence documentation)
Subversion, FishEye and Crucible permissions - Source and Reviews
Configuring repository permissions
Bamboo permissions - Builds
Grant global permissions
Configure a plan's permissions
Related topics
Managing application access
Managing anonymous access
You can enable and disable anonymous access to your Atlassian OnDemand applications individually as needed. Anonymous access is
managed via permissions in each application as described follows.
Anonymous users do not count towards your license.
On this page:
Enabling anonymous access in JIRA
Enabling anonymous access in Confluence
Enabling anonymous access in Subversion
Enabling anonymous access in Bamboo
Audience: Administrators
Enabling anonymous access in JIRA
To allow anonymous users to access a JIRA project, grant the 'Browse Projects' permission to 'Anyone' in the permission scheme that is
associated with the project.
Procedure:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Go to the Issues tab. In the left-hand menu, go to Misc. Schemes > Permission Schemes. The existing permission schemes are
displayed.
3. Click the permission scheme that is associated with the project. The 'Edit Permissions' page appears.
4. Locate the Browse Projects permission, click the Add link in the Operations' column.The 'Add Permission' page appears.
5. Select Group > Anyone, and click the Add button. The permission scheme is updated and the associated JIRA project now allows
anonymous access.
For detailed information on changing project permissions in JIRA, refer to Managing Project Permissions (JIRA documentation).
Screenshot: Enabling anonymous access in JIRA
48
Atlassian OnDemand October 2011 Documentation
Enabling anonymous access in Confluence
Procedure for sites with multiple applications:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Go to the Wiki tab, and then Permissions > Global Permissions. The settings for your wiki will appear.
3. Click any Edit Permission button and change the Anonymous Access setting to allow anonymous access to your project's wiki.
Procedure for sites with Confluence only:
1. Log in as an administrator, and go to the Confluence 'Administration Console' by clicking Browse > Confluence Admin.
2. Under the Security section, select Global Permissions. The settings for your wiki will appear.
3. Click any Edit Permission button and change the Anonymous Access setting to allow anonymous access to your project's wiki.
Enabling anonymous access in Subversion
Anonymous access to your project repository is disabled by default. For instructions, see Enabling Anonymous Access to a Repository.
Enabling anonymous access in Bamboo
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Builds tab. The 'Builds' administration options will display.
3. In the left-hand menu, go to Security > Global Permissions.
4. Click the Edit Global Permissions button. The 'Global Permissions' page will become editable.
5. In the second table, locate Anonymous users, and select the Access check box in that row.
6. Click the Save button.
Anonymous users will now be able to access your Bamboo system. However, they can only view plans and build results for plans where
the 'Access' plan permission has been granted to 'Anonymous users'.
Default groups and permissions in Atlassian OnDemand
If your site has JIRA OnDemand and/or more OnDemand applications, the following default groups are automatically set up when your
Atlassian OnDemand site is created.
By default, new users will be added to the 'users' group. This is because the 'users' group is the only default group with the 'JIRA Users'
global permission. If you have other groups that also have this global permission, new users are added to these groups automatically as well.
49
Atlassian OnDemand October 2011 Documentation
Audience: Administrators
If your site has Confluence OnDemand only, refer to Default groups in Confluence OnDemand.
Table : Default groups in Atlassian OnDemand
Groups in sites with
JIRA
Default permissions in applications
users
This group contains every user in your site.
JIRA:
the 'JIRA Users' and 'Bulk Change' global permissions. 'JIRA Users' allows users to log in
to Atlassian OnDemand, and and 'Bulk Change' allows users to bulk edit issues.
a member of the 'Users' project role, which allows members to see all project issues
(unless protected by a security level) and create new issues.
Confluence:
the permission to create and view Confluence content for the project
Bamboo
non-administrator access
Subversion:
read only access
developers
This group typically contains people who perform work on issues.
JIRA:
the 'Browse Users', 'Create Shared Filter' and 'Manage Group Filter Subscriptions'
global permissions in JIRA.
a member of the 'Developers' project role, which allows members to edit, move, assign, be
assigned, link, work on, resolve and close issues.
Confluence:
the 'Personal Space' global permissions
Bamboo:
non-administrator access
Subversion:
read/write access
administrators
This group typically contains people who are administrators.
JIRA:
the 'JIRA Administrators' global permissions.
a member of the 'Administrators' project role, which allows members to edit project
versions and manage project content (delete issues, comments, manage watchers).
Confluence:
the 'Attach Files to User Profile', 'Personal Space', 'Create Space' and 'Confluence
Administrator' global permissions.
Bamboo:
administrator access and the permission to create plans
Subversion:
read/write access
confluence-administrators
Not for customer use.
system-administrators
Not for customer use.
Managing users and groups for sites integrated with Google Apps
For a site that is integrated with Google Apps, there are two types of users: Google Apps users and external users.
External users are essentially OnDemand users as they are created in OnDemand.
During synchronisation between Google Apps and OnDemand, only Google users are synchronised. Groups and group memberships are not
changed.
Audience: Administrators
external user
An external user is a user who does not have access to your company email domain, but who you allow to access your Atlassian
OnDemand site, for example. e.g. client, contact, or remote worker.
50
Atlassian OnDemand October 2011 Documentation
Tasks that need to be done in Google apps:
Create, delete, and rename Google Apps users
Reset passwords
Where:
Log in to your Google Apps domain as an administrator and go to 'Organization & Users' on the toolbar.
Tasks that need to be done in Atlassian OnDemand:
Manage allocation of users to groups
Manage how groups access functionality
Managing application access
Create, delete, and rename external (non-Google) users
How:
Managing users
Managing groups
Managing application access
Managing application permissions
Managing anonymous access
Default groups and permissions in Atlassian OnDemand
Related topics
Converting Google Apps Users to External Users
Managing Username Conflicts
Merging OnDemand and Google Apps user bases
Synchronising Atlassian OnDemand and Google Apps Users
Converting Google Apps Users to External Users
If you are using Atlassian OnDemand with Google Apps integration, there may be times when you need to convert one of your Google Apps
users to an external user. An example is when an employee becomes a contractor.
Procedure
1. In Atlassian OnDemand, note the groups that the user is assigned to. You can do this by accessing the User Management >Users
administration page, selecting the user and then writing down the groups listed under the Groups column.
2. In your Google domain, delete the user.
3. Synchronise your users between Atlassian OnDemand and Google.
This will disable the user you have removed from Google by removing the user from all groups with login permission.
4. Now you can manually re-enable the user as an external user by re-assigning the user to the groups from which the user account
was removed. To do this:
In Atlassian OnDemand administration console, go to User Management > Users.
Select the user and click the username.
In the user information screen which opens, click 'Edit Groups'.
In the 'Edit User Groups' screen, hold down the 'Ctrl' key, and then click to select the groups the user was originally
assigned to.
Click 'Join' to re-assign the user to these groups.
5. Note that as Atlassian OnDemand is unable to retrieve the password used in Google, the user's password will be randomised at this
point. You will need to either reset the user's password via the admin console or have the user reset it when logging in directly to
OnDemand by clicking 'Can't access your account?' on the form.
The user can now log in through the 'Log in directly' method as shown in the screenshot.
Next step: You should now update the user's email address in OnDemand to change it from your Google domain.
Screenshot : Logging in directly to OnDemand
Managing Username Conflicts
51
Atlassian OnDemand October 2011 Documentation
A username conflict is the situation where the same username exists in both your Atlassian OnDemand and Google Apps user bases but the
username is associated with different emails in the two sites.
When merging or synchronising your OnDemand and Google Apps user bases, the system will send the administrator an email if any
username conflict is detected.
The username for Google Apps users is the first part of the email address, i.e. the part before the @ sign. For example, jsmith is the
username for jsmith@gmail.com.
Solutions
If the conflicting usernames are for the same user, link the usernames. See the following section for instructions.
If the usernames are for different people, delete the username either in Google Apps or OnDemand and then create a new one as
you see fit.
Linking conflicting usernames
To manage username conflicts:
1. If you receive a system email advising of a username conflict, navigate to the Username Conflicts screen by:
either following the link in the email
or going to the administration console, and then clicking General tab > Username Conflicts.
2. In the Username Conflicts screen, use the Link operation to link conflicting usernames. The Confirm Link Usernames dialog
opens.
3. Click Yes to confirm the linking action. The Google Apps email will be copied and overwrites the OnDemand email.
Merging OnDemand and Google Apps user bases
This page guides you through the process of migrating a Google Apps user base into the Atlassian OnDemand user base. This is typically
done immediately after integrating Google Apps with Atlassian OnDemand.
Audience: Administrators
On this page:
Before you begin
Merging users
Using the CSV export to merge users
End user actions
Before you begin
When you integrate OnDemand with Google Apps, Atlassian OnDemand will automatically merge the user bases in Atlassian OnDemand
and Google Apps. To streamline the process, before you merge users from the two systems you should confirm that:
You have an administrator user whose username is identical in both Atlassian OnDemand and in Google Apps.
Each user has a username in both Atlassian OnDemand and Google Apps.
Each of these user names is identical.
Each of these users' email addresses is identical.
You are matching usernames and not email addresses, when matching Google usernames to Atlassian OnDemand. For example,
the Google username pictured in the following screenshot is 'george', not 'george@mydomain.com'.
52
Atlassian OnDemand October 2011 Documentation
Merging users
To merge your Atlassian OnDemand and Google Apps user bases:
1. After integrating OnDemand with Google Apps, when you first log in with your Atlassian OnDemand administrator username, the '
Setting up the user integration with your Google Apps Domain' screen will appear. This screen summarises your user bases
after migration. It is divided into four areas:
Screen
Area
Function
Existing
user(s)
to be
linked
Where existing Google Apps and Atlassian OnDemand users have different email addresses associated with their
user name, select 'Link' to confirm that these users can access Atlassian OnDemand with their Google Apps Log In.
External
user(s)
* These users do not have a Google Apps Log In and are identified in the system as 'external' to Google Apps users
* These users can not access Google Apps-specific functionality of the Google Apps Activity Bar, such as Google
Calendar, GMail, Google Docs, or Google Site.
* Under the Make External column, select Enable to provide these users with Atlassian OnDemand log in access.
* If some of these users are Google users but they yet haven't been created in your Google Apps Domain, you can
select the link: 'Export these users to your Google Apps domain' to download a CSV export file, which you can
then upload to your Google Apps Domain to create these users in bulk.
* If you encounter problems using the automatic user merging facility, you can choose to use the CSV export function
to help prepare your user base before fully migrating to Google Apps. The CSV export facility will also appear as an
option during the migration if the automatic merging process detects any problems when matching user names.
New
user(s)
These are any new users which you have added to your Google Apps account since integrating with Atlassian
OnDemand. They will be imported into Atlassian OnDemand.
Linked
user(s)
These are existing users which are already linked to a Google Apps account. Atlassian OnDemand will use their
details for 'first name', 'last name', and 'email address'.
2. Review the screen and determine if you need to either link any Google Apps and Atlassian OnDemand email addresses, or make
any users external:
To link email addresses, under Existing users(s) to be linked, select the 'Link' checkbox.
To make users external, under External user(s), select the 'Enable' checkbox.
3. Under the drop-down labelled with your log in name, select Administration. In the administration console, select the General tab,
then select Google Management.
4. Under Set default access level for new users, click to select the required access level — Developer, Collaborator, or No Access –
then click 'Save'
53
Atlassian OnDemand October 2011 Documentation
New Atlassian OnDemand users are automatically assigned the default application access at their initial login,
which is set up in Administration > General tab > User Management > Application Access.
If you don't want new users to count towards your license, you can:
clear the selection on the default application page
revoke the application access from a particular user
5. Under 'Synchronise Users', click 'Start Synchronisation' to immediately synchronise your Atlassian OnDemand and Google user
databases. Your migration and merging of user bases is now complete.
Using the CSV export to merge users
If any users cannot be matched exactly during your user base migration, these users will display in the External user(s) area of the Setting
up the user integration with your Google Apps Domain screen, along with the option to create a CSV export of your user database.
To merge your Atlassian OnDemand and Google Apps user bases using the CSV export:
1. On the Setting up the user integration with your Google Apps Domain screen, under External Users, click the 'Export these
users to your Google Apps domain' link.
2. Export your user database from Atlassian OnDemand by clicking 'Save'.
3. Delete any external users and inactive users from the CSV file.
4. For all remaining users in the CSV file modify the 'first name', 'last name' and 'password' as necessary. The username must remain
the same.
5. Re-import your user database into Google Apps by clicking through to the appropriate page in the Google Apps administrator pages
and uploading the CSV file. This will allow a smooth merging of the user databases, by creating Google Apps accounts for any
Atlassian OnDemand accounts that do not already have a corresponding Google Apps account. Once you're ready, click 'I have
received confirmation from Google that the import is complete'.
6. Now, go to the Atlassian OnDemand administrator screen, set the default access level for new users, and click 'Start
Synchronisation'. Your migration and merging of user bases is now complete.
End user actions
End users will need to carry out the following actions after the migration:
1. Log in to Atlassian OnDemand, using the password the administrator provides.
2. Create a new password when prompted.
Note that new Atlassian OnDemand users will be given the default application access at their initial login.
Managing Large User Bases with Google Apps Integration
Due to performance considerations, the upper limit of users Atlassian OnDemand synchronises with Google Apps at one time is 1,000.
On this page:
Migration of large user bases
Ongoing synchronisation of large user bases
Mitigation Strategies
Migration of large user bases
Where you migrate a large user base with over 1,000 users, OnDemand will synchronise your user base progressively. This means that the
system adds users after their initial login. Administrators cannot modify any user's access rights, i.e. application access, until the user has
logged in for the first time. When a user logs in for the first time, the equivalent OnDemand account will be created and the user will be
granted the default application access.
Ongoing synchronisation of large user bases
For subsequent synchronisations after the initial user base migration, OnDemand synchronises new and updated user records only.
If you have more than 1,000 new and updated user records, OnDemand will not perform user synchronisation even if you enabled it. Instead,
users will be added and updated upon authentication (that is, when they first log in).
Mitigation Strategies
If you have an urgent need to carry out actions on a large user base, we recommend getting in touch with Atlassian support. Our support
engineers will be happy to assist you with this process.
54
Atlassian OnDemand October 2011 Documentation
Synchronising Atlassian OnDemand and Google Apps Users
User data is regularly synchronised between Atlassian OnDemand and Google Apps. You can change the synchronisation settings as
needed at any time.
Enable and disable automatic user synchronisation
Specify the synchronisation interval
Synchronise your user data on an 'as required' basis
Audience: Administrators
Configuring synchronisation of user data with Google Apps
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click Google Management.
3. Configure the default application access for new users as needed. To edit the setting, click the Edit link. This takes you to the default
application access page.
4. Configure the default user groups as needed. To edit the setting, select one or more groups and click the Save button.
5. Select whether Google Apps user Synchronization is enabled, and how often your user data is synchronised, then click 'Save
Synchronization Settings'.
6. To start synchronising users, click Start Synchronization. An example system log from the most recent user data synchronisation is
shown below. You can also click 'Download full log' to download a text file of this synchronisation log.
You can configure these settings:
Setting
Description
Allowed
Values
Set Default Access
Level for New
Users
This sets the default access level for new users the first time they log in to OnDemand.
'No
Access'
Default User
Groups for New
Users
This sets the default group that new users are added to after their initial login.
'Users'
Google Apps User
Synchronization
This switches automatic synchronisation on or off.
'Enabled'
Default
'Enabled'
'Disabled'
Synchronization
Interval
Adjusts how often the synchronisation process runs.
Any
value in
minutes
60
minutes
Google Apps
Domain
This is a link to the administration interface on your Google Apps domain. Click this link
to visit your Google Apps Domain and manage users or Google-specific settings.
Cannot
be
changed
Link is
always
shown
Synchronize Users
Enables you to immediately synchronise user bases. You can also download the log as
a text file.
Managing users and groups for JIRA OnDemand
Managing users in sites that only use JIRA OnDemand is similar to downloadable JIRA. See the 'User and Group Management' section in
JIRA Administrator's Guide.
If site is integrated with Google Apps, create Google users in Google Apps. All other user-related administration is performed in JIRA.
Audience: Administrators
55
Atlassian OnDemand October 2011 Documentation
If your site has
multiple OnDemand applications, refer to Managing Users and Groups.
Confluence OnDemand only, refer to Managing users and groups for Confluence OnDemand
Managing users and groups for Confluence OnDemand
Learn how to manage users in sites that only use Confluence OnDemand.
Default groups in Confluence OnDemand
Adding users in Confluence OnDemand
Managing groups in Confluence OnDemand
Audience: Administrators
If your site has JIRA OnDemand and/or other OnDemand applications, refer to Managing Users and Groups.
Default groups in Confluence OnDemand
If your Atlassian OnDemand site has Confluence OnDemand only, the following groups are automatically configured when your site is
created.
All new users are added to the 'confluence-users' group.
Audience: Administrators
If your site has multiple OnDemand applications, refer to Default groups and permissions in Atlassian OnDemand.
Table : Default groups in Confluence OnDemand
Groups
Description
confluence-users
This group is the default group for all new users. Permissions you assign to this group will be assigned to all
newly signed-up users of Confluence.
administrators
This is a group of 'super-users' who can access the 'Administration Console' and perform site-wide
administration. Members of this group can also see all spaces in Confluence.
system-administrators
Not for customer use.
confluence-administrators
Not for customer use.
Related topics
Adding users in Confluence OnDemand
Managing groups in Confluence OnDemand
Adding users in Confluence OnDemand
If your site uses Confluence OnDemand only, create users by completing the following steps.
All new users are added to the 'confluence-users' group automatically.
Audience: Administrators
Procedure
To create users:
1. Log in as an administrator, and go to the Confluence 'Administration Console' by clicking Browse > Confluence Admin.
2.
56
Atlassian OnDemand October 2011 Documentation
2. Under the Security section, select Manage Users.
3. Click Add User at the top of the page.
4. Enter the user's details, for example:
Username: jwong
Full Name: James Wong
Password and Confirm Password: 1234
Email: jwong@example.com
5. Click the Create button to create the user.
6. Confluence does not send the username and password to a new user automatically, so you will need to send those details to your
users manually.
Tip: If applicable, you can use one universal password for all users and notify multiple users at once. You'll just need to ask them to
change their password at the first login.
Related topics
Managing groups in Confluence OnDemand
Default groups in Confluence OnDemand
Configuring Default Space Permissions
Managing groups in Confluence OnDemand
Groups are handy when multiple users have the same application permission settings. Instead of having to configure application permissions
for each user individually, you can configure permissions at the group level.
Audience: Administrators
Procedure
1. Create groups
1.
2.
3.
4.
5.
Log in as an administrator, and go to the Confluence 'Administration Console' by clicking Browse > Confluence Admin.
Under the Security section, select Manage Groups. You will see a list of default groups.
Click the Add Group link at the top of the page.
Enter a name for the group, for example: department managers.The group name must be in lower case.
Click Save. The group is created and you will see the list of all existing groups.
You are now ready to start adding users to the group.
2. Add members to groups
1. Click the group name you just created in the group list.
2. Click the Add Members link at the top of the page.
3. The Add Members page appears. Type in the usernames of the people you want to add to the group. You can also search for and
select users by clicking the
icon.
4. After you have added the required usernames, click the Add button to add the members to the group.
Next: After setting up users and groups, you can continue to configure permissions.
Related topics
Adding users in Confluence OnDemand
Default groups in Confluence OnDemand
Administering your Account
You can change a number of your OnDemand account settings.
The account settings described here are for your organisation's OnDemand account, not your personal user account.
Changing your OnDemand 'From' Email Header Format
Changing your Account Language
Requesting support
Changing your Account Name
Enabling Public Signup and CAPTCHA
Viewing your user count
Changing your Welcome Message
Integrating OnDemand with Google Apps
Changing your OnDemand 'From' Email Header Format
57
Atlassian OnDemand October 2011 Documentation
The 'From' header is the email address that outgoing mails will appear to have come from.
To change your OnDemand 'From' Email Header Format:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues administration console will display.
3. In the left-hand menu, click the General Configuration option. Your account settings will display.
4. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode.
5. Update the 'Email from:' field to your desired email header. This will set the format in notification emails. You can use the following
variables in your email header: ${fullname}, ${email}, ${email.hostname}
For example, setting the header format to:
${fullname} (JIRA)
would result in notification emails with headers like this one: From: Joesph Smith (JIRA) <jira@company.com>
Please note that this field only sets the 'From' Email Header, not the email address itself.
6. Click the Update button to change your account settings.
Changing your Account Language
Please note that although Internationalisation functionality is present in Atlassian OnDemand, only English language packs are available at
this point in time.
Screenshot: 'Changing your Account Language'
Requesting support
To create support requests on Atlassian OnDemand, please file issues in the OnDemand project at https://support.atlassian.com. If you do
not have an account yet, you need to create one.
When creating support requests, please provide as much detail as possible. This will help us resolve your issues faster.
You can view your issue's status at the site after you have submitted it. There may be a small delay while the support system processes
your request.
You can also ask questions at https://answers.atlassian.com/ to get help from the community.
Changing your Account Name
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues administration console will display.
3. In the left-hand menu, click the General Configuration option that displays below it. Your account settings will display (see
screenshot below).
4.
58
Atlassian OnDemand October 2011 Documentation
4. Click the Edit Configuration link at the bottom of the page. The page will display in editable mode.
5. Update the Application Title field as desired. You would typically set this to the name of your company or organisation.
6. Click the Update button to change your account settings.
Screenshot: Changing your Account Name
Enabling Public Signup and CAPTCHA
Public signup allows your site visitors to immediately create their own user accounts. If signup is not enabled, only administrators can create
new user accounts.
As with users created by administrators, new user accounts created via public signup are granted with the default application access and
added to the groups that have the JIRA Users global permission in the same way.
Audience: Administrators
To enable public signup and CAPTCHA:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues administration console will display.
3. In the left-menu, click the General Configuration option that displays below it. Your account settings will display (see screenshot
below).
4. Click the Edit Configuration link at the bottom of the page. The page will display in editable mode.
5. Update the signup mode to be public. To do this, update the Mode field to 'Public'. This will allow any users to sign up and then post
issues.
59
Atlassian OnDemand October 2011 Documentation
Please note, OnDemand is priced based on the number of users in your installation. Enabling public signup may
cause you to exceed your user limit.
6. To enable CAPTCHA (i.e. validation by image) on signup, set the CAPTCHA on signup field to ON.
7. Click the Update button to save your account settings.
Screenshot: Enabling Public Signup and CAPTCHA
Viewing your user count
You can find out how many user licenses remain unused easily in the administration console.
To view your remaining licenses:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, go to User Management > Application Access.
3. At the top of the page, you will see the OnDemand applications that your site has. Below each application, the number of remaining
user licenses is displayed.
Bamboo OnDemand has the unlimited license because it is licensed based on the number of elastic agents your site utilises instead of
the number of users.
Screenshot: Remaining user licenses for each application
To find out the number of licenses you ordered for the OnDemand applications, log in to your my.atlassian.com account.
60
Atlassian OnDemand October 2011 Documentation
Changing your Welcome Message
The welcome message appears in the Introduction gadget, overwriting the default text of the gadget . By default, users of your site can see
the welcome message both before they log in and on the default dashboard after logging in.
To display the welcome message to users before they log in, make sure that the default dashboard for your site contains the
Introduction gadget.
Audience: Administrators
To change your welcome message:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues administration console will display.
3. In the left-hand menu, click the General Configuration option. At the bottom of the the displayed page, click the Edit
Configuration link. The page will display in editable mode.
4. In the Setting section, find the Introduction field and update it to your desired welcome message.
You can use HTML in your welcome message, but it must be correctly formatted (e.g. ensure all HTML tags are
closed).
5. Click the Update button to change your account settings.
Related topics
Configuring the Default Dashboard (JIRA OnDemand)
Integrating OnDemand with Google Apps
Follow these instructions if you want to add Google Apps integration to your Atlassian OnDemand site.
Audience: Administrators
Before You Begin
Your Atlassian OnDemand site must have JIRA OnDemand to be able to integrated with Google Apps.
Ensure that you have an administrator user whose username is the same in both OnDemand and Google Apps.
When matching Google usernames to OnDemand, ensure that you are matching usernames and not email addresses. For example,
the Google username pictured in the following screenshot is 'george', not 'george@mydomain.com'.
Migrating to Google Apps
1. Adding Google Apps integration to your Atlassian OnDemand instance
To do this:
1. Go to the Google Apps Marketplace and add Atlassian OnDemand.
2. Enter your My Atlassian credentials in the order form that is displayed. You must use the same My Atlassian credentials that you
purchased Atlassian OnDemand with.
3. Choose to enable Google Apps when prompted. A support ticket for your migration will then be created, and our technical support
61
Atlassian OnDemand October 2011 Documentation
3.
staff will coordinate the migration with you. You will be notified when the migration is complete.
2. Enabling single sign-in if you are on Google Apps Premier Edition
If your Google Apps edition is premier, single sign-in is disabled for your domain because Google does not allow OpenID authentication by
default.This means that you and your users cannot log in to Atlassian OnDemand services with your Google account.
Regular Google Apps accounts work fine.
To enable OpenID authentication:
1.
2.
3.
4.
Log in to your Google Apps account as administrator.
Go to Advanced tools
In the Authentication section, click Federated Login using OpenID.
Select the Allow users to sign in to third party websites using OpenID check box .
Next: Merging OnDemand and Google Apps user bases
Managing permissions
Overview
There are two aspects to the permission management in Atlassian OnDemand.
Licensing and authentication via application access. Application access controls the applications that users can log in and is for
licensing purposes only. Giving a user access to an application means that the user will count towards that application's license.
Authorisation via application permissions. Application permissions control what users can do and what data they can see within a
particular application.
Audience: Administrators
Differences between application access and application permissions
Application access is for license management and does not restrict data or notifications for users. The data that users can see and the
notifications they receive are determined by the permissions granted at the application level.
To configure what applications a user can access, i.e. licenses:
Managing application access
For example, user Kate Watson (kwatson) is a business analyst and only uses JIRA and Confluence. Grant her access to
these two applications and then she will be able to start using them.
To configure what functions a user can use in applications:
Managing application permissions
For example, if you want to restrict user Kate Watson (kwatson) from creating spaces in Confluence, revoke the 'Create Space'
global permission from her and the groups she's in in Confluence.
62
Atlassian OnDemand October 2011 Documentation
Managing project visibility
In this example, you will see how to control who can access and work with your projects by setting up permissions.
In the default group and permission setup of Atlassian OnDemand, all users are added to the 'users' group and this group has the read
access to everything. The other two default groups, i.e. 'developers' and 'administrators' have varying permissions on top of that for the
'users' group.
Audience: Administrators
Default groups and permissions in Atlassian OnDemand
Default groups in Confluence OnDemand
If some users should not be able to see certain projects, then you need to:
1. Create groups for each separate set of users, e.g. a group for each company, or perhaps a group for each project.
2. Edit JIRA role memberships, Confluence space permissions and Subversion permissions to use the new groups instead of the
default groups.
For instance, say there are some contractors who should only be able to view project 'Timesheet Mobile App'. In this case it makes sense to
split users by company, e.g. by creating two new groups mycompany-users and contractors. Add the relevant users to these groups
(keeping all of them in the default users group too). Then redesign the permissions in each application:
JIRA — In JIRA, we want to make most projects visible only to mycompany-users, and one project visible to mycompany-users
and contractors. For every project listed in the administration section, click the project name, find the Project Roles section and
click "View members" and edit the "Users" role groups. Remove the users group and add either mycompany-users or
contractors as needed.
Confluence — In the Confluence application, i.e. the 'Wiki' tab (not in the administration console), go through the spaces one by
one. Click the "Browse" dropdown arrow, select "Space Admin", and then click "Permissions" to show the space permissions. You
will see the "users" group has view permissions. Grant the mycompany-users group the same permissions, then delete the users
group entry. For the 'Timesheet Mobile App' project, grant the contractors group view permissions.
Source — Manage your Subversion and FishEye permissions as described in Configuring repository permissions. Go through the
projects replacing instances of the users group with mycompany-users, and in the 'Timesheet Mobile App' project,
contractors.
Reviews — Project review permissions are inherited from Crucible's default permission schemes. However, they are modified
according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions
that apply to a project's source also apply to that project's reviews.
Bamboo — You cannot restrict the visibility of a Bamboo project; however, you can restrict permissions for individual plans in a
project. See Granting Plan Permissions to Users or Groups in the Bamboo documentation for further details.
It is important that you go through all projects, to replace the users group with a more specific group. The reason is that all users belong to
the users group, and any project visible to users will remain visible to everyone.
Note that newly created users, being only in the users group (the only group given the 'JIRA Users' JIRA global permission), will not be
able to see any projects until added to mycompany-users or contractors.
Notes on restricting visibility
New users are automatically added to groups that have the 'JIRA Users' global permission. By default, this is the users group. Hence, in
the example, you cannot simply add the contractors group to the 'JIRA Users' permission. The reason is that this setting would mean
that newly added contractors would be added to the users group (not desired, since users can see all content) and newly added
employees would be in the contractors group (also not desired, since they are not contractors).
Configuring the look and feel
You can change the appearance of your Atlassian OnDemand site by using the "Look and Feel" administration page. Refer to the following
information about how to configure the appearance for your OnDemand application combination.
Confluence only
For a Confluence OnDemand only site, you can customise the appearance both at the site level and at the space level.
Instructions: Customising Look and Feel Overview (Confluence documentation)
Restrictions: Note that you cannot customise the layout for Confluence OnDemand. See Restricted Functions in
Atlassian OnDemand for details.
63
Atlassian OnDemand October 2011 Documentation
JIRA only
Instructions: Customising the Look and Feel (JIRA documentation)
Restrictions: Note that you cannot customise the layout for Confluence OnDemand. See Restricted Functions in
Atlassian OnDemand for details.
Multiple OnDemand applications
Global customisation:
Changing the Logo
Configuring Global and Default Application Tabs
Editing the Date and Time Formats for 'Issues' (JIRA)
Editing the colour scheme
Application-specific:
Confluence: You can customise the appearance of Confluence spaces for which you are the space administrator.
Instructions Customising the Look and Feel (Confluence documentation)
Changing the Logo
You can use your own logo and favicon for your Atlassian OnDemand site. A favicon is also known as a shortcut or bookmark icon.
If your site has Confluence only
You can't use your own image as the favicon.
Before you begin
Not all browsers display all image types. To display a favicon, your image must be in an image format supported by your browser.
The Wikipedia list of browser support for images might help you select a proper image format.
The recommended height for the logo image is 48 pixels.
The favicon image must be a square image and the recommended size is 32 pixels for both the height and the width.
If the image size is different from the recommended size, Atlassian OnDemand scales your images to the recommended sizes
automatically.
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Look and Feel option in the left menu. The look and feel configuration page will display.
3. Click the Edit Configuration link at the bottom of the page. The logo and favicon configuration page will display.
4. Specify the images to be used as the logo and favicon.
To upload an image, click the Upload icon and browse to the image.
To use an existing image on the web, click the URL icon and enter the URL to the image.
5. Click the Update button to save the new image settings. Your logo will now appear on your site and the favicon will take effect as
well.
Screenshot: Changing the Logo
64
Atlassian OnDemand October 2011 Documentation
Configuring Global and Default Application Tabs
You can customise the application tabs for each of your projects. You can also configure the global tabs and default tabs for applications
tabs.
Global tabs are the tabs that are displayed when no project is selected.
Default tabs are the tabs that are displayed for projects which do not have a customised tab configuration. These tabs are assigned
to all new projects.
Audience: Administrators
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click the Tabs option.
3. Configure tabs under the 'Global tabs' section and the 'Project default tabs' section as needed.
Related topics
Customising Application Tabs for your Projec
Editing the Date and Time Formats for 'Issues' (JIRA)
You can customise the time and date formats used throughout JIRA on the 'Look and Feel' page.
Audience: Administrators
To change your date and time formats for 'Issues' (JIRA):
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Look and Feel option in the left-hand menu. The look and feel configuration page will display.
3. Click the Edit Configuration link at the bottom of the page. The page will display in editable mode.
4. In the Date/Time Formats section, update the values for each of the fields you wish to change.
5. Click the Update button at the bottom of the page to save your changes. For details and examples of date and time configuration,
refer to the Date/Time Formats page (JIRA documentation).
Please note, the date and time formats will apply to pages within 'Issues' (JIRA) only. They do not apply to the other applications, e.g.
'Wiki'.
Screenshot: Changing Date and Time Formats
65
Atlassian OnDemand October 2011 Documentation
Editing the colour scheme
You can change the colour scheme to suit your needs with the Look and Feel settings in the administration console. You can change the
colour of the header and menu (e.g. subheader) of the projects toolbar. The colour of headings and links in the 'Issues' application can be
customised as well.
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the left-hand menu, click Look and Feel. The look and feel configuration page will display.
3. At the bottom of the page, click the Edit Configuration link. The logo and favicon configuration page will display.
4. Click Customize Colours And Date to expand the look and feel configuration options.
5. In the Colourssection, update the colours for the page elements by using one of the following methods. To find out where the colour
options apply in a colour scheme, read the section below.
Specify the hexadecimal RGB colour codes.
Click on the square colour sample and selecting the colour in the new window.
6. Click the Update button at the bottom of the page to save your changes.
7. Refresh the page in the browser to see the changes.
Colour scheme elements
The JIRA documentation provides explanations for each of the colour scheme elements.
Please take note of the following Atlassian OnDemand-specific information when reading the JIRA documentation:
Header Separator Colour — This setting is currently not used in Atlassian OnDemand.
Drop-down arrow — Atlassian OnDemand only setting. The colour of the drop-down indicator on the menus in the header (e.g. a
light-coloured arrow for dark backgrounds or a dark-coloured arrow for light backgrounds):
The Link Colour, Link Archive Colour and Heading Colour elements only affect the appearance of pages within the 'Issues'
application, i.e. JIRA. They do not affect the other applications (e.g. 'Wiki').
OnDemand Cookies
OnDemand uses Seraph, an open source framework, for HTTP cookie authentication.
Authentication Cookies
The 'Remember Me' Cookie
Cookie Key and Value
Use of Cookie for Authentication
Life of 'Remember Me' Cookies
Other cookie usage
Authentication Cookies
66
Atlassian OnDemand October 2011 Documentation
OnDemand uses two cookies:
The JSESSIONID cookie is created by the application server and used for session tracking purposes.
The 'remember me' cookie, seraph.rememberme.cookie, is generated by OnDemand when the user
selects the Remember me checkbox on the login page.
You can read about cookies on the Wikipedia page.
The 'Remember Me' Cookie
The 'remember me' cookie is a long-lived HTTP cookie. This cookie can be used to authenticate an unauthenticated session. OnDemand
generates this cookie when the user selects the Remember me checkbox on the login page.
Cookie Key and Value
By default, the cookie key is studio.crowd.tokenkey
The cookie contains a unique identifier plus a securely-generated random string.
Use of Cookie for Authentication
When a user requests a web page, if the request is not already authenticated via session-based authentication or otherwise, OnDemand will
match the 'remember me' cookie (if present) against the token stored for the user in the OnDemand database (if present).
If the random string matches the value stored in the database and the cookie has not expired, the user is authenticated.
Life of 'Remember Me' Cookies
The life of the remember me cookies is 14 days. This is the system default value and is not configurable.
Other cookie usage
There are several cookies in OnDemand that are used for storing basic presentation states, such as the number of log lines to show, which
tab was previously selected etc. They are:
Cookie Key
Purpose
Cookie Contents
Expiry
atlassian.xsrf.token
Prevents XSRF attacks. Ensures that during a
user's session, browser requests sent to a
OnDemand server originated from that OnDemand
server instance. For more information about XSRF
checking by JIRA, see Form Token Checking on
the Atlassian Developers site.
Your OnDemand server's Server
ID, a securely-generated random
string (i.e. token) and a flag that
indicates whether or not the user
was logged in at the time the
token was generated.
At the
end of
every
session
or when
the
browser
is
closed.
studio.project.rec.used.cookie
Stores the most recently used projects. Used by
OnDemand to track recently viewed projects for the
user.
The project keys of all the recently
viewed projects. (seperated by
'-_-')
One
year
from the
date it is
set or
was last
updated.
AJS.conglomerate.cookie
Tracks which general tabs were last used or
expansion elements were last opened or closed.
One or more key-value strings
that indicate the states of your last
general tab views or expansion
elements.
One
year
from the
date it is
set or
was last
updated.
Using Atlassian OnDemand
Creating Links
Creating your own dashboard
Managing your profile
Working with Activities
Working with Google Apps Integration
Creating Links
67
Atlassian OnDemand October 2011 Documentation
You can create links to your issues, wiki, source and reviews. Once created, links enable you to quickly jump to related information.
For example, when developing a new feature, you may want to add links to the new source files in the original JIRA issue. Simply type the
source file name in a text field of the issue (e.g. the 'Description' or 'Comment' field) prefixed with source:. The link to the source file will
automatically be created upon saving your change.
Prerequisites:
To create links in JIRA OnDemand to point to other applications, your administrator must configure the renderer to be Wiki Style Renderer for
the fields you want to use the feature in. For instructions on how to do this, see Configuring cross-application linking in JIRA OnDemand.
How to create links
To link to
...
Type this
Examples
an issue
<Issue Key>
TEST-123
ACME-456
a wiki
page in
the same
project
[<Page Name>]
[My Draft Page]
a wiki
page in a
different
project
[<Space Key>:<Page Name>]
[TEST:My Draft Page]
a
changeset
revision:<Changeset Number>
revision:98765
rev:<Changeset Number>
rev:98765
r<Changeset Number>
r98765
source:<Filename> or
source:/<Filename>
source:pom.xm
a source
file
source:webapps/pom.xml
The difference between the two
formats is the slash */* before the
<Filename>. The slash */*
indicates that the <Filename> is
an absolute path and the link will
point to the file specified by the
path. Without the slash before
<Filename>, the <Filename>
is treated as a relative path and
instead of pointing to the
specified file, OnDemand
searches for the path within a
project.
source:/branches/webapps/pom.xml
source:src/main/java/com/atlassian/util/concurrent/BlockingReference.j
source:/trunk/src/main/java/com/atlassian/util/concurrent/BlockingRefe
When using relative paths, i.e.
without the slash, do not include
the 1st level directory in the
<Filename>, for example use
source:src/Foo.java instead
of
source:trunk/src/Foo.java
. The reason is that FishEye
indexes files without the 1st level
directory and including the 1st
level directory in relative paths
will lead to zero search results.
a review
<Review Key>
Screenshot: Creating Links in JIRA
68
CR-TEST-34567
Atlassian OnDemand October 2011 Documentation
Related topics
Configuring cross-application linking in JIRA OnDemand
Creating your own dashboard
The Dashboard is the first screen you see when you log in to Atlassian OnDemand. Each of OnDemand applications also contains a
dashboard. You can create your own dashboard and customise it to display the information that is most interesting to you.
If you are anywhere else in OnDemand, you can access your dashboards by clicking the site logo in the top left corner.
The information boxes on the dashboard are called Gadgets.
Procedure
To create a dashboard:
1. From the main screen, select the Dashboards > Manage Dashboards.
2. In the top right corner of the displayed 'Manage Dashboards' screen, select Create New Dashboard.
3. In the 'Create New Dashboard' screen, fill in the fields to create your dashboard.
You can then continue to customise your dashboard.
To customise your dashboard:
Choose a
dashboard layout
At the top right corner of the dashboard, click the 'Edit Layout' link. Select your required layout from the layout
options presented.
Add a gadget
To add a gadget:
1.
2.
3.
4.
At the top right of the dashboard, click the 'Add Gadget' link.
Click the 'Add it now' button beneath your chosen gadget.
Click the 'Finished' button to return to your dashboard.
If the gadget you have selected requires configuration, you will be presented with the gadget's
configuration page. Configure as required, and click 'Save'.
Move a gadget
To move a gadget to a different position on your dashboard, click the gadget and drag and drop it to its new
position.
Remove a gadget
To remove a gadget:
1. Hold your mouse over the top right corner of the gadget. A down-arrow appears.
2. Click the down-arrow to display an options menu.
3. Click 'Delete'.
Related topics
Workspace
69
Atlassian OnDemand October 2011 Documentation
Managing your profile
You can view user-specific information and personalise your user experience in Atlassian OnDemand by managing your profile.
In your user profile page, you can access reports on your votes, watches and reviews, as well as perform user-related functions such as
changing your password. You can also set your personal preferences for individual applications.
To edit your user profile:
1. Click the menu labelled with your user name in the header.
2. In the drop-down menu, click Profile in the drop-down menu that displays. The summary for your user profile will appear.
3. To edit cross-application settings such as your password and timezone: click the pencil icon in the Details or Preferences area as
needed.
4. To edit application-specific settings: in the top-right corner of the profile summary page, click Tools and you will see the options for
the individual applications. Note that not all options in the referenced documentation are available in OnDemand.
Issues preferences
Wiki preferences
Source and review preferences
Screenshot: Editing your profile (Click to enlarge the image)
Changing Your Password in Atlassian OnDemand
This page provides information on how to change passwords for Atlassian OnDemand, both with and without Google Apps integration.
On this page:
In standard Atlassian OnDemand
In Atlassian OnDemand with Google Apps integration
In standard Atlassian OnDemand
Changing your password
You can change your password by going to your profile. If you have forgotten your password, you can click the "forgot password" link on the
login screen to have a new password sent to you.
Changing passwords as an administrator
As an administrator, you can change passwords for any user by accessing the 'User' administration page.
In Atlassian OnDemand with Google Apps integration
When Atlassian OnDemand is integrated with Google Apps, users have two passwords. One is their Google password for access to Google
Apps and Atlassian OnDemand, and the other one is a secondary 'OnDemand' password that is used to access Subversion, RSS feeds and
for use with the Atlassian IDE Connectors. New users will be asked to set this secondary password when they first log in to Atlassian
OnDemand.
These two passwords need to be changed separately as described below.
Changing your Google password as a user
70
Atlassian OnDemand October 2011 Documentation
As a user, you can change your Google password by selecting the 'Forgot password' link on the Google Apps login screen.
Changing Google passwords as an administrator
As an administrator, you can change the Google password for any user by accessing the Google Apps administration and following these
instructions.
Changing your OnDemand password
OnDemand passwords (used for Subversion, RSS feeds, etc.) can be changed using the instructions for standard Atlassian OnDemand.
Working with Activities
The Activity Stream gadget displays the combined activities of the applications available in Atlassian OnDemand. Example activities are the
closing of a Crucible review and the creation of a JIRA issue. Activity streams are also interactive information sources and provide a number
of links which you can action on, for instance you can vote on, comment on or watch issues, create reviews for changesets, and comment on
Confluence pages. Depending on what the activity is about, your action will be reflected in the appropriate object (issue, changeset or wiki
page/blog, etc.) in the relevant application.
The Activity Stream gadget appears by default in a number of places such as the Activity Stream area on the user profile page. Besides the
default activity streams, you can also add activity streams to dashboards, wiki pages or blog posts.
Screenshots: Activity Streams (click to view full-size image)
The Activity Stream area on the user profile page
The user-added activity streams are configurable.
On this page:
Adding the Activity Stream gadget
Filtering activities
Subscribing to activities
Condensing activities
Adding the Activity Stream gadget
You can add the Activity Stream gadget to your own dashboards, wiki pages or blog posts.
Procedure
To add a gadget to your dashboards, refer to the Customising the Dashboard page (Adding a Gadget section) of the JIRA
documentation.
To add a gadget to wiki pages or blog posts, refer to the Gadget Macro page (Inserting Gadgets into a Confluence Page or Blog
Post section ) of the Confluence documentation.
After adding the gadget, modify the settings to choose what activities to display.
Filtering activities
By creating filters and modifying display options on the Activity Stream gadget, you can reduce the number of displayed activities or only
71
Atlassian OnDemand October 2011 Documentation
display specific events.
Before you begin
You can only filter activities for the Activity Stream gadgets that are added by yourself.
Procedure
1. Click the Filter
button in the top right corner of the activity stream area.
2. Modify the settings as needed, for example specifying the title that you want to display on your gadget, enter the maximum of
activities to display and creating filters to show specific types of events.
Global filters: Global filters apply to all applications.
Stream filters: Stream filters apply to specific applications. You can choose to include or exclude activities from a certain
application by selecting or clearing the check box before the application.
More about filters: There are a number of filter types available and their values are specified in different ways. For example
for username and issue key filters, directly enter the value or multiple values separated by commas. For the filters whose
values are available in the form of lists such as Project and Activity filters, just select a value or multiple values by holding
down the Ctrl key.
Subscribing to activities
Each activity stream gadget provides an RSS feed and you can subscribe to the RSS feed to keep up to date with the latest activities.
To subscribe to a RSS feed:
1. Click the RSS
symbol in the top right corner of the activity stream area.
2. Select your RSS reader to subscribe with.
Condensing activities
By default, the activity stream displays activities in the Full View. In the Full View, you can view activity details and the interaction options
such as Watch are also displayed. If you want to see the summary information about activities only, use the List View to condense the list.
Figure 1: Switching between Full View and List View
Working with Google Apps Integration
You can view and work with Google documents, calendar events, and Emails directly in OnDemand.
Logging In and Out With Google Apps Integration Using Google Docs with Google Apps Integration Using Google Calendar with Google
Apps Integration Using the Activity Bar
Related topics
Managing users and groups for sites integrated with Google Apps
Integrating OnDemand with Google Apps
Logging In and Out With Google Apps Integration
This page contains instructions on how to log in and out of Atlassian OnDemand with Google Apps credentials.
On this page:
Overview
Logging In
Logging Out
Audience: Users
72
Atlassian OnDemand October 2011 Documentation
Overview
When you use Atlassian OnDemand with Google Apps Integration, you need to manage your login status in both of these systems. When
you log in to Google Apps, you access your Google email, calendar, and documents. The Google Apps Marketplace offers products and
services designed to integrate with your Google Apps. As a separately licensed product, Atlassian OnDemand integrates with Google Apps
and you can access Google products such as via the Activity Bar), but has a different login to your Google Apps.
Logging In
Logging in from Google Apps
Log in to Google Apps. You will then be redirected to Atlassian OnDemand with Google Apps Integration.
Logging in directly from Atlassian OnDemand
When you visit the Atlassian OnDemand login page, you will be redirected to log into Google Apps.
Logging in without a Google Apps account
If you do not have a Google Apps account, you can log in to Atlassian OnDemand an an 'external user', i.e. non-Google user. You will need
to log in with the login details provided by your OnDemand administrator.
To log in without a Google Apps account:
1. From the 'Log In' drop-down, select the Log in directly option.
2. At the Log in using your Atlassian OnDemand dialog, enter the login details provided by your administrator.
3. Click the Log In button to start using Atlassian OnDemand.
Setting your Subversion and RSS Log In Passwords
There are two passwords in Atlassian OnDemand when it is integrated with Google Apps: the Google Apps password, and the Subversion
password. These two passwords are managed separately in Google Apps and OnDemand respectively.
However, you can access Subversion with the same Google Apps password.The first time you log in via Google Apps, you will be prompted
to set your password for Subversion and RSS feeds. Just specify the same password as your Google credentials and then you will be able to
use a single password .
Screenshot: Logging into the repository
Logging Out
You need to log out of Google Apps and Atlassian OnDemand independently. When you log out of Atlassian OnDemand while you are still
logged in to Google Apps, you can return to OnDemand without entering your password. As a security measure, the system will prompt you
to log out of Google Apps if you have exited Atlassian OnDemand but are still logged in to the Google domain.
1. Log out of Google Apps
73
Atlassian OnDemand October 2011 Documentation
Click 'Log out' from the Google Apps interface.
2. Log out of Atlassian OnDemand
Click 'Log Out' from the Atlassian OnDemand.
Screenshot: Logging out of Atlassian OnDemand
Using Google Docs with Google Apps Integration
This page contains instructions on how to use Google Docs in OnDemand.
On this page:
Viewing recently updated Google Docs from the Activity Bar
Attaching Google Docs to issues
Attaching Google Docs to wiki pages
Attaching a list of Google Docs to a wiki page
Viewing recently updated Google Docs from the Activity Bar
Clicking the
button on the Activity Bar shows a list of recently updated documents. Click any link to open the document.
Attaching Google Docs to issues
To do this:
1. Create or open the desired JIRA issue.
2. Click the 'Attach Google Docs' link. The 'Google Docs Picker' window appears. Type text into the 'Title Contains' field to search
for a document, and you can restrict the documents displayed by selecting an option from the 'Doc Type' drop-down menu.
3. To select the document(s) you want to attach, check the box next to the document file name and click 'Attach Selected Documents
'.
4. You will be returned to the view issue page. The attached documents will appear as a list in the ' Google Documents' section.
Note that attached Google Docs are not static, they will always be up to date with the most recent edits made in Google Apps. Users will
only be able to view documents which they are allowed access to in Google Docs. You can only add one custom Google Docs field to a JIRA
issue.
Screenshot: Google Docs Picker
74
Atlassian OnDemand October 2011 Documentation
Attaching Google Docs to wiki pages
To do this:
1.
2.
3.
4.
5.
In the editing mode of a page, place the text cursor where you would like to insert the Google Document.
In the toolbar, click Insert > Other Macros. The 'Select Macro' dialog appears.
In the search box at the top right of the dialog, type Google. The Google Docs macros will appear in the list.
Select the appropriate macro and follow the instructions in the dialog to insert the document.
The Google Docs macro is added to the page with the selected documents, which will appear inline when rendered. For now, the
macro will appear in the editor window looking like the following:
{gdocument:docid=0AV1fqMj98CsNZGhodHN6NXhfNGR3bmZ4cGY1|height=100%}
6. Click Save on the wiki page. After the page is saved, you will be able to read the document in the wiki page. An ' Edit' link will appear
beneath the document, allowing you to instantly edit the document in Google Apps.
Screenshot: Browsing Google Docs macros
Attaching a list of Google Docs to a wiki page
1. In the editing mode of a page, use the 'Google Documents List' macro to display a list of Google documents on a wiki page.
2. After saving the page, you will see the document list in the wiki page.
Screenshot: List of Google Docs in a Confluence wiki page
75
2.
Atlassian OnDemand October 2011 Documentation
Using Google Calendar with Google Apps Integration
This page explains the Google Calendar integration in Atlassian OnDemand and how to use it.
On this page:
Viewing upcoming Google Calendar events from OnDemand
Adding a Google Calendar event from OnDemand
Removing an event from Google Calendar
Related topics
Viewing upcoming Google Calendar events from OnDemand
Clicking the Google Calendar button
Calendar.
on the Activity Bar will show a list of upcoming events. Click any link to open the event in Google
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar
Adding a Google Calendar event from OnDemand
To add an event to the calendar, click the Google Calendar button
on the Activity Bar, then click the plus sign icon
of the dialog. A form field opens, where you can simply type the event details in then click 'Create', as in this example:
in the corner
5pm requirements meeting
This example would add an event to the calendar called 'requirements meeting' at 5pm today. A small notification message will appear inline,
confirming that the creation was successful. You can also set events for different days by typing in the day, as in the following example:
5pm tuesday requirements meeting
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar
Screenshot: Adding a Google Calendar event from the Activity Bar
76
Atlassian OnDemand October 2011 Documentation
Screenshot: Notification on creating an event
Removing an event from Google Calendar
Google Calendar events cannot be deleted in OnDemand and you can only delete an event in Google. To remove an event from Google
Calendar, launch Google Calendar by clicking the Google Calendar button
Calendar will launch in a new browser window.
on the Activity Bar, then clicking 'See More'. Google
Related topics
Using the Activity Bar
Using the Activity Bar
If you are using OnDemand with Google Apps integration, you have a menu bar at the bottom of the screen called the Activity Bar. This
feature provides you with quick access to OnDemand and Google Apps functionality.
Activity Bar (OnDemand-only access):
Users who do not have Google IDs (i.e. external users) will only see and be able to access OnDemand features:
Recent Activity
Recent Issues
Favourite Pages
Recent Builds
Outstanding Reviews
Screenshot: External User Activity Bar
Activity Bar (Google Apps and Atlassian OnDemand integration):
Users who have Google IDs will be able to access both OnDemand and Google features:
Recent Activity
Recent Issues
Favourite Pages
Recent Builds
Outstanding Reviews
Gmail Messages
Google Calendar Events
Google Docs
Google Sites
Screenshot: The Activity Bar
77
Atlassian OnDemand October 2011 Documentation
Viewing Recent Activity with the Activity Bar
1. Click the Atlassian button
on the Activity Bar. You can view the relevant information by clicking a link.
Screenshot : Recent Activity in the Activity Bar
Viewing Recent Issues with the Activity Bar
1. Click the issues button
on the Activity Bar.
Screenshot: Recent Issues in the Activity Bar
To add an issue via the Activity Bar:
1. Click the issues button
2. Click the plus sign icon
on the Activity Bar.
in the corner of the dialogue. A dialogue box will be displayed.
See Working with Issues for more information about JIRA issues.
Viewing Favourite Pages with the Activity Bar
1. Click the wiki favourite button
will be displayed.
on the Activity Bar. A short list of Confluence wiki pages that you have selected as favourites
Screenshot: Favourite pages in the Activity Bar
See Working with the Wiki for more information about using Confluence wiki pages.
78
Atlassian OnDemand October 2011 Documentation
Viewing Recent Builds with the Activity Ba
1. Click builds button
on the Activity Bar.
Screenshot: List of recent build activity on the Activity Bar
See Working with Builds for more information about using Bamboo builds in OnDemand.
Viewing Outstanding Reviews with the Activity Bar
1. Click the reviews button
in a red star
on the Activity Bar. A list of outstanding reviews that you are involved in will be displayed. A number
superimposed over the button shows how many new reviews you have.
Screenshot: List of outstanding reviews on the Activity Bar
See Working with Reviews for more information about using Crucible reviews.
Viewing Gmail Messages with the Activity Bar
1. Click the Gmail button
waiting in Gmail.
on the Activity Bar. A red number on the chatbar icon
Screenshot: List of unread Gmail messages on the Activity Bar
79
shows how many unread messages are
Atlassian OnDemand October 2011 Documentation
Viewing Upcoming Google Calendar Events with the Activity Bar
1. Click the Google Calendar button
on the Activity Bar. A list of upcoming events will be displayed.
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar
See Using Google Calendar with Google Apps Integration for more detail on how Google Calendar integrates with OnDemand.
Viewing Google Docs with the Activity Bar
1. Click the Google Docs button
on the Activity Bar. A list of recently updated documents will be displayed.
Screenshot: List of recently updated Google Docs on the Activity Bar
See Using Google Docs with Google Apps Integration for more detail on how Google Docs integrates with OnDemand.
Launching Google Sites from the Activity Bar
80
Atlassian OnDemand October 2011 Documentation
To launch Google Sites from the Activity Bar:
1. Click the Google Sites button
on the Activity Bar. Google Sites will be launched in a new web browser window. You will be
automatically logged in with your Google ID.
Screenshot: Google Sites, launched by the Activity Bar
JIRA OnDemand
JIRA provides issue tracking and project tracking for software development teams to improve code quality and the speed of development.
JIRA OnDemand, i.e. the Issues application, is the hosted offering of JIRA. If you are using JIRA OnDemand together with other OnDemand
applications, you will be able to take advantage of a number of pre-configured integration features, such as linking between applications.
New to JIRA OnDemand?
Administrators
Getting Started Guide
Users
Getting Started Guide
Important information
Please note the following important information before you begin using JIRA OnDemand:
Some functions in JIRA OnDemand are restricted for security reasons. Read more about Restricted Functions in Atlassian
OnDemand.
To find out which JIRA version is running in Atlassian OnDemand, see Atlassian OnDemand Application Versions.
Extending JIRA OnDemand
JIRA OnDemand's functionality can be extended further by enabling commercial add-ons provided by Atlassian. See the Atlassian
OnDemand Plugin Policy for instructions on how to order these add-ons. The following add-ons are available:
GreenHopper is an agile project management tool that helps you manage JIRA issues in an agile environment.
81
Atlassian OnDemand October 2011 Documentation
Got GreenHopper? Check out the GreenHopper documentation.
Bonfire is an agile testing tool that allows you to report JIRA bugs directly from the web application being tested.
Got Bonfire? Check out the Bonfire documentation.
About the OnDemand documentation
The JIRA OnDemand documentation links to the documentation for downloadable JIRA extensively. Use the back button on your browser to
return to the OnDemand documentation, if you are directed to the documentation for downloadable JIRA.
Key topics
Administering Issues
Administration console differences
JIRA Administrator's Guide
Enabling sub-tasks for a project
Configuring JIRA Plugins
Linking a bitbucket or GitHub repository with JIRA OnDemand
Integrating Flowdock with JIRA OnDemand
Connecting Zephyr with JIRA OnDemand
Configuring Cloud Connectors in JIRA OnDemand
Working with Issues
JIRA User's Guide
Creating an issue
Managing agile projects
Creating issue comments via emails
Administering Issues
JIRA OnDemand, i.e. the Issues application, is based on JIRA. The administration of JIRA OnDemand is mostly the same as that of
downloadable JIRA except the functions specific to JIRA OnDemand indicated below and certain restrictions due to security considerations.
An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a JIRA project.
Audience: Administrators
Administration specific to JIRA OnDemand
Page: Connecting Zephyr with JIRA OnDemand
Page: Integrating Flowdock with JIRA OnDemand
Page: Linking a bitbucket or GitHub repository with JIRA OnDemand
Administering JIRA and add-ons
JIRA
JIRA Administrator's Guide
Before referring to this guide, please read the navigation differences between JIRA OnDemand and JIRA page.
82
Atlassian OnDemand October 2011 Documentation
To know what functions are restricted in JIRA OnDemand compared with downloadable JIRA, refer to Restricted Functions.
Add-ons
If you have enabled GreenHopper for your site, refer to GreenHopper documentation:
GreenHopper Administrator's Guide
Other add-ons do not involve administrative operations and your team can start using them as soon as they are enabled.
Accessing the Issues administration settings
To administer the Issues application, use the 'Issues' administration tab in the administration console.
To access the Issues tab in the administration console:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues administration console will display (see screenshot on the right).
For an overview of the administration options for the 'Issues' application, refer to the following appendix.
For details about administering JIRA and GreenHopper, please see the documentation linked in the JIRA and GreenHopper administration
section above.
Screenshot: Administering Issues (click to view larger image)
Appendix – Administration options in the Issues application
The following table lists the administration options in the Issues application.
83
Category
Functions
General
Configuration
Configure general issue settings, such as internationalisation, the ability of customers to vote on and watch issues,
visibility of comments and user emails, auto-completion on issue picker and user pickers, etc.
Projects
View the list of existing JIRA projects and their summary. A Project Summary shows the current settings for a project.
User Settings
* Global Permissions — Manage system-wide permissions (granted to groups of users).
* User Preferences — Manage the default settings for user profiles.
* Roles — Define and assign project roles.
Atlassian OnDemand October 2011 Documentation
84
Issue Types
* Issue Types — Add, edit and delete issue types as well as configure issue type schemes and translations
(internationalisation).
* Sub-Tasks — Manage sub-task settings for issues.
Workflows
* Workflows — Manage workflows for your projects.
* Workflow Schemes — Manage workflow schemes for your projects.
Screens
* Screens — Configure screens, i.e. which fields are displayed on a screen.
* Screen Schemes — Configure screen schemes to determine which screen is displayed to a user for a particular issue
operation.
* Issue Type Screen Schemes — Manage the screen schemes that apply to issue types.
Fields
* Custom Fields — Add, configure and delete your custom fields.
* Field Configurations — Configure field behaviour, such as field description, visibility, whether it is enabled, etc.
* Field Configuration Schemes — Manage field configuration schemes to apply field configurations to issue types.
Issue
Attributes
* Statuses — Add, edit and delete issue statuses (used on workflows) as well as configure translations
(internationalisation) for statuses.
* Resolutions — Add, edit and delete issue resolutions as well as configure translations (internationalisation) for
resolutions.
* Priorities — Add, edit and delete issue priorities as well as configure translations (internationalisation) for priorities.
Issue
Features
* Time Tracking — Manage time tracking (i.e. logging work) settings for issues. Time Tracking is ON by default. Read
Configuring Time Tracking (JIRA documentation) about how to configure the settings.
* Issue Linking — Manage issue links (e.g. an issue may depend on another issue). This is separate to creating links.
GreenHopper
* General Configuration — Configure general GreenHopper settings.
* Project Templates — Manage project templates, e.g. editing a template or creating a new one.
* Enabled Projects — Enable or disable a project to use GreenHopper.
* License Details — Manage the license for the GreenHopper plugin.
System Info
Display the system information for your JIRA application.
User
Interfaces
* System Dashboard — Configure the default dashboard for your site.
* Navigator Columns — Configure the navigator columns (used to display results when searching for issues)
* Announcement Banner — Set an HTML announcement that will appear as a system-wide banner.
Mail
* Mail Queue — Manage the JIRA event queue. You have the option of flushing the mail queue to send mails
immediately.
* Send E-mail — Send an email to selected JIRA user groups or project roles.
Misc.
Schemes
* Issue Security Schemes — Manage issue security levels and schemes for your projects (i.e. who can individual
issues in a project).
* Notification Schemes — Manage notification schemes for your projects (i.e. emails notifications for events during an
issue lifecycle).
* Permission Schemes — Manage permission schemes for each of your projects.
Advanced
* Indexing — Re-index the JIRA application.
* Attachments — Configure file attachment settings.
* Events — Add, remove and configure events as well as the notification schemes and workflows that they apply to.
* Scheme Tools — Use scheme tools evolve your schemes from user-based to role-base, and rationalise your
schemes.
Tempo
Disable and enable Tempo, manage the license and configure the various settings.
Plugins
* Plugins — Enable, disable and configure JIRA plugins. For instructions of how to do this, refer to the Configuring JIRA
Plugins page.
* GitHub OAuth Settings — Configure the OAuth settings if you associate private GitHub repositories with JIRA
projects.
* Bulk Configure GitHub Repositories — Associate GitHub repositories with JIRA OnDemand or manage existing
ones.
* Bitbucket — Associate Bitbucket repositories with JIRA OnDemand or manage existing ones.
* Gliffy JIRA Plugin — Manage the license for the Gliffy plugin.
* Balsamiq Mockups License — Manage the license for Balsamiq.
Cloud
Connectors
Manage the license and configure the various settings. For instructions of how to configure them, refer to Configuring
CustomWare connectors in JIRA OnDemand.
Atlassian OnDemand October 2011 Documentation
Administration console differences
Depending on what applications your site has, the administration console might look different.
JIRA OnDemand only: the console is the same with downloadable JIRA and uses top drop-down menus.
More than one OnDemand applications: the console uses left-hand menus.
When you refer to the JIRA Administrator's Guide, please note that the instructions on how to navigate to a specific administration
option may not apply to JIRA OnDemand. The administration settings themselves are the same.
Tip of accesing administration menus
You can easily locate administration menus by searching for them. Type g + g anywhere in Atlassian OnDemand to bring up
the Administration Search box, in which you can search for menus you want to work with.
For example, the following screenshots illustrate how to navigate to issue type configuration in OnDemand and JIRA respectively.
Multiple OnDemand applications
JIRA OnDemand only and downloadable JIRA
85
Atlassian OnDemand October 2011 Documentation
Related topics
Atlassian OnDemand Application Versions
JIRA Administrator's Guide
Atlassian OnDemand includes JIRA 5.0 for issue tracking. Use the search or click any of the links below to view the relevant page in the
JIRA Administrator's Guide. You will need to use the 'Back' button on your browser to return to the JIRA OnDemand documentation.
Please note, some JIRA functionality is restricted in JIRA OnDemand.
Search the JIRA 5.0 documentation only:
Getting Help
Configuring the Layout and Design
Customising the Look and Feel
Choosing a Default Language
Configuring the Default Issue Navigator
Configuring the Default Dashboard
Using Dashboard Gadgets
Configuring an Announcement Banner
Enabling Logout Confirmation
User and Group Management
Managing Users
Managing Groups
Managing Project Roles
Migrating User Groups to Project RolesClearing 'Remember my login' Tokens
86
Atlassian OnDemand October 2011 Documentation
Disabling Remember My Login on this Computer
Enabling Public Signup and CAPTCHA
Project Management
Defining a Project
Managing Project Role Membership
Defining a Component
Managing Versions
Running a Bamboo Build when Releasing a Version
Creating Release Notes
Configuring Project Keys
Configuring Security
Configuring Issue Level Security
Managing Project Permissions
Managing Global Permissions
Configuring Fields and Screens
Configuring Built-in Fields
Defining 'Issue Type' Field Values
Associating Issue Types with Projects
Defining 'Priority' Field Values
Defining 'Resolution' Field Values
Defining 'Status' Field Values
Adding a Custom Field
Configuring a Custom Field
Creating Help for a Custom Field
Specifying Field Behaviour
Associating Field Behaviour with Issue Types
Configuring Renderers
Defining a Screen
Associating a Screen with an Issue Operation
Associating a Screen with an Issue Type
Configuring Workflow
Activating Workflow
Adding a Custom Event
Configuring the Initial Status
Workflow Properties
Configuring Email
Configuring Email Notifications
Creating a Notification Scheme
Customising Email Content
Creating Issues and Comments from Email — JIRA OnDemand includes a mail service configured to create issue comments from
replies to JIRA notifications. Setting up a JIRA service to create issues and comments from an external POP/IMAP server is not
currently supported.
Moving or Archiving Individual Projects
Archiving a Project — For offline archiving, Atlassian support will assist with generating a usable XML backups for downloadable
JIRA, only if you have a pending cancellation of a paid-subscription JIRA OnDemand account. Request an export by filing a ticket at
https://support.atlassian.com.
Integrating with a Build Management System
Integrating JIRA with Bamboo
Configuring Global Settings
Configuring Time Tracking
Configuring JIRA Options — gzip is always set to off.
Setting Properties and Options on Startup
Recognized System Properties for JIRA
Configuring File Attachments — Attachments enabled by default, maximum size set to 100MB.
Configuring Issue Cloning
Configuring Issue Linking
Configuring Sub-tasks
Managing Shared Filters
Managing Shared Dashboards
Server Administration
87
Atlassian OnDemand October 2011 Documentation
Search Indexing — Indexing path cannot be changed.
Viewing your System Information
Appendix A - Extending JIRA
Managing JIRA's Plugins — Plugins cannot be installed or uninstalled.
Enabling sub-tasks for a project
Enabling sub-tasks for a project is a two-step process as described below.
Procedure
1. Enable sub-tasks
To to this:
1. In the administration console, go to Issues > Issue Types > Sub-Tasks.
2. Add sub-task issue types with your project
For the sub-task issue types to be available for your project, you need to add the sub-task issue types to the issue type scheme that your
project is associated with.
To do this:
1.
2.
3.
4.
In the administration console, go to Issues > Issue Types > Issue Types.The 'Manage Issue Types' page displays.
Go to the Issue Types Scheme tab and locate your project.
In the Operations column of your project, click the Edit link.
Add the sub-task issue types as needed and then save your changes.
Related topics
Associating Issue Types with Projects
Configuring Sub-tasks
Configuring JIRA Plugins
Overview
You can enable and disable plugins and their modules as needed and view the change log of plugins. You can also configure the plugins that
offer configuration options.
Restriction: You can only enable or disable the bundled plugins in Atlassian OnDemand and cannot install or remove any plugins. For
more information, please read the Atlassian OnDemand Plugin Policy.
Audience: Administrators
Disabling or Enabling a JIRA Plugin
Viewing your JIRA Plugins
Viewing the JIRA Plugin Audit Log
Differences between system plugins and user-installed plugins
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that are shipped with the stand-alone version of the product and included in Atlassian OnDemand. These
plugins are integral to the functioning of the system and cannot be disabled.
User-installed plugins are not included with the stand-alone version of the product and have been bundled with Atlassian
OnDemand. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well,
although modules that are integral to the functioning of the plugin cannot be disabled.
88
Atlassian OnDemand October 2011 Documentation
Related topics
Configuring Confluence Plugins
Disabling or Enabling a JIRA Plugin
You can enable and disable JIRA plugins in your Atlassian OnDemand site. With the Safe Mode, you can disable all user-installed plugins in
your site with one click, which might help you diagnose plugin-related problems more easily.
Audience: Administrators
On this page:
Disabling a plugin
Enabling a plugin
Disabling and enabling all user-installed plugins (Safe Mode)
Restriction: You cannot install new plugins nor remove existing plugins as per the Atlassian OnDemand Plugin Policy.
Disabling a plugin
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues (JIRA) administration console will display.
3. In the left-hand menu, click Plugins > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To disable a JIRA plugin:
1.
2.
3.
4.
Click the Manage Existing tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon:
Locate the plugin that you want to disable and click the title to expand the plugin details section.
Click the Disable button.
Once a plugin has been disabled, you may need to restart your application for your change to take effect. If so, you will see a
message for the plugin, Disabled, requires restart.
Once the plugin is fully disabled, you will see an Enable link for the plugin.
Enabling a plugin
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues (JIRA) administration console will display.
3. In the left-hand menu, click Plugins > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To enable a JIRA plugin:
1.
2.
3.
4.
Click the Manage Existing tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon:
Locate the plugin that you want to enable and click the title to expand the plugin details section.
Click the Enable button.
Once a plugin has been enabled, you may need to restart your application for your change to take effect. If so, you will see a
message for the plugin, Enabled, requires restart.
Once the plugin is fully disabled, you will see a Disable link for the plugin.
Disabling and enabling all user-installed plugins (Safe Mode)
Running your application in Safe Mode disables all user-installed (i.e. non-system) plugins at once. All plugins that were disabled when you
entered Safe Mode will be re-enabled when you exit Safe Mode.
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues (JIRA) administration console will display.
3. In the left-hand menu, click Plugins > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To enable Safe Mode:
1. Click the Manage Existing tab.
89
Atlassian OnDemand October 2011 Documentation
1.
The system displays a list the installed plugins.
2. Click the Enable Safe Mode link.
3. Click the Continue button in the confirmation window.
All user installed plugins will be disabled and your application will now be running in safe mode.
4. Make changes to your installed plugins as desired.
For example, you may want to enable/disable specific plugins or plugin modules.
5. Exit safe mode by clicking one of the links in the Safe Mode banner:
Click Exit Safe Mode and restore the previous configuration to restore your plugin configuration to its state before you
entered Safe Mode.
Click Exit Safe Mode and keep the current configuration to keep all changes made to your plugin configuration during
Safe Mode.
Viewing your JIRA Plugins
This page explains how to view the JIRA plugins and their details in Atlassian OnDemand.
Audience: Administrators
Viewing JIRA plugins
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues (JIRA) administration console will display.
3. In the left-hand menu, click Plugins > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To view JIRA plugins:
Click the Manage Existing tab to list the plugins installed in your application. The application groups plugins into User-installed Plugins and
System Plugins. The System Plugins are hidden by default. Use the following actions when working with the plugin list:
Enter keywords in the Filter visible plugins text box to filter the list.
Click the Show System Plugins link to see the hidden system plugins.
Click the name of a plugin to view the plugins details.
Click Enable Safe Mode to run your application in safe mode. This mode disables all user installed plugins.
Enabled plugins have this icon
, and this icon
indicates disabled plugins.
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that are shipped with the stand-alone version of the product and included in Atlassian OnDemand. These
plugins are integral to the functioning of the system and cannot be disabled.
User-installed plugins are not included with the stand-alone version of the product and have been bundled with Atlassian
OnDemand. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well,
although modules that are integral to the functioning of the plugin cannot be disabled.
Viewing a plugin's details
You can view the details for a plugin when you click the plugin name in the installed plugins list. The details contain a short description of the
plugin as well as buttons and links for plugin operations.
Plugin key – A unique key the identifies each plugin in the system.
Developer – The name of the plugin developer and a link to the developer's homepage, if provided by the plugin developer.
Plugin version – The version of the plugin currently installed.
Manage plugin modules — Click this link to display the plugin modules below the plugin summary. A module is a component of the
plugin. This link will only appear if the plugin has modules. If you want to enable or disable a plugin module, hover your mouse over
the module and click the 'Enable'/'Disable' button for that module.
Plugin details – Click this link to display the plugin information on the Atlassian Plugin Exchange.
Configure – Click this link to display the configuration settings for the plugin in the Universal Plugin Manager. This link will be
disabled if the plugin is disabled. Please note that not all plugins have settings that can be configured through the Universal Plugin
Manager.
Disable – Click this button to disable the plugin in your application. This button will only appear if the plugin is enabled.
Enable – Click this button to enable the plugin in your application. This button will only appear if the plugin is disabled.
Related Topics
90
Atlassian OnDemand October 2011 Documentation
Disabling or Enabling a JIRA Plugin
Viewing the JIRA Plugin Audit Log
You can check the log for all the plugin activities in your Atlassian OnDemand instance, for example enabling plugins and disabling plugins
and the users who made the changes.
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Issues tab. The Issues (JIRA) administration console will display.
3. In the left-hand menu, click Plugins > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To view the plugin audit log:
1. Click the Audit Log tab.
The plugin audit log appears with a list of the 25 most recent entries.
2. Use the arrows if you want to view older entries.
3. Click the orange RSS icon if you want to receive the audit log activity in an RSS feed.
Screenshot: Viewing the plugin audit log
Linking a bitbucket or GitHub repository with JIRA OnDemand
JIRA OnDemand includes a bitbucket & GitHub Connector plugin. This system plugin allows you to link bitbucket or GitHub repositories
(repos) with their corresponding JIRA project. You can use the connector to connect to public or private repositories. Once linked, the plugin
identifies DVCS commit messages that reference a specific JIRA issue key and records the commit in JIRA. The information appears in the
issue's Activity and Commits section. The plugin records the commit message, the list of changed files, and provides links to view the
change set.
JIRA requires that a connected repository provide a POST service. The POST service allows JIRA to hook into a source code commit and
obtain the proper data. You can enable this service through your hosted repository or you can enable this service through the bitbucket &
GitHub plugin on JIRA. If you want to enable the service through JIRA, you must provide JIRA with the username/password of a user with
administrative access to the repository.
On this page:
Prequisite for GitHub private repositories
Procedures
Example of how commit information appears in a project
Using with Force Sync operations to troubleshoot
91
Atlassian OnDemand October 2011 Documentation
Prequisite for GitHub private repositories
If you are planning on connecting to GitHub private repositories, you must configure OAuth settings for GitHub before connecting to your
repos. To configure the OAuth settings, do the following:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3. Open the Issues tab and click Source Control > GitHub OAuth Settings.
4. Follow the instructions on the page.
Procedures
To display a list of hosted projects linked to JIRA, open your JIRA instance in your browser and do the following:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3. Open the Issues tab and click Source Control > Bitbucket and and GitHub Repositories.
The Bulk Configure Repositories page appears. The page lists Existing Linked Repositories. Each repository entry includes the
repository URL and its corresponding project key.
To add a repository to this list, scroll down past the list to the blue form.
1. Click Choose project and select the JIRA project you want to link the repository to.
2. Enter the URL of the hosted repository.
JIRA uses the HTTPS protocol to connect to the repository.
3. Click the Add Repository button.
JIRA verifies it can connect to the repository.
4. If the repository you specified is private, JIRA prompts you for a valid username/password to connect to the repository.
5. Check Install postcommit service.
6. Then, depending on which hosting service you are using, do the following:
For bitbucket repositories
For GitHub repositories
Enter the credentials of a repository administrator.
Click the Add Repository button.
The system informs prompts you to authorize the connection:
If you do not enable the postcommit service
at this point, you
must ensure that the service is enabled
through the
hosted service. For information on enabling
a post service on
bitbucket, see Setting Up the bitbucket
POST Service.
Click the Add Repository button.
Press Allow.
Your repository appears in the the Bulk Configure Repositories page.
Ensure your project users have the correct permissions
Project users must all have View Version Control permissions. Without the proper permissions, users can not see the
Bitbucket tab even on linked projects.
Automatic synchronisation
92
Atlassian OnDemand October 2011 Documentation
After you link a repository, JIRA automatically starts looking for commits that reference issue keys for the associated JIRA project. The
summary shows the sync results and errors if any. A synchronisation of commit data from the DVCS repository to JIRA can take some time.
As the synchronisation progresses, the commits appear in related issues.
Example of how commit information appears in a project
Commit code as follows, and you will see this commit in the activity section of the JIRA issue PONE-1.
hg commit -m "DVCS-2 add a README file to the project."
hg push
Screenshot: Bitbucket commits on the Activity tab of the DVCS-2 issue
Screenshot: Bitbucket commits on the Commits tab of the DVCS-2 issue
Using with Force Sync operations to troubleshoot
93
Atlassian OnDemand October 2011 Documentation
If you see inconsistencies between the displayed commits in JIRA and the actual activity in your repository, you should run a Force Sync
operation. The Force Sync operation compares the existing commit data in JIRA with that in the linked repository. The system restores any
missing commit data to JIRA. A forced synchronization does not affect the commits in hosted DVCS. You should run Force Sync operations
when:
There are missing commit activities in JIRA.
You haven't seen commits appearing in JIRA for a longer period of time than usual.
The hosted DVCS system is back online after an offline period and you want to retrieve the commit data immediately. Otherwise, you
must wait for service to send the data.
To run a Force Sync operation:
1. Log in a user with administrator access to your JIRA instance.
2. Choose username > Administration from the dashboard menu.
The Administrator page appears.
3. Open the Issues tab and click Source Control > Bitbucket and and GitHub Repositories.
The Bulk Configure Repositories page appears. The page lists Existing Linked Repositories.
4. Locate the repository that you want to synchronise.
5. Click the Force Sync link.
A synchronisation starts. After the synchronisation is complete, a summary for the synchronisation displays under the repository
listing in JIRA.
Related topics
Setting Up the bitbucket POST Service
Post-Receive Hooks
Integrating Flowdock with JIRA OnDemand
You can integrate Flowdock with JIRA OnDemand and issues from your JIRA projects will be included in your Flowdock flows.
Procedure
Before you begin:
If you link a JIRA project to a Flowdock flow, all JIRA comments will appear on FlowDock regardless of the restriction level that is
set when creating the comment. Please ensure that you only link JIRA projects to Flowdock flows when it is acceptable for all JIRA
comments to be visible.
To integrate Flowdock:
1. Log in as an administrator, and go to Administration > Issues tab > Plugins on the left menu.
2. In the System Plugins section, click Show System Plugins. Then locate Flowdock for JIRA, and click Configure . The Flowdock
integration page will display all JIRA projects set up in OnDemand.
3. Enter your Flowdock API key against the JIRA projects that you want to include in your Flowdock flow.
To get your Flowdock API key, log in to Flowdock and view the Integrating with variety of issue trackers page. Your API key will be
displayed in the JIRA instructions.
4. Click Save. The API key information will be saved and the Flowdock integration page will refresh.
You will now receive messages in your Flowdock flow for any issue activity (e.g. issue creation, issue comments added, issue fields updated,
etc) in the configured JIRA projects.
Connecting Zephyr with JIRA OnDemand
By connecting JIRA OnDemand with Zephyr, you can save the efforts of switching between applications, maintaining data in two locations,
and creating manual reports for testing status, traceability, and auditing.
Important: After Zephyr is enabled, the OnDemand data consumed by Zephyr will be exposed publicly.
To enable Zephyr:
1. Log in as an administrator, and go to Administration >Issues tab > Plugins. The plugin section is expanded and you will see the
list of user-installed plugins.
2. Near the bottom of the page, locate the Zephyr RPC JIRA Plugin and click it to display the available options.
3. Click Enable. The Zephyr plugin will be enabled.
Related topics
http://www.getzephyr.com/buy/index.php
https://plugins.atlassian.com/plugin/details/18715
94
Atlassian OnDemand October 2011 Documentation
Configuring Cloud Connectors in JIRA OnDemand
Before you being
Make sure that the Accept Remote API calls is set to ON.This setting is ON by default.
To locate the option:
1. Go to Administration > Issues > General Configuration. The General Configuration page displays.
2. At the bottom of the page, click Edit Configuration. The fields on the General Configuration page become editable.
3. Find the Accept Remote API calls setting In the Options section.
Configuring the connectors
Accessing the Connectors configuration settings:
JIRA OnDemand only: Administration > Plugins
Multiple applications: Administration > Issues > Cloud Connectors
For detailed configuration instructions, refer to the following CustomWare documentation.
To configure the connectors:
Get Satisfaction: http://wiki.customware.net/repository/display/GSJIRA/Administrators+Guide
Salesforce.com: http://wiki.customware.net/repository/display/SFJIRA4/Administrators+Guide
Source Labs: http://wiki.customware.net/repository/display/SLJIRA/Administrators+Guide
uTest: http://wiki.customware.net/repository/display/UTJIRA/Administrators+Guide#AdministratorsGuide-Configuration
Zendesk: http://wiki.customware.net/repository/display/ZDJIRA/Home
Note: The connectors are enabled by default in JIRA OnDemand, so you do not need to perform any installation tasks. The installation
instructions in the referenced documentation are for downloadable JIRA. Similarly, you do not need to configure application links either.
Working with Issues
JIRA OnDemand, i.e. the Issues application, is based on JIRA. Besides the functionality that is available in downloadable JIRA, JIRA
OnDemand offers functions that are specific in OnDemand.
An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a JIRA project.
Audience: Users
Using JIRA OnDemand
The following functions are handy to use in JIRA OnDemand.
Page: Creating issue comments via emails
Page: Actioning Issues via Builds
Using JIRA and add-ons
JIRA
JIRA User's Guide
Add-ons
Depending on what add-ons your administrator enabled for your site, your issues application may also include the following additional
features:
95
Atlassian OnDemand October 2011 Documentation
GreenHopper User's Guide
Bonfire User Guide
Balsamiq Mockups for JIRA User Guide
Accessing the Issues application
To work on issues, e.g. creating issues and searching for issues, use the ’Issues' application. This is also the place for using JIRA add-ons
such as GreenHopper and Bonfire.
To access the Issues application:
1. Click the 'Issues' tab in the navigation bar. This takes you to JIRA.
Screenshot: Example Issues dashboard (click to enlarge image)
JIRA User's Guide
Atlassian OnDemand includes JIRA 5.0 for issue tracking. Use the search or click any of the links below to view the relevant page in the
JIRA User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA OnDemand documentation.
Please note, some JIRA functionality is restricted in JIRA OnDemand.
Search the JIRA 5.0 documentation:
JIRA Concepts
What is a Project
What is Workflow
What is an Issue
Getting Started
Logging in to JIRA
Exploring the JIRA Workspace
Using Keyboard Shortcuts
96
Atlassian OnDemand October 2011 Documentation
Working with Issues
Attaching a File
Attaching a Screenshot
Cloning an Issue
Commenting on an Issue
Creating an Issue
Creating a Sub-Task
Editing an Issue
Editing Rich-Text Fields
Emailing an Issue
Labelling an Issue
Linking Issues
Logging Work on an Issue
Modifying Multiple ('Bulk') Issues
Moving an Issue
Scheduling an Issue
Setting Security on an Issue
Viewing an Issue's Change History
Viewing an Issue's Crucible Reviews
Viewing an Issue's FishEye Changesets
Viewing the Bamboo Builds related to an Issue
Watching and Voting on an Issue
Searching for Issues
Using Quick Search
Performing Text Searches
Advanced Searching
Using the Issue Navigator
Customising your Issue Navigator
Saving Searches ('Issue Filters')
Receiving Search Results as an RSS Feed
Exporting Search Results to Microsoft Word
Exporting Search Results to Microsoft Excel
Displaying Search Results as a Chart
Displaying Search Results in XML
Receiving Search Results via Email
Emailing a Search Result
Generating Reports
Workload Pie Chart Report
User Workload Report
Version Workload Report
Time Tracking Report
Single Level Group By Report
Created vs Resolved Issues Report
Resolution Time Report
Pie Chart Report
Average Age Report
Recently Created Issues Report
Time Since Issues Report
Browsing a Project
Browsing a Project's Summary
Browsing a Project's Issues
Browsing a Project's Road Map
Browsing a Project's Change Log
Browsing a Project's Popular Issues
Browsing a Project's Versions
Browsing a Version's Summary
Browsing a Version's Issues
Browsing a Version's Popular Issues
Browsing a Version's Bamboo Builds
Browsing a Project's Components
Browsing a Component's Summary
Browsing a Component's Issues
Browsing a Component's Road Map
Browsing a Component's Change Log
Browsing a Component's Popular Issues
Browsing a Project's Labels
Browsing a Project's Bamboo Builds
Browsing a Project's FishEye Changesets
Browsing a Project's Crucible Reviews
Viewing a Project's Burndown Chart
Customising the Dashboard
97
Atlassian OnDemand October 2011 Documentation
Managing Multiple Dashboard Pages
Changing the Look and Behaviour of a Gadget
Adding the Activity Stream Gadget
Adding the Administration Gadget
Adding the Assigned To Me Gadget
Adding the Average Age Gadget
Adding the Bamboo Charts Gadget
Adding the Bamboo Plan Summary Chart Gadget
Adding the Bamboo Plans Gadget
Adding the Bugzilla ID Search Gadget
Adding the Calendar Gadget
Adding the Clover Coverage Gadget
Adding the Created vs Resolved Gadget
Adding the Crucible Charts Gadget
Adding the Favourite Filters Gadget
Adding the Filter Results Gadget
Adding the FishEye Charts Gadget
Adding the FishEye Recent Changesets Gadget
Adding the In Progress Gadget
Adding the Introduction Gadget
Adding the Issue Statistics Gadget
Adding the JIRA News Gadget
Adding the Pie Chart Gadget
Adding the Projects Gadget
Adding the Quick Links Gadget
Adding the Recently Created Issues Gadget
Adding the Resolution Time Gadget
Adding the Road Map Gadget
Adding the Text Gadget
Adding the Time Since Issues Gadget
Adding the Two-Dimensional Filter Statistics Gadget
Adding the Voted Issues Gadget
Adding the Watched Issues Gadget
Adding the Heat Map Gadget
Adding the Labels Gadget
Managing your User Profile
Adding a User Avatar
Allowing OAuth Access
Changing your Password
Choosing a Language
Using Hover Profile
Choosing a Time Zone
Creating an issue
Issues can only be created when there is at least one project.
Procedure
1. Go to the Issues tab in the top navigation bar.
2. Click Issues >Create Issue, or type c.
In the displayed 'Create Issue' dialog, fill in the issue details.
3. Optional: Customise the dialog to display only the fields you use most often. To do this, click the Configure Fields button and
remove or add fields as you wish. Your settings are saved for future usage automatically.
4. Click the Create button.
Tip: If you want to create multiple issues with similar field values, click the Create another check box before clicking the Create button.
JIRA will then create your issue and automatically pre-populate a new Create Issue dialog box with your previous field values. The
Summary field and attachments are not carried across.
98
Atlassian OnDemand October 2011 Documentation
Related topics
Creating new projects
Creating an Issue (JIRA documentation)
Copy of Creating an issue - page structure
Issues can only be created when there is at least one project.
To create an issue:
1. Go to the Issues tab in the top navigation bar.
2. Click Issues > Create Issue.
3. In the 'Create Issue' screen, select the relevant project and issue type, and then click the 'Next' button.
4. Complete the issue details as required.
5. Click the 'Create' button.
Related topics
Creating new projects
Creating an Issue (JIRA documentation)
Managing agile projects
If your projects use agile methodologies, you can use GreenHopper to manage them. GreenHopper is a JIRA add-on that is purchased
separately from JIRA OnDemand.
Here's how you can use GreenHopper:
Planning Board – where you plan your sprint and organise issues for a sprint
Task Board – the task board typically shows all the work you're undertaking in a sprint
Chart Board – a graphical representation of the progress of ongoing versions
Released Board – gives you access to charts and release notes for the released versions of your projects
99
Atlassian OnDemand October 2011 Documentation
The use of the functionality introduced on this page depends on the purchase of GreenHopper.
On this page:
Moving issues into a sprint
Relating the task board to the default workflow
Transitioning issues along a workflow by drag-and-drop
Moving issues into a sprint
The Planning Board is where you plan your sprint and organise issues into a plan of work for a sprint.
1.
2.
3.
4.
5.
6.
7.
Click the 'Agile' drop-down menu in the top navigation bar and select 'Planning Board'.
In the 'Planning Board' field, select the required project.
In the column at the right of the screen, click the 'Add' link. The 'Add Version' pop-up will appear.
In the 'Version Name' field, type the name of your new sprint version (e.g. 'Sprint 1').
In the 'Parent' field, select your major version (e.g. 'Version 1').
Enter the 'Start Date', 'Release Date' and 'Description' for your new sprint version.
Click the 'Create' button to create the version, then click the 'Create and Close' button to create the version and return to the
Planning Board.
Screenshot: GreenHopper Planning Board
Relating the task board to the default workflow
The Task Board typically contains the following three columns, from left to right, which map to issue statuses.
To Do
In Progress
Done
Open
In Progress
Resolved
Reopened
Closed
For Kanban practitioners, you can set multiple constraints on each of the Task Board columns so that your team can easily visualise and
monitor the progress of your workflow.
Screenshot: The Task Board displaying issue status in columns
100
Atlassian OnDemand October 2011 Documentation
See also:
Adding Constraints to your Task Board Columns (Kanban)
Working with Issues in GreenHopper
Transitioning issues along a workflow by drag-and-drop
On task board, you can transition issues along a workflow by dragging and dropping cards between workflow statuses.
1.
2.
3.
4.
5.
Select your project, click the 'Agile' drop-down menu in the top navigation bar and select Task Board.
In the 'Planning Board' field, select the required project. The 'Task Board' will refresh with information for your project.
In the 'Version' dropdown, select the version which contains issues that you want to transition.
Transition an issue by dragging and dropping the card between the columns on your Task Board.
Complete the transition card, if it displays. Select the desired workflow action. You can also optionally add a comment for this
transition.
6. The issue status will update when you drop in into the destination column.
See also:
Transitioning Issues in GreenHopper
Scheduling and Assigning Issues in GreenHopper
Creating issue comments via emails
When you receive an issue-related email from Atlassian OnDemand, you can comment on the issue by replying to the email directly.
Atlassian OnDemand automatically adds your reply to the email as issue comments.
Issue-related emails are the emails whose subjects include issue keys.
Confluence OnDemand
With Confluence, your team can manage and share information online easily.
Confluence OnDemand, i.e. the Wiki application, is the hosted offering of Confluence. If you are using Confluence OnDemand together with
other OnDemand applications, you will be able to take advantage of a number of preconfigured integration features, such as linking between
applications.
101
Atlassian OnDemand October 2011 Documentation
New to Confluence OnDemand?
Administrators
Getting Started Guide - Confluence
Getting Started Guide - Confluence OnDemand only
Users
Getting Started Guide
Important information
Please note the following important information before you begin using Confluence OnDemand:
Some functions in Confluence OnDemand are restricted for security reasons. Read more about Restricted Functions in Atlassian
OnDemand.
To find out which Confluence version is running in Atlassian OnDemand, see Atlassian OnDemand Application Versions.
Extending Confluence OnDemand
JIRA OnDemand's functionality can be extended further by enabling commercial add-ons provided by Atlassian. See the Atlassian
OnDemand Plugin Policy for instructions on how to order these add-ons. The following add-ons are available:
Team Calendars lets you set up and manage calendars for your teams in Confluence.
Got Team Calendars? Check out the Team Calendars documentation?
About the OnDemand documentation
The Confluence OnDemand documentation links to the documentation for downloadable Confluence extensively. Use the back button on
your browser to return to the OnDemand documentation, if you are directed to the documentation for downloadable Confluence.
Key topics
Administering the Wiki
Configuring Default Space Permissions
Configuring Confluence Plugins
Applying a Theme to a Space
Creating Confluence templates
Confluence Administrator's Guide
Working with the Wiki
Confluence User's Guide
Viewing drafts
Administering the Wiki
Confluence OnDemand, i.e. the Wiki application, is based on Confluence. The administration of Confluence OnDemand is mostly the same
as that of downloadable Confluence except the functions specific to Confluence OnDemand as indicated below and certain restrictions due to
security considerations.
The wiki is a collection of online documents, i.e. pages.
Audience: Administrators
Administration specific to Confluence OnDemand
Page: Configuring Default Space Permissions
102
Atlassian OnDemand October 2011 Documentation
Administering Confluence and add-ons
Confluence
Confluence Administrator's Guide
To know what functions are restricted in Confluence OnDemand compared with downloadable Confluence, refer to Restricted
Functions.
Add-ons
Confluence add-ons do not involve administrative operations and your team can start using them as soon as they are enabled.
Accessing the Wiki administration area
To administer the Wiki application, use the Wiki administration console.
To go to the Wiki administration console:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Wiki tab. The Wiki (Confluence) administration console will display.
Please note, the wiki administration console described above is used for administering the global settings for your wiki
application. If you would like to administer a space, e.g. editing the space details, changing the space theme, configuring the space
permissions, etc, you need to use the 'Space Admin' console. This is accessed by navigating to the desired space and selecting '
Space Admin' from the 'Browse' menu.
Screenshot: Administering Wiki (click to enlarge the image)
Appendix - Administration options in the Wiki application
Category
Functions
Configuration
Global Configuration — Configure your global wiki settings including feature settings, security and privacy,
formatting and international settings, attachment settings and connection timeouts.
Manage Referrers — Manage external referrers for your wiki.
Plugins — Configure, enable and disable Confluence plugins.
Shortcut Links — Add, edit and delete your custom shortcut links.
External Gadgets — Manage gadgets from applications such as Confluence and JIRA, or gadgets from other
websites such as iGoogle.
Global Templates — Create new page templates and manage imported templates for use across your wiki.
Import Templates — Confluence ships with a number of templates and these templates are not available for
use by default. Import these page templates by using this option, and these templates will be available for use
across your wiki or within a specific space.
Spam Prevention — Adjust spam prevention settings, such as Captcha.
Default Space Content — Customise the default content of the home page of a new space.
WebDAV Configuration — Configure WebDAV (file management) for your wiki.
103
Atlassian OnDemand October 2011 Documentation
Permissions
Global Permissions — Manage the permissions assigned to users and user groups for your wiki.
Space Permissions — Manage the permissions assigned to users and user groups for your wiki spaces (for
example, the wiki for each project). You can also set the default space permissions for new spaces.
Configuring Default Space Permissions
You can configure a set of default permissions that are automatically applied to newly created spaces in your wiki.
Then according to the access needs in each space, you can change space permissions for each space separately.
Procedure
1. Accessing the setting for space permissions
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Wiki tab. The Wiki administration console will appear.
3. In the left-hand menu, click Permissions > Space Permissions. The 'Space Permissions' screen will appear. The table under the
'Default Space Permissions' header shows the permissions assigned to user groups by default when a space is created.
Screenshot 1: Viewing space permissions (Click to enlarge the image.)
2. Editing default space permissions
1. Click the Edit Permissions button below the table to edit the default space permissions. The table will display in editable mode.
2. Update the default space permissions as needed and click the Savebutton to save the changes.
Select a check box to grant the permission for a function (column) to a user group (row).
Clear a check box to remove the permission for a function from a user group.
If you do not see the user group to which you want to grant permissions in the table, it means that the user group does not
have the View permission. A user group must have the View permission before it can be granted with other permissions. To
grant the View permission to the user group not listed in the table, enter the name of the user group in the 'Grant browse
permission to' textbox and click the Add button. You can then grant additional permissions to that group by selecting check
boxes in the user group's row.
Tip: Click the magnifying glass icon
Screenshot 2: Editing default space permissions
104
to open the Group Search dialog and search for user groups.
Atlassian OnDemand October 2011 Documentation
Related topics
Assigning Space Permissions (Confluence documentation)
Configuring Confluence Plugins
You can enable and disable plugins and their modules as needed and view the change log of plugins. You can also configure the plugins that
offer configuration options.
Restriction: You cannot install new plugins nor remove existing plugins as per the Atlassian OnDemand Plugin Policy.
Audience: Administrators
Configuring a Confluence Plugin
Disabling or Enabling a Confluence Plugin
Viewing the Confluence Plugin Audit Log
Viewing your Confluence Plugins
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that are shipped with the stand-alone version of the product and included in Atlassian OnDemand. These
plugins are integral to the functioning of the system and cannot be disabled.
User-installed plugins are not included with the stand-alone version of the product and have been bundled with Atlassian
OnDemand. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well,
although modules that are integral to the functioning of the plugin cannot be disabled.
Configuring a Confluence Plugin
A number of Confluence plugins have advanced configuration options. If you have one of these plugins enabled, you can view and update
these configuration options.
Audience: Administrators
Procedure
105
Atlassian OnDemand October 2011 Documentation
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To configure a Confluence plugin:
1. Click the Manage Existing tab.
2. Locate the plugin that you want to configure and click its title.
The plugin details section expands.
3. Click the Configure button for that plugin.
The advanced configuration options appear.
If the plugin is disable, you cannot configure it and so the Configure button does not appear. If there are no
advanced configuration options for the plugin, there is no Configure button.
4. Update the configuration settings as desired and save your changes.
Note: The plugin itself provides advanced configuration options. If you encounter any problems after you click the Configure button,
the plugin is responsible for the issue, not the UPM.
Screenshot: Configuring a plugin
Related topics
Disabling or Enabling a Confluence Plugin
Disabling or Enabling a Confluence Plugin
You can enable and disable Confluence plugins in your Atlassian OnDemand site. With the Safe Mode, you can disable all user-installed
plugins in your site with one click, which might help you diagnose plugin-related problems more easily.
Restriction: You cannot install new plugins nor remove existing plugins as per the Atlassian OnDemand Plugin Policy.
Audience: Administrators
On this page:
Disabling a plugin
Enabling a plugin
Disabling and enabling all user-installed plugins (Safe Mode)
Disabling a plugin
To access the Universal Plugin Manager:
1.
106
Atlassian OnDemand October 2011 Documentation
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To disable a Confluence plugin:
1.
2.
3.
4.
Click the Manage Existing tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon:
Locate the plugin that you want to disable and click the title to expand the plugin details section.
Click the Disable button.
Once a plugin has been disabled, you may need to restart your application for your change to take effect. If so, you will see a
message for the plugin, Disabled, requires restart.
Once the plugin is fully disabled, you will see an Enable link for the plugin.
Screenshot 1: Disabling a plugin
Enabling a plugin
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To enable a Confluence plugin:
1.
2.
3.
4.
Click the Manage Existing tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon:
Locate the plugin that you want to enable and click the title to expand the plugin details section.
Click the Enable button.
Once a plugin has been enabled, you may need to restart your application for your change to take effect. If so, you will see a
message for the plugin, Enabled, requires restart.
Once the plugin is fully disabled, you will see a Disable link for the plugin.
Screenshot 2: Enabling a Plugin
107
Atlassian OnDemand October 2011 Documentation
Disabling and enabling all user-installed plugins (Safe Mode)
Running your application in Safe Mode disables all user installed (i.e. non-system) plugins at once. All plugins that were disabled when you
entered Safe Mode will be re-enabled when you exit Safe Mode.
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To enable Safe Mode:
1. Click the Manage Existing tab.
The system displays a list the installed plugins.
2. Click the Enable Safe Mode link.
3. Click the Continue button in the confirmation window.
All user installed plugins will be disabled and your application will now be running in safe mode.
4. Make changes to your installed plugins as desired.
For example, you may want to enable/disable specific plugins or plugin modules.
5. Exit safe mode by clicking one of the links in the Safe Mode banner:
Click Exit Safe Mode and restore the previous configuration to restore your plugin configuration to its state before you
entered Safe Mode.
Click Exit Safe Mode and keep the current configuration to keep all changes made to your plugin configuration during
Safe Mode.
Screenshot 3: Running Confluence in Safe mode
The Safe Mode is enabled
108
The Enable Safe Mode link
Atlassian OnDemand October 2011 Documentation
Viewing the Confluence Plugin Audit Log
You can check the log for all the plugin activities in your Atlassian OnDemand instance, for example enabling plugins and disabling plugins
and the users who made the changes.
Audience: Administrators
Procedure
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To view the plugin audit log:
1. Click the Audit Log tab.
The plugin audit log appears with a list of the 25 most recent entries.
2. Use the arrows if you want to view older entries.
3. Click the orange RSS icon if you want to receive the audit log activity in an RSS feed.
Screenshot 1: Viewing the plugins audit log
Viewing your Confluence Plugins
This page explains how to view the Confluence plugins and their details in Atlassian OnDemand.
Audience: Administrators
109
Atlassian OnDemand October 2011 Documentation
On this page:
Viewing Confluence plugins
Viewing a plugin's details
Related topics
Viewing Confluence plugins
To access the Universal Plugin Manager:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display.
3. In the left-hand menu, click Configuration > Plugins. The Universal Plugin Manager will appear and display the plugins installed.
To view Confluence plugins:
Click the Manage Existing tab to list the plugins installed in your application. The application groups plugins into User-installed Plugins and
System Plugins. The System Plugins are hidden by default. Use the following actions when working with the plugin list:
Enter keywords in the Filter visible plugins text box to filter the list.
Click the Show System Plugins link to see the hidden system plugins.
Click the name of a plugin to view the plugins details.
Click Enable Safe Mode to run your application in safe mode. This mode disables all user installed plugins.
Enabled plugins have this icon
, and this icon
indicates disabled plugins.
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that are shipped with the stand-alone version of the product and included in Atlassian OnDemand. These
plugins are integral to the functioning of the system and cannot be disabled.
User-installed plugins are not included with the stand-alone version of the product and have been bundled with Atlassian
OnDemand. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well,
although modules that are integral to the functioning of the plugin cannot be disabled.
Screenshot 1: Viewing plugins (Confluence)
110
Atlassian OnDemand October 2011 Documentation
Viewing a plugin's details
You can view the details for a plugin when you click the name of a plugin in the installed plugins list. The summary contains a short
description of the plugin as well as buttons and links for plugin operations and related information.
Screenshot 2: Viewing a plugin's details
111
Atlassian OnDemand October 2011 Documentation
Plugin key – A unique key the identifies each plugin in the system.
Developer – The name of the plugin developer and a link to the developer's homepage, if provided by the plugin developer.
Plugin version – The version of the plugin currently installed.
Manage plugin modules — Click this link to display the plugin modules below the plugin summary. A module is a component of the
plugin. This link will only appear if the plugin has modules. If you want to enable or disable a plugin module, hover your mouse over
the module and click the 'Enable'/'Disable' button for that module.
Plugin details – Click this link to display the plugin information on the Atlassian Plugin Exchange.
Configure – Click this link to display the configuration settings for the plugin in the Universal Plugin Manager. This link will be
disabled if the plugin is disabled. Please note that not all plugins have settings that can be configured through the Universal Plugin
Manager.
Disable – Click this button to disable the plugin in your application. This button will only appear if the plugin is enabled.
Enable – Click this button to enable the plugin in your application. This button will only appear if the plugin is disabled.
Related topics
Configuring a Confluence Plugin
Disabling or Enabling a Confluence Plugin
Applying a Theme to a Space
Themes allow you to personalise the 'look and feel' of Confluence OnDemand. You can apply a theme to each of your wiki spaces. Choose a
specific theme to provide specific functionality or to significantly alter the appearance of your wiki.
You need to be a space administrator to edit the look and feel of a space.
On this page:
Themes in Confluence OnDemand
Applying a theme to a space
Customising the Atlassian OnDemand Documentation Theme
Related topics
Themes in Confluence OnDemand
Confluence OnDemand comes with a selection of themes:
Theme
112
Features
Atlassian OnDemand October 2011 Documentation
Default Theme
This is the default look and feel of all OnDemand spaces. Using this theme enables you to customise the colour
scheme and layout for individual spaces.
Atlassian
OnDemand
Theme
This theme features a cross-application navigation bar, which contains tabs for easy access to your Issues, Wiki,
Source, Reviews, and Builds functionality.
Atlassian
OnDemand
Documentation
Theme
You can configure this theme to include a collapsible left navigation sidebar, custom sidebar links, and header and
footer text. The sidebar contains a collapsible navigation tree that can be used to browse through the space. Your wiki
will retain the Atlassian OnDemand header, along with any custom logos you have uploaded.
Please see Customising the Atlassian OnDemand Documentation Theme below for instructions and examples of how
to tailor this theme to your needs.
Applying a theme to a space
Procedure
1.
2.
3.
4.
5.
Log into as an administrator. In the navigation bar, click the Wiki tab. The wiki dashboard appears.
Select your desired space. The homepage for the space will display.
In the top right corner of the wiki, click Browse > Space Admin. The 'Space Administration' console for your space will display.
In the Look and Feel area of the left-hand menu, select Themes. The current theme and themes available for selection will display.
Click the radio button next to your required theme, and then click the Confirm button to select this theme.
Customising the Atlassian OnDemand Documentation Theme
Procedure
1.
2.
3.
4.
5.
Log in as an administrator. In the navigation bar, click the Wiki tab. The wiki dashboard appears.
Select your desired space. The homepage for the space will display.
In the top right corner of the wiki, click Browse > Space Admin. The 'Space Administration' console for your space will display.
In the Look and Feel area of the left-hand menu, select Themes. The current theme and themes available for selection will display.
Select the Atlassian OnDemand Documentation Theme, and then click the Confirm button to select this theme. This theme will
be displayed as the current theme and you will see the Configure theme option under the theme.
6. Select Configure Theme to customise the theme, for example, by providing header and footer messages, or links.
Screenshot 1: Configuring your Documentation Theme (click to enlarge images)
Customising the Documentation Theme
Effects of the theme customisation
Related topics
Customising Look and Feel (Confluence documentation)
Creating Confluence templates
A template is a Confluence page with predefined content and can be used as a prototype when creating new pages. Templates are handy to
113
Atlassian OnDemand October 2011 Documentation
use for giving pages a common style or format.
Global templates are available in every space across the site. Only Confluence administrators can create global templates.
Space templates are only available in the space in which they are defined. Both Confluence administrators and space
administrators can create space templates.
Procedure
1. Go to the 'Create Template' page.
To add space templates, go to Browse > Advanced in any place of your space. Then, in the left-hand panel, click
Templates and then click the Add New Space Template link.
To add global templates, go to Browse > Confluence Admin. Then, under the Configuration section of the left-hand
panel, click Global Templates and then click the Add New Space Template link.
2. The 'Create Template' page appears. Enter a name for your template in the Name field and an optional description in the
Description field.
3. Using regular Wiki Markup and form field markup (if you are using forms), enter content in the text-entry box as you would in any
other page.
Related topics
Global Templates (Confluence)
Confluence Administrator's Guide
Atlassian OnDemand includes Confluence 4.1 for its wiki. Use the search or click any of the links below to view the relevant page in the
Confluence Administrator's Guide. You will need to use the 'Back' button on your browser to return to the Confluence OnDemand
documentation.
Please note, some Confluence functionality is restricted in Confluence OnDemand.
Search the Confluence 4.1 documentation:
Only available in when using Confluence OnDemand without other OnDemand applications.
Configuring Confluence
Site Configuration
Configuring the Site Home Page
Configuring the Administrator Contact Page
Editing the Site Title
Editing the Global Logo
Customising Default Space Content
Configuring the Destination of View Space Links
Editing the Site Welcome Message
Configuring the What's New Dialog
Optional Settings
Configuring a WebDAV client for Confluence
Enabling OpenSearch
Enabling the Did You Mean Feature
Enabling the Remote API — Enabled by default
Enabling Threaded Comments
Enabling Trackback
Other Settings
Configuring Attachment Size
Configuring Character Encoding
Configuring HTTP Timeout Settings
Configuring Indexing Language
Configuring Number Formats
Configuring Shortcut Links
Configuring Time and Date Formats
Configuring Confluence Security
Enabling or Disabling Public Signup
Managing External Referrers
Excluding external referrers
Hiding external referrers
Ignoring External Referrers
Configuring Captcha for Spam Prevention
Hiding External Links From Search Engines
Configuring XSRF Protection — Enabled and cannot be disabled
Anonymous Access to Remote API
114
Atlassian OnDemand October 2011 Documentation
Design and Layout
Customising Look and Feel Overview — Custom layouts are not permitted.
Customising Colour Schemes
Global Templates
Importing Templates
Customising PDF or HTML Content
Themes Overview
Applying a Theme to a Site
Customising the Left Navigation Theme
Installing Plugins and Macros
Installing and Configuring Plugins using the Universal Plugin Manager — Can only view, enable and disable plugins.
Configuring a Plugin
Disabling or Enabling a Plugin
Viewing the Plugin Audit Log
Viewing your Installed Plugins
Configuring the Office Connector
User Management
Understanding User Management in Confluence
Confluence User Management
Searching For and Managing Users
Adding a New User
Adding a Group
Adding or Removing Users in Groups
Changing Usernames
Editing User Details
Global Groups Overview
Global Permissions Overview
Removing a Group
Removing or Deactivating a User
Setting up Anonymous Access
Viewing members of a group
Resetting the Login Count for a User
Working with the Wiki
Confluence OnDemand, i.e. the Wiki application, is based on Confluence.
The wiki is a collection of online documents, i.e. pages. A space is a group of pages within the wiki. You can think of each space as a
sub-site, or mini-site, each with its own home page.
In Atlassian OnDemand, a space can be associated with a project. This allows links to be automatically created on your wiki pages, pointing
to associated issues, source files, changesets and code reviews.
Audience: Users
A few things to get started
Add a page
Add a blog post
Add a space
Using Confluence and add-ons
Confluence
Confluence User's Guide
Add-ons
Depending on what add-ons your administrator enabled for your site, your issues application may also include the following additional
features:
Team Calendars
Balsamiq Mockups for JIRA User Guide
Gliffy
115
Atlassian OnDemand October 2011 Documentation
Accessing the Wiki application
To access the Wiki application and work with pages:
1. Click the Wiki tab in the navigation bar. This takes you to Confluence.
Confluence User's Guide
Atlassian OnDemand includes Confluence 4.1 for its wiki. Use the search or click any of the links below to view the relevant page in the
Confluence User's Guide. You will need to use the 'Back' button on your browser to return to the Confluence OnDemand documentation.
Please note, some Confluence functionality is restricted in Confluence OnDemand.
Search the Confluence 4.1 documentation:
Getting Started
Dashboard
Page in View Mode
Confluence Glossary
Confluence Icons
Keyboard Shortcuts
Creating Content
Using the Editor
Working with Text Effects
Working with Links
Linking to Personal Spaces and User Profiles
Linking from an Image
Using a Link to Create a New Email Message
Linking to Attachments
Working with Anchors
Linking to Confluence Pages from Outside Confluence
Trackback
Editing and Removing Links
Linking to Pages
Linking to Blog Posts
Linking to Images
Working with Drafts
Configuring the Time Interval at which Drafts are Saved
Concurrent Editing and Merging Changes
Resuming the Editing of a Draft
Recording Change Comments
Using Images
Displaying Images
Image File Formats
Using Autocomplete
Using Special Characters
Inserting Emoticons and Icons
Inserting Symbols
Working with the Macro Browser
Inserting JIRA Issues
Adding a Page
Adding a Blog Post
Working with Tables
Working with Templates
Adding a Template
Creating a Page using a Template
Editing a template
Removing a Template
Confluence Wiki Markup
Form Field Markup for Templates
Working with the Office Connector
Office Connector Prerequisites
Displaying Office Files in Confluence
Importing an Office Document into Confluence
Editing an Office Document from Confluence
Editing an Office Spreadsheet from Confluence
Editing an Office Presentation from Confluence
Installing the Firefox Add-On for the Office Connector
116
Atlassian OnDemand October 2011 Documentation
Sharing Content
Network Overview
Subscribing to a Network RSS Feed
User Status Updates
Using Mentions
Watching Changes
Tracking Updates to Confluence Pages and Spaces
Subscribing to Email Notifications of Updates to Confluence Content
Watching a Page or Blog Post
Watching a Space
Managing Watchers
Subscribing to RSS Feeds within Confluence
Using pre-specified RSS feeds
Using the RSS Feed Builder
Working with RSS Feeds
RSS Readers Compatibility
Searching Confluence
Confluence Search Fields
Confluence Search Syntax
Ranking of Search Results
Searching the People Directory
Text Tokenisation and Filtering
Organising Content
Working with Pages
Moving a Page
Working with Page Families
Viewing a Page's Family
Setting a Page Family to Alphabetical Order
Using the Documentation Theme
Sequential Order of Pages
Viewing Page Information
Copying a Page
Working with Comments
Adding a Comment
Deleting Comments
Editing a Comment
Linking to Comments
Recently Viewed Content
E-mailing a Page
Renaming a Page
Deleting a Page
Purging Deleted Pages
Restoring a Deleted Page
Page History and Page Comparison Views
Restoring an Older Version of a Page
Viewing an Older Version of a Page
Using a WebDAV Client to Work with Pages
Working with Blog Posts
Deleting Blog Posts
Editing Blog Posts
Viewing Blog Posts
Working with Spaces
Viewing Space Activity
Viewing All Confluence Spaces
Administering Spaces
Deleting a Space
Setting up a New Global Space
Setting up your Personal Space
Exporting Confluence Pages and Spaces to Other Formats
Exporting Confluence Pages and Spaces to HTML
Exporting Confluence Pages and Spaces to PDF
Customising Exports to PDF
Advanced PDF Export Customisations
Creating PDF in Another Language
Exporting to a Word document
Exporting Confluence Pages and Spaces to XML
Browsing a space
Editing Space Details
Managing Orphaned Pages
Managing Undefined Pages
Viewing Hierarchy of Pages within a Space
117
Atlassian OnDemand October 2011 Documentation
Viewing Pages Alphabetically
Viewing Recently Updated Content
Viewing Space Details
Space Backup and Restore
Archiving Mail Overview
Adding a Mail Account
Deleting Mail
Fetching Mail
Importing Mail
Managing Mail Accounts
Restoring Mail
Viewing Mail
Working with Labels
Adding a Global Label
Adding a Personal Label
Using Labels to Categorise Spaces
Navigating Pages by Label
Removing a Label from a Page
Using Label Macros to Categorise Wiki Content
Content by Label Macro
Labels List Macro
Navigation Map Macro
Popular Labels Macro
Recently Used Labels Macro
Related Labels Macro
Viewing Global Labels
Viewing labelled pages
Viewing personal labels
Viewing Popular Labels
Working with Favourites
Adding Favourites
Removing Favourites
Viewing Favourites
Working with Attachments
Using Drag-and-Drop in Confluence
Attaching Files to a Page
Attachment Versions
Deleting an Attachment
Displaying a List of Attachments in a Page
Downloading Attachments
Editing Attachment Properties
Embedding Multimedia Content
Embedding PowerPoint Presentations in a Page
Finding an Attachment
Moving an Attachment
Choose a Page
Viewing Attachment Details
Customising Confluence
Personal Customisations
User Profile Overview — Note, user profile configuration is available under Profile -> Wiki Profile
Changing Password
Editing User Settings
Editing Your User Profile
Email Address Privacy
Updating Email Address
Choosing a Profile Picture
Deleting a Profile Picture
Viewing User Profile
Viewing and Revoking OAuth Access Tokens
Choosing Your Homepage
Customising your Personal Dashboard
Customising Look and Feel
Applying a Theme to a Space
Configuring the Documentation Theme
Configuring the Easy Reader Theme
Changing a Space's Logo
Changing the Confluence Browser Icon, aka favicon
Choosing Your Homepage
Customising Space Layouts
Editing a Space's Colour Scheme
Styling Confluence with CSS
Basic Styling Tutorial
Styling Fonts in Confluence
Styling Tabs in Confluence
Using CSS to Customise the Easy Reader Theme
Customising your Personal Dashboard
Permissions Overview
Page Restrictions
118
Atlassian OnDemand October 2011 Documentation
Inaccessible Page
Setting a Page's Restrictions
Viewing a Page's Restrictions
Site Administrators and their Permissions
Contacting Confluence Administrators
Space Administrators and their Permissions
Space Permissions Overview
Assigning Space Permissions
Revoking Space Permissions
Viewing Space Permissions
Users and Groups
Searching for Users
Viewing Restricted Pages
Working with Confluence Gadgets
Adding a Confluence Gadget to a JIRA Dashboard
Configuring Confluence Gadgets for Use in Other Applications
Confluence Gadgets
Activity Stream Gadget
Confluence News Gadget
Confluence Page Gadget
Confluence Quicknav Gadget
Adding JIRA Gadgets to a Confluence Page
Working with Macros
Anchor Macro
Attachments Macro
Blog Posts Macro
Change-History Macro
Chart Macro
Cheese Macro
Children Display Macro
Code Block Macro
Column Macro
Content by User Macro
Contributors Macro
Contributors Summary Macro
Create Space Button Macro
Excerpt Include Macro
Excerpt Macro
Expand Macro
Favourite Pages Macro
Gadget Macro
Gallery Macro
Global Reports Macro
HTML Include Macro
HTML Macro
IM Presence Macro
Include Page Macro
Info Macro
JIRA Issues Macro
JIRA Macro
JIRA Portlet Macro
JUnit Report Macro
Livesearch Macro
Loremipsum Macro
Metadata Macro
Detailssummary Macro
Multimedia Macro
Network Macro
Noformat Macro
Note Macro
Page Index Macro
Page Tree Macro
Page Tree Search Macro
Panel Macro
User Profile Macro
Recently Updated Dashboard Macro
Recently Updated Macro
RSS Feed Macro
Search Results Macro
Section Macro
Space Details Macro
Space Jump Macro
Spaces List Macro
Status Macro
Table of Contents Macro
Table of Content Zone Macro
Tasklist Macro
Tip Macro
User List Macro
User Status List Macro
119
Atlassian OnDemand October 2011 Documentation
View File Macro
Warning Macro
Widget Connector Macro
Widget Connector Examples
Guides to Specific Uses of Confluence
Developing Technical Documentation on Confluence Wiki
Creating your Technical Documentation Space
Using Templates in Technical Documentation
Re-using Content in Technical Documentation
Managing the Life Cycle of your Technical Documentation
Providing PDF Versions of your Technical Documentation
Exporting and Printing Technical Documentation
Essential Confluence Features for Technical Documentation
Confluence Plugins for Technical Documentation
Further Reading about Developing Technical Documentation on Confluence
Developing a Knowledge Base on Confluence Wiki
Creating Your Knowledge Base Space
Using Templates and Formatting Macros in a Knowledge Base
Proactive Communications in a Knowledge Base
Additional Plugins for a Knowledge Base
Developing an Intranet on Confluence Wiki
Viewing drafts
If your site has multiple applications that include the Wiki (Confluence), use the following instructions to access your wiki drafts.
Procedure
1. Log in to your site.
2. On the Wiki tab, go to Browse > User Settings.
3. On the displayed page, go to the Drafts tab to see your draft pages.
Screenshot: Navigating to User Settings in the Wiki tab
Source and Review Bundle
The Source and Review bundle consists of FishEye, Crucible and the integrated Subversion. FishEye and Crucible provide source repository
browsing and code reviews to your software development teams to improve code quality and the speed of development.
FishEye OnDemand, i.e. the Source application, and Crucible OnDemand, i.e. the Reviews application, are the hosted offerings of FishEye
and Crucible. If you are using Fisheye OnDemand and Crucible OnDemand together with other OnDemand applications, you will be able to
take advantage of a number of preconfigured integration features, such as linking between applications
New to FishEye OnDemand/Crucible OnDemand?
Administrators
Getting Started Guide
Users
Getting Started Guide
Important information
120
Atlassian OnDemand October 2011 Documentation
Please note the following important information before you begin using FishEye OnDemand/Crucible OnDemand:
Some functions in FishEye OnDemand and Crucible OnDemand are restricted for security reasons. Read more about Restricted
Functions in Atlassian OnDemand.
To find out which FishEye version and Crucible version is running in Atlassian OnDemand, see Atlassian OnDemand Application
Versions.
About the OnDemand documentation
The FishEye OnDemand/Crucible OnDemand documentation link to the documentation for downloadable FishEye/Crucible extensively. Use
the back button on your browser to return to the OnDemand documentation, if you are directed to the documentation for downloadable
FishEye/Crucible.
Key topics
Administering Reviews
Administering Source
Configuring commits to require a JIRA issue key
Configuring repository permissions
Working with Reviews
Crucible User's Guide
Working with Source
FishEye User's Guide
Checking changesets committed against an issue
Working with the Repository
.
Administering Reviews
The permissions of Crucible, i.e. the Reviews application, inherit that of the Source application. This means that the same read and commit
permissions that apply to a project's source also apply to that project's reviews.
About reviews: Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after
being committed to a repository.
Audience: Administrators
For information on how to set up permissions for your source, refer to Administering Source.
Administering Reviews
Configuring review permissions
The permissions of reviews inherit that of the source repository of a given project. See Administering Source.
Configuring review settings
You can configure the default reviewers and moderators for a project, as well as the default review duration. To to this, go to the Reviews
administration area and select the appropriate setting:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Reviews tab. The Reviews administration console will appear. Each of the administration options for your 'Reviews'
application are divided into the categories listed below.
121
Category
Functions
Review Defaults
Configure the default settings for new reviews for your projects individually.
New Project Defaults
Select the default review period, and specify if a moderator is required
Atlassian OnDemand October 2011 Documentation
Defect Classifications
Customise the defect classifications for your reviews.
Screenshot: Administering Reviews
Administering Source
The Source application is based on FishEye and includes the integrated Subversion. There is no configuration required on the part of
administrations for your team to start using the Source application. The administration options help you control access to your source and
provides additional integration functionality with JIRA OnDemand.
Audience: Administrators
Administering Source
Configuring commits to require a JIRA issue key
Configuring repository permissions
Accessing the Source administration area
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Source tab. The Source administration console will appear.
Screenshot: Administering Source (Click to enlarge)
Related topics
Administering Reviews
122
Atlassian OnDemand October 2011 Documentation
Administering Issues
Configuring commits to require a JIRA issue key
As an administrator, you can configure commits to be associated with an open JIRA issue key. If this functionality is enabled, a commit will
not be successful unless it includes an open JIRA issue key. An open JIRA issue key is an issue key that has not been resolved.
To require commits to include a JIRA issue key:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the 'Source' tab. The Source administration console will display.
3. Click the 'SVN Commit Hooks' option in the left menu. The 'SVN Commit Hooks' page will display.
4. Select the checkbox, 'Require JIRA issue key for a successful commit'.
5. Click 'Save'.
Screenshot: Configuring SVN Commit Hooks
Related topics
Creating links to JIRA issue keys
Configuring repository permissions
Repository permissions are applied to Subversion repositories, and control the permissions of both the source and review applications.
Repository permissions can be assigned to user groups only, not to individual users. If you want to assign a repository permission to a
particular user, you need to add the user to a user group with the desired permission.
Audience: Administrators
Permission management in other apps:
Managing application permissions
Permissions levels
There are two levels of repository permissions: read and commit.
In your source – FishEye and Subversion:
The read permissions controls if a user group can view the source code in a directory
The commit permission controls if a user group can commit changes to the directory, i.e. read and write.
In your reviews – Crucible:
These two levels of permissions apply to a project's reviews as follows:
commit: A user group must have this permission to be able to create reviews.
read: A user group must have this permission to be able to participate in reviews, i.e. reviewing code.
Initial setup in your site
The initial setup of your Atlassian OnDemand site assigns read permission to the 'users' group and commit permission to the '
developers' and 'administrators' groups. For more information about the default permission settings, refer to Managing Users and
Groups.
123
Atlassian OnDemand October 2011 Documentation
How to configure
Project-specific permissions overwrite the default permissions.
Configuring repository permissions for a project
Configuring default repository permissions
Enabling Anonymous Access to a Repository
Configuring repository permissions for a project
You can configure the permissions for a project's source repository at the project level or at the path level for specific directories. Subversion
permissions can be assigned to user groups only, but not to individual users. If you want to assign a repository permission to a particular
user, you can add the user to a user group with the desired permission.
Audience: Administrators
On this page:
Configuring repository permissions at the project level
Configuring repository permissions at the path level
More options on the SVN Permission Manager page
Related topics
Configuring repository permissions at the project level
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Source tab. The Source administration console will display.
3. Click the Project Permissions option in the left menu. The 'SVN Permission Manager' page will display, listing all projects that you
have permission to administer.
4. Click the Configure link next to the project that you wish to update the permissions for.The 'Manage Repository' page will display
(see screenshot below).
The 'Read' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The 'Commit'
panel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository.
5. Configure permissions as needed.
To grant permissions to a group, select the group in the Group drop-down list under the appropriate panel, and click the
Add button. Note that a user group does not need to have the 'Read' permission, if it has been granted the 'Commit'
permission.
To remove a permission from a user group, click the remove link next to the user group. Note that removing the 'Commit'
permission from a user group will remove both read and write access from the user group. If you want to retain the group's
read access, you will need to grant the 'Read' permission to the group.
Anonymous access to a project's repository is disabled by default. You can enable anonymous access to a repository via the
administration console. For instructions on how to do this, refer to Enabling Anonymous Access to a Repository.
Screenshot 1: Subversion Permission Manager
124
Atlassian OnDemand October 2011 Documentation
Configuring repository permissions at the path level
Branches do not inherit path permissions
If you have set up path-level permissions for a specific path in your Subversion repository (e.g. /DOM/trunk/private)
and then create a branch of that path (e.g. /DOM/branches/branch1/private), the branch will not inherit the
path-level permissions. You must set up the path-level permissions for the branch separately.
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Go to Source > Project Permissions. The 'SVN Permission Manager' page will display, listing all projects that you have the
permission to administer.
3. In the Modify commit permissions for an arbitrary path text box, enter the path of the directory that you want to configure
permissions for, and click Add.
The 'Manage Permissions for Path' page will display (see screenshot 2 below). The permissions shown will be inherited from the
parent or project in the repository hierarchy, unless explicitly overridden.
If a user group has the 'Read Only' permission, users in the group can access the path but not commit to the path. Read
only permission may have been inherited from the parent or project in the repository hierarchy, or explicitly
granted/overridden.
If a user group has the 'Commit' permission, users in the group will be able to commit to the path.
4. Modify the path permissions as needed.
To add path permissions to a user group,
a. In Add Permission section, select the desired user group in the first drop-down list and the permission in the
second drop-down list.
b. Click the Add button. The path permissions will be added.
To change the existing path permissions for a user group,
a. In the Permissions section, locate the group and select the path permission under the Actual column.
b. Click the Save button. The path permissions will be updated.
To remove an existing path permission for a user group,
a. In the Permissions section, locate the group and select the check box under the Remove column.
b. Click the Save button. The path permissions will be removed.
Path permission changes may take a few minutes to take effect due to caching.
Screenshot 2 : Managing repository permissions for a path
More options on the SVN Permission Manager page
The 'SVN Permission Manager' page also contains two other links as shown in the following screenshot:
Synchronise FishEye permissions— this link will set your FishEye permissions to be the same as your Subversion permissions.
You should not have to use this function, except on advice from the Atlassian Support team.
Modify settings applied to new projects — this link takes you to the Configuring default repository permissions page.
Screenshot 3 : Managing repository permissions for a path
125
Atlassian OnDemand October 2011 Documentation
Related topics
Configuring default repository permissions
Configuring default repository permissions
Default repository permissions apply to Subversion repositories of any new projects created.
To override the default permissions, you can modify repository permissions at the project level for each your projects individually. Read more
about configuring repository permissions for a project.
Audience: Administrators
Overview of repository permissions:
Configuring repository permissions
Procedure
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Source tab. The Source administration console will appear.
3. In the left-hand menu, click the Default Permissions option. The 'Manage Default Repository Permissions' page will display (see
screenshot below).
The 'Read' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The 'Commit'
panel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository.
4. Configure permissions as needed.
To grant permissions to a group, select the group in the Group drop-down list under the appropriate panel, and click the
Add button. Note, that a user group does not need to be the 'Read' permission, if it has been granted the 'Commit'
permission.
To remove a permission from a user group, click the remove link next to the user group. Note, that removing the 'Commit'
permission from a user group will remove read and write access from the user group. You will need to add the 'Read'
permission to the user group, if you still wish the user group to retain read access to your repository.
Anonymous access to your project repository is disabled by default. You can enable anonymous access to your repository by following
instructions in the Enabling Anonymous Access to a Repository page.
Screenshot: Manage Default Repository Permissions
126
Atlassian OnDemand October 2011 Documentation
Related topics
Configuring repository permissions for a project
Enabling Anonymous Access to a Repository
You can configure your project source directories to be anonymously accessible. By default, anonymous access is disabled. If anonymous
access is enabled, anonymous users will be granted read-only access to the project repository (e.g. allowing code checkouts, exports, etc),
and they will be able to access the Source tab in your site.
Anonymous repository access can be enabled for each individual project. You can also enable anonymous repository access for all new
projects created.
Audience: Administrators
You cannot enable or disable anonymous access globally for all projects. You must change this setting for each project separately.
Enabling anonymous repository access for a project
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Source tab. The Source administration console will appear.
3. Click the Project Permissions option in the left menu. The 'SVN Permission Manager' page will display, listing all projects that you
have permission to administer.
4. Click the Configure link next to the project that you wish to enable anonymous repository access for. The 'Manage Repository'
page will display.
5. Click Enable anonymous access to enable anonymous access to the project. This will override your global preferences for
anonymous repository access.
Enabling anonymous repository access for all new projects
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Source tab. The Source administration console will appear.
3. Click the Default Permissions option in the left menu.
4. Click Enable anonymous access to enable anonymous access for all new project repositories.
Related topics
127
Atlassian OnDemand October 2011 Documentation
Managing anonymous access
Working with Reviews
Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being
committed to a repository.
Audience: Users
Using Crucible
Crucible User's Guide
Accessing the Reviews application
To work on code reviews, e.g. creating and participating in reviews, use the ’Reviews' application.
To access the Reviews application:
1. Click the Reviews tab in the navigation bar. This takes you to Crucible.
Crucible User's Guide
Atlassian OnDemand includes Crucible 2.7 for code reviews. Use the search or click any of the links below to view the relevant page in the
Crucible User's Guide. You will need to use the 'Back' button on your browser to return to the Crucible OnDemand documentation.
Please note, some Crucible functionality is restricted in Crucible OnDemand.
Search the Crucible 2.7 documentation:
Getting Started with Crucible
Using the Crucible Screens
Browsing All Reviews
Browsing Source Files
Using the Dashboard
Browsing Your Reviews
Browsing Reviews, Source and Issues Activity
Viewing Your Favourites
Crucible Icons
Searching in Crucible
Viewing People's Statistics
Browsing Projects
Viewing Project Statistics
Viewing Reports
Review Coverage Report
Changeset Discussions
Changing your User Profile
Roles and Status Classifications
Conducting a Review
Creating a Review
Creating a Patch Review
Creating a Review within Crucible
Creating a Review from FishEye
Creating a Review from JIRA
Creating a Review from a URL
Creating a Snippet Review
Selecting the Files for the Review
Iterative Reviews
Adding Reviewers
Issuing a Review
128
Atlassian OnDemand October 2011 Documentation
Performing the Review
Adding Comments
Flagging Defects
Completing your Review
Sending a Review's Comments via Email
Using JIRA Integration in Crucible Reviews
Using the Review History Dialog
Tracking Crucible Review Metrics
Using Progress Tracking
Using Time Tracking
Summarising and Closing the Review
Moving a Review to Another Project
Deleting an Abandoned Review
Defining your Workflow
Using Favourites
Using Keyboard Shortcuts in Crucible
Using RSS Feeds in Crucible
Using Wiki Markup in Crucible
Using Gadgets in Crucible
Working with Source
The Source application is based on FishEye and includes the integrated Subversion. With FishEye, you can easily browse and search your
source repository.
Audience: Users
Using FishEye
FishEye User's Guide
Checking changesets committed against an issue
Accessing the Source application
To access the Source application and work with your source code:
1. Click the Source tab in the navigation bar. This takes you to FishEye.
FishEye User's Guide
Atlassian OnDemand includes FishEye 2.7 for browsing source code. Use the search or click any of the links below to view the relevant
page in the FishEye User's Guide. You will need to use the 'Back' button on your browser to return to the FishEye OnDemand
documentation.
Please note, some FishEye functionality is restricted in FishEye OnDemand.
Search the FishEye 2.7 documentation:
Using the FishEye Screens
Browsing through a Repository
Searching the Repository
Viewing a File
Viewing File Content
Using Side by Side Diff View
Viewing a File History
Viewing the Changelog
Copying and Pasting Code from FishEye
FishEye Charts
Using Favourites
Changeset Discussions
Viewing People's Statistics
129
Atlassian OnDemand October 2011 Documentation
Changing your User Profile
Antglob Reference Guide
Date Expressions Reference Guide
EyeQL Reference Guide
Checking changesets committed against an issue
You can view changesets committed against a particular issue in JIRA if the commit messages have included the JIRA issue key.
Procedure
1. Locate the issue.
2. In the Activity area of the issue, go to the Source. You will see the changesets committed against the issue:
who committed the code
what changes were made
comments associated with the change
Related topics
Using Smart Commits
Working with the Repository
The Subversion repository in the Source and Review bundle contains your source code. To work with the repository, you can either access
the files directly using the Subversion command-line client or use an IDE (integrated development environment).
On this page:
Using the Subversion command-line client
Using an IDE
Using the Subversion command-line client
Subversion has a wide range of functions available via its command-line client. The following section describes how to use some of the more
commonly used commands in Subversion.
Checking out a working copy
Checking out a project is typically the first step in working with your source repository. This will create a local working copy of the project on
your machine.
To check out a working copy
1. Open a Subversion command-line client.
2. Enter the following command:
svn checkout https://<account_name>.atlassian.net/svn/<project_key>/trunk
where <account> is the account name that you provided at signup and <project_key> is the key of the project that you defined
at project creation.
Enter the username only, i.e. if your Google Apps login is 'fred@googleappscomain.com', then simply supply the username '
fred'.
If you wish, you can check out a particular Subversion directory in your project (e.g. a branch of code), by specifying
<project_key>/<directory_name> instead of <project_name>/trunk.
3. A confirmation message will be displayed at the end of a successful checkout, e.g. 'Checked out revision 1001'.
Updating your working copy
Before you begin making changes to your working copy, it is highly recommended that you update your working copy with changes that other
users (with access to the repository) may have committed.
To update your working copy
1. Open a Subversion command-line client.
2. Enter the following command:
svn update
3. A confirmation message will be displayed at the end of a successful update, e.g. 'Updated to revision 2442.', as well as the list of
files updated in your working copy.
130
Atlassian OnDemand October 2011 Documentation
Committing changes to the repository
Once you have finished making changes to your working copy, you can commit your changes to the repository by using the svn commit
command.
To commit changes to your Subversion project
1. Open a Subversion command-line client.
2. Enter the following command:
svn commit -m "<commit_message>"
where <commit_message> is the description of your changes for this commit. This description will be recorded against the commit
in the repository.
3. A confirmation message will be displayed at the end of a successful commit, e.g. 'Committed revision 932'.
Other useful Subversion commands
The table below lists other commonly used Subversion commands in a basic work cycle.
SVN help
Help on every command is integrated into Subversion. For further information on the commands below, try entering svn help
<command>.
e.g. svn help checkout
Command
Description
svn add
Add a new item (i.e. file or directory) to your repository.
svn copy
Copy an item and add the new copied item to your repository.
svn
delete
Delete an item from both your working copy and repository.
svn move
Copy an item and delete the original in your working copy and repository.
svn
status
Determine what changes (at the file/directory level) have been made to your working copy.
svn diff
Display what has changed in each file that has been modified (i.e. the 'difference' between your modified file and the
original).
svn
revert
Revert the working copy, removing all changes.
Using an IDE
The steps required to configure an IDE with a source repository vary depending on which IDE you are using. Usually, you need to provide the
following repository details when configuring the IDE:
Location of your repository — that is, https://<account_name>.atlassian.net, where <account> is the account name that
you provided at signup
The Username and Password that you use to access your source repository — these will be the same details that you use to
access your Atlassian OnDemand site.
For instructions on configuring your source repository and working with your source repository, refer to your IDE documentation.
Many thanks to Collins-Sussman, Fitzpatrick and Pilato whose book 'Version Control with Subversion' (2007) provided much of the content for this page. Adapting
material from this book is permitted under the work's license — read the license details.
Bamboo OnDemand
Bamboo OnDemand, i.e. the Builds application, is the hosted offering of Bamboo. If you are using Bamboo OnDemand together with other
OnDemand applications, you will be able to take advantage of a number of preconfigured integration features, such as linking between
applications.
131
Atlassian OnDemand October 2011 Documentation
New to Bamboo OnDemand?
Administrators
Getting Started Guide
Users
Getting Started Guide
Important information
Please note the following important information before you begin using Bamboo OnDemand:
Some functions in Bamboo OnDemand are restricted for security reasons. Read more about Restricted Functions in Atlassian
OnDemand.
To find out which Bamboo version is running in Atlassian OnDemand, see Atlassian OnDemand Application Versions.
About the OnDemand documentation
The Bamboo OnDemand documentation links to the documentation for downloadable Bamboo extensively. Use the back button on your
browser to return to the OnDemand documentation, if you are directed to the documentation for downloadable Bamboo.
Key topics
Administering Builds
Integrating Builds with your Issues Workflow
Bamboo Administrator's Guide
Working with Builds
Bamboo User's Guide
Actioning Issues via Builds
Administering Builds
The source in your repository can be built by the 'Builds' application (Bamboo).
and, you must have an Amazon account and input your account information in Bamboo.
New to Bamboo OnDemand?
Getting started with Bamboo OnDemand
How Bamboo OnDemand builds your code
You can set up Bamboo and JIRA to integrate your development process. Once automated, you could have a process like the following: a
developer commits a code change to SVN repository to resolve a JIRA issue; Bamboo detects this change and as a result, a build plan is
triggered to build the project; The result of the build is reflected in Bamboo and the corresponding JIRA issue.
For information on how to do this, see Integrating Builds with your Issues Workflow.
Bamboo builds your source code using various "builders", such as Ant, Maven, etc.
Bamboo can coordinate a large amount of machines to run multiple builds concurrently. Bamboo calls these machines "build
agents".
Bamboo OnDemand utilises the Amazon Elastic Compute Cloud (EC2) to get these "build agents"; i.e. Bamboo OnDemand does not
run builds locally; instead, builds are run on EC2 .
Administering Builds
132
Atlassian OnDemand October 2011 Documentation
Bamboo Administrator's Guide
To administer the Builds application, use the 'Builds' administration tab in the administration console.
To access the Builds tab in the administration console:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click the Builds tab. The Builds administration console will display.
For an overview of the administration options for the 'Builds' application, refer to the following appendix.
Appendix
Category
Functions
Build
Resources
* Agents — View and manage running (elastic) agents.
* Agent Matrix — View which active Bamboo agents can execute which plans (depending on plan requirements and
agent capabilities).
* Global Variables — Define global variables that can be used across all build plans.
Elastic Bamboo
* Configuration — Configure Elastic Bamboo settings.
* Instances — View and manage elastic instances.
* Image Configurations — Manage elastic image configurations, including custom images, EBS volumes, instance
type and availability zone.
* Instance Schedule — Schedule the startup and shutdown of instances of a particular elastic image.
* Agent History — View the history of elastic agents.
Plans
* Concurrent Builds — Enable and disable concurrent builds, and configure the default number of concurrent builds.
* Build Expiry — Schedule when build results and/or artifacts will be deleted.
* Bulk Action — Modify multiple plans at once, e.g. add notifications, etc.
* Build Monitoring — Configure build monitoring, including hung build and build queue timeout events.
* Remove Plans — Delete build plans.
* Move Plans — Move build plans between projects.
* Bulk Edit Plan Permissions — Apply permissions to multiple build plans at once.
Security
* Global Permissions — Manage Bamboo global plan permissions.
The 'Restricted Admin' permission in Bamboo OnDemand is the restricted 'Admin' permission in downloadable
Bamboo. The restrictions are:
Local agents cannot be created because Bamboo OnDemand uses Elastic Agents.
Users and groups are managed by JIRA OnDemand.
Communication
* IM Server — Configure the instant messaging server for Bamboo.
System
* General Configuration — Configure general settings, such as the name of the Bamboo instance (displayed on the
'Builds' dashboard), compression of artifacts, enabling the remote API (not the REST API which is enabled by
default).
* System Information — View system information about Bamboo.
* Log Settings — Configure runtime logging settings.
* System Errors — View Bamboo system errors.
Plugins
* Auto-Favourite Plugin — Enable/Disable the Auto-Favourite Plugin.
Integrating Builds with your Issues Workflow
You can configure a workflow in the issues application, so that the workflow can be actioned by the completion of a build. For example, you
can configure a workflow to automatically progress an issue from 'Building' to 'Resolved' status when an build related to that issue (i.e. JIRA
issue key added to commit message) has successfully completed. Alternatively, you can configure the same workflow to progress an issue
from 'Building' to 'Build Broken' status if a build related to that issue fails.
133
Atlassian OnDemand October 2011 Documentation
On this page:
Understanding the 'Builds Workflow'
Using the 'Builds Workflow' in your projects
Modifying the 'Builds Workflow'
Integrating build transitions into your custom workflow
A Builds Workflow exists in JIRA and it incorporates the common statuses and transitions (see the Understanding the 'Builds Workflow'
section below).
If you are new to JIRA and Bamboo, we recommend that you use the 'Builds Workflow' as modifying an existing workflow is not a
trivial task.
If you have an existing workflow that you would like to modify to include build statuses and transitions, we recommend that you
take a copy of the 'Builds Workflow' and modify it.
If you want to integrate Bamboo transitions into your existing workflow, you can edit your workflow to add the transitions. We
recommend that you avoid doing unless you have a good understanding of JIRA workflows.
Understanding the 'Builds Workflow'
Diagram: Builds Workflow
134
#
Transition
1
Start Progress
2
Stop Progress
3
Resolve Issue
4
Close Issue
5
Reopen Issue
6
Wait for Build
7
Build Passed
8
Build Failed
Atlassian OnDemand October 2011 Documentation
The 'Wait for Build', 'Build Passed' and 'Build Failed' transitions are Bamboo-specific transitions:
'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build
commit command. Note, you must manually enter the #build commit command in your commit message to trigger the transition, as
described in Using Smart Commits.
'Build Passed' — This transition will be automatically triggered when a build for this issue passes.
'Build Failed' — This transition will be automatically triggered when a build for this issue fails.
Using the 'Builds Workflow' in your projects
The following instructions describe how to create a workflow scheme that uses the 'Builds Workflow', and then associate the workflow
scheme with a project. If you want to add the 'Builds Workflow' to an existing workflow scheme, ignore steps 4-6 below and assign the
workflow to your existing workflow scheme instead.
Procedure
1. Creating a workflow scheme that uses the Builds Workflow
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Go to the Issues tab in the administration console. The 'Issues' administration console will display.
3. In the left-hand menu, go to Workflows >Workflow Schemes. The 'Workflow Schemes' page will display.
4. Click Add workflow scheme. The 'Add Workflow Scheme' page will display.
5. Enter a Name and Description' for your workflow scheme and click the Add button. Your workflow scheme will be created and you
will see the page for editing the workflow.
6. Click the Assign a workflow link. The 'Add Workflow to Scheme' page will display.
7. In the Issue Type dropdown, select the issue types that you want the 'Builds Workflow' to apply to. In the Workflow drop-down list,
select Builds Workflow. Click Add. The 'Builds Workflow' to your new workflow scheme for the selected issue types.
2. Associating the workflow scheme with your project
1. In left-hand menu of the Issues tab, go to Projects and select the project you wish to use the 'Builds Workflow' with. The project
summary page appears.
2. Locate the Workflows section and click More.
3. In the top right corner of the displayed page, click Actions > Select a scheme. The 'Associate Workflow Scheme to Project' screen
135
Atlassian OnDemand October 2011 Documentation
3.
will display.
4. In the drop-down list, select the newly created workflow scheme, and click the Associate button.
5. Select any statuses to migrate from the old workflow scheme to the new one (if any) and click the 'Associate' button. The 'Builds
Workflow' will be associated with your project via your workflow scheme.
Issues (of the issue types specified in your workflow scheme) will now use the 'Builds Workflow'. If you add the issue key of an issue to the
commit message when committing, the issue will be automatically transitioned along the workflow when the build starts/succeeds/fails.
Modifying the 'Builds Workflow'
You cannot modify the 'Builds Workflow' itself because it is non-editable. However, you can copy it and edit the copy if the original 'Builds
Workflow' doesn't suit the needs of your project. You can then activate the new (copied) workflow by adding it to a workflow scheme and then
associating that scheme with your projects.
Copying and editing the 'Builds Workflow'
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. In the displayed administration console, go to the 'Issues' tab .
3. In the left menu, go to 'Schemes' > 'Workflow Schemes'. The 'Workflow Schemes' page will display.
4. Click the View all workflows link. The 'View Workflows' page will display.
5. Locate the Builds Workflow and click Copy in the Operations column.
6. Enter a Name and Description for the new (copied) workflow scheme and click the Copy button. The new workflow will be created
and displayed on the 'View Workflows' page.
7. You can now edit and activate your new workflow as needed. See Configuring Workflow and Activating Workflow in the JIRA
documentation for more information on how to do this.
Integrating build transitions into your custom workflow
If modifying a copy of the 'Builds Workflow' is not feasible for your projects, it is possible to manually modify your existing workflow to include
the Bamboo transitions. It is recommended that you avoid doing so unless you have a good understanding of JIRA workflows.
To integrate build transitions into your existing custom workflow, edit your workflow and configure appropriate issue statuses and issue
transitions as described below.
Configuring your issue statuses
We recommend that you set up issue statuses for your workflow to indicate when a build related to an issue is building or the build is broken
(e.g. 'Building', 'Build Broken'). There is no technical restriction preventing you from incorporating Bamboo-specific build transitions into a
JIRA workflow without these intermediate states, however, in practice it will cause problems.
For example, a developer may work on an issue, and commit several times over the course of a few days for that issue.
Even if earlier commits cause the build to pass, the developer may not have finished working on the issue and will need to commit more code
without successful builds resolving the issue. Hence, an intermediate state (e.g. 'Building') is required which a developer will only transition
the issue into (i.e. using the #build commit command), if they want the issue to be resolved from that particular build.
Configuring your issue transitions
Automatic issue transitioning via builds is controlled by both commit commands and Bamboo-specific transition properties in JIRA, as
described below:
Commit Command — The #build commit command is mapped to the 'Waiting for Build' transition. Hence, if you add the 'Waiting
for Build' transition to your workflow, your users will be able to automatically trigger the transition by using the #build commit
command in their commit messages.
Bamboo-specific transition properties— The Bamboo-specific transition properties on the transitions that you want to be triggered
when a Bamboo build passes or fails. The following properties are supported:
Property
Value
Description
build.passed.transition
anything
A transition with this property will be triggered when a build for this issue
passes, and the transition is available to the issue in its current state.
build.failed.transition
anything
A transition with this property will be triggered when a build for this issue
fails, and the transition is available to the issue in its current state.
build.passed.resolution
any valid
resolution, e.g.
'Fixed'
The issue resolution will be set as specified by this property, if the transition
with this property is triggered by a build.
Please note, you cannot set up common transition properties in JIRA. You will need to manually re-enter the transition property
on each transition that you want it added to.
136
Atlassian OnDemand October 2011 Documentation
Bamboo Administrator's Guide
Atlassian OnDemand includes Bamboo 3.0, its continuous integration build server. Use the search or click any of the links below to view
the relevant page in the Bamboo Administrator's Guide. You will need to use the 'Back' button on your browser to return to the Bamboo
OnDemand documentation.
Please note, some Bamboo functionality is restricted in Bamboo OnDemand.
Search the Bamboo 3.0 documentation:
Configuring Projects, Plans, Stages and Jobs
Configuring a Plan
Creating a Plan
Creating a New Plan
Editing a Plan
Configuring a Plan's Notifications
Configuring a Plan's Permissions
Configuring Expiry of a Plan's Job Build Results
Renaming a Plan, its Project or changing the Plan's Description
Disabling or Deleting a Plan
Deleting the Results of a Plan Build
Stopping an Active Plan Build
Configuring Concurrent Builds
Modifying Multiple (Bulk) Plans
Moving Plans to a Different Project
Setting up Build Dependencies
Dependency Blocking Strategies
Configuring a Stage
Creating a Stage
Deleting a Stage
Editing a Stage
Configuring a Job
Creating a Job
Editing a Job
Configuring a Job's Requirements
Renaming a Job or changing the Job's Description
Configuring Automatic Labelling of Job Build Results
Configuring a Job's Build Artifacts
Configuring Artifact Sharing between Jobs
Configuring Miscellaneous Settings for a Job
Disabling or Deleting a Job
Deleting a Job's Current Working Files
Stopping an Active Job Build
Specifying a Builder
Ant
Custom Command Builder
devenv.com
Grails
Maven
NAnt
PHPUnit
Script Builder
Using Global or Build-specific Variables
Defining Global Variables
Configuring Agents and Capabilities
Bamboo OnDemand only uses elastic agents.
Configuring Capabilities
Editing a Capability
Renaming a Capability
Viewing a Capability's Agents and Jobs
Working with Builds
Triggering a Plan Build
Triggering a Plan Build when Code is Updated
Polling the Repository for Changes
Repository Triggers the Build when Changes are Committed
Triggering a Plan Build Based on a Schedule
Cron Based Scheduling
Single Daily Build
137
Atlassian OnDemand October 2011 Documentation
Triggering a Plan Build Manually
Reordering Jobs in the Build Queue
Monitoring Job Builds
Configuring the Hanging Job Build Event
Configuring the Job Build Queue Timeout Event
Disabling Build Monitoring
Working with Elastic Bamboo
About Elastic Bamboo
Elastic Bamboo Costs
Getting Started with Elastic Bamboo
Configuring Elastic Bamboo
Generating your AWS Private Key File and Certificate File
Configuring Elastic Instances to use the EBS
Populating your EBS volume
Managing Elastic Bamboo
Managing your Elastic Images
Viewing an Elastic Image
Managing your Elastic Image Configurations
Updating Elastic Images for Bamboo Upgrades
Managing your Elastic Instances
Viewing an Elastic Instance
Accessing an Elastic Instance
Starting an Elastic Instance
Scheduling your Elastic Instances
Shutting Down an Elastic Instance
Managing your Elastic Agents
Viewing your Elastic Agents
Viewing your Elastic Agent Usage History
Configuring Elastic Agent Capabilities
Disabling an Elastic Agent
Running Job Builds using Elastic Bamboo
Disabling Elastic Bamboo
Configuring Email and Instant Messaging Notifications
Configuring Notifications for a Plan and its Jobs
Configuring Bamboo to use Instant Messaging
Configuring Bamboo to use Google Talk for Instant Messaging
Managing Users and Permissions
Managing Permissions for Users and Groups
Granting Plan Permissions to Users or Groups
Granting Global Permissions to Users or Groups
Allowing Anonymous Users to access Bamboo
Global Security and Permission Properties
Enabling or Disabling Public Signup
Enabling or Disabling Contact Details Display
Enabling or Disabling Captcha for Failed Logins
Configuring System Settings
Viewing Bamboo's System Information
Specifying Bamboo's Title
Logging in Bamboo
Enabling GZIP Compression
Enabling Bamboo's Remote API
Working with Builds
A build is the execution of either a Plan or a Job. The execution of a Plan is referred to as a 'Plan build' and that of a Job is a 'Job build'.
A Plan defines everything about your entire build process. Plans:
consist of one or more Jobs, which are organised into one or more Stages;
contains a single 'Default Job' in a single Stage, after creating a new Plan;
define default settings for what gets built by Jobs in the Plan (i.e. the 'default source repository');
define how the Plan's build is triggered;
define who will be notified of the Job's build result;
define who has permission to view and perform various actions on the Plan and its Jobs.
Every plan belongs to a Project.
Projects and plans can only be configured by Bamboo administrators (see Creating a Plan).
138
Atlassian OnDemand October 2011 Documentation
Working with Builds
Getting started with Bamboo OnDemand
Bamboo User's Guide
Actioning Issues via Builds
Accessing the Builds application
1. Click the Build tab in the header. This takes you to Bamboo.
Bamboo User's Guide
Atlassian OnDemand includes Bamboo 3.0 for its continuous integration build server. Use the search or click any of the links below to view
the relevant page in the Bamboo User's Guide. You will need to use the 'Back' button on your browser to return to the Bamboo OnDemand
documentation.
Please note, some Bamboo functionality is restricted in Bamboo OnDemand.
Search the Bamboo 3.0 documentation:
Getting Started
Using the Bamboo Dashboard
Viewing Bamboo's Current Activity
Viewing your Latest Build Results
Working with Favourites
Adding a Plan to your Favourites
Removing a Plan from your Favourites
Displaying the Wallboard
Viewing Bamboo's Agents
Working with Projects, Stages, Plans and Jobs
Working with Plans
Viewing a Plan's Details
Viewing the JIRA Issues linked to the Builds in a Build Plan
Working with Stages
Working with Jobs
Viewing a Job
Viewing a Job's Maven Dependencies
Viewing the Clover Coverage Summary for a Job
Working with Build Results
Viewing a Build Result
Viewing the Code Changes that Triggered a Build
Viewing a Build's Artifacts
Viewing a Build Log
Viewing the Metadata for a Build Result
Viewing the Clover Code-Coverage for a Build Result
Viewing the JIRA Issues for a Build Result
Linking JIRA Issues to a Build
Working with Tests
Viewing Test Results for a Build
Viewing a Test's History
Viewing Test Statistics for a Job
Reporting on Plan Trends
Viewing Build Statistics for a Plan
Generating Reports across Multiple Plans
'Build Activity' Report
'Build Duration' Report
'Clover Code Coverage' Report
'Clover Lines of Code' Report
'Number of Build Failures' Report
'Percentage of Successful Builds' Report
139
Atlassian OnDemand October 2011 Documentation
'Time to Fix' Report
'Number of Tests' Report
Reporting on Author Trends
Viewing Build Statistics for all Authors
Viewing Build Results for an Author
Generating Reports on Selected Authors
'Build Activity per Author' Report
'Number of Build Failures per Author' Report
'Number of Builds Broken per Author' Report
'Number of Builds Fixed per Author' Report
'Percentage of Successful Builds per Author' Report
Working with Comments
Commenting about a Build Result
Viewing Comments about a Build Result
Viewing Code Check-in Comments
Working with Labels
Labelling a Build Result
Removing a Label from a Build Result
Viewing Labelled Build Results
Viewing Popular Labels
Subscribing to RSS Feeds
Subscribing to an RSS Feed for All Build Results for All Plans
Subscribing to an RSS Feed for All Build Results for a Particular Plan
Subscribing to an RSS Feed for Failed Builds for All Plans
Subscribing to an RSS Feed for Failed Builds for a Particular Plan
Subscribing to an RSS Feed for Labelled Build Results
Working with Instant Messenger (IM) Notifications
Labelling a Build Result via IM
Commenting about a Build Result via IM
Actioning Issues via Builds
If your administrator has integrated builds with issues, you will be able to action issues via builds. If the default 'Builds Workflow' is being
used with your project, the workflow will look like this:
Please check with your administrator to see whether the default 'Builds Workflow' has been modified.
Diagram: Builds Workflow
140
#
Transition
1
Start Progress
2
Stop Progress
3
Resolve Issue
4
Close Issue
5
Reopen Issue
6
Wait for Build
7
Build Passed
Atlassian OnDemand October 2011 Documentation
8
Build Failed
The 'Wait for Build', 'Build Passed' and 'Build Failed' transitions are Bamboo-specific transitions:
'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build
commit command. Note, you must manually enter the #build commit command in your commit message to trigger the transition, as
described in Using Smart Commits.
'Build Passed' — This transition will be automatically triggered when a build for this issue passes.
'Build Failed' — This transition will be automatically triggered when a build for this issue fails.
If you want to resolve an issue via a particular (successful) build, you can add the #build commit command to your commit message. If
the build is successful, the issue will automatically transition to 'Resolved'. If the build fails, it will automatically transition to 'Build Broken'.
You can still commit without the issue potentially transitioning to 'Resolved' simply by omitting the #build commit command from your
commit message.
Glossary
changelog
changeset
external user
issue
JIRA project
page
project
repository
review
source
space
141
Atlassian OnDemand October 2011 Documentation
user
wiki
changelog
A changelog is a chronological list of the changesets that were committed to a repository.
For more information, please see Working with Source.
changeset
A changeset is a collection of source files that are committed to the repository at the same time. A changeset can be associated with one or
more reviews.In Atlassian OnDemand, a repository can be associated with projects, and therefore, a changeset can automatically link to any
associated issues and wiki pages.
For more information, please see Working with Source.
external user
An external user is a user who does not have access to your company email domain, but who you allow to access your Atlassian OnDemand
site, for example. e.g. client, contact, or remote worker.
Example scenarios:
Users who have Google Apps accounts, but who do not have access rights to your email or business login details.
Users who don't have a Google ID because they have email accounts on domains other than Google.
External user accounts are created as OnDemand users.
For more information, please see:
Managing External Users with Google Apps Integration
Managing Users and Groups
issue
An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a JIRA project.
For more information, please see Working with Issues.
JIRA project
See What is a Project in JIRA documentation.
See also:
project
page
A page is an online document within the wiki. Each page belongs to a space.
For more information, please see Working with the Wiki.
project
In Atlassian OnDemand, a project is like a container and includes the following objects if the corresponding application is available in your
site:
a JIRA project
a wiki space
a build project
a source repository
The association between these objects in a project makes it possible to automatically link between issues, wiki documents, source files, plan,
changesets, code reviews and build result.
142
Atlassian OnDemand October 2011 Documentation
For more information, please see Creating new projects.
repository
A repository (e.g. Subversion, Perforce or CVS) contains your source code.
Note: In Atlassian OnDemand, a source repository can be associated with one or more projects.
For more information, please see Working with Source.
review
Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being
committed to a repository.
For more information, please see Working with Reviews.
See also: repository
source
Your source (e.g. your source code) resides in a repository such as Subversion, Perforce or CVS.
For more information, please see Working with Source.
space
A space is a group of pages within the wiki. You can think of each space as a sub-site, or mini-site, each with its own home page.
In Atlassian OnDemand, a space can be associated with a project. This allows links to be automatically created on your wiki pages, pointing
to associated issues, source files, changesets and code reviews.For more information, see Working with the Wiki.
user
A user is the account for an individual who accesses your Atlassian OnDemand site.
See also External user.
wiki
The wiki is a collection of online documents, i.e. pages. Wikis are useful for collaboration, information sharing and documentation.
For more information, see Working with the Wiki.
Atlassian OnDemand release summary
20 February 2012
Changes in this week:
Accessing administration menus faster
GreenHopper upgrade
Bonfire upgrade
New JIRA OnDemand features
Sharing issues
Mentioning users
Creating and editing issues rapidly
Searching for issues based on their history
Accessing administration menus faster
Type 'g' + 'g' from anywhere in your Atlassian OnDemand site to bring up the Administration Search box and start typing the name of the
administration menus you want to work with.
Please be aware of the following limitations:
143
Atlassian OnDemand October 2011 Documentation
You cannot search for FishEye and Crucible menus at the moment.
If you use Internet Explorer 9, this functionality does not work when you are in the Builds (Bamboo) application. You can bring up the
search box, but searching does not work.
Screenshot 1: Searching for permission
Screenshot 2: Searching for 'import'
GreenHopper upgrade
GreenHopper has been upgraded from version 5.7 to 5.9. A number of new features have been released since version 5.7, including the
highly requested multiple project support by the Rapid Board. Please check out the following page for an overview of the new features:
GreenHopper OnDemand Release Summary
Bonfire upgrade
Bonfire has been upgraded from version 1.8 to 1.9. Please use the following link to view the features included by this release: Bonfire 1.9
Release Notes.
New JIRA OnDemand features
Sharing issues
144
Atlassian OnDemand October 2011 Documentation
Have you been sharing pages in Confluence with the Share button? Now you can share JIRA issues with other people in the same way.
When viewing an issue on the 'view issue' page or a search result on the issue navigator, type s or click the Share button at the top-right,
and specify OnDemand users or any email address of people you want to share the issues with. Recipients will receive an email with the link
to the issue or a search result, depending on what you shared.
Mentioning users
Also similar to how it works in Confluence, when you mention other users' names by typing '@' first, the mentioned users will receive email
notifications about the issue automatically.
To do this, type '@' in an issue's Description or Comment field, then start typing the user's name, and then select the user from the
suggested list of users. An email will be automatically sent to the mentioned users.
Creating and editing issues rapidly
Working with issues is now faster than before. Specifically, you'll see these changes:
Creating and editing issues is now performed in a dialog box rather than a separate form. Therefore, your pages are not reloaded
any more when you start creating or editing an issue or sub-task.
Customise what fields you want to see
You can customise the Create Issue/Edit Issue dialog boxes to display only the fields you use most often. To do this, click the
Configure Fields button and remove or add fields as you wish. Your settings are saved for future usage automatically.
Creating a series of issues with similar options
If you want to create multiple issues with similar field values, use the Create another check box before clicking the Create button.
JIRA will then create your issue and automatically pre-populate a new Create Issue dialog box with your previous field values. The
Summary field and attachments are not carried across.
Tip: The keyboard shortcut for creating issues is 'c' and that for editing issues is 'e'.
145
Atlassian OnDemand October 2011 Documentation
Searching for issues based on their history
'CHANGED' operator introduced
You can use the CHANGED operator to search for issues with specific field changes. This operator accepts the optional predicates FROM,
TO, ON, DURING, BEFORE, AFTER and BY, and can be used on the Status, Assignee, Priority, Reporter, Resolution and Fix Version
fields.
For example,the following query:
project = JIRA AND fixVersion changed TO "5.0"
shows all the issues logged against the JIRA project, whose Fix Version field was changed to "5.0". You can see it in real use via this link.
The following example is a more complex JQL query. It will find any issues whose Status field value was at some point "In QA Review" but
changed to "QA Rejected", by user freddo between the start and end of the current week.
status changed FROM "In QA Review" TO "QA Rejected" BY freddo AFTER startOfWeek() BEFORE
endOfWeek()
'WAS' operator enhanced
You can now use the WAS operator to work with the Fix Version field. For example, the following JQL query:
fixVersion WAS 4.4
Will find any issues whose Fix Version field was at some point (or currently is) set to 4.4.
Known Issues and Workarounds
Search previous features:
146
Atlassian OnDemand October 2011 Documentation
February 2012 — Commit commands changes; Improved FishEye and Crucible search; Repo commit graph; JIRA
transitions in Crucible; and more.
January 2012 — UI improvements in bitbucket & GitHub Connector plugin; Bonfire upgrade;
December 2011 — New Confluence features; Confluence space importer; Zephyr bundled; Updated
GitHub/Bitbucket connector;
November 2011 — Changes of notification email prefixes; Domain name changes;
The launch
Known Issues and Workarounds
February 2012
This week:
Commit commands changes; Improved FishEye and Crucible search; Repo commit graph; JIRA transitions in Crucible; and
more.
6 February 2012
New FishEye and Crucible features
FishEye OnDemand has been upgraded with a number of new features. These include:
Commit commands have changed. Workflow mappings for custom transitions do not have to be defined anymore as FishEye will
match the transition name automatically. You can now create reviews via commit comments as well.
For important information about the changes to commit commands, please see Changes to Commit Commands.
Improved FishEye/Crucible quick search with pattern matches against CamelCase strings for files and directories, and an improved
look and feel.
Repository commit graph. A visualisation tool for your repository.
Redesigned HTML emails.
Dashboard and navigation improvements.
A number of small improvements including syntax highlighting for Java 7, Groovy, Velocity and Scala, and HEAD label in revisions
page only appearing for the currently selected branch (or default branch if All is selected).
Crucible OnDemand has also been upgraded with a number of new features. These include:
JIRA transitions in Crucible. Transition a JIRA issue through its workflow when closing a review.
FishEye/Crucible quick search now finds review data.
HTML emails for reviews.
Review reminder emails.
Dashboard and navigation improvements.
Review creation without metadata changes.
Improved patch anchoring.
A number of small improvements including syntax highlighting for Java 7, Groovy, Velocity and Scala, and issue dialogs that appear
when hovering over an issue key in a review.
For further details, see February 2012 - FishEye Crucible 2.7 upgrade notes .
Here are a few sample screenshots (click to see full-size images).
Improved quick search:
147
Atlassian OnDemand October 2011 Documentation
JIRA transitions in Crucible:
Review reminders:
February 2012 - FishEye Crucible 2.7 upgrade notes
148
Atlassian OnDemand October 2011 Documentation
On this page:
Summary of FishEye and Crucible releases
FishEye 2.7 — 7 September 2011 (release notes)
FishEye 2.6 — 6 June 2011 (release notes)
Crucible 2.7 — 7 September 2011 (release notes)
Crucible 2.6 — 6 June 2011 (release notes)
Changes to Commit Commands
Summary of FishEye and Crucible releases
FishEye 2.7 — 7 September 2011 (release notes)
Applies to FishEye OnDemand:
Smart Commits – Replaces OnDemand commit commands. See Changes to Commit Commands below.
JIRA FishEye Plugin Improvements
Small Improvements
Syntax highlighting for Java 7, Groovy, Velocity and Scala.
HEAD label in revisions page only appears for currently selected branch (or default branch if All is selected).
Does not apply to FishEye OnDemand:
Managed Git Repositories
Web Hooks
Small Improvements
FishEye can now run on Java 7
Improved user interface for the administration screens
Improved plugin points for developers
FishEye 2.6 — 6 June 2011 (release notes)
Applies to FishEye OnDemand:
Repository Commit Graph
Improved Quick Search – Please note, this only applies to the quick search in FishEye OnDemand, not the Atlassian OnDemand
quick search available in the navigation bar.
Redesigned HTML Emails
Dashboard and Navigation Improvements
Does not apply to FishEye OnDemand:
User Management via JIRA
Improved Support for Git Branches
Git Commit Authors include Email Address
Mercurial Indexing Improvements
Crucible 2.7 — 7 September 2011 (release notes)
Applies to Crucible OnDemand:
JIRA Transitions in Crucible
Review Reminders
Small Improvements – As per the FishEye 2.7 Small Improvements
Does not apply to Crucible OnDemand:
Small Improvements – As per the FishEye 2.7 Small Improvements
Crucible 2.6 — 6 June 2011 (release notes)
Applies to Crucible OnDemand:
New Quick Search
HTML Emails for Reviews
Dashboard and Navigation Improvements
Review Creation without Metadata Changes
Improved Patch Anchoring
Does not apply to Crucible OnDemand:
SQL Server Support
Oracle Support
Changes to Commit Commands
149
Atlassian OnDemand October 2011 Documentation
Commit commands have been replaced with FishEye smart commits, with the introduction of FishEye 2.7 OnDemand.
Please be aware of the following changes between commit commands and smart commits. Documentation for smart commits is available in
the FishEye documentation: Using Smart Commits.
Commit Commands
Smart Commits
Crucible reviews could not be created using commit commands.
Crucible reviews can now be created using smart commits.
Commit commands supports the JIRA default workflow
transitions. Commit commands for custom workflow transitions
had to be manually configured.
FishEye will automatically find and match the prefix for an issue
transition, regardless of whether it is a default or custom JIRA
transition.
For example, if you have transition name with spaces, such as
finish work then specifying #finish is sufficient. Hyphens
replace spaces: #finish-work
Commit commands allowed the resolution to be set when
resolving an issue.
Smart commits do not allow the resolution to be set when resolving
an issue.
Logging work – a work log description can be saved when
logging work.
Smart commits currently do not allow a work log description to be
saved when logging work.
FE-3757 - Authenticate to see issue details
Logging work – work can be logged with multiple time
parameters (e.g. 4d 2h).
Smart commits currently only allows a single time parameter. If more
than one time parameter is entered, then only the first is recorded.
FE-3885 - Authenticate to see issue details
Triggering builds – builds can be triggered via commit
commands.
Triggering builds – builds cannot be triggered via smart commits.
January 2012
This month:
UI improvements in bitbucket & GitHub Connector plugin; Bonfire upgrade;
16 January 2012
UI improvements in bitbucket & GitHub Connector plugin
The commits from bitbucket and GitHub are now displayed under the Commits tab as well as the Activity tab for the referenced issue.
There used to be separate tabs for bitbucket and GitHub. The UI has been improved as well.
Screenshot: Bitbucket commits on the Commits tab of the DVCS-2 issue
Screenshot: Bitbucket commits on the Commits tab of the DVCS-2 issue
150
Atlassian OnDemand October 2011 Documentation
9 January 2012
Happy New Year!
Bonfire upgrade
Bonfire has been upgraded from version 1.3 to 1.7. A number of new features have been released since version 1.3. Please check out the
following release notes for an overview of the new features:
Bonfire 1.7.1 Release Notes
Bonfire 1.6.2 Release Notes
Bonfire 1.5.1 Release Notes
Bonfire 1.4 Release Notes
Administrators can now resolve the problem where a user is locked out of FishEye/Crucible REST APIs
Users can become locked out of the FishEye and Crucible REST APIs as a result of attempting to use incorrect credentials to log in to those
applications. The most common cause of this is when the Atlassian IDE Connector is set up to use incorrect credentials, for example due to
the user having changed their password.
If this happens to your users, you can resolve the issue by resetting the FishEye CAPTCHA for the user.
For details about using this, see the Users are locked out of FishEye and Crucible REST APIs FAQ.
In the past when this functionality was not available, you'd have to open a support ticket for this problem to be sorted out.
December 2011
This month:
New Confluence features; Confluence space importer; Zephyr bundled; Updated GitHub/Bitbucket connector;
19 December 2011
New Confluence features
Confluence OnDemand has been upgraded with a number of new features. These include:
151
Atlassian OnDemand October 2011 Documentation
New border effects for images.
Autoconversion of links when pasted into the editor. For example, if you paste a YouTube URL into the editor, it will automatically be
converted into a Confluence widget displaying the video.
Find-and-replace feature in the editor. Use Ctrl + F to try it
New network tab on the Confluence dashboard that allows you to see updates only from people that you follow.
Global PDF stylesheets that apply to all spaces for exports.
New translation feature – After opening the Confluence dashboard, append this text to your URL: ?i18ntranslate=on This will
allow you to see the key name for each UI element to aid translations. Turn it off by appending ?i18ntranslate=off
Other improvements, including new icons, improved UI for favourites, a global plugin and macro timeout setting, and the ability to
use any character in page titles, like semicolons and exclamation marks.
Take a tour of the highlights of the Confluence OnDemand features in this upgrade:
Confluence space importer
It is now possible to import Confluence spaces to Atlassian OnDemand. For instructions on how to do this, please refer to Importing wiki data
.
Zephyr Test Management plugin is bundled
Zephyr is now bundled with JIRA OnDemand. You can enable it with just a click and start using the two applications together. Please note
that after Zephyr is enabled, the OnDemand data consumed by Zephyr will be exposed publicly.
For instructions on how to enable it, please refer to Connecting Zephyr with JIRA OnDemand.
GitHub/Bitbucket connector improvements
We've tweaked the GitHub and Bitbucket connector configuration in Atlassian OnDemand. Administrators will now be able to connect both
Bitbucket and GitHub repositories via the same administration screen. We've simplified the setup process as well.
For instructions on how to use this, see Integrating Bitbucket with JIRA OnDemand and Integrating GitHub with JIRA OnDemand.
November 2011
This month:
Changes of notification email prefixes; Domain name changes;
21 November 2011
Changes of notification email prefixes
The notification emails sent out by Atlassian OnDemand start using product names as the prefixes.
For example, emails from JIRA are now prefixed with [JIRA]; the [FishEye] prefix is used for repository watches and [Crucible] for
reviews.
7 November 2011
Domain name changes
The domain name for signups after 8 November 2011 is https://<account_name>.atlassian.net.
The domain name for customers who signed up prior to this date will remain unchanged, i.e. https://<account_name>.jira.com.
The launch
25 October 2011
We are proud to announce the launch of Atlassian OnDemand, a flexible development & collaboration platform for teams of any size.
Overview
Available applications
You can choose from JIRA, Confluence, FishEye/Crucible/Subversion and Bamboo for your team and add or remove applications as
152
Atlassian OnDemand October 2011 Documentation
your business requirements change. For a brief introduction of these applications and what they can do for your team, see:
Overview from www.atlassian.com
Overview in this documentation
Choosing applications
Free 30-day trial
Try it yourself by signing up for a free trial at https://my.atlassian.com/ondemand/signup.
Features
Besides the rich functionality in each individual OnDemand application, integration between applications is a highlight of Atlassian
OnDemand.
Google Apps integration
By integrating OnDemand and Google Apps, your team can access and work with Google documents in Atlassian OnDemand directly.
Users are shared between the two sites as well.
For more information, see Working with Google Apps Integration and Managing users and groups for sites integrated with Google
Apps.
Linking between applications
You can create links between source files, issues, wiki pages and reviews and quickly jump between applications for related
information. Creating links is as simple as inserting text into your application. For example, you can link a source file with a JIRA issue
by typing the filename into your JIRA issue.
Read more about Creating Links.
And we have Confluence 4!
Check out the features in Confluence 4 at www.atlassian.com/software/confluence/tour/.
Existing Enterprise Hosted and JIRA Studio customers
Atlassian OnDemand is Atlassian's new suite of hosted services, replacing Enterprise Hosted and JIRA Studio. Enterprise Hosted and
JIRA Studio will be phased out, however we have a migration plan for existing customers that allows you to continue using the service
and at the same time, take advantage of the OnDemand pricing.
Please check out our FAQ for existing customers: http://www.atlassian.com/licensing/ondemand-faq-existing-customers.
Known Issues and Workarounds
This page contains known issues of Atlassian OnDemand and information about fixes or workarounds that exist for these limitations and
issues.
General usage
Google activity bar not displayed for sites with JIRA OnDemand only
If your site only uses JIRA OnDemand, it is a known issue that the Google activity bar is not displayed as expected. All other Google
integration functionality is available, e.g. user synchronisation and attaching Google documents.
Workaround: N/A.
We are working on fixing this problem and you can find out the progress at https://studio.atlassian.com/browse/JST-5686.
Administration
Limitations for searching administration menus
With the functionality where you bring up the Administration Search box by typing 'g' + 'g' from anywhere in your Atlassian OnDemand site
and search for administration menus, please be aware of the following limitations.
You cannot search for FishEye and Crucible menus at the moment.
If you use Internet Explorer 9, this functionality does not work when you are in the Builds (Bamboo) application. You can bring up the
search box, but searching does not work.
Users continue receiving email notifications from applications for which access has been revoked
153
Atlassian OnDemand October 2011 Documentation
After you revoke a user's access to an application in the Application Access page of the administration console, the user will still be receiving
notifications from the application.
This behaviour respects that of the individual applications. For example, in JIRA, a user who has been deactivated, i.e. removed from all
groups, continues to receive notifications until the user is removed from the notification groups. That's the way JIRA works, so we're
respecting that.
Workaround: N/A.
Support
Restricted Functions in Atlassian OnDemand
Supported browsers
Atlassian OnDemand Application Versions
Atlassian OnDemand licensing
Support Policies
Atlassian OnDemand Plugin Policy
About Your Data
Maintenance windows
Restricted Functions in Atlassian OnDemand
Atlassian OnDemand contains fully functional versions of JIRA, Confluence, FishEye, Crucible, Subversion and Bamboo. 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 Atlassian OnDemand. This means,
The function is pre-configured and cannot be altered by anyone, or,
The function can only be configured by Atlassian OnDemand Technical Support — changes can be requested by
filing a ticket at https://support.atlassian.com under the 'OnDemand' project.
The functions that are restricted in Atlassian OnDemand are listed below.
On this page:
Atlassian OnDemand General
JIRA
Confluence
FishEye and Crucible
Bamboo
Subversion
Atlassian OnDemand General
Imports — Please read Importing Data for information on supported imports for Atlassian OnDemand.
Themes — Custom themes, look & feel, etc, are not supported in most cases.
Templates — External Confluence templates are not supported.
Plugins — Atlassian OnDemand contains a number of popular plugins. Please read the Atlassian OnDemand Plugin Policy for the
list of supported plugins. Requests for additional plugins should be created as a feature request at https://studio.atlassian.com under
the Atlassian OnDemand project.
Alternate Languages —There's no full support for alternate languages except English (US) at the moment. Please follow JST-801
for updates on this feature.
Backups — Refer to our Data Backups policy.
Custom Domains — Your instance will be accessible at https://<account_name>.atlassian.net, where <account_name>
is a unique word you specify when signing up. Use of custom domain names is not currently supported.
Changing Domains — Currently we're unable to change your Atlassian OnDemand domain after the instance has been created.
Please choose carefully when signing up.
JIRA
154
Atlassian OnDemand October 2011 Documentation
Generally speaking, all functions performed by the 'JIRA System Administrator' in download JIRA are restricted in Atlassian OnDemand. The
following table lists all of the functions that are restricted in Atlassian OnDemand, even to users with administrator permissions. The table
below also lists whether the function can be configured by Atlassian OnDemand Technical Support on request. If not, then it is unavailable
for configuration in Atlassian OnDemand.
Restricted
Function
Configurable
on Request?
General
Configuration
NO
Notes
Advanced
settings
155
Permissions
NO
'JIRA System Administrator' permission is not available in Atlassian OnDemand.
SMTP Mail server
NO
Atlassian OnDemand comes with an internal SMTP server configured to send notifications.
The [JIRA] prefix is not configurable.
POP/IMAP Mail
servers
NO
Atlassian OnDemand includes a mail service configured to create issue comments from replies to
JIRA notifications. Setting up a JIRA service to create issues and comments from an external
POP/IMAP server is not currently supported.
Configure a CVS
source code
repository
NO
CVS repositories are not supported.
Configure
listeners
NO
Configure
services
NO
Customising
source files
NO
Customising email
content
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
Atlassian support will assist with generating a usable XML backups for downloadable instances,
only if you have a pending cancellation of a paid-subscription Atlassian OnDemand
account. Commercial customers can request an export by filing a ticket at
https://support.atlassian.com.
Import data from
external systems
(CSV / Excel)
NO
Please read Importing Data for information on supported imports for Atlassian OnDemand.
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.
Atlassian OnDemand October 2011 Documentation
Import XML
workflows into
JIRA
NO
Plugins
NO
Only default plugins are allowed. Please see Atlassian OnDemand Plugin Policy for the list of
supported plugins.
Plugin Repository
NO
Only default plugins are allowed. Please see Atlassian OnDemand Plugin Policy for the list of
supported plugins.
Disable
attachments,
Set the
attachment path
or size limit
NO
Attachments enabled by default, maximum size set to 100MB.
Run Jelly scripts
NO
Please see JST-1439 on the status.
Configure LDAP
integration
NO
Configure trusted
applications
NO
Configure
application links
NO
Configure issue
links
NO
Access license
details
NO
Modify SysAdmin
users & attributes
NO
Remote API
(XML-RPC,
SOAP)
YES
This is already enabled by default. For more information, see JIRA Remote API.
Confluence
Generally speaking, all functions performed by the Confluence 'System Administrator' in download Confluence are restricted in Atlassian
OnDemand. The following table lists all of the functions that are restricted in Atlassian OnDemand, even to users with administrator
permissions. The table also lists whether the function can be configured by Atlassian OnDemand Technical Support on request. If not, then it
is unavailable for configuration in Atlassian OnDemand.
Restricted Function
Configurable on
Request?
Notes
Permissions
NO
Confluence 'System Administrator' permission is not available in Atlassian
OnDemand.
General Configuration
NO
Public signup is managed via JIRA.
NO
Backups are managed globally.
Server Base URL
External user
management
Public Signup
Daily Backup Admin
156
Atlassian OnDemand October 2011 Documentation
Plugins
NO
Only default plugins are allowed. Please see Atlassian OnDemand Plugin Policy for
the list of supported plugins.
Plugin Repository
NO
Only default plugins are allowed. Please see Atlassian OnDemand Plugin Policy for
the list of supported plugins.
Mail Servers
NO
Atlassian OnDemand comes with an internal SMTP server configured to send
notifications.
The [Confluence] prefix is not configurable.
Mail Archiving (at the
space level)
NO
User Macros
NO
Attachment Storage
NO
Attachments enabled by default, maximum size set to 10MB.
Look and Feel
NO
As Confluence uses a custom theme, it is not possible to customise the layout.
Layouts
Custom CSS
It is also not possible to style Confluence with CSS.
Custom HTML
NO
Backup & Restore
Backup - YES
Restore - NO
SnipSnap Import
NO
Logging and Profiling
NO
Cluster Configuration
NO
Remote API (XML-RPC,
SOAP)
YES
External Gadgets
NO
Confluence exports can be requested by filing a ticket at
https://support.atlassian.com.
This is already enabled by default. For more information, see Confluence Remote
API.
FishEye and Crucible
A small set of administrative functions are available for FishEye and Crucible.
The administration consoles in the downloadable versions of FishEye and Crucible are unavailable to Atlassian OnDemand customers. We
have configured the administration options for these applications 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 Atlassian
OnDemand project.
Please note, however, that the FishEye remote API (REST, XML-RPC) is available to Atlassian OnDemand customers. For more information,
see FishEye Remote API.
Bamboo
The following table lists all of the functions that are restricted in Atlassian OnDemand, even to users with administrator permissions. The
table also lists whether the function can be configured by Atlassian OnDemand Technical Support on request (if not, then it is unavailable for
configuration in Atlassian OnDemand).
157
Restricted
Function
Configurable
on Request?
Notes
Configure
builders
NO
Bamboo OnDemand only runs builds using elastic agents. Hence, capabilities can only be configured
by using a custom image.
Atlassian OnDemand October 2011 Documentation
Configure
JDKs
NO
Bamboo OnDemand only runs builds using elastic agents. Hence, capabilities can only be configured
by using a custom image.
Configure
Server
Capabilities
NO
Bamboo OnDemand only runs builds using elastic agents. Hence, capabilities can only be configured
by using a custom image.
Support
Custom
Elastic
Images
NO
Due to its wide scope, support of customised elastic images is not provided. We recommend using the
default image with an EBS volume instead. You can customise the default image via scripts stored on
your EBS snapshot during startup.
Plugin
Installation
NO
Configure
Users
NO
Bamboo users are managed via Atlassian OnDemand's users and groups.
Configure
Groups
NO
Bamboo user groups are managed via Atlassian OnDemand's users and groups.
Configure
Security
Settings
NO
Configure
Mail Server
NO
Atlassian OnDemand comes with an internal SMTP server configured to send notifications.
The [Bamboo] prefix is not configurable.
IM settings
NO
This feature can be discussed here.
Database
Configuration
NO
License
Details
NO
Indexing
NO
Scheduled
Backups
NO
Export Data
NO
Import Data
NO
Create/Delete
Projects
NO
JIRA OnDemand manages the projects for all applications. To create or delete projects, go to the
Administration > General > Projects page.
Clover plugin
NO
Clover is not included by Bamboo OnDemand, and the integration of Clover with Bamboo OnDemand is
not supported. The screen captures in the referenced Bamboo documentation might display Clover
interfaces and they only apply to the download Bamboo.
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.
Restricted
Function
158
Configurable
on Request?
Notes
Atlassian OnDemand October 2011 Documentation
Custom
Hooks
NO
A pre-commit hook is available that requires a JIRA issue key. Custom hooks are not available at the
moment due to reasons listed here. If you have suggestions on hooks you'd like to see in the future,
please request the feature here.
Backups
Full - Yes
Subversion full exports can be requested by filing a ticket at https://support.atlassian.com. It's also
possible to use svnsync to mirror the repository.
Supported browsers
This page describes the supported browsers for Atlassian OnDemand.
Key:
= Supported;
= Not Supported;
Your site's applications
Confluence only
= Supported but not recommended or with restrictions;
Microsoft Internet
Explorer
9.0
8.0
JIRA
Mozilla Firefox
Safari
Chrome
Latest stable
version
Latest stable
version
Latest stable
version
Latest stable
version
Latest stable
version
9.0
8.0
7.0
JIRA + Confluence
9.0
8.0
JIRA + FishEye/Crucible/SVN
9.0
8.0
7.0
JIRA + Confluence + FishEye/Crucible/SVN
9.0
8.0
JIRA + FishEye/Crucible/SVN + Bamboo
9.0
3.6.x [1]
JIRA + Confluence + FishEye/Crucible/SVN
+ Bamboo
8.0
3.5.x
3.0.x
Notes
1. If you use Firefox version 3.6, it is recommended that you use version 3.6.2 or above because of the data loss issue in Firefox 3.6.0.
2. Mobiles are not supported.
End of Support Announcements for Atlassian OnDemand
hidden. only visible to atlassian staff. Since AOD has only launch the 1st release, end of support info does not seem to be
necessary right now.
Atlassian OnDemand is composed of individual applications that are integrated in a hosted environment. As such, the support for web
browsers is subject to the end of support dates of the individual applications.
To find out the current application versions that are running in Atlassian OnDemand, read the Atlassian OnDemand Application Versions
page.
The following section lists the End of Support pages for the individual applications.
Bamboo
Crucible
Confluence
FishEye
JIRA
159
Atlassian OnDemand October 2011 Documentation
Atlassian OnDemand Application Versions
The following tables display the current versions of the applications running in Atlassian OnDemand.
Please also see Restricted Functions in Atlassian OnDemand for information on functions that are restricted in Atlassian OnDemand.
OnDemand applications
Application
Version in OnDemand
Last updated in
Information
Issues (JIRA)
JIRA 5.0
February 2012
JIRA 5.0 Release Notes
Wiki (Confluence)
Confluence 4.1
December 2011
Confluence 4.1 Release Notes
Confluence 4.0 Release Notes
Source (FishEye)
FishEye 2.7
February 2012
FishEye 2.7 Release Notes
Reviews (Crucible)
Crucible 2.7
February 2012
Crucible 2.7 Release Notes
Builds (Bamboo)
Bamboo 3.0
October 2011
Bamboo 3.0 Release Notes
(effectively the same as Bamboo 3.0)
Repository (Subversion)
Subversion 1.6.11
October 2011
Subversion Project Home
Single Sign-on (Crowd)
Crowd 2.2
October 2011
Crowd 2.2.2 Release Notes
(effectively the same as Crowd 2.2)
Add-ons
Add-on
Version in OnDemand
Last updated in
Bonfire
1.9
February 2012
Gliffy in JIRA
3.7
February 2012
Gliffy in Confluence
4.0
January 2012
GreenHopper
5.9
February 2012
Team Calendars
1.8
February 2012
When will my applications be upgraded?
We are committed to providing you with the latest versions of each of the applications (i.e. JIRA, Confluence, FishEye,
Crucible, Bamboo, Subversion). The upgrade process for the applications will begin as soon as possible, after the
equivalent version of the downloadable product is released. However, it might take a few weeks for the application version
to become available to you, as each application version must undergo rigorous testing first before we apply it to Atlassian
OnDemand. New features from each upgrade are outlined in the Atlassian OnDemand release summary.
We cannot delay the upgrade of any applications under any circumstances. Follow OnDemand on Twitter to keep
up-to-date with system maintenance and upgrades. If you suspect that an application upgrade will create problems for you,
please contact our support staff for assistance in mitigating any risks. You can contact our support staff by raising a ticket in
our support system under the 'OnDemand' project.
Atlassian OnDemand licensing
Atlassian OnDemand licensing is user-based. This means that the pricing for your site is determined by the number of users that you want to
have access to it. The only exception is Bamboo OnDemand, for which the calculation is based on the number of agents.
Refer to the following pages to see how the price is calculated:
Pricing: www.atlassian.com/software/ondemand/pricing
Ordering FAQ: http://www.atlassian.com/licensing/ondemand
160
Atlassian OnDemand October 2011 Documentation
How do I calculate the user count for my account?
The user count is calculated based on your application access settings, i.e. the number of users you grant access to a particular application.
You can view the user count in the Application Access administration console. For detailed instructions, see viewing your Account
Information.
How do I reduce the user count of my account?
If you have reached the user limit for an application, you have the following options:
Revoke application access from some users — you can remove access from users that do not need to work with the application.
To make this change, read the instructions on Managing application access.
Upgrade your account — if you do not want to remove access from users, you may wish to consider upgrading your account to add
more users. To make this change, read the instructions on upgrading your account.
Please note that the 'contegix' and 'sysadmin' administrative accounts do not count towards your license total.
Support Policies
Welcome to the support policies index page. Here, you'll find information about how Atlassian Support can help you and how to get in touch
with our helpful support engineers. Please choose the relevant page below to find out more.
Bug Fixing Policy
How to Report a Security Issue
New Features Policy
Security Advisory Publishing Policy
Security Update Policy
Severity Levels for Security Issues
Update Policy
To request support from Atlassian, please raise a support issue in our online support system. To do this, visit support.atlassian.com, log in
(creating an account if need be) and create an issue under the OnDemand project. Our friendly support engineers will get right back to you
with an answer.
See How to Get Legendary Support from Atlassian for an overview of the scope of support, operation hours and more.
Bug Fixing Policy
Summary
Atlassian Support will help with workarounds and bug reporting.
Critical bugs will generally be fixed in the next maintenance release.
Non critical bugs will be scheduled according to a variety of considerations.
Raising a Bug Report
Atlassian Support is eager and happy to help verify bugs — we take pride in it! Please open a support request in our support system
providing as much information as possible about how to replicate the problem you are experiencing. We will replicate the bug to verify, then
lodge the report for you. We'll also try to construct workarounds if they're possible.
Customers and plugin developers are also welcome to open bug reports on our issue tracking systems directly. Use http://jira.atlassian.com
for the stand-alone products and http://studio.atlassian.com for JIRA Studio and Atlassian OnDemand.
When raising a new bug, you should rate the priority of a bug according to our JIRA usage guidelines. Customers should watch a filed bug in
order to receive e-mail notification when a "Fix Version" is scheduled for release.
How Atlassian Approaches Bug Fixing
Maintenance (bug fix) releases come out more frequently than major releases and attempt to target the most critical bugs affecting our
customers. The notation for a maintenance release is the final number in the version (ie the 1 in 3.0.1).
If a bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable to
perform their normal functions) then it will be fixed in the next maintenance release provided that:
The fix is technically feasible (i.e. it doesn't require a major architectural change).
It does not impact the quality or integrity of a product.
For non-critical bugs, the developer assigned to fixing bugs prioritises the non-critical bug according to these factors:
161
Atlassian OnDemand October 2011 Documentation
How many of our supported configurations are affected by the problem.
Whether there is an effective workaround or patch.
How difficult the issue is to fix.
Whether many bugs in one area can be fixed at one time.
The developers responsible for bug fixing also monitor comments on existing bugs and new bugs submitted in JIRA, so you can provide
feedback in this way. We give high priority consideration to security issues.
When considering the priority of a non-critical bug we try to determine a 'value' score for a bug which takes into account the severity of the
bug from the customer's perspective, how prevalent the bug is and whether roadmap features may render the bug obsolete. We combine this
with a complexity score (i.e. how difficult the bug is). These two dimensions are used when developers self serve from the bug pile.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
How to Report a Security Issue
Finding and Reporting a Security Vulnerability
If you find a security bug in the product, please open an issue on http://jira.atlassian.com in the relevant project.
Set the priority of the bug to 'Blocker'.
Provide as much information on reproducing the bug as possible.
Set the security level of the bug to 'Developer and Reporters only'.
All communication about the vulnerability should be performed through JIRA, so that Atlassian can keep track of the issue and get a patch
out as soon as possible.
If you discover a security vulnerability, please attempt to create a test case that proves this vulnerability locally before
opening either a bug or a support issue. When creating an issue, please include information on how the vulnerability can be
reproduced; see our Bug Fixing Policy for general bug reporting guidelines. We will prioritise fixing the reported vulnerability
if your report has information on how the vulnerability can be exploited.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
New Features Policy
Summary
We encourage and display customer comments and votes openly in our issue tracking systems, http://jira.atlassian.com and
http://studio.atlassian.com.
We do not publish roadmaps.
Product Managers review our most popular voted issues on a regular basis.
We schedule features based on a variety of factors.
Our Atlassian Bug Fixing Policy is distinct from our Feature Request process.
Atlassian provides consistent updates on the top 20 feature/improvement requests (in our issue tracker systems).
How to Track what Features are Being Implemented
When a new feature or improvement is scheduled, the 'fix-for' version will be indicated in the JIRA issue. This happens for the upcoming
release only. We maintain roadmaps for more distant releases internally, but because these roadmaps are often pre-empted by changing
customer demands, we do not publish them.
How Atlassian Chooses What to Implement
In every major release we aim to implement highly requested features, but it is not the only determining factor. Other factors include:
Direct feedback from face to face meetings with customers, and through our support and sales channels.
Availability of staff to implement features.
Impact of the proposed changes on the application and its underlying architecture.
How well defined the requested feature is (some issues gain in popularity rapidly, allowing little time to plan their implementation).
Our long-term strategic vision for the product.
How to Contribute to Feature Development
Influencing Atlassian's release cycle
We encourage our customers to vote on feature requests in JIRA. The current tally of votes is available online in our issue tracking systems,
162
Atlassian OnDemand October 2011 Documentation
http://jira.atlassian.com and http://studio.atlassian.com. Find out if your improvement request already exists. If it does, please vote for it. If
you do not find it, create a new feature or improvement request online.
Extending Atlassian Products
Atlassian products have powerful and flexible extension APIs. If you would like to see a particular feature implemented, it may be possible to
develop the feature as a plugin. Documentation regarding the plugin APIs is available. Advice on extending either product may be available
on the user mailing-lists, or at Atlassian Answers.
If you require significant customisations, you may wish to get in touch with our partners. They specialise in extending Atlassian products and
can do this work for you. If you are interested, please contact us.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Security Advisory Publishing Policy
Publication of Security Advisories
When a security vulnerability in an Atlassian product is discovered and resolved, Atlassian will inform customers through the following
mechanisms:
We will post a security advisory in the latest documentation of the affected product at the same time as releasing a fix for the
vulnerability. This applies to all security advisories, including severity levels of critical, high, medium and low.
We will send a copy of all security advisories to the 'Technical Alerts' mailing list for the product concerned.
Note: To manage your email subscriptions and ensure you are on this list, please go to my.atlassian.com and click 'Email Prefs' near
the top right of the page.
If the person who reported the vulnerability wants to publish an advisory through some other agency, such as CERT, we will assist in
the production of that advisory and link to it from our own.
Early warning of critical security vulnerabilities:
If the vulnerability is rated critical (see our criteria for setting severity levels) we will send an early warning to the 'Technical Alerts'
mailing list approximately one week before releasing the fix. This early warning is in addition to the security advisory itself, described
above.
However, if the vulnerability is publicly known or being exploited, we will release the security advisory and patches as soon as
possible, potentially without early warning.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Security Update Policy
When a security issue is discovered, Atlassian will endeavour to:
Add security fixes for the current release of a product to the next Atlassian OnDemand update.
Visit our general Atlassian OnDemand Update Policy as well.
The development of Atlassian OnDemand can be followed on our bug tracking system.
Further reading
See Atlassian Support Offerings for more support-related information.
Severity Levels for Security Issues
Severity Levels
Atlassian security advisories include a severity level. This severity level is based on our self-calculated CVSS score for each specific
vulnerability. CVSS is an industry standard vulnerability metric. You can learn more about CVSS at FIRST.org web site.
CVSS scores are mapped into the following severity ratings:
Critical
High
Medium
Low
An approximate mapping guideline is as follows:
CVSS score range
163
Severity in advisory
Atlassian OnDemand October 2011 Documentation
0 – 2.9
Low
3 – 5.9
Medium
6.0 – 7.9
High
8.0 – 10.0
Critical
Below is a summary of the factors which illustrate types of vulnerabilities usually resulting in a specific severity level. Please keep in mind
that this rating does not take into account details of your installation.
Severity Level: Critical
Vulnerabilities that score in the critical range usually have the following characteristics:
Exploitation of the vulnerability results in root-level compromise of servers or infrastructure devices.
The information required in order to exploit the vulnerability, such as example code, is widely available to attackers.
Exploitation is usually straightforward, in the sense that the attacker does not need any special authentication credentials or
knowledge about individual victims, and does not need to persuade a target user, for example via social engineering, into performing
any special functions.
For critical vulnerabilities, is advised that you patch or upgrade as soon as possible, unless you have other mitigating measures in place. For
example, if your installation is not accessible from the Internet, this may be a mitigating factor.
Severity Level: High
Vulnerabilities that score in the high range usually have the following characteristics:
The vulnerability is difficult to exploit.
Exploitation does not result in elevated privileges.
Exploitation does not result in a significant data loss.
Severity Level: Medium
Vulnerabilities that score in the medium range usually have the following characteristics:
Denial of service vulnerabilities that are difficult to set up.
Exploits that require an attacker to reside on the same local network as the victim.
Vulnerabilities that affect only nonstandard configurations or obscure applications.
Vulnerabilities that require the attacker to manipulate individual victims via social engineering tactics.
Vulnerabilities where exploitation provides only very limited access.
Severity Level: Low
Vulnerabilities in the low range typically have very little impact on an organisation's business. Exploitation of such vulnerabilities usually
requires local or physical system access.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Update Policy
If a problem has been fixed in an Atlassian application, provided that an update does not impact the quality or integrity of a product, Atlassian
will ensure that patches for products are added to the next maintenance release.
As Atlassian OnDemand is a hosted service, patches do not apply. Rather, the Atlassian OnDemand system is upgraded regularly to
incorporate recent updates to the component applications, including patches for these individual applications.
Updates for the component applications are issued under the following conditions:
The bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable
to perform their normal functions).
An update is technically feasible (i.e. it doesn't require a major architectural change).
OR
The issue is a security issue, and falls under our Security Policy.
Atlassian does not provide updates for non-critical bugs.
The development of Atlassian OnDemand can be followed on our bug tracking system.
Further reading
164
Atlassian OnDemand October 2011 Documentation
See Atlassian Support Offerings for more support-related information.
Atlassian OnDemand Plugin Policy
Atlassian OnDemand comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existing
plugins. The commercial and bundled plugins listed below are included with the service, and can be enabled, disabled and/or configured via
your OnDemand administration console.
On this page:
Plugin Bundling
Add-Ons in the Future
Commercial Plugins
Hosted Commercial Plugins
Direct Purchase Commercial Plugins
Bundled Plugins
Issues (JIRA)
Wiki (Confluence)
Builds (Bamboo)
Reviews (Crucible)
Plugin Bundling
Add-Ons in the Future
We understand how important plugins are, and are committed to providing ways for Atlassian OnDemand subscribers to extend and integrate
their instances. We are currently working on ways to provide add-ons independent of the current in-process plugin framework. In this way, we
will provide hosted add-ons that are stable, secure, and can be developed and maintained by their contributors. As these efforts begin to
yield results, updates will be provided on this page.
As soon as we're ready, we will be reaching out to developers of plugins for which there are bundling requests directly with more information
on what's coming and how they can participate.
Commercial Plugins
The following third-party plugins are available in Atlassian OnDemand under commercial licenses. This means that the plugins are installed
in OnDemand, but you need to purchase the relevant third-party license for each plugin to use it.
Hosted Commercial Plugins
The following plugins are available under Atlassian's Hosted Commercial Add-ons program. You may order licenses for these products by
logging into your account at http://my.atlassian.com.
Family / Base product
Add-ons
Confluence
Gliffy
Team Calendars
JIRA
Bonfire
Direct Purchase Commercial Plugins
Gliffy
GreenHopper
Licenses for the following products must
be purchased directly from the plugin vendor. See the individual products below for more
information.
The Tempo Plugin for JIRA. This plugin enables you to track time using JIRA. A 30-day trial for Tempo is enabled as part of the
30-day trial of JIRA, after which you must purchase a license for it. Further information on working with Tempo is available from this
Tempo Plugin FAQ.
The Balsamiq Mockups for JIRA and Confluence plugins. A 30-day trial for Balsamiq (JIRA and Confluence) is available if you want
to try it out. After the 30-day trial, you must purchase a license for it in Balsamiq's website.
Balsamiq Mockups for JIRA: view how to enable it on disable or enable a JIRA plugin
Balsamiq Mockups for Confluence: view how to enable it on disable or enable a Confluence plugin
CustomWare Salesforce.com Connector
Bundled Plugins
Issues (JIRA)
The following plugins are installed on JIRA OnDemand. You can disable or enable a JIRA plugin as needed.
Flowdock for JIRA
GreenHopper
CustomWare Get Satisfaction Connector Plugin
CustomWare Sauce Labs Connector Plugin
165
Atlassian OnDemand October 2011 Documentation
CustomWare uTest Connector Plugin
CustomWare Zendesk Connector Plugin
DVCS Connector Plugin
JIRA Bamboo Plugin
JIRA Calendar Plugin
JIRA Charting Plugin
JIRA FishEye Plugin
JIRA Miscellaneous Workflow Extensions Plugin
JIRA Suite Utilities Plugin
JIRA Toolkit Plugin
JIRA Timesheet Report and Portlet Plugin
JIRA Wallboards Plugin
Zephyr Test Management Plugin
Wiki (Confluence)
The following plugins are installed on Confluence OnDemand. You can disable or enable a Confluence plugin as needed.
Content Formatting Macros
Table Plugin
Builds (Bamboo)
The Auto-Favourite Plugin is bundled with Bamboo and enabled by default.
Reviews (Crucible)
While Crucible boasts a plugin API, we do not currently offer any plugins for Crucible.
Third-Party Plugin Process
JIRA Studio comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existing plugins.
Requests for additional plugins should be created as feature requests in the 'JIRA Studio' project on https://studio.atlassian.com. Plugins will
be evaluated for compatibility with JIRA Studio and may be bundled in a future release.
For plugin vendors this means that any plugin you wish to be used with JIRA Studio needs to be tested against JIRA Studio, verified by the
JIRA Studio team, and then added to a future release of JIRA Studio.
Getting commercial plugins verified for JIRA Studio
For vendors to verify a commercial plugin,
1. Create a feature request in the 'JIRA Studio' project on https://studio.atlassian.com, if one doesn't already exist. This
will notify the team and product manager of the desire to bundle the plugin. Please include a link to the plugin's page
on plugins.atlassian.com.
2. Create a support request in the 'JIRA Studio' project on http://support.atlassian.com to have the plugin installed on the
Studio Plugin Testing instance, and have a user created with administrative access so you can test the plugin with
JIRA Studio.
3. Once you verify that the plugin works with JIRA Studio, update the feature request on StAC to note that the plugin
appears compatible.
4. The feature request will then be placed into the feature backlog for JIRA Studio development. We can not guarantee
that any given plugin will be certified and bundled with a future release, but will prioritise bundling of future plugins
based on customer interest. Plugin vendors who are seeing interest from customers should encourage these
customers to vote on the feature request at StAC.
Unless otherwise stated, bundled third-party plugins are not considered "supported" by Atlassian, and support and future
version compatibility is the responsibility of the vendor.
At this time, we have no plans to offer additional third-party commercial plugins for sale directly from the Atlassian website
or order form.
About Your Data
This page contains information on the deletion policy for Atlassian OnDemand.
On this page:
Data backups
Data deletion policy
What happens if I want to delete my Atlassian OnDemand instance?
166
Atlassian OnDemand October 2011 Documentation
Data retention
Requesting a data export
How to claim accounts
How billing works
Data backups
Point in time backups for your instance are taken every 24 hours for purposes of recovery from application failure. Beginning with our
OnDemand platform backups are stored at a location separate from the data center. Use of backup data to roll back changes to application
data is not supported. Backups are retained for seven days, and then deleted.
Data deletion policy
What happens if I want to delete my Atlassian OnDemand instance?
If you cancel your Atlassian OnDemand subscription, the system image and the data stored in it will eventually be deleted.
The events that occur during account cancellation are outlined below:
1. Cancel your subscription. Your OnDemand instance will remain active until the end of your final subscription period.
2. Once your subscription period is finished, your instance will be deactivated shortly afterward.
3. Once your instance is deactivated, Atlassian will retain your image and its data for 15 days. During this time, you can have your
instance reactivated by renewing your subscription.
4. Once 15 days has elapsed after deactivation, Atlassian will delete the system image and all of its data. Once this is done, the data
cannot be recovered.
Atlassian will not delete any of your data stored in Google Apps Marketplace, such as users or information in your Google
Apps database, Google Docs, Gmail messages, Google Calendar entries, Google Chat, or Google Sites.
Data retention
Your data is retained for 15 days after deactivation. After that time, Atlassian will delete the system image and all of its data. Once this is
done, the data cannot be recovered.
Requesting a data export
Due to the complexity of export operations support cannot provide exports for trial instances of OnDemand. Development is
working on a customer-facing backup manager and will release it shortly. The issue is tracked here: JST-5677. Please
watch the issue to see the progress.
Data exports from OnDemand will only be provided in the case that you are cancelling the OnDemand service. You can request this one-time
export at any time once you have decided to cancel your service as long as your instance is still active and accessible, i.e. before the end of
your final subscription period. You can request this by submitting a support request.
If you are in need of a Confluence backup, you can produce a space backup at any time and the assistance of our support team is not
needed, i.e. you do not need to submit a support request.
Once your system image and its data have been deleted, that information cannot be retrieved.
How to claim accounts
Once your instance is deactivated, Atlassian will retain your image and its data for 15 days. During this time, you can have your instance
reactivated by paying for a new subscription.
How billing works
Atlassian OnDemand fees are paid in advance, so when you deactivate your account, Atlassian will stop billing you immediately. Your
OnDemand instance will remain active until the end of your final subscription period.
Atlassian offer full refunds during the first month of paid service following the end of the evaluation. After the first paid month, Atlassian does
not provide refunds for paid services.
Maintenance windows
Regular weekly maintenance windows
In order to more quickly and regularly bring new Atlassian product features and fixes to you, we are updating your instances in weekly
167
Atlassian OnDemand October 2011 Documentation
maintenance windows at the times listed below.
Your region
Window
APAC
every Monday at 20:00 - 22:00, Sydney time
EMEA
every Monday at 00:00 - 02:00, Geneva time
(including India)
U.S.
every Sunday at 19:00 - 21:00, San Francisco time
Communication on maintenance windows
Regular weekly maintenance windows: We will not send maintenance notifications unless we need to deviate from the weekly
schedule.
Other types of maintenance: For other required maintenance such as urgent fixes, we will notify you at least 12 hours in advance,
by sending an email message to all technical contacts listed under your account at my.atlassian.com.
Follow us on Twitter: We will tweet any maintenance scheduled outside of the weekly regular windows as well as any outages with
the @OnDemandStatus account (OnDemand on Twitter).
Related topics
Where do I set the region used for maintenance windows?
Atlassian OnDemand FAQ
Need more help?
Do you have a question, or need help with Atlassian OnDemand? Check out Answers from the community. To request
support, create a support request.
Usage
How can I edit or reassign closed issues?
How can I prevent certain users seeing certain content?
How do I access my Subversion repository?
How do I file bugs or log feature requests?
How do I update JIRA issues via subversion commit messages?
How should OnDemand be configured for a shared code module?
What is the server base URL for my wiki in Atlassian OnDemand?
What is the URL for my installation of Atlassian OnDemand?
What happens to my existing projects if I purchase new applications?
Integration with Google Apps
Google Apps Integration FAQ
168
Atlassian OnDemand October 2011 Documentation
Configuration and Administration
Can I use a custom Elastic Bamboo image?
Subversion is constantly asking users to re-authenticate and failing with the correct credentials
Can I change the look and feel of Atlassian OnDemand?
Can I install my own plugins?
Are alternative languages available for Atlassian OnDemand?
What remote APIs are supported in Atlassian OnDemand?
Can I use EBS volumes with Elastic Bamboo?
How do I create a backup copy of my Subversion repository?
How do I add Google Apps to Atlassian OnDemand?
Can I use Clover with Atlassian OnDemand?
How do I import Subversion data for a single project?
How do I migrate from Visual SourceSafe to Atlassian OnDemand?
How are we notified of system maintenance?
When will my Atlassian OnDemand applications be upgraded?
Where do I set the region used for maintenance windows?
Users are locked out of FishEye and Crucible REST APIs
I cannot log in using my Google Apps account
I cannot find my applications after adding them
Do you support SSL?
Subscription and Account
Can I disable a user without deleting them?
How do I add a technical contact to my account?
How do I get started with the Tempo Plugin?
How do I upgrade my account, renew my license, change credit card details, etc?
How is the user count of my account calculated? How do I reduce my user count?
What are the storage and bandwidth limits?
What database does the Atlassian OnDemand instance use?
What domain name will my OnDemand service be on? Can I use my own domain name?
What happens to my OnDemand instance when my account is cancelled?
What is the minimum number of users allowable in an upgrade?
What is the minimum term of service?
Support
Supported browsers
About Your Data
Atlassian OnDemand Application Versions
Restricted Functions in Atlassian OnDemand
Atlassian OnDemand licensing
Atlassian OnDemand Plugin Policy
Support Policies
Usage FAQ
Find answers to common questions about using Atlassian OnDemand here.
How can I edit or reassign closed issues?
How can I prevent certain users seeing certain content?
How do I access my Subversion repository?
How do I file bugs or log feature requests?
How do I update JIRA issues via subversion commit messages?
How should OnDemand be configured for a shared code module?
What is the server base URL for my wiki in Atlassian OnDemand?
What is the URL for my installation of Atlassian OnDemand?
What happens to my existing projects if I purchase new applications?
169
Atlassian OnDemand October 2011 Documentation
Other FAQs
Don't know how to configure something in OnDemand? Try the Configuration and Administration FAQ.
How can I edit or reassign closed issues?
JIRA's default workflow prevents closed issues from being edited or reassigned. If you wish to loosen this restriction, it can be done by
editing the JIRA workflow and removing the jira.issue.editable flag from the Closed step:
1. If you are using the default jira workflow, copy the workflow and edit the copy. If you are already using a customised workflow,
create a draft of it and edit the draft.
2. In the workflow, remove the jira.issue.editable flag as described in the JIRA workflow documentation.
3. Activate the workflow by creating a Workflow Scheme that uses your edited workflow, and associating the workflow scheme with the
relevant projects.
You will now be able to edit or bulk edit the issues.
How can I prevent certain users seeing certain content?
You can use the following options to restrict access:
1. Restrict application access, i.e. licenses. Users without the access to a particular application cannot log in to it.
2. Restrict issue visibility to just the reporter and some group. For instance you may wish to let end users raise issues, and not see
issues raised by other users. This can be achieved by creating an issue security scheme and applying it to the project.
3. Divide users into groups, and restrict which projects a group can see. For instance one might have a Finance project that only
finance people should be able to see. This can be achieved by defining a new group for the finance department and configuring
permissions for the new group in each application as needed. For details, see the Managing application permissions page.
How do I access my Subversion repository?
Accessing the Subversion repository
You may view your repository and code activity via the 'Source' tab.
In order to add, update or delete files in Subversion, you will need to use an appropriate tool to access Subversion at the following location:
https://<account_name>.atlassian.net/svn
where <account_name> is the account name that you provided at signup.
For example, you may check out source code as a specified user by executing this Subversion command:
> svn co --username USERNAME https://<account_name>.atlassian.net/svn
The free "Version Control with Subversion" (Pilato, Collins-Sussman, Fitzpatrick; 2004 O'Reilly) online Subversion reference contains
detailed documentation on using the Subversion repository.
Troubleshooting
If you receive an error like the following:
svn: E175009: Unable to connect to a repository at URL
'https://example.atlassian.net/svn/FOO/trunk/'
svn: E175009: XML parsing failed: (411 Length Required)
you need to ensure that your SVN client is using the Neon HTTP library, which is the default, and not Serf. This is due to a bug in Serf with
reverse proxies.
How do I file bugs or log feature requests?
If you find a bug in Atlassian OnDemand, or have a suggestion for improving it, please file a Bug or Feature Request at
https://studio.atlassian.com under the OnDemand project. You may need to create an account if you do not have one already.
Please also see 'How we choose what to implement' for further details on how we handle feature requests and bugs.
How do I update JIRA issues via subversion commit messages?
If you are working with code in the Source and Review bundle, you can action JIRA issues via commit messages. By using particular
170
Atlassian OnDemand October 2011 Documentation
keywords in your commit message, you can log work, add comments or change the status of an issue. This makes it easy for you to maintain
any issues that are related to the code you are changing. See Using Smart Commits for more details .
This functionality is currently only available for Subversion repositories and does not work with Bitbucket or GitHub integration. If you'd like to
see this functionality made available for Bitbucket or GitHub, please vote for it at https://studio.atlassian.com/browse/BBC-123.
How should OnDemand be configured for a shared code module?
Developers often factor out reusable code out of projects into separate modules, which are then moved to a Subversion directory separate
from the main codebase. These modules are often not large enough to warrant their own JIRA project or Confluence space. In this case it is
desirable to have just a FishEye module (under the 'Source' tab) for viewing the source, with no other references to the module in the project
list drop-down or elsewhere.
This can be achieved by setting the JIRA project and Confluence space invisible and then associating the Subversion repository with all the
projects that use the common module.
To set the JIRA project and Confluence space invisible:
1. Create an OnDemand project (eg. COMMON) and go to the JIRA project configuration page.
2. In the new project's admin section:
a. In the People section, find the Project Roles row, click View members and remove the groups from all roles. This
effectively makes the JIRA project invisible everywhere except in the admin section.
b. Click Space Admin, then Permissions, and revoke the 'View' permission from all groups. This makes the Confluence
space invisible to everyone except the user who created the project.
c. Click Manage Project Tabs and hide the Issues and Wiki tabs.
The project will now be invisible except for within the 'Source' tab.
Now for each project that uses the common module:
1. Go to that project's OnDemand administration page and on the 'Subversion Repository' line and click Select
2. For 'FishEye repository key', enter the module name (eg. COMMON) and add it as a non-primary association.
Now any commits in the COMMON codebase that reference an issue key will appear on the referenced issue's 'Source' tab.
What is the server base URL for my wiki in Atlassian OnDemand?
The server base URL for the wiki in Atlassian OnDemand is in the following format.
https://<account_name>.atlassian.net/wiki
where <account_name> is the account name of your OnDemand site.
What is the URL for my installation of Atlassian OnDemand?
URL
By default, you are assigned a domain name of:
https://<account_name>.atlassian.net
where account_name is the account name you provided at sign-up.
The URL cannot be changed afterwards.
After you sign up, the installation takes about 15 minutes to finish and your URL should be available after that amount of time.
Wiki URL
The URL for your wiki is: https://<account_name>.atlassian.net/wiki
What happens to my existing projects if I purchase new applications?
After you purchase new Atlassian OnDemand applications, the relevant objects in the newly purchased applications will be automatically
created for your existing projects.
For example:
Your site already has JIRA and you have created JIRA projects. After you add Confluence, Confluence spaces will be automatically
created for the existing JIRA projects.
Similarly, if you add the Source and Review Bundle to your site, source repositories will be automatically created for the existing
projects.
See the project page for information about what an OnDemand project is.
Configuration and Administration FAQ
171
Atlassian OnDemand October 2011 Documentation
Find answers to common questions about configuring and administering Atlassian OnDemand here.
Can I use a custom Elastic Bamboo image?
Subversion is constantly asking users to re-authenticate and failing with the correct credentials
Can I change the look and feel of Atlassian OnDemand?
Can I install my own plugins?
Are alternative languages available for Atlassian OnDemand?
What remote APIs are supported in Atlassian OnDemand?
Can I use EBS volumes with Elastic Bamboo?
How do I create a backup copy of my Subversion repository?
How do I add Google Apps to Atlassian OnDemand?
Can I use Clover with Atlassian OnDemand?
How do I import Subversion data for a single project?
How do I migrate from Visual SourceSafe to Atlassian OnDemand?
How are we notified of system maintenance?
When will my Atlassian OnDemand applications be upgraded?
Where do I set the region used for maintenance windows?
Users are locked out of FishEye and Crucible REST APIs
I cannot log in using my Google Apps account
I cannot find my applications after adding them
Do you support SSL?
Other FAQs?
Don't know how to use something in OnDemand? Try the Usage FAQ.
Have a question about Google Apps integration? Try the Google Apps Integration FAQ.
Can I use a custom Elastic Bamboo image?
The Atlassian default image is used to create elastic agents for your Bamboo OnDemand. This means that all elastic agents will inherit
capabilities from the default image.
If you want to use a custom Elastic Bamboo image, you can create one by following the instructions in the Bamboo documentation. However,
please note that we do not support custom elastic images in OnDemand.
Maintaining your elastic image
If you use a custom elastic image with your Bamboo OnDemand, you will need to ensure that it is running the correct agent
version. This means that you may need to periodically upgrade your image to match the Bamboo OnDemand version, e.g.
if Bamboo OnDemand is running Bamboo 3.0, your agent version needs to be 3.0. You can view the Bamboo OnDemand
on the Atlassian OnDemand Application Versions page.
Using an EBS volume instead of a custom image
For easier maintainability, you should use an EBS volume with the default Bamboo image rather than creating your own
custom image, as creating a custom image is not a trivial process. You do not need to update your image each time
Bamboo OnDemand is upgraded if you use this method. You can read about EBS volumes and reasons for using them in
the Bamboo documentation.
Subversion is constantly asking users to re-authenticate and failing with the correct
credentials
Certains user groups of Subversion may experience authentication issues such as this:
Authentication realm: <https://example.jira.com:443>
Password for 'jturner':
Authentication realm: <https://example.jira.com:443>
Username: jturner
Password for 'jturner':
Authentication realm: <https://example.jira.com:443>
Username: svn: PROPFIND of '/svntest': authorization
Subversion Repository
Subversion Repository
Subversion Repository
failed (https://example.jira.com)
This may be due to a configuration issue on your Subversion permissions. Subversion clients require unnecessary read access on the root
path.
172
Atlassian OnDemand October 2011 Documentation
To workaround this problem, ensure that a group which all Subversion users belong to (such as users) has read access to the root path. The
permission from the root path will be inherited by your project folders. You can then revoke the read permission under each project. See also
how to set default permissions for new projects.
The permission changes may require up to five minutes to take effect.
Can I change the look and feel of Atlassian OnDemand?
Atlassian OnDemand does not allow the modification or installation of themes, but you can modify the look and feel of some aspects of your
site. See Configuring the look and feel for further details.
If your site has multiple OnDemand applications, changes may not apply to all applications, e.g. the colours of the links and headers in
content can only be modified for JIRA.
Can I install my own plugins?
You can not install your own plugins. You can only enable or disable the bundled plugins in Atlassian OnDemand.
Please read the Atlassian OnDemand Plugin Policy for the list of installed plugins and instructions on how to request plugins.
Are alternative languages available for Atlassian OnDemand?
Due to limited language support in some of the applications that comprise Atlassian OnDemand, English (US) is currently the only supported
language. Please follow JST-801 for updates.
What remote APIs are supported in Atlassian OnDemand?
Atlassian OnDemand supports the remote APIs listed below. The OnDemand remote APIs are identical to the remote APIs shipped with the
downloadable version of these products.
JIRA — XML-RPC and SOAP APIs. Read more about the JIRA Remote API.
Confluence — XML-RPC and SOAP APIs. Read more about the Confluence Remote API.
FishEye — XML-RPC and REST APIs. Read more about the FishEye Remote API.
If you are having problems using these remote APIs, please raise a support request at https://support.atlassian.com under the OnDemand
project.
Related topics
What is the server base URL for my wiki in Atlassian OnDemand?
Can I use EBS volumes with Elastic Bamboo?
If you are using Elastic Bamboo in Atlassian OnDemand, you can configure it to use EBS volumes.
What are EBS volumes?
The Amazon Elastic Block Store (EBS) provides 'EBS volumes' which can attach to EC2 instances. EBS volumes (and the 'EBS snapshots'
created from these volumes) provide persistent storage for your elastic instances.
If you have relatively static resources required for building your Bamboo Jobs (such as, source code checkouts and Maven repository
artifacts), you can add these to an EBS volume. From this volume, you can create an EBS snapshot, which effectively records the 'state' of
an EBS volume at a given point in time.
How do I use an EBS volume with Elastic Bamboo?
If you want to use an EBS volume, you can create one by following the instructions in the Bamboo documentation. You will also need to
create a support ticket and attach your private key and certificate file. Our support team will copy these files to the EC2 directory of your
OnDemand instance and configure Bamboo to use those files.
Related topics
Getting started with Bamboo OnDemand
How do I create a backup copy of my Subversion repository?
If you would like a local read-only mirror of the OnDemand-hosted Subversion repository, you can do it with the svnsync command.
The domain name for sites created before Nov 8, 2011 is https://<account_name>.jira.com.
Please replace atlassian.net with jira.com as needed.
173
Atlassian OnDemand October 2011 Documentation
For example:
$ mkdir backupsvn
$ svnadmin create backupsvn
$ cat > backupsvn/hooks/pre-revprop-change << EOF
#!/bin/sh
EOF
$ chmod +x backupsvn/hooks/pre-revprop-change
$ svnsync init file://`pwd`/backupsvn https://<account_name>.atlassian.net/svn/
Copied properties for revision 0.
$ svnsync sync file://`pwd`/backupsvn
Committed revision 1.
Copied properties for revision 1.
Committed revision 2.
Copied properties for revision 2.
Committed revision 3.
Copied properties for revision 3
....
See this write-up for a full overview of the process.
If you find your sync is timing out after an hour or so, you may need to adjust the http-timeout setting in your SVN client as described
here.
How do I add Google Apps to Atlassian OnDemand?
This page contains up to date information on how to add Google Apps to your Atlassian OnDemand site.
On this page:
Does Google Apps integration cost extra?
Which versions of Google Apps support OnDemand?
Can I create user accounts in OnDemand for users who are not members of my Google Apps domain?
How do I get Google Apps pre-packaged?
Upgrade process to Google Apps for existing OnDemand customers
How do you evaluate OnDemand with Google Apps integration?
Can existing OnDemand evaluators enable Google Apps integration?
After migrating to Google Apps, can I change the history of my Subversion repository and issues?
Is the number of users based on the number of Google Apps domain accounts, or can we enable OnDemand just for some of them?
(to limit cost of licenses)
Can non-Google Apps users authenticate to Atlassian OnDemand after I've migrated?
Does Google Apps integration cost extra?
No, it's available at no additional cost to Atlassian OnDemand customers, including evaluators.
Which versions of Google Apps support OnDemand?
Atlassian OnDemand works with all versions of Google Apps.
Can I create user accounts in OnDemand for users who are not members of my Google Apps domain?
Yes. You can provide access to OnDemand for clients, contacts, or remote workers who do not have access to your Google Apps domain, or
who do not have a Google Apps account. Refer to the right-hand panel in page: Managing users and groups for sites integrated with Google
Apps.
How do I get Google Apps pre-packaged?
New OnDemand customers can have Google Apps integration set up right from provisioning. Simply add OnDemand via the Google Apps
Marketplace and enjoy Google Apps integration as soon as your OnDemand site is live.
Upgrade process to Google Apps for existing OnDemand customers
After you integrate OnDemand and Google Apps, you will need to merge the user accounts between systems. Your OnDemand service will
depend on Google for user account management.
See Integrating OnDemand with Google Apps for more information.
How do you evaluate OnDemand with Google Apps integration?
This can be done via the OnDemand listing on Google Apps Marketplace.
174
Atlassian OnDemand October 2011 Documentation
Can existing OnDemand evaluators enable Google Apps integration?
No. Existing evaluators can sign up for a new evaluation from Google Apps Marketplace if desired.
After migrating to Google Apps, can I change the history of my Subversion repository and issues?
(In other words, can we preserve the names of the owners of the tickets and revision authors after migration?)
Not at this stage. If a solution becomes available, we will update this page.
Is the number of users based on the number of Google Apps domain accounts, or can we enable OnDemand just
for some of them? (to limit cost of licenses)
Users will not count towards your license until they are granted access to a particular application. For Google Apps users, they will be
automatically assigned access to the applications at their initial login according to your setting for default application access. For details, see
Managing application access.
Can non-Google Apps users authenticate to Atlassian OnDemand after I've migrated?
Yes. You can provide external users — remote workers, clients, contractors — with logins to your OnDemand instance. See how to do this in
Managing Users with Google Apps Integration. However, users who don't have a Google ID will not be able to access Google-specific
features of the Google Apps Activity Bar, e.g. Google Docs.
Can I use Clover with Atlassian OnDemand?
The use of Clover with Atlassian OnDemand is not supported.
How do I import Subversion data for a single project?
The Subversion importer overwrites any existing Subversion data for all projects. The Subversion importer cannot merge data into an existing
repository.
If you want to import Subversion data for a single project without losing existing data in OnDemand, use the following process:
1. Clone the existing OnDemand SVN data locally by following the instructions on Mirror your Subversion repository locally.
2. Merge your new project's data with the mirrored local SVN data, e.g.:
$ cat newproj.svn.dump | svnadmin load --parent-dir NEWPROJ /path/to/my/svn/
3. Create a new dump of the new data set in the repository.
4. Upload the new data set with the Subversion Importer.
Related topic
Importing Versioned Data into Subversion
How do I migrate from Visual SourceSafe to Atlassian OnDemand?
To migrate from Visual SourceSafe to Atlassian OnDemand:
1. Export your data from Visual SourceSafe in the Subversion format.
2. Import the Subversion data.
How do I use Visual Studio to access code, and check in and check out source files?
You can use the Atlassian Connector for Visual Studio for this purpose.
Read the documentation and then download the Connector at the download page.
Related topics
Requesting support
How do I import Subversion data for a single project?
How are we notified of system maintenance?
Please see the Maintenance windows page.
175
Atlassian OnDemand October 2011 Documentation
Related topics
Requesting support
Where do I set the region used for maintenance windows?
When will my Atlassian OnDemand applications be upgraded?
We are committed to providing you with the latest versions of each of the applications (i.e. JIRA, Confluence, FishEye, Crucible, Bamboo,
Subversion). The upgrade process for the applications will begin as soon as possible, after the equivalent version of the downloadable
product is released. However, it might take a few weeks for the application version to become available to you, as each application version
must undergo rigorous testing first before we apply it to Atlassian OnDemand. New features from each upgrade are outlined in the Atlassian
OnDemand release summary.
We cannot delay the upgrade of any applications under any circumstances. Follow OnDemand on Twitter to keep up-to-date with
system maintenance and upgrades. If you suspect that an application upgrade will create problems for you, please contact our support staff
for assistance in mitigating any risks. You can contact our support staff by raising a ticket in our support system under the 'OnDemand'
project.
Related topics
Atlassian OnDemand Application Versions
Maintenance windows
How are we notified of system maintenance?
Where do I set the region used for maintenance windows?
The region used is based on the main Technical Contact's address in my.atlassian.com.
Please log in to my.atlassian.com to change the region setting.
Related topics
Maintenance windows
Users are locked out of FishEye and Crucible REST APIs
Users can become locked out of the FishEye and Crucible REST APIs as a result of attempting to use incorrect credentials to log in to those
applications. The most common cause of this is when the Atlassian IDE Connector is set up to use incorrect credentials, for example due to
the user having changed their password.
If this happens to your users, you can resolve the issue by resetting the FishEye CAPTCHA for the user.
The way it works is that after the reset operation, CAPTCHA is no longer required by FishEye and your users can therefore log in again after
fixing the credentials.
To reset the FishEye CAPTCHA for your users:
1. Log in as an administrator, click the menu labelled with your user name in the header, and select Administration. The
administration console appears with the General tab active.
2. Click User Management > Users.
3. Locate the user name, and click the name to open the user details.
4. Locate Reset FishEye CAPTCHA, and click Reset.
Action for the your users:
Your users must update their credentials in the services that are causing the authentication failures.
I cannot log in using my Google Apps account
If you encounter the error that says the single sign-in feature is disabled for your domain when logging in to Atlassian OnDemand with your
Google Apps account, the cause is that Google does not allow OpenID authentication through Google Apps premier accounts by default.
Regular Google Apps accounts work fine.
To solve the issue:
1.
2.
3.
4.
176
Log in to your Google Apps account as administrator.
Go to Advanced tools
In the Authentication section, click Federated Login using OpenID.
Select the Allow users to sign in to third party websites using OpenID check box .
Atlassian4.OnDemand October 2011 Documentation
I cannot find my applications after adding them
After you add new applications on top of what you already have, e.g. adding Confluence OnDemand on top of JIRA, you and your users will
not be able to access the newly added applications until you grant application access to these applications for your users.
To grant application access to the newly added applications:
1. Go to https://<account_name>.atlassian.net/secure/admin/user/ApplicationAccessConfig!default.jspa
or
https://<account_name>.jira.com/secure/admin/user/ApplicationAccessConfig!default.jspa
2. Configure application access as needed. For more information, please see Managing application access.
Do you support SSL?
All Atlassian OnDemand sites enforce SSL by default.
Related topics
What domain name will my OnDemand service be on? Can I use my own domain name?
Subscription and Account FAQ
Find answers to common questions about your Atlassian OnDemand account and ordering Atlassian OnDemand here.
Can I disable a user without deleting them?
How do I add a technical contact to my account?
How do I get started with the Tempo Plugin?
How do I upgrade my account, renew my license, change credit card details, etc?
How is the user count of my account calculated? How do I reduce my user count?
What are the storage and bandwidth limits?
What database does the Atlassian OnDemand instance use?
What domain name will my OnDemand service be on? Can I use my own domain name?
What happens to my OnDemand instance when my account is cancelled?
What is the minimum number of users allowable in an upgrade?
What is the minimum term of service?
Other Atlassian OnDemand FAQs
Don't know how to configure something? Try the Configuration and Administration FAQ.
Don't know how to use something? Try the Usage FAQ.
Can I disable a user without deleting them?
You can disable a user by removing their ability to log in. To do so, just revoke application access from the user by using the the instructions
on Managing application access.
Note that revoking application access from a user does not remove the user from any notification groups, and therefore the user will continue
receiving notification emails. But they will not be able to log in.
Disabled users do not count towards your licence, but they will remain in the system.
177
Atlassian OnDemand October 2011 Documentation
Related topics
Managing permissions
Atlassian OnDemand licensing
How do I add a technical contact to my account?
You can add a technical contact person to your account at my.atlassian.com by entering the person's email address in your hosted account
details on the 'Licenses' page.
To add a technical contact to your account:
1.
2.
3.
4.
5.
Sign in at my.atlassian.com.
In the header, click Licenses.
Located the Atlassian OnDemand license, and click the plus '+' sign to expand the options for the account.
Locate the Technical Contact field, enter your contact's email address, and click Add.
If the person has not yet signed up to my.atlassian.com, you will be prompted for more information. Enter the information and click '
Save'.
The person will receive an email informing them that they have been automatically signed up at my.atlassian.com. The email will
contain their username and password.
You can assign an unlimited number of technical contacts to your account. However, if you have a large number of contacts, you may wish to
create a mail alias at your organisation to manage the list. We currently can't add technical contacts to Evaluation licenses.
Adding a technical contact to my.atlassian.com does not automatically add the person as a user on your hosted system and does not
affect the number of users in your account.
How do I get started with the Tempo Plugin?
The Tempo plugin requires time-tracking to be enabled in JIRA. Time-tracking is enabled by default, but if you have disabled it, you will need
to re-enable it before using this plugin.
If you need help using the Tempo plugin, the Tempo website provides administration and user documentation:
Tempo Administration Documentation
Tempo User Documentation
How do I upgrade my account, renew my license, change credit card details, etc?
Accounts are managed through your My Atlassian account.
Go to http://my.atlassian.com to increase or decrease your account's user licenses, renew your license, change your credit card details,
update your personal information, etc.
How is the user count of my account calculated? How do I reduce my user count?
The user count is calculated based on your application access settings, i.e. the number of users you grant access to a particular application.
You can view the user count in the Application Access administration console. For detailed instructions, see viewing your Account
Information.
How do I reduce the user count of my account?
If you have reached the user limit for an application, you have the following options:
Revoke application access from some users — you can remove access from users that do not need to work with the application.
To make this change, read the instructions on Managing application access.
Upgrade your account — if you do not want to remove access from users, you may wish to consider upgrading your account to add
more users. To make this change, read the instructions on upgrading your account.
Please note that the 'contegix' and 'sysadmin' administrative accounts do not count towards your license total.
What are the storage and bandwidth limits?
The initial storage available for each Atlassian OnDemand instance is 25GB. Accounts that exceed that amount will be billed an over limit
fee of $1.00 per gigabyte per month, or if different, the then-current fee.
There are no bandwidth limits.
What database does the Atlassian OnDemand instance use?
All Atlassian OnDemand instances run on the open source PostgreSQL database.
178
Atlassian OnDemand October 2011 Documentation
What domain name will my OnDemand service be on? Can I use my own domain
name?
Your site is assigned a domain name of https://<account_name>.atlassian.net, where account_name is the account name you
provided at sign-up.
After you sign up, the installation takes about 15 minutes to finish and your URL should be available after that amount of time.
Use of custom domain names is not currently supported. And the URL cannot be changed afterwards.
Why is my site on the jira.com?
There has been a domain name change on November 7, 2011. Before this date, the signups were assigned the domain name of
https://<account_name>.jira.com.
What happens to my OnDemand instance when my account is cancelled?
Please see this FAQ: http://www.atlassian.com/licensing/ondemand
What is the minimum number of users allowable in an upgrade?
Please refer to the following pages:
Ordering FAQ: http://www.atlassian.com/licensing/ondemand#orderingatlassianondemand-1
Pricing: www.atlassian.com/software/ondemand/pricing
What is the minimum term of service?
The minimum term of service is one month.
See also:
Order FAQ on www.atlassian.com
Google Apps Integration FAQ
This page contains frequently asked questions about using Atlassian OnDemand with Google Apps Integration.
How do you evaluate or buy Atlassian OnDemand with Google Apps integration?
This can be done via the OnDemand listing on Google Apps Marketplace.
Does Google Apps integration cost extra?
No, it's available at no additional cost to Atlassian OnDemand customers, including evaluators.
Which versions of Google Apps support OnDemand?
Atlassian OnDemand works with all versions of Google Apps.
Can I create user accounts in OnDemand for users who are not members of my Google Apps domain?
Yes. You can provide access to OnDemand for clients, contacts, or remote workers who do not have access to your Google Apps domain, or
who do not have a Google Apps account. Refer to the right-hand panel in page: Managing users and groups for sites integrated with Google
Apps.
How do I get Google Apps pre-packaged?
New OnDemand customers can have Google Apps integration set up right from provisioning. Simply add OnDemand via the Google Apps
Marketplace and enjoy Google Apps integration as soon as your OnDemand site is live.
Upgrade process to Google Apps for existing OnDemand customers
After you integrate OnDemand and Google Apps, you will need to merge the user accounts between systems. Your OnDemand service will
depend on Google for user account management.
See Integrating OnDemand with Google Apps for more information.
How do you evaluate OnDemand with Google Apps integration?
This can be done via the OnDemand listing on Google Apps Marketplace.
179
Atlassian OnDemand October 2011 Documentation
Can existing OnDemand evaluators enable Google Apps integration?
No. Existing evaluators can sign up for a new evaluation from Google Apps Marketplace if desired.
After migrating to Google Apps, can I change the history of my Subversion repository and issues?
(In other words, can we preserve the names of the owners of the tickets and revision authors after migration?)
Not at this stage. If a solution becomes available, we will update this page.
Is the number of users based on the number of Google Apps domain accounts, or can we enable OnDemand just
for some of them? (to limit cost of licenses)
Users will not count towards your license until they are granted access to a particular application. For Google Apps users, they will be
automatically assigned access to the applications at their initial login according to your setting for default application access. For details, see
Managing application access.
Can non-Google Apps users authenticate to Atlassian OnDemand after I've migrated?
Yes. You can provide external users — remote workers, clients, contractors — with logins to your OnDemand instance. See how to do this in
Managing Users with Google Apps Integration. However, users who don't have a Google ID will not be able to access Google-specific
features of the Google Apps Activity Bar, e.g. Google Docs.
Contributing to the Atlassian OnDemand Documentation
Would you like to share your hints, tips and techniques with us and with other users? We welcome your contributions.
On this page:
Contributing Documentation in Other Languages
Updating the Documentation Itself
Getting Permission to Update the Documentation
Following our Style Guide
How We Manage Community Updates
Contributing Documentation in Other Languages
Have you written a guide to Atlassian OnDemand in a language other than English, or translated one of our guides? Let us know, and we will
link to your guide from our documentation. More....
Updating the Documentation Itself
Have you found a mistake in the documentation, or do you have a small addition that would be so easy to add yourself rather than asking us
to do it? You can update the documentation page directly.
Getting Permission to Update the Documentation
Our documentation wiki contains developer-focused documentation (such as API guides, plugin and gadget development guides and guides
to other frameworks) as well as product documentation (user's guides, administrator's guides and installation guides). The wiki permissions
are different for each type of documentation.
If you want to update the Developer Network or other developer-focused wiki spaces, just sign up for a wiki username then log in
and make the change.
If you want to update the Atlassian OnDemand product documentation, we ask you to sign the Atlassian Contributor License
Agreement (ACLA) before we grant you wiki permissions to update the documentation space. Please read the ACLA to see the
terms of the agreement and the documentation it covers. Then sign and submit the agreement as described on the form attached to
that page.
Following our Style Guide
Please read our short guidelines for authors.
How We Manage Community Updates
Here is a quick guide to how we manage community contributions to our documentation and the copyright that applies to the documentation:
Monitoring by technical writers. The Atlassian technical writers monitor the updates to the documentation spaces, using RSS
feeds and watching the spaces. If someone makes an update that needs some attention from us, we will make the necessary
changes.
Wiki permissions. We use wiki permissions to determine who can edit the documentation spaces. We ask people to sign the
180
Atlassian OnDemand October 2011 Documentation
Atlassian Contributor License Agreement (ACLA) and submit it to us. That allows us to verify that the applicant is a real person. Then
we give them permission to update the documentation.
Copyright. The Atlassian documentation is published under a Creative Commons CC BY license. Specifically, we use a Creative
Commons Attribution 2.5 Australia License. This means that anyone can copy, distribute and adapt our documentation provided they
acknowledge the source of the documentation. The CC BY license is shown in the footer of every page, so that anyone who
contributes to our documentation knows that their contribution falls under the same copyright.
Related Topics:
Contributing to the JIRA Documentation
Contributing to the Confluence Documentation
Contributing to the FishEye Documentation
Contributing to the Crucible Documentation
Contributing to the Bamboo Documentation
Author Guidelines
Atlassian Contributor License Agreement
Atlassian OnDemand Documentation in Other Languages
Below are some links to Atlassian OnDemand documentation written in other languages. In some cases, the documentation may be a
translation of the English documentation. In other cases, the documentation is an alternative guide written from scratch in another language.
This page presents an opportunity for customers and community authors to share documentation that they have written in other languages.
Please be aware that these are external guides.
Most of the links point to external sites, and some of the information is relevant to a specific release. Atlassian provides
these links because the information is useful and relevant at the time it was written. Please check carefully whether the
information is still relevant when you read it. The information in the linked guides has not been tested or reviewed by
Atlassian.
On this page:
No guides yet
None
No guides yet
We do not yet have any guides to link here. Be the first to suggest one!
Adding Your Own Guide to this Page
Have you written a document for Atlassian OnDemand in another language? Add a comment to this page, linking to your guide. We will
include it if the content fits the requirements of this page.
Giving Feedback about One of the Guides
If you have feedback on one of the guides listed above, please give the feedback to the author of the linked guide.
If you want to let us know how useful (or otherwise) one of these guides is, please add a comment to this page.
Other Sources of Information
Atlassian website
Atlassian blog
Migrating from JIRA Studio to Atlassian OnDemand
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.
181
Atlassian OnDemand October 2011 Documentation
On this page:
Access level changes for your users
What are the changes?
What does this mean in terms of licensing if you continue with the Studio pricing?
What next?
Bamboo is enabled
Confluence 4.1 - a new text editor
What are the changes?
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 users
OnDemand application access
Developer
JIRA + Confluence + FishEye/Crucible + Bamboo + GreenHopper
Collaborator
JIRA + 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:
Confluence 4.0 Editor - What's Changed for Wiki Markup Users
Confluence 4.0 Editor - What's Changed for Users of the Old Rich Text Editor
182
Atlassian OnDemand October 2011 Documentation
Please also check out the following Release Notes to find out the new features.
Confluence 4.1 Release Notes
There is also a video on the December 2011 page that shows the 4.1 features relevant to Confluence OnDemand.
Confluence 4.0 Release Notes
Migration FAQ
This page is your one stop shop for anything migration related. Please bookmark this page and check it for more information on
what stage of Migration we are in. We can't anticipate all questions though, so please don't hesitate to leave a comment if we
missed something.
JIRA Studio Migration FAQ
What is involved in the Migration?
Is everyone being migrated?
Will my jira.com URL change as part of the move to OnDemand?
How do I find out what my new pricing would be if I opt-in?
I have received my Opt-In email. Now what?
Enterprise Hosted Migration FAQ
What is involved in the Migration?
Will my onjira.com/onconfluence.com URL change as part of the move to OnDemand?
When will you be starting this migration?
How long will it take?
Is everyone being migrated?
JIRA Studio Migration FAQ
What is involved in the Migration?
This is a two-step migration:
Step one is to migrate Studio customers from our old servers and infrastructure to the new OnDemand platform. This process should
be fairly invisible to you.
Once that is complete, customers will be able to upgrade their Studio instances to the new OnDemand services by logging into
my.atlassian.com and configuring their OnDemand account.
Is everyone being migrated?
Most JIRA Studio customers are being migrated over to our new Infrastructure and will have the ability to opt in for OnDemand
pricing and services.
The rest of the users have customizations that we can not support have already been contacted regarding their options going
forward (see 'Customizations' below).
Will my jira.com URL change as part of the move to OnDemand?
No, you will keep your jira.com domain. However, custom domains that are not jira.com will not be supported.
How do I find out what my new pricing would be if I opt-in?
Please check out this signup page, you can play around with different application and user tier options and see what the pricing would be:
I have received my Opt-In email. Now what?
Monthly: Opt in for the features your group needs at the user tier you need them at. Your instance will then be upgraded.
Annual: Opt in for the features your group needs at the user tier you need them at. You can select any user tier you want. The new
pricing will begin on your next annual renewal.
Enterprise Hosted Migration FAQ
What is involved in the Migration?
First you will need to opt-in to the migration by logging into my.atlassian.com.
OnDemand is always on the latest version of Atlassian products, so first we will upgrade your instance to the latest version
Once that is complete, we will migrate you over to the OnDemand service during a two-hour maintenance window.
Then you will be able to log into my.atlassian.com and configure your service.
Will my onjira.com/onconfluence.com URL change as part of the move to OnDemand?
Yes. Your url will change to our new atlassian.net domain. We are not currently supporting any custom domains or redirects.
183
Atlassian OnDemand October 2011 Documentation
When will you be starting this migration?
We expect to begin working on Enterprise Hosted migrations in February.
How long will it take?
We expect it will take several months to migrate all opted-in accounts. Customers may continue to opt-in over this time thru December 2012.
Is everyone being migrated?
Only customers who opt-in will be migrated.
184
Download PDF
Similar pages