1.2.1.5.1 managing project visibility ondemand october 2011 documentation 4 atlassian ondemand...

1. Atlassian OnDemand Documentation Home . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41.1 Getting started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1.1.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1.2 Workspace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.1.3 Choosing applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1.4 Getting started administering Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

1.1.4.1 Getting started with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.1.4.2 Getting started with Bamboo OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.1.4.3 Getting started with Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.1.4.4 Getting started with Confluence OnDemand only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161.1.4.5 Getting started with Source and Review Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

1.1.5 Getting started using Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.1.6 Getting started for evaluators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

1.2 Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241.2.1 Administering Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

1.2.1.1 Administering Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.2.1.1.1 Creating new projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251.2.1.1.2 Deleting a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261.2.1.1.3 Setting project permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.2.1.1.4 Associating a JIRA project with multiple FishEye repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.2.1.1.5 Associating a JIRA project with a Confluence space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271.2.1.1.6 Customising Application Tabs for your Project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291.2.1.1.7 Linking activities from bitbucket or GitHub to JIRA Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.2.1.1.8 Configuring cross-application linking in JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

1.2.1.2 Managing data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.2.1.2.1 Importing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 331.2.1.2.2 Uploading Data via WebDAV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

1.2.1.3 Managing Users and Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 431.2.1.3.1 Managing users and groups for sites with multiple OnDemand applications . . . . . . . . . . . . . . . . . . . . . . . . 441.2.1.3.2 Managing users and groups for sites integrated with Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 501.2.1.3.3 Managing users and groups for JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551.2.1.3.4 Managing users and groups for Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

1.2.1.4 Administering your Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571.2.1.4.1 Changing your OnDemand 'From' Email Header Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571.2.1.4.2 Changing your Account Language . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581.2.1.4.3 Requesting support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581.2.1.4.4 Changing your Account Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581.2.1.4.5 Enabling Public Signup and CAPTCHA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 591.2.1.4.6 Viewing your user count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.2.1.4.7 Changing your Welcome Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601.2.1.4.8 Integrating OnDemand with Google Apps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

1.2.1.5 Managing permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

1.2.1.5.1 Managing project visibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 631.2.1.6 Configuring the look and feel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

1.2.1.6.1 Changing the Logo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 641.2.1.6.2 Configuring Global and Default Application Tabs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.2.1.6.3 Editing the Date and Time Formats for 'Issues' (JIRA) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651.2.1.6.4 Editing the colour scheme . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

1.2.1.7 OnDemand Cookies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661.2.2 Using Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

1.2.2.1 Creating Links . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671.2.2.2 Creating your own dashboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 691.2.2.3 Managing your profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

1.2.2.3.1 Changing Your Password in Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 701.2.2.4 Working with Activities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 711.2.2.5 Working with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

1.2.2.5.1 Logging In and Out With Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721.2.2.5.2 Using Google Docs with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741.2.2.5.3 Using Google Calendar with Google Apps Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 761.2.2.5.4 Using the Activity Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

1.3 JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 811.3.1 Administering Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

1.3.1.1 Administration console differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 851.3.1.2 JIRA Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 861.3.1.3 Enabling sub-tasks for a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881.3.1.4 Configuring JIRA Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

1.3.1.4.1 Disabling or Enabling a JIRA Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 891.3.1.4.2 Viewing your JIRA Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901.3.1.4.3 Viewing the JIRA Plugin Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91

1.3.1.5 Linking a bitbucket or GitHub repository with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911.3.1.6 Integrating Flowdock with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941.3.1.7 Connecting Zephyr with JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 941.3.1.8 Configuring Cloud Connectors in JIRA OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

1.3.2 Working with Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 951.3.2.1 JIRA User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 961.3.2.2 Creating an issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

1.3.2.2.1 Copy of Creating an issue - page structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991.3.2.3 Managing agile projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 991.3.2.4 Creating issue comments via emails . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

1.4 Confluence OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1011.4.1 Administering the Wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

1.4.1.1 Configuring Default Space Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041.4.1.2 Configuring Confluence Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

1.4.1.2.1 Configuring a Confluence Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051.4.1.2.2 Disabling or Enabling a Confluence Plugin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1061.4.1.2.3 Viewing the Confluence Plugin Audit Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1091.4.1.2.4 Viewing your Confluence Plugins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

1.4.1.3 Applying a Theme to a Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1121.4.1.4 Creating Confluence templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1131.4.1.5 Confluence Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

1.4.2 Working with the Wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1151.4.2.1 Confluence User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1161.4.2.2 Viewing drafts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120

1.5 Source and Review Bundle . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1201.5.1 Administering Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1211.5.2 Administering Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122

1.5.2.1 Configuring commits to require a JIRA issue key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1231.5.2.2 Configuring repository permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123

1.5.2.2.1 Configuring repository permissions for a project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1241.5.2.2.2 Configuring default repository permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1261.5.2.2.3 Enabling Anonymous Access to a Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

1.5.3 Working with Reviews . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281.5.3.1 Crucible User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

1.5.4 Working with Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1291.5.4.1 FishEye User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1291.5.4.2 Checking changesets committed against an issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130

1.5.5 Working with the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301.6 Bamboo OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131

1.6.1 Administering Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1321.6.1.1 Integrating Builds with your Issues Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1331.6.1.2 Bamboo Administrator's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137

1.6.2 Working with Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1381.6.2.1 Bamboo User's Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1391.6.2.2 Actioning Issues via Builds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140

1.7 Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1411.7.1 changelog . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.2 changeset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.3 external user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.4 issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.5 JIRA project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.6 page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1421.7.7 project . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142

1.7.8 repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.7.9 review . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.7.10 source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.7.11 space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.7.12 user . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.7.13 wiki . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143

1.8 Atlassian OnDemand release summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1431.8.1 February 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147

1.8.1.1 February 2012 - FishEye Crucible 2.7 upgrade notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1481.8.2 January 2012 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1501.8.3 December 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1511.8.4 November 2011 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521.8.5 The launch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1521.8.6 Known Issues and Workarounds . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

1.9 Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541.9.1 Restricted Functions in Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1541.9.2 Supported browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 159

1.9.2.1 End of Support Announcements for Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591.9.3 Atlassian OnDemand Application Versions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1591.9.4 Atlassian OnDemand licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1601.9.5 Support Policies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 161

1.9.5.1 Bug Fixing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1611.9.5.2 How to Report a Security Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621.9.5.3 New Features Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1621.9.5.4 Security Advisory Publishing Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631.9.5.5 Security Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631.9.5.6 Severity Levels for Security Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1631.9.5.7 Update Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

1.9.6 Atlassian OnDemand Plugin Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1651.9.6.1 Third-Party Plugin Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

1.9.7 About Your Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1661.9.8 Maintenance windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

1.10 Atlassian OnDemand FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1681.10.1 Usage FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169

1.10.1.1 How can I edit or reassign closed issues? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701.10.1.2 How can I prevent certain users seeing certain content? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701.10.1.3 How do I access my Subversion repository? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701.10.1.4 How do I file bugs or log feature requests? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701.10.1.5 How do I update JIRA issues via subversion commit messages? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1701.10.1.6 How should OnDemand be configured for a shared code module? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711.10.1.7 What is the server base URL for my wiki in Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711.10.1.8 What is the URL for my installation of Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711.10.1.9 What happens to my existing projects if I purchase new applications? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171

1.10.2 Configuration and Administration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1711.10.2.1 Can I use a custom Elastic Bamboo image? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1721.10.2.2 Subversion is constantly asking users to re-authenticate and failing with the correct credentials . . . . . . . . . . . . 1721.10.2.3 Can I change the look and feel of Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.4 Can I install my own plugins? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.5 Are alternative languages available for Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.6 What remote APIs are supported in Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.7 Can I use EBS volumes with Elastic Bamboo? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.8 How do I create a backup copy of my Subversion repository? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1731.10.2.9 How do I add Google Apps to Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1741.10.2.10 Can I use Clover with Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751.10.2.11 How do I import Subversion data for a single project? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751.10.2.12 How do I migrate from Visual SourceSafe to Atlassian OnDemand? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751.10.2.13 How are we notified of system maintenance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1751.10.2.14 When will my Atlassian OnDemand applications be upgraded? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761.10.2.15 Where do I set the region used for maintenance windows? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761.10.2.16 Users are locked out of FishEye and Crucible REST APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761.10.2.17 I cannot log in using my Google Apps account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1761.10.2.18 I cannot find my applications after adding them . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771.10.2.19 Do you support SSL? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 177

1.10.3 Subscription and Account FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771.10.3.1 Can I disable a user without deleting them? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1771.10.3.2 How do I add a technical contact to my account? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.3 How do I get started with the Tempo Plugin? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.4 How do I upgrade my account, renew my license, change credit card details, etc? . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.5 How is the user count of my account calculated? How do I reduce my user count? . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.6 What are the storage and bandwidth limits? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.7 What database does the Atlassian OnDemand instance use? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1781.10.3.8 What domain name will my OnDemand service be on? Can I use my own domain name? . . . . . . . . . . . . . . . . 1791.10.3.9 What happens to my OnDemand instance when my account is cancelled? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791.10.3.10 What is the minimum number of users allowable in an upgrade? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791.10.3.11 What is the minimum term of service? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179

1.10.4 Google Apps Integration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1791.11 Contributing to the Atlassian OnDemand Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180

1.11.1 Atlassian OnDemand Documentation in Other Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1811.12 Migrating from JIRA Studio to Atlassian OnDemand . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181

1.12.1 Migration FAQ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

Atlassian OnDemand October 2011 Documentation

4

Atlassian OnDemand Documentation HomeAtlassian 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 addingmore applications.

Getting Started

Quick Start Guide for usersQuick Start Guide for administratorsImporting DataOverviewChoosing applications

FAQ

Domain nameStorage and bandwidth limitsAdding Google Apps to Atlassian OnDemand

See more

JIRA Studio customers

Migrating from JIRA Studio to Atlassian OnDemand

Administering AOD

Creating users and groupsGranting application access to users Creating new projectsConfiguring the look and feel

Using AOD

Overview of the workspaceCreating an issueCreating links

Resources

Answers from the communityOnDemand on TwitterAtlassian Training

for Evaluators

Free Trial

Release Summary

Atlassian OnDemand release summary

Support

Atlassian SupportSupport PoliciesAtlassian OnDemand Plugin Policy

Feedback and Feature Requests

https://answers.atlassian.com/tags/ondemand/

http://twitter.com/#%21/OnDemandStatus

http://www.atlassian.com/training

https://my.atlassian.com/ondemand/signup

http://support.atlassian.com


5

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 [email protected].

Getting started

Getting to know your site

Overview of applicationsWorkspace

Start using Atlassian OnDemand

Getting started using Atlassian OnDemand, e.g.:

JIRA:

Creating and assigning issuesViewing your issues with gadgets

FishEye/Crucible/Subversion:

Viewing changesetsCreating code reviews

Confluence:

Creating a page

Bamboo:

Creating a build plan

Start administering Atlassian OnDemand

Getting started with JIRA OnDemandGetting started with Bamboo OnDemandGetting started with Confluence OnDemandGetting started with Confluence OnDemand onlyGetting started with Source and Review Bundle

Personalisation

Creating your own dashboardManaging your profile

Overview

Atlassian OnDemand (AOD) is a collaboration platform for software development teams of any size. This platform is a set of Atlassianapplications 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 account.my.atlassian.com

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 .JIRAConfluence OnDemand — to share information among the team, for example creating documents, sharing and discussing ideas,specs, mockups, and diagrams. Based on .ConfluenceSource and Review Bundle — to search, view and review code. Based on and . The bundle includes theFishEye Crucibleintegrated Subversion (SVN) as well.Bamboo OnDemand — to build and deploy software. Based on . Bamboo OnDemand runs builds on using Bamboo elastic agents

, and Elastic Bamboo utilises computing resources from the .Elastic Bamboo Amazon Elastic Compute Cloud (EC2)Add-Ons

GreenHopper: to manage JIRA projects in the agile way. More on GreenHopper

http://studio.atlassian.com/browse/JST

https://my.atlassian.com/login

http://www.atlassian.com/software/jira/

http://www.atlassian.com/software/confluence/

http://www.atlassian.com/software/fisheye/

http://www.atlassian.com/software/crucible/

http://www.atlassian.com/software/bamboo/

http://aws.amazon.com/ec2/

http://www.atlassian.com/software/greenhopper/


6

Balsamiq: to create and edit UI mockups in JIRA issues or Confluence pages. More on BalsamiqGliffy: to create online diagrams such as flow charts and organisation charts in Confluence pages. More on .GliffyTeam 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 page to decide what applications to use and for information aboutChoosing applications Atlassian OnDemand Plugin Policyavailable plugins.

The page shows the current version running in OnDemand.Application Versions

Atlassian OnDemand compared with downloadable Atlassian products

The hosted Atlassian OnDemand sites offer most of the functions available in the corresponding downloadable products, but somedifferences 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, forexample, for , and for . In circumstances where a functionality is different betweenJIRA JIRA OnDemand Confluence Confluence OnDemandOnDemand and the downloadable product, we will mark the relevant information as such accordingly.

Related topics

Getting started administering Atlassian OnDemandGetting 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 defaultlook and feel and layout. The navigation bar shows the enabled Atlassian OnDemand applications for your site. In this example, all AtlassianOnDemand applications are enabled, that is JIRA, Confluence, FishEye, Crucible and Bamboo.

Figure 1: Default Atlassian OnDemand workspace

Control ormenu

Description

http://balsamiq.com/

http://www.gliffy.com/products/confluence-plugin/

http://www.atlassian.com/software/team-calendars/overview


7

Projectdrop-downmenu

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.

Applicationmenus

The menus are context-sensitive and you will see different options depending on what application you are working with.

Userdrop-downmenu

This menu displays your username (e.g. 'Joseph Smith'). Use it to access your own access your user profile and (if youare an administrator) administration functions.

Historydrop-downmenu

This menu displays up to twenty pages that you navigated.

QuickSearch

Build information (e.g. build plans, build results) is currently not searchable. Build information is available in the Buildsapplication, and is also captured in the drop-down menu and the activity stream.History

Customised workspace

Your workspace might look different from the default depending on:

your team's application selectionyour administrator's setup for your sitewhat 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 family and the family. Confluence and JIRA are the base products in the: Confluence JIRAtwo 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 documentationUse 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, addGreenHopper on top of JIRA to manage your project in the agile way.


8

Family / Baseproduct

Application combinations Included products Add-ons

Confluence Confluence OnDemand Confluence onlyGliffyTeamCalendars

JIRA JIRA OnDemand JIRA onlyBonfireGliffyGreenHopperJIRA 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

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, justenable and disable them in your account, and the products will be automatically installed or uninstalled for your site. Themy.atlassian.comonly exception to this rule is the expansion to multiple applications from Confluence OnDemand only. If you want to add other applications ontop 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 topurchase for an application, e.g. 500 users for Confluence and 50 users for JIRA. When the number of users that needs access to anapplication 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 page.Managing permissions

Related topics

Restricted Functions in Atlassian OnDemandSupported BrowsersOrdering 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

https://my.atlassian.com/login

http://www.atlassian.com/licensing/ondemand




9

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, clickthe menu labelled with your user name in the header, and select . The administration console appears with the tabAdministration Generalactive.

The administration console uses a tab layout for most of the service combinations except Confluence On Demand. Use the tab forGeneralthe 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

OverviewGetting started using Atlassian OnDemandRestricted 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, show you how to configure JIRA to and finally preview a few of JIRA OnDemand.yourself let your team get involved advanced features

What is Atlassian OnDemand? Read the page for a brief introduction.Overview

Audience: Administrators

The administration consoles are different between the sites that have JIRA OnDemand only and those with multipleapplications.

See for more information and screenshots.Administration console differences


10

1.

2.

3.

1. 2.

1.

2. 3. 4.

5.

(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 page.Importing Data

Congratulations! You have imported existing data into JIRA OnDemand. Next, try creating a JIRA project.

Step 2. Create a project

Log in as an administrator. Click your user name (top right corner) and then the link. The administration console willAdministrationappear with the page displayed. ProjectsClick . Enter the project details, as follows:Add Project

In the field, type a descriptive name for your project, typically two or three words, e.g. 'Online Banking'. You canNamechange the project name later.In the field, type a prefix for issues in your project, typically three or four characters, e.g.'EBNK'. You change theKey cannotkey after the project is created.In the field, select the user to whom issues should be assigned by default. You can set this to yourself at thisProject Leadstage and change the setting later.

Click the button.Add

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 and resolving it, or setting up project / , or creating an issue versions components. Once you've tried out JIRA for yourself, get your team involved by creating some users.customising the dashboard

Step 3. Create users

The process for adding users depends on whether you have Google Apps integration enabled for your OnDemand instance. When youcreate new users, they are automatically added to the group by default and can log in to your site.users

Add OnDemand (non-Google Apps) users:

In the administration console, go to > > .General User Management UsersClick the link, and fill out the fields on the displayed form.Add User

Further instructions can be found here: .Managing Users and Groups

Add Google Apps users:

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

Create Google users as needed.Anywhere in Atlassian OnDemand, type to bring up the box, and search for .g + g Administration Search Google ManagementOn the displayed page, locate the button and click it to transfer the users from Google Apps to AtlassianStart SynchronizationOnDemand.Grant users with access to applications. Type and search for (or g + g Application Access General > User Management >

). Configure the desired access to Atlassian applications and click .Application Access 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 for more information.Google Apps Integration FAQ

Congratulations! You have created new users. Next, try creating a custom workflow for your team to use.

Step 4. Customise a workflow


11

1. 2. 3. 4.

1. 2. 3. 4. 5.

1. 2. 3.

1. 2. 3.

4.

A JIRA is the set of and that an issue goes through during its lifecycle. A isworkflow steps (or statuses) transitions read-only default workflowpre-configured for JIRA. The instructions below will show you how to copy this workflow to create your own custom workflow.

In the administration console, go to > .Issues WorkflowsClick for the ' default workflow.Copy jira'Enter a name and description for the workflow and click .CopyClick for your new workflow. The will open. Try modifying your workflow, then saving your changes.Design workflow designer

You have now created your own custom workflow. To use it with a project, you'll need to . See for furtheractivate it Activating Workflowinstructions.

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 canaccess 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 groupthe access to a project.

Type to bring up the box, and search for (or > ).g + g Administration Search Groups General GroupsAt the bottom of the displayed page, add a new group.Navigate to > in the administration console and click the project that you want to grant your group permission to.Issues ProjectsIn the section, click .People View Project RolesFind the row for the ' ' project role and click the groups. Enter the name of your group and click .Users Update

You have now given your new group the permission to access your project. For further information on configuring security, see the followingtopics:

Managing permissionsManaging project visibilityConfigure security (JIRA documentation)

Congratulations! You have now set up JIRA for use by your team. Try assigning issues to different people, or another person'swatchingissue for updates, or to a group. Once you've gotten your team involved, try configuring some advanced features.restricting an issue

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 functionalityvia 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 for moreplugin policyinformation. The instructions below describe how to enable one of the non-commercial plugins, the plugin.JIRA Suite Utilities

Type and search for (or > in the administration console).g + g Plugins Issues PluginsClick the ' ' row in the 'User-installed Plugins' table.JIRA Suite UtilitiesClick ' '.Enable

You have now enabled a plugin. Check out some of the commercial plugins on offer, such as for agile project managementGreenHopperand for agile testing. Once you've configured your add-ons, try creating links to other OnDemand applications.Bonfire

Creating links to and from JIRA OnDemand


If you are using JIRA OnDemand with other OnDemand applications, you can create links to and from the other applications. The instructionsbelow will describe how to create a link to a wiki page from an issue.

Navigate to and create a new page titled .Confluence OnDemand Feature SpecificationNavigate to JIRA OnDemand and create a new issue.In the issue description, enter the following text:

[Feature Specification]

https://studio.plugins.atlassian.com/wiki/display/JSUTIL/JIRA+Suite+Utilities+Documentation


http://www.atlassian.com/software/bonfire/


12

4.

1. 2.

3.

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 . Once you'veCreating Linksfinished creating links, try configuring commit commands for JIRA.

Configuring commit commands


If you have the Source and Review Bundle, then you can configure commit commands for JIRA. This feature allows users to action JIRA via commands in commit messages. The instructions below will show you how to use one of these commands.issues

Create an issue. Note down the issue key for the issue, e.g. .EBNK-123Commit 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.

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 (FishEye documentation).Using Smart Commits

Congratulations! You have now set up some of the advanced features of JIRA OnDemand. For more information on JIRA OnDemand, seethe .JIRA OnDemand documentation


Using this guide, you will complete the required build configuration and be able to run a test build on one of your repositories.


Before you begin

Bamboo OnDemand runs builds on using , and Elastic Bamboo utilises computing resources from the elastic agents Elastic Bamboo Amazon. You will be charged by Amazon for your EC2 compute usage. These charges are separate to your AtlassianElastic Compute Cloud (EC2)

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 page to create aGetting started with JIRA OnDemandproject. 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 pageUpload your AWS private key file and certificate file by opening a support ticket and attaching the files to the support ticket. Oursupport 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 page.Amazon EC2 pricing pageYou can track your EC2 usage on the .AWS Account pageYour Elastic Bamboo compute usage will not be distinguishable from your non-Bamboo EC2 compute usage in yourAWS 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 SubversionImporting Versioned Data into Subversion



https://aws-portal.amazon.com/gp/aws/developer/registration/index.html

http://aws.amazon.com/ec2/#pricing

http://aws.amazon.com/account/


13

1. 2. 3. 4. 5.

6.

1. 2.

3.

1. 2. 3. 4. 5. 6.

7.

Congratulations! You have imported your existing source code. Next, try configuring Elastic Bamboo to run your builds.

Step 2. Configure Elastic Bamboo

Log in as an administrator, and go to > > . The 'Configuration Details' page will appear.Administration Builds Elastic BambooRead and accept the . The 'Elastic Bamboo Configuration' page will refresh.Atlassian Hosted Services Terms of UseClick the button to enable Elastic Bamboo. You will then see the fields to enter the Elastic Bamboo configuration details.EnableIn the section, enter the and .Configuration Details AWS Access Key ID AWS Secret Access KeyIn the section, modify the field to be 1. As a start, we willElastic Bamboo Global Settings Maximum Number of Elastic Instancecreate only 1 plan at this stage, and therefore one instance is enough. You can change this setting later as needed.Leave all the other settings as default, and click the button.Save

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

In the the administration console, click > . The 'Manage Elastic Instances' page will appear.Builds Elastic Bamboo InstancesClick the ' ' link. The 'Start New Elastic Instances' screen will appear.Start New Elastic Instances

In the ' ' field, enter 1 .Number of instancesLeave the ' ' field as 'Default'.Elastic Image Configuration Name

Click the ' ' button. The 'Manage Elastic Instances' page will appear, showing the startup process of your new instances.Submit

default image: If the default image does not contain the capabilities that meet your build requirements, you can use an EBS with the default image to extend the build resource.volume

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

Go to > .Builds Create PlanIn the section, select your project, enter the name and key for the plan.Plan DetailsIn the section, select the repository type and specify the repository URL.Source RepositoryLeave the settings as default for now.Build StrategyIn the section, specify the builder and other settings as needed.Build ConfigurationLeave the rest of the settings as default and select the check box in the section so that the build will start runningEnable this Planafter the plan is created.Click the button. You will see the new plan displayed in the ' ' tab on the ' ' dashboard. A build will startCreate All Projects Buildsrunning and the progress is displayed along the process.

http://docs.amazonwebservices.com/fws/latest/GettingStartedGuide/index.html?AWSCredentials.html

http://confluence.atlassian.com/display/BAMBOO030/default+image

http://confluence.atlassian.com/display/BAMBOO030/Configuring+Elastic+Instances+to+use+the+EBS

http://confluence.atlassian.com/display/BAMBOO030/Configuring+Elastic+Instances+to+use+the+EBS


14

1. 2.

3.

What are plans and what do the settings for a plan mean? and plans 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 BambooOnDemand.

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 isthat a large portion of the Elastic Bamboo cost is from the instance running time.

To shut down elastic instances:

Navigate to ' ' > ' ' > ' ' > ' 'Administration Builds Elastic Bamboo InstancesClick the ' ' link in the ' ' column, next to the instance that you wish to shut down. The 'Shut Down Instance'Shut Down Operationsscreen will display.Click the ' ' button to shut down the elastic instance. The elastic instance that you have shut down will display a 'ShuttingConfirmdown' 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 NotificationsConfiguring Concurrent BuildsUsing 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 , the blog post talks about how theContinuous Integration (CI) Pipelining the build for fun and profitAtlassian 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 ConfluenceOnDemand only, refer to instead. The instructions on this page will help you Getting started with Confluence OnDemand only create a spaceto share information, to the site via users and groups and permissions, and togive your team access try some advanced featurescustomise your site.

What is Atlassian OnDemand? Read the page.Overview


http://martinfowler.com/articles/continuousIntegration.html

http://blogs.atlassian.com/developer/2011/07/pipelining_the_build_for_fun_and_profit.html


15

1. 2. 3.

1. 2.

1.

2. 3.

4.

1. 2.

3.

On this page:

Step 1. Create a spaceStep 2. Create users and groupsStep3. Set permissionsNext steps

Step 1. Create a space

Skip to if you have already created a JIRA project. Otherwise, use the following instructions to create a space:the next step

Click the tab to go to the Confluence dashboard and click the ' ' link.Wiki Add SpaceThe ' ' screen appears. Enter a and a short, unique .Create Space space name space keyLeave all the other settings as default, and click ' ' to add your space to your site.OK

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 or a . Once you have triedcreating a page blog postcreating 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 youcreate new users, they are automatically added to the group by default and can log in to your site.users

Add OnDemand (non-Google Apps) users:

In the administration console, go to ' ' > ' ' > ' '.General User Management UsersClick the ' ' link, and fill out the fields on the displayed form.Add User

Further instructions on managing OnDemand users can be found here: .Managing Users and Groups

Add Google Apps users:

Google users are created in Google Apps. Log in to your Google domain as administrator, and on the Google Apps toolbar, click .Organization & Users

Create Google users.In the Atlassian OnDemand administration console, synchnronise the users from Google Apps to OnDemand. To do this, navigate to

> , and click .General Google Management Start SynchronizationGrant users with access to applications. Go to > > and configure the desiredGeneral User Management Application Accessaccess 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 configureapplication-specific permissions in the individual applications.

Interested in Google Apps integration for your OnDemand instance? It's free!

See the for more information.Google Apps Integration FAQ

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 and . For example, set which groups can createglobal permissions space permissionsspaces at the global level and specify which groups can remove pages at the space level.

To set permissions:

Log in as an administrator, and go to the 'Administration Console' by clicking > .your username AdministrationClick . In the left-hand panel, click Wiki Permissions

https://confluence.atlassian.com/display/AOD/Managing+Users+and+Groups

https://confluence.atlassian.com/display/AOD/Managing+users+and+groups+for+sites+integrated+with+Google+Apps

https://confluence.atlassian.com/display/AOD/Managing+users+and+groups+for+sites+integrated+with+Google+Apps


16

3.

4.

1. 2.

1. 2.

3. 4.

1. 2. 3.

Click or as needed.Global Permissions Space Permissions If you selected global permissions, click to enable the editable mode, and set permissions as needed.Edit PermissionsIf you selected space permissions, click the link to navigate to the settings page. Click Manage Permissions Edit

, and then set permissions as needed.PermissionsClick to save changes.Save All

You can change permission settings at any time. apply to all spaces.Global permissions apply to a specific space. More on .Space permissions space permissions

do not contribute to the user number allocated by your license. Anonymous access is available only ifAnonymous usersenabled 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 and . Once you've gotten your team involved, try configuring some advanced features.sharing content watching changes

Next steps

Now that you've gotten Confluence OnDemand set up for your team, try out some of the advanced Confluence features. Add your personaltouch by customising the site and space, import templates to standardise content format and extend Confluence's base functionality viaplugins.

Customising the look and feel


With themes, colour schemes and logos, you can adapt your site or specific spaces as needed.

In your space, go to > .Browse Space AdminIn 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 losethe OnDemand context, that is they will not see the other tabs. Please ensure that your Confluence space has links back into the OnDemandsite.

Themes: screen layout. Themes can be applied at the site level or the space level.

Setting up templates


To get started, import the global templates that Confluence comes with and then customise them as needed.

Go to the tab of the 'Administration Console'.WikiIn the left-hand panel, select > . You will the list of default templates. To preview a template, clickConfiguration Import Templatesthe template name.Select the templates you want to use and the space to import them into, and then click . The templates are imported.ImportFollow the instructions on the page to edit the templates as needed.

Templates: Confluence pages with predefined content. are available in every space across the site.Global templates are only available in the space in which they are defined.Space templates

Managing plugins


Go to > . The administration console appears.Browse Confluence AdminUnder the section of the left-hand panel, click . You will see a list of user-installed plugins.Configuration PluginsClick 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


17

1.

2. 3.

1. 2. 3. 4.

If you site contains Confluence OnDemand only, use this guide to create a space for your team to start sharing information. If your sitecontains 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 page.Overview


On this page:

Step 1. Create a spaceStep 2. Create usersStep 3. Set permissionsNext steps

Step 1. Create a space

Go to the Confluence dashboard by clicking the link at the top left of your screen, and then click the link thatDashboard Add Spaceis below the welcome message.The 'Create Space' screen appears. Enter a and a unique .space name space keyLeave all the other settings as default, and click to add the space to your site.OK

Your site comes with a space that contains a tutorial. Use the tutorial to learn the basics of using Confluence,Demonstrationsuch as using the Dashboard, creating spaces pages and publishing blog posts. You can find the space on theDemonstrationdashboard.

Congratulations! You have created a space for your team to share information. Try or a . Once you have triedcreating a page blog postcreating content yourself, give your team access to the space by creating users and groups, and setting permissions.

Step 2. Create users

Log in as an administrator, and go to the Confluence 'Administration Console' by clicking > .Browse Confluence AdminUnder the section, select . At the top of the page, click .Security Manage Users Add UserEnter 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 and respectively. For example, set whichglobal permissions space permissions

http://confluence.atlassian.com/display/DOC/Creating+a+Page

http://confluence.atlassian.com/display/DOC/Adding+Blog+Posts


18

1. 2.

1. 2. 3.

1. 2.

1.

2. 3.

1. 2. 3.

groups can create spaces at the global level and specify which groups can remove pages at the space level.

To set global permissions:

Under the section of the administration console, click . The global permission page will appear.Security Global PermissionsClick to enable the editable mode, and set permissions as needed. Click to save changes.Edit Permissions Save All

To set space permissions:

In your space, click > at the top of the page. The space administration page appears.Browse Space AdminUnder the section in the left-hand panel, click .Security PermissionsClick to enable the editable mode, and set the permissions as needed. Click to save changes.Edit Permissions Save All

You can change permission settings at any time. apply to all spaces.Global permissions apply to a specific space. More on .Space permissions space permissions

do not contribute to the user number allocated by your license. Anonymous access is available only ifAnonymous usersenabled 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 and . Once you've gotten your team involved, try configuring some advanced features.sharing content watching changes

Next steps

Now that you've gotten Confluence OnDemand set up for your team, try out some of the advanced Confluence features. Add your personaltouch by customising the site and space, import templates to standardise content creation and extend Confluence's base functionality viaplugins.

Customising the look and feel


With themes, colour schemes and logos, you can adapt your site or specific spaces as needed.

In your space, go to > .Browse Space AdminIn 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


To get started, import the global templates that Confluence comes with and then customise them as needed.

Under the section, select . You will the list of default templates. To preview a template, click theConfiguration Import Templatestemplate name.Select the templates you want to use and the space to import them into, and then click . The templates are imported.ImportFollow the instructions on the page to edit the templates as needed.

Templates: Confluence pages with predefined content. are available in every space across the site.Global templates are only available in the space in which they are defined.Space templates

Managing plugins


Go to > . The administration console appears.Browse Confluence AdminUnder the section of the left-hand panel, click . You will see a list of user-installed plugins.Configuration PluginsClick the plugins to view their details. Then enable and disable them as needed.

You cannot install your own plugins See the . plugin policy.


19

1. 2. 3.

4.

1.

2.

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 longa project has been created. Using this guide, you will learn the basics about managing source code repository permissions and reviewpermissions.

What is Atlassian OnDemand? Read the page for a brief introduction.Overview


On this page:

Step 1. Create a project(optional) Step 2. Import Subversion data(optional)

Step 3. Try browsing your repositoryStep 4. Try creating a reviewNext steps

(optional) Step 1. Create a project

Follow the instructions in the page to create a project. A Subversion source repository is createdGetting started with JIRA OnDemandautomatically when a project is being created, and then your team can start browsing the source code with FishEye or reviewing the sourcecode 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 SubversionImporting 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 theSource and Review Bundle.

Step 3. Try browsing your repository

Log in as a administrator or user and select your project.Navigate to ' > ' '. Your repository will be shown in the 'Repositories' tab.'Source BrowseClick the repository to view it. You can navigate around your repository via the navigation tree on the left. For more information onbrowsing your code, see .Browsing through a RepositoryYou 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 and . Once you have explored your repository, tryusing the search viewing a filecreating a review.

Step 4. Try creating a review

Log in as a administrator or user and select your project.


20

2. 3. 4.

1. 2. 3.

Navigate to ' > 'Create new review'. The create review wizard will open.'ReviewsAdd content to your review. For example, you may browse and add a changeset.Click ' ' to create the review.Start review

Congratulations! You have created a review. Try , and . Once youadding reviewers selecting more files for review performing the reviewhave 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 readpermission and commit permission for a project's source code at the group level in FishEye, and then Crucible will inherit the samepermissions for the reviews in the project.

Set the default permissions for all new projectsSet 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 withcode more efficiently.

Configure commits to require a JIRA issue keyAction issues via commit messages

Create a review for a changeset from the Source tab


In the header, select a project from the project drop-down menu and click the tab.SourceClick to open the source-related activity stream, and then click the button to display commits only.Activity CommitsHover 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

. Follow the instructions to complete the review setting.Create ReviewScreenshot: Creating a review from the Source tab

Getting started using Atlassian OnDemandThe information on this page will help you get started using Atlassian OnDemand. Depending on what applications you have access to, youcan get started by trying out the functionality in the relevant sections below.

On this page:

JIRAConfluenceFishEye/Crucible/SubversionBamboo

JIRA


21

Create an issueAdd gadgets to view the information that you need on the dashboard, e.g.:

The Assigned To Me GadgetThe 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

http://confluence.atlassian.com/display/JIRA/Using+Keyboard+Shortcuts


22

1. 2.

Create a page by going to the tab and using the button in the top right corner. Wiki Add 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 menu in the top right corner and click .Tools Watch

More info: Working with the wiki

FishEye/Crucible/Subversion

View changesets by going to the tab. Browse and drill down to branches in the left navigation.SourceCreate and participate in code reviews.

Go to the tab and click .Review Create new reviewSet up the review by following the instructions.

View all the code changes committed against an issue by going to the tab of the issue in JIRA.SourceCheck out Getting started with Source and Review Bundle

More info: , and Working with the Repository Getting Started with Crucible Working with source

Bamboo


23

Create a Plan

More info: and Getting started with Bamboo OnDemand 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 dataimport SVN data integrate with external repos (GH, BB)

Create an account. (link to WAC FAQ)

Importing data

link to importing userslink 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 issuesassignment 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, digrammingreporting and graphs

DeveloperAccess my JIRA Studio IssuesI can tackle my task.JIRA Studio/IssuesDeveloper


24

Commit some codeit can be reviewed and built.Source (FE/CRU)

Lead Developer/DeveloperReview the codeI 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 lookand 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:


Managing data




25



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 from 'g' + 'g'anywhere in your Atlassian OnDemand site. This brings up the box, in which you can search for menus.Administration Search

Screenshot: Searching for permissions when viewing an issue


Creating new projectsDeleting a projectSetting project permissionsAssociating a JIRA project with multiple FishEye repositoriesAssociating a JIRA project with a Confluence spaceCustomising Application Tabs for your ProjectLinking activities from bitbucket or GitHub to JIRA IssuesConfiguring cross-application linking in JIRA OnDemand

Creating new projects

In Atlassian OnDemand, a is like a container and includes the following objects if the corresponding application is available in yourprojectsite:

a JIRA projecta wiki spacea build projecta source repository



26

1.

2. 3.

4.

5. 6.

1.

2.

3.

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 applicationaccess, see .Managing application access

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.You will see the existing projects if any.GeneralClick . The 'Add A New Project' page will appear.Add ProjectIn the field, type the name of the new project (e.g. 'Timesheet Mobile App'). The project name is displayed on the Dashboard.NameYou can change the project name at any time.In the 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.Key'TST-1'). You cannot change the project key later after the project is created.In the field, type the name of the user to be assigned as the project lead for the project.Project LeadClick the button to add the new project.Add

Result: Depending on what applications are available in your site, a JIRA project, a Confluence space, a Subversion repository, a FishEyerepository 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 forthe 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, wikidocuments, 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 withAtlassian 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 option.DeleteFor information on how to set application access, see Managing application access.

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active. The 'Administration' page appears, listing all of the projects currently setGeneralup in OnDemand.Locate the project you want to delete. In the column, click the link. The 'Delete Atlassian OnDemand project'Operations Deletepage appears.Click the button to delete the project.Delete


27

1.

2. 3.

4. 5.

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 theprimary identifier in Subversion.FishEye and Crucible are treated as one application, hence if your FishEye repository is successfully deleted then yourCrucible 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. Inorder to set the permissions for a project, you will need to configure each component (i.e. application) separately.

The page shows you how to configure your project with an example.Managing project visibilityOn the page, you will find links to the documentation on those settings in each application.Managing application permissions

Associating a JIRA project with multiple FishEye repositories

By default, a JIRA issue will display the changeset from Subversion in the tab if the commit message references the JIRA issue inSourcequestion 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 therepositories with the project:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the list of projects, click the project you wish to modify, e.g. Online banking.In the section, locate , and click the link. You will see the page where you can associateSettings FishEye Repository Selectrepositories with the project.In the field, enter the repository key for the repository that you want displayed in issues' source tab.FishEye repository keyClick . 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.


28

1.

2. 3. 4.

1.

2. 3.

On this page:

Associating a space with a JIRA project via General settingsAssociating a space with a JIRA project via Wiki setting

Associating a space with a JIRA project via General settings

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the list of projects, click the project you wish to modify, e.g. Online banking.In the section, locate , and click the link.Settings Confluence Space SelectEnter the Confluence space key you want to link with the project, and click . Associate

Associating a space with a JIRA project via Wiki setting

Go to a page in the space and choose > .Browse Space Admin

In the left-hand menu, click in the Application Links section.XML ExportEnter the JIRA project key you want to link with the Confluence space, and click .Associate


29

1.

2. 3.

1.

2. 3. 4. 5.

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 displayan external URL.


On this page:

Configuring application tabs for your projectAdding an application tab to your projectRenaming default application tabs

Configuring application tabs for your project

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active. You will see the list of projects currently set up.GeneralClick the name of the project that you want to customise. The global settings for the project will appear.At the bottom of the section, click ' '. The 'Tab Administration' page will display.Tabs More

To hide or show an application tab, click the ' ' or ' ' links in the ' ' column for the tab respectively.Hide Show Actions

To move an application tab, click the up ( ) and down ( ) arrows in the ' ' column for the tab.ActionsTo reset the display to the default tab configuration, click the ' ' link. Note that this willReset Default Tab Configurationremove any custom tabs that you have added.To edit the default tab configuration for all projects, click the ' ' link. Read more about defaultEdit Default Tab Configurationapplication tabs in .Configuring Global and Default Application Tabs

Adding an application tab to your project

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active. You will see the list of projects currently set up.GeneralClick the name of the project that you want to customise. The global settings for the project will appear.At the bottom of the section, click ' '. The 'Tab Administration' page will display.Tabs MoreClick the ' ' link, and then specify the tab name in the field and and the .Add Custom Tab Display Name URLClick the button to add the tab.Save


30

1. 2.

3. 4.

1. 2.

3.

1. 2.

3.

4.

5.

6.

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. ), the entire external page will be loaded without any OnDemand context when you click the 'Home'http://www.youtube.com

tab. Please ensure that your external page has links back into OnDemand; otherwise the user will only be able to navigateback 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 theaddress 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 pluginidentifies DVCS commit messages that reference a specific JIRA issue key and records the commit in JIRA. The information appears in theissue's and section. The plugin records the commit message, the list of changed files, and provides links to view theActivity Commitschange set.

JIRA requires that a connected repository provide a POST service. The POST service allows JIRA to hook into a source code commit andobtain 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 withadministrative access to the repository.

On this page:

Prequisite for GitHub private repositoriesProceduresExample of how commit information appears in a projectUsing with Force Sync operations to troubleshoot

Prequisite for GitHub private repositories

If you are planning on connecting to GitHub repositories, you must configure OAuth settings for GitHub before connecting to yourprivaterepos. To configure the OAuth settings, do the following:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.AdministratorOpen the tab and click .Issues Source Control > GitHub OAuth SettingsFollow 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:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.AdministratorOpen the tab and click . Issues Source Control > Bitbucket and and GitHub RepositoriesThe page appears. The page lists . Each repository entry includes theBulk Configure Repositories Existing Linked Repositoriesrepository URL and its corresponding project key.

To add a repository to this list, scroll down past the list to the blue form.

Click and select the JIRA project you want to link the repository to.Choose projectEnter the URL of the hosted repository.JIRA uses the HTTPS protocol to connect to the repository.Click the button.Add Repository JIRA verifies it can connect to the repository. If the repository you specified is private, JIRA prompts you for a valid username/password to connect to the repository.

Check .Install postcommit service

Then, depending on which hosting service you are using, do the following:

http://www.youtube.com


31

6.

For bitbucket repositories For GitHub repositories

Enter the credentials of a repository administrator.

If you do not enable the postcommit serviceat this point, you must ensure that the service is enabledthrough thehosted service. For information on enablinga post service on bitbucket, see Setting Up the bitbucket

.POST Service

Click the button.Add Repository


The system informs prompts you to authorize the connection:

Press .Allow

Your repository appears in the the page.Bulk Configure Repositories

Ensure your project users have the correct permissions

Project users must all have permissions. Without the proper permissions, users can not see the View Version Control tab even on linked projects.Bitbucket

Automatic synchronisation

After you link a repository, JIRA automatically starts looking for commits that reference issue keys for the associated JIRA project. Thesummary 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 tab of the DVCS-2 issueActivity


32

1. 2.

3.

Screenshot: Bitbucket commits on the tab of the DVCS-2 issueCommits

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 Syncoperation. The operation compares the existing commit data in JIRA with that in the linked repository. The system restores anyForce Syncmissing commit data to JIRA. A forced synchronization does not affect the commits in hosted DVCS. You should run operationsForce Syncwhen:

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, youmust wait for service to send the data.

To run a Force Sync operation:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.Administrator


33

3.

4. 5.

1.

2.

3. 4.

Open the Issues tab and click . Source Control > Bitbucket and and GitHub RepositoriesThe page appears. The page lists .Bulk Configure Repositories Existing Linked RepositoriesLocate the repository that you want to synchronise.Click the link. Force SyncA synchronisation starts. After the synchronisation is complete, a summary for the synchronisation displays under the repositorylisting in JIRA.

Related topics

Setting Up the bitbucket POST Service

Post-Receive Hooks

Configuring cross-application linking in JIRA OnDemand

In order to in JIRA OnDemand to point to other applications, the fields where links are created must use the ,create links Wiki Style Renderere.g. the and fields of your project's JIRA issues.Comment Description

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.. GeneralGo to the JIRA project configuration page. To do this, click your project name, and in the area, find the caption andSettings JIRAclick .ConfigureOn the JIRA project configuration page, go to the section.FieldsClick your project's field configuration and configure the to be . Renderers Wiki Style RendererIf the field configuration applies to multiple projects and you don't want other projects to be affected by the change, you can copy thereferenced and associate your project with the new field configuration before changing the settings.Field Configuration Scheme

Configuring renderes in JIRA OnDemand

Related topics

Creating LinksConfiguring Renderers

Managing data

Atlassian OnDemand provides mechanisms for handling data outside of the application user interface. You may need to use these to importdata into OnDemand or provide us with large amounts of data for a support case.

Read more about managing data in the topics below:

Importing DataUploading Data via WebDAV

Importing Data

Use the information on this page to learn how to import data into Atlassian OnDemand.


http://help.github.com/post-receive-hooks/


34

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 issuetrackers (e.g. Bugzilla).

Importing Issues

The JIRA importer has been designed to overwrite the existing JIRA data in your Atlassian OnDemand service. Please beaware that if you choose to import data after you have used JIRA OnDemand for a while, you will lose all the data input in theinterim.

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 importyour 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 issuetrackers such as Bugzilla.

On this page:

Before you beginProcedure

1. Get the data2. Import the data

After the importGranting application access to new usersSetting 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


35

1.

2.

3.

4.

5.

1. 2.

3.

Before you begin

The import process overwrites all the existing data and configuration in JIRA OnDemand and cross-application settings. Forexample, 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 encodingmethods, 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

. For example, if JIRA OnDemand runs JIRA 4.4, then the import from JIRA 4.4.1 to JIRAJIRA OnDemand versionOnDemand will not work. If you use JIRA Hosted and its version is newer than JIRA OnDemand, importing data is notpossible and you will have to wait until JIRA OnDemand is upgraded to a version the same as or higher than your JIRAHosted version.

Third-party issue trackers only: If you do not have a local JIRA instance, download or an earlier version of JIRAthe same versionfrom the and obtain an evaluation license for it from .JIRA Archive Downloads my.atlassian.com

Procedure

1. Get the data

Third-party issue trackers only: Import data from your existing third-party issue trackers to a local JIRA instance. Find the instructionson the page.Migrating from Other Issue TrackersLog in to Atlassian OnDemand as an administrator, and go to . The JIRA Import Wizard appears.Administration > JIRA ImportRead the prerequisites to view the supported formats for the data to be imported.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 page.Backing up data (JIRA documentation)For JIRA Hosted users, skip the attachment compression step and proceed to the following step.Optional: If you want to import avatars or logos, back them up as well. To do this, compress the and /data/avatars

directories individually. Make sure that the and directories are at the top level./data/logos /avatars /logosJIRA Hosted only: To obtain the XML backup you just created and the attachments, open an issue at inhttps://support.atlassian.comthe 'OnDemand' project and our support staff will provide you with the files.

Supported file formats for the backup data:

Issues: , Zip containing XML file ( ), GZipped XML file ( ), BZip2 XML file ( )XML .zip .xml.gz .xml.bz2Attachments, avatars and logos: , , . .zip .tar.gz/.tgz tar.bz2

2. Import the data

Upload the files to Atlassian OnDemand by .using WebDAVLog in to Atlassian OnDemand as an administrator, and go to . The JIRA Import WizardAdministration > General > JIRA Importappears.Click the button and follow the instructions on the wizard to finish the import process.NextThe wizard checks URLs in the specified XML backup, and will let you choose whether or not to update URLs to point to the newJIRA 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

http://www.atlassian.com/software/jira/ArchiveDownloads.jspa

https://my.atlassian.com/

http://confluence.atlassian.com/display/JIRA/Migrating+from+Other+Issue+Trackers

http://confluence.atlassian.com/display/JIRA/Backing+Up+Data

https://support.atlassian.com


36

The import process does not honour the default application access settings and does not give access to any applications to new users. Youmust 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 ' and ' global permissions, for example'JIRA Administrators 'JIRA Usersyou added a group called to the global permission, you must configure the JIRA global permission settings inmanagers 'JIRA Users'OnDemand after the import.

This is because the import process does not import the settings of the , ' and ''JIRA System Administrators' JIRA Administrators' JIRA' global permissions. The other global permission settings such as ' ' are imported.Users Browse Users

'JIRA System Administrators': As Atlassian OnDemand is a hosted product, you do not have the JIRA System Administratorspermission. Hence, there is no configuration required for this permission.JIRA Administrators' and global permissions: configure these two permissions by adding groups and users to them 'JIRA Users'as needed.

Permissions for other applications

Application permissions are managed in each application individually. If your site has other OnDemand applications, e.g. Confluence orBamboo, refer to for information on how to configure permission for these applicationsManaging application permissions

Related topics

Wiki permissions

Source permissions

Build permissions


Importing wiki data

You can import content to Confluence OnDemand from both Confluence and other Confluence OnDemand instances. The import works atthe space level. If you want to import the entire content of a Confluence site into Confluence OnDemand, you can do it by importing thespaces one at a time.


On this page:

Before you beginImporting Confluence spaces to Confluence OnDemand

1. Export space data from source Confluence instance2. 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 samemajor version. For example, if the current version of Confluence OnDemand is 4.1.3, only space exports from Confluence 4.1.x canbe imported. To find out the version of Confluence OnDemand, please refer to .Atlassian OnDemand Application VersionsLinking spaces to JIRA projects — If your OnDemand site also has JIRA, you can link a Confluence space to a JIRA project whenimporting 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. Ifanother space with the JIRA project key is already associated with the JIRA project, you can use one of the following methods towork 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 JIRAproject, and then associate this space with the JIRA project after the import. For instructions, see Associating a JIRA project

.with a Confluence spaceIf you do not need the existing space's content any more, remove that space before the import. The space importer does notoverwrite an existing space.

Renaming spaces — Renaming Confluence spaces is not supported. Confluence spaces can be linked to JIRA projects asdescribed above, but they will not have matching names. Alternatively, spaces can be renamed using a locally installed evaluationcopy 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 beingtracked as . Creating a new personal space and moving the imported content to it page by page is the only workaround atJST-5760this time.

http://confluence.atlassian.com/display/AOD/Configuring+Default+Repository+Permissions

https://studio.atlassian.com/browse/JST-5760


37

1. 2.

3. 4.

1.

2. 3.

4.

5. 6.

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:

Log in to the source Confluence or Atlassian OnDemand site.Navigate to any page in the space you wish to export and choose > .Browse Space Admin

Click on the tab.Advanced 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

If your exported archive is larger than 100 MB, upload the file to Atlassian OnDemand . For archives smaller than 100via WebDAVMB, you do not have to use WebDAV to upload data.Log in as an administrator to Atlassian OnDemand.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 > . Then click the tab, and in(Your username) Administration Wikithe left-hand menu, click > .Configuration Import Spaces

Select the XML archive you want to import.If you didn't upload the archive via WebDAV, specify your file by using the button.Choose FileIf you uploaded the archive via WebDAV, click the file in the field.WebDAV Files

Optional: For sites with multiple OnDemand applications, specify the JIRA project you would like to link this space to.Click the button to import your Confluence space.Import

This will not import user accounts. Please see if you would like to do this.Importing Users

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 examplesof the appropriate CSV format are available on the page.Crowd CSV Import

There are some OnDemand-specific groups to be aware of:

Users must be in the group in order to log in (by default).usersIf you would like to specify application access, subject to your licence, you can include the following group memberships for users inthe 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 and submit a so that the support staff can import the users for you.WebDAV support request

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 yourdatabase 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 queriesfurther.



38

1.

2.

3.

4.

5.

users.sql

copy (SELECT user_name AS username, first_name AS first, last_name AS last, email_address ASmail, 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 and file in that can be sent to Support. You can read moreusers.csv group_memberships.csv /tmpabout for more options.Postgres's COPY command

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 themand 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 themthat 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:

Create a private page

Brainstorm topics to cover

Melanie

Jeff Curry

Azwandi

Maleko

Dylan Hansen

Anyone else?

Fill in content

Fill in while brainstorming

Mel to follow up on remainder with experts

Get approval from Douglas

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 inadvance!

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 inadvance?Outline steps the customer is going to need to take on their side.Paint a picture of the process:

How to exportWhen to provide the exports, relative to the scheduled time slotWill 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?

http://www.postgresql.org/docs/8.4/static/sql-copy.html

https://support.atlassian.com/browse/JST-21737


39

Resetting passwords?What are risk factors that may cause things to go awry?

Custom plugins...Crowd connected to LDAPAnything we can be aware of up-front would be helpful in ensuring the support engineer will have the resources they need atGo 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, whereasan (see ) only stores the most recent state. Please note, the import processsvn import Importing Unversioned Data into Subversiondescribed below will overwrite any existing Subversion data for all projects in your OnDemand repository. If you want to import Subversiondata 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 file2. Altering the structure of your Subversion repository3. Testing the Integrity of the Dump File4. Importing the SVN Dump File to Atlassian OnDemandTroubleshootingRelated topics

1. Creating an SVN dump file

You can generate a Subversion dump file from the SVN host by using the command, e.g.svnadmin dump

$ 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 OnDemandassume that the content follows the standard layout (e.g. project creation/deletion). Atlassian OnDemand does not provide enough control tomanage arbitrary mappings.

The standard Subversion layout in Atlassian OnDemand is described below:

Your OnDemand site has a single Subversion repository, at ./svn/https://<account_name>.atlassian.netThe convention is to have a top-level directory per project, whose name is the same as the project key. Please note, all Subversioncontent in your dump file must be associated with a OnDemand project. If a project does not yet exist, you need to create it beforeyou import. See for instructions.Adding New ProjectsFor example, given two projects, " " (project key " ") and " " (project " "), Subversion may lookPlugins PL Plugins for Eclipse PLElike 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-leveldirectories 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. . However, only new commits made aftersvn rename Plugins PLthe rename will appear in Source application. - OR -alter the structure (including history) of the repository using Subversion tools ( ).see below- OR -

http://svnbook.red-bean.com/en/1.1/re31.html


40

1.

2.

3.

1. 2.

3. 4. 5.

work with our , or , to get your repository into the format required byPremium Hosted Services Partner another partnerAtlassian 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 aboveyou can alter it yourself.

First, export a subset of your repository while creating an SVN dump file using the tool. In the following example, the resultingsvndumpfilterdump file will only contain the data under the 'PL' top-level directory. This rewrites the history, so 'PLE' and other top-level directories will notexist 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: . Run the script to rename directories through the entire repository history. Forsvn-dump-relocexample, 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:

Create a test repository:

$ svnadmin create /tmp/test_repo

Load in the dump file using :svnadmin load

$ cat svn.dump | svnadmin load /tmp/test_repo

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 yourAtlassian OnDemand instance.

Procedure:

Log in to Atlassian OnDemand as an administrator.Compress your Subversion dump file and upload it to the sub-directory in the WebDAV directory share. See dump_files Uploading

for instructions. To compress the dump file, you can use gzip or bzip2. The importer can import the zipped files.Data via WebDAVClick your username, select ' ' from the dropdown. The administration console will be displayed.AdministrationIn the tab, go to ' '.Source Import SVN RepositoryThe SVN dump files that you have uploaded to will be displayed. Click ' ' next to the file you want to import. Thedump-files Importimporter 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), youwill be asked to confirm whether you want to overwrite it.

http://svnbook.red-bean.com/en/1.5/svn.ref.svndumpfilter.html

http://search.cpan.org/%7Esalva/SVN-DumpReloc-0.02/bin/svn-dump-reloc

http://svnbook.red-bean.com/en/1.1/re36.html


41

5.

6.

7. 8.

1. 2.

3. 4.

If you have users in the dump file that do not exist in OnDemand instance, you will be asked to confirm whether you stillwant to do the import. You can still import your file, however, if you want to match all committers to users, you will need tocreate the missing users before doing the import. Unmapped committers will remain in the SVN history, and will simply nothave a JIRA/FishEye user associated with them.

The importer will back up your existing OnDemand repository as a SVN dump file in your WebDAV sub-directory. Thedump-filesimport will then be completed.If your import is successful, a confirmation message will be displayed.Optional: You can delete the SVN dump files (the imported file or the backup of your old data) from your WebDAV directory after theimport.

Please note: your Subversion users will need to check out a new copy of Subversion content after your repository is moved to OnDemand.See for guidance.Working with the Repository

Troubleshooting

The files in your existing OnDemand repository may be associated with entities like code reviews. If you overwrite these files onimport, you might experience errors when trying to access the files (e.g. via the code review). for assistance.Raise a support request

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 importcommand in a . This command allows you to import a directory, which may contain further levels of directories and files,Subversion Clientinto a Subversion repository. However, the command will only import an tree of files into Subversion, that is e.g.svn import unversionedno history will be retained.

Access to the Subversion Administration Console is , and as a result you will not be able to import full directories and history intorestrictedSubversion. 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 with as needed.atlassian.net jira.com

To import unversioned data into Subversion:

Open a Subversion console.If you have already created your project in OnDemand, enter the following command to import your local directory into your project'sSubversion 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 command. However, we strongly recommend thatsvn createyou create your by in the OnDemand application.<project_key>/trunk creating a project

You will see a commit message on your console at the completion of a successful import (e.g. 'Committed revision 1').Check that your files have been correctly imported by using the command to display the files in your target directory. Forsvn listexample, svn list /<project_key>/trunkhttps://<account_name>.atlassian.net/svn

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 (Web-based Distributed Authoring and Versioning) directory share, and you can useWebDAVthis 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 belongto the group.administrators

Please note that this directory share is intended to be used for general file storage. It is also different from the not Confluence WebDAV accessible at interface /wiki/plugins/servlet/confluence/default.https://<account_name>.atlassian.net

On this page:

http://www.webdav.org/

http://confluence.atlassian.com/display/DOC/Using+a+WebDAV+Client+to+Work+with+Pages

http://confluence.atlassian.com/display/DOC/Using+a+WebDAV+Client+to+Work+with+Pages


42

1. 2.

3.

1.

2.

Supported WebDAV clientsAccessing your WebDAV directory

Accessing your WebDAV directory in OS XAccessing your WebDAV directory in Windows XPAccessing your WebDAV directory in Windows VistaAccessing your WebDAV directory in LinuxAccessing your WebDAV directory using a client

Troubleshooting




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 fordetails:

OperatingSystem

OnDemand WebDAV Directory compatibility Recommended Alternative Clients

OS X All versions of OS X should be compatible. We highly recommend , if you don't want toTransmituse the OS X WebDAV functionality. A free, opensource alternative is .Cyberduck

WindowsXP

Windows XP may not work with the WebDAV directory, ascompatibility is highly dependent on the service packs andhotfixes that are installed.

The is a free time-limited DAV BitKinex WebDAV Clientclient. Please note that this client has not been testedthoroughly with the OnDemandWebDAV directory.

WindowsVista

Windows Vista has a working redirector for DAV over HTTPS.Please note that this has not been tested thoroughly with theOnDemand WebDAV directory.

The is a free time-limited DAV BitKinex WebDAV Clientclient. Please note that this client has not been testedthoroughly 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 toprovide a password for Subversion access the first time you logged into Atlassian OnDemand. Use that password toaccess WebDAV, not your Google Apps password.

Accessing your WebDAV directory in OS X

Activate the Finder in OS X and select from the menu.Connect to Server GoEnter the following URL:

where <account_name> is the account name that your administrator/webdavhttps://<account_name>.atlassian.netprovided at signup.

You must use , not https http.You will be prompted for a username and password. Enter the username and password that you use to log into AtlassianOnDemand.

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 directoryfrom My Network Places.

Navigate to and click .My Network Places Add a network place

http://www.panic.com

http://cyberduck.ch/

http://www.bitkinex.com/webdavclient/

http://www.bitkinex.com/webdavclient/

http://www.webdav.org/cadaver/


43

2. 3. 4.

5.

6. 7.

1. 2.

3. 4.

5.

1. 2.

The ' ' will display. Click . A list of service providers will be displayed.Add Network Place Wizard NextSelect > .Choose another network location NextYou will be prompted to enter a URL in the ' ' field on the next page. Enter the following URL and click Internet or network address

:Next where <account_name> is the account name that your administrator/webdavhttps://<account_name>.atlassian.net

provided at signup.

You must use , not https http.You will be prompted for a username and password. Enter the username and password that you use to log into AtlassianOnDemand and click OK.Enter a name that will used to reference the WebDAV directory on your computer.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.

Open and click .My Computer Map Network DriveThe ' ' screen will display. Click Map Network Drive Connect to a Web site that you can use to store your documents and

> .pictures NextClick > .Choose a custom network location NextYou will be prompted to enter a URL in the ' ' field on the next page. Enter the following URL and click Internet or network address

:Next where <account_name> is the account name that your administrator/webdavhttps://<account_name>.atlassian.net

provided at signup.

You must use , not https http.You will be prompted for a username and password. Enter the username and password that you use to log into AtlassianOnDemand 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 you may need to download and install the following Vista update — to be valid', KB907306

Accessing your WebDAV directory in Linux

This method is one of the ways to set up WebDAV access in Linux.

Install a WebDAV client. For example, to install Cadaver on Debian/Ubuntu, run .sudo apt-get install cadaverConnect to , using your Atlassian OnDemand username and password,/webdavhttps://<account_name>.atlassian.netand use the to upload a file.putcommand

$ cadaver https://<account_name>.atlassian.net/webdavAuthentication required for WebDAV on server `*.atlassian.net':Username: jsmithPassword: dav:/webdav/> put .WinkUploading .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: where <account_name> is the account name that your administrator/webdav,https://<account_name>.atlassian.net

provided at signup.

You must use , not https http.The authentication credentials required to access the WebDAV directory are the username and password that you use to log intoAtlassian 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


http://www.microsoft.com/downloads/details.aspx?FamilyID=17c36612-632e-4c04-9382-987622ed1d64&DisplayLang=en



44

A is the account for an individual who accesses your Atlassian OnDemand site.user

If multiple users in your orgnisation share the same , you can use groups for easier permission setup andapplication permissionsmaintenance.


If you have JIRA, or JIRA plus more:

For example , or , user administration is centralised in JIRA, i.e. the application.JIRA + Confluence JIRA + Bamboo Issues

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:

UsersApplication accessApplication permissions

Users must be granted to a given application in order to be able to log in to a particular application. Once they log in to anapplication accessapplication, what they can see and do is determined by the permissions they have for that application.


If your site has

Confluence OnDemand only, refer to .Managing users and groups for Confluence OnDemandJIRA OnDemand only, refer to .Managing users and groups for JIRA OnDemand


45

1.

2.

3.

4.

5.

6.

7.

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 applicationpermissions 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 isthe prerequisite for a user to be able to use the application. Giving a user access to an application means that the user will counttowards 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 taskssuch 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.


If your site has

JIRA OnDemand only: refer to .Managing users and groups for JIRA OnDemandConfluence OnDemand only: .Managing users and groups for Confluence OnDemand

Adding a new user and granting application access

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . Then in the top right area of the page, click . The 'Create NewUser Management > Users Add UserUser' page appears.Enter the details for the new user, for example:

Username: jsmithPassword and Confirm Password: 1234Full Name: Joseph SmithEmail: [email protected]

To send the username and password to the user automatically in an email after the account is created, select the Send Notification check box.Email

After receiving the email, the user can follow the link in the email to set their password. The link is valid for 24 hours.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

check box.developers groupGrant 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.Click the button.CreateWhen users are created, they are automatically added to any groups that are granted with the global permission. TheJIRA Usersdefault group that has this global permission is the group.users

When you set application access for a new user in step , access to certain applications might be already selected for you. What6applications 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 control, you will see .Add User Add External (non-Google) user

Related topics

Managing groups


Managing application access: Learn how to set default application access.

Default groups and permissions

external user

Managing groups


46

1.

2. 3.

1. 2.

1.

2. 3.

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 global permission. The default'JIRA Users'group that has this global permission is the ' group.'users


If your site has Confluence OnDemand only, refer to .Managing groups in Confluence OnDemand

Adding groups

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . The 'Groups' administration page appears.User Management > GroupsLocate the caption. In the field, enter the new group name and click the button. The group is added.Add Group Name Add Group

Editing group membership

On the 'Groups' administration page, you can edit group members by clicking the link.Edit MembersSpecify user names in the or column and click the corresponding button.Leave Join

Related topics


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


On this page:

Setting default applications for new usersGranting application access to a new userViewing a user's application accessGranting and revoking application access for an existing userGranting 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 applicationsautomatically. If your site is integrated with Google Apps, access to the default applications will be granted to Google users at their initiallogin.

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . The 'Set Default Application Access' page appears.User Management > Default Application AccessUse the check boxes under the applications to set default applications, and then click the button.Save

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 page.Managing users


47

1.

2. 3.

1.

2. 3.

4.

1. 2. 3. 4.

1.

2. 3. 4. 5.

Viewing a user's application access

To view the applications a user has access to, the easiest way is through the page.Application Access

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . The 'Application Access' page appears.User Management > Application AccessLocate 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 Searchbutton. 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 pageApplication AccessThe page in administration pageUser Details Users

Procedure via the Application Access page:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . The 'Application Access' page appears.User Management > Application AccessLocate 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 Searchbutton. The user will be displayed.Use the check boxes under the applications to change the user's application access, and then click the button to saveUpdatechanges.

Procedure via the User Details page:

On the tab of the administration console, click .General User Management > UsersSearch for the the user with the filter, and then click the username to display the page.User DetailsFind the item and click the pencil icon next to it. The application access settings become editable.ApplicationsEdit the check boxes as needed and then click the button to save the changes.Done

To remove a user's access to Subversion, you have to remove that user's FishEye/Crucible access. The removal of FishEye/Crucibleaccess happens immediately, but the removal of Subversion access might need a few minutes to take effect.

Granting application access to multiple users

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click .User Management > Bulk Add Application AccessSelect the check box under the application for which you want to grant access.In the user entry box, enter the usernames and separate them by commas, or click the icon to search for users.UsersAfter usernames are entered, click the button to save the changes.Submit


Application permissions control what users can do and what data they can see within a particular application. Each application's permissionsare configured separately and define the level of access to a given application only.


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 havethe ' ' global permission or belong to groups that have this permission. Even for users that only need to access Confluence, theyJIRA Usersstill need the ' ' global permission; otherwise, they cannot log in to Confluence.JIRA Users

JIRA permissions - Issues

Configuring Security (JIRA documentation) – the information covers the various aspects of security within JIRA.

Note that the information on does not apply to Atlassian OnDemand.system administrators

Confluence permissions - Wiki

Global permissions (Confluence documentation) Note that the information on does not apply tosystem administratorsAtlassian OnDemand.


48

1.

2.

3. 4. 5.

Configuring default space permissionsSpace Administrators and their Permissions (Confluence documentation)

Subversion, FishEye and Crucible permissions - Source and Reviews

Configuring repository permissions

Bamboo permissions - Builds

Grant global permissionsConfigure a plan's permissions

Related topics


Managing anonymous access

You can enable and disable anonymous access to your Atlassian OnDemand applications individually as needed. Anonymous access ismanaged via permissions in each application as described follows.

Anonymous users do not count towards your license.

On this page:

Enabling anonymous access in JIRAEnabling anonymous access in ConfluenceEnabling anonymous access in SubversionEnabling anonymous access in Bamboo


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 isassociated with the project.

Procedure:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralGo to the tab. In the left-hand menu, go to > . The existing permission schemes areIssues Misc. Schemes Permission Schemesdisplayed.Click the permission scheme that is associated with the project. The 'Edit Permissions' page appears.Locate the permission, click the link in the Operations' column.The 'Add Permission' page appears. Browse Projects AddSelect > , and click the button. The permission scheme is updated and the associated JIRA project now allowsGroup Anyone Addanonymous access.

For detailed information on changing project permissions in JIRA, refer to (JIRA documentation).Managing Project Permissions

Screenshot: Enabling anonymous access in JIRA


49

1.

2. 3.

1. 2. 3.

1.

2. 3. 4. 5. 6.

Enabling anonymous access in Confluence

Procedure for sites with multiple applications:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralGo to the tab, and then > . The settings for your wiki will appear.Wiki Permissions Global PermissionsClick any button and change the setting to allow anonymous access to your project's wiki.Edit Permission Anonymous Access

Procedure for sites with Confluence only:

Log in as an administrator, and go to the Confluence 'Administration Console' by clicking > .Browse Confluence AdminUnder the section, select . The settings for your wiki will appear.Security Global PermissionsClick any button and change the setting to allow anonymous access to your project's wiki.Edit Permission Anonymous Access

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

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The 'Builds' administration options will display.BuildsIn the left-hand menu, go to > .Security Global PermissionsClick the button. The 'Global Permissions' page will become editable.Edit Global PermissionsIn the second table, locate , and select the check box in that row.Anonymous users AccessClick the button.Save

Anonymous users will now be able to access your Bamboo system. However, they can only view plans and build results for plans wherethe ' ' has been granted to 'Anonymous users'.Access plan permission

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 yourAtlassian OnDemand site is created.

By default, new users will be added to the ' group. This is because the 'users' group is the only default group with the 'users '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.


50


If your site has Confluence OnDemand only, refer to .Default groups in Confluence OnDemand

Table : Default groups in Atlassian OnDemand

Groups in sites withJIRA

Default permissions in applications

users This group contains every user in your site.

JIRA:the and global permissions. 'JIRA Users' allows users to log in'JIRA Users' 'Bulk Change'to Atlassian OnDemand, and and 'Bulk Change' allows users to bulk edit issues.a member of the project role, which allows members to see all project issues'Users'(unless protected by a ) and create new issues.security level

Confluence: the permission to create and view Confluence content for the project

Bamboonon-administrator access

Subversion:read only access

developers This group typically contains people who perform work on issues.

JIRA:the and 'Browse Users', 'Create Shared Filter' 'Manage Group Filter Subscriptions'global permissions in JIRA.a member of the project role, which allows members to edit, move, assign, be'Developers'assigned, link, work on, resolve and close issues.

Confluence:the global permissions'Personal Space'

Bamboo:non-administrator access

Subversion:read/write access

administrators This group typically contains people who are administrators.

JIRA:the global permissions.'JIRA Administrators'a member of the project role, which allows members to edit project'Administrators'versions and manage project content (delete issues, comments, manage watchers).

Confluence:the 'Attach Files to User Profile', 'Personal Space', 'Create Space' and 'ConfluenceAdministrator' 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 , there are two types of users: Google Apps users and external users. integrated with Google Apps

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 notchanged.


external user

An is a user who does not have access to your company email domain, but who you allow to access your Atlassianexternal userOnDemand site, for example. e.g. client, contact, or remote worker.


51

1.

2. 3.

4.

5.

Tasks that need to be done in Google apps:

Create, delete, and rename Google Apps usersReset passwords

Where:

Log in to your Google Apps domain as an administrator and go to ' ' on the toolbar.Organization & Users

Tasks that need to be done in Atlassian OnDemand:

Manage allocation of users to groupsManage how groups access functionalityManaging application accessCreate, delete, and rename external (non-Google) users

How:

Managing usersManaging groupsManaging application accessManaging application permissionsManaging anonymous accessDefault groups and permissions in Atlassian OnDemand

Related topics

Converting Google Apps Users to External UsersManaging Username ConflictsMerging OnDemand and Google Apps user basesSynchronising 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 Appsusers to an external user. An example is when an employee becomes a contractor.

Procedure

In Atlassian OnDemand, note the groups that the user is assigned to. You can do this by accessing the User Management >Usersadministration page, selecting the user and then writing down the groups listed under the column.GroupsIn your Google domain, delete the user.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.Now you can manually re-enable the user as an external user by re-assigning the user to the groups from which the user accountwas removed. To do this:

In Atlassian OnDemand administration console, go to .User Management > UsersSelect the user and click the username.In the user information screen which opens, click ' '.Edit GroupsIn the ' ' screen, hold down the ' ' key, and then click to select the groups the user was originallyEdit User Groups Ctrlassigned to.Click ' ' to re-assign the user to these groups.Join

Note that as Atlassian OnDemand is unable to retrieve the password used in Google, the user's password will be randomised at thispoint. You will need to either reset the user's password via the admin console or have the user reset it when logging in directly toOnDemand by clicking ' ' on the form.Can't access your account?

The user can now log in through the method as shown in the screenshot.'Log in directly'

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


52

1.

2.

3.

A is the situation where the same username exists in both your Atlassian OnDemand and Google Apps user bases but theusername conflictusername 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 anyusername 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, is the jsmithusername for [email protected]

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 asyou see fit.

Linking conflicting usernames

To manage username conflicts:

If you receive a system email advising of a username conflict, navigate to the screen by:Username Conflicts either following the link in the emailor going to the administration console, and then clicking tab > .General Username Conflicts

In the screen, use the operation to link conflicting usernames. The dialogUsername Conflicts Link Confirm Link Usernamesopens.Click to confirm the linking action. The Google Apps email will be copied and overwrites the OnDemand email.Yes

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 typicallydone immediately after .integrating Google Apps with Atlassian OnDemand


On this page:

Before you beginMerging usersUsing the CSV export to merge usersEnd user actions

Before you begin

When you , Atlassian OnDemand will automatically merge the user bases in Atlassian OnDemandintegrate OnDemand with Google Appsand 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 email addresses, when matching Google usernames to Atlassian OnDemand. For example,notthe Google username pictured in the following screenshot is ' ', not ' '.george [email protected]


53

1.

2.

3.

4.

Merging users

To merge your Atlassian OnDemand and Google Apps user bases:

After integrating OnDemand with Google Apps, when you first log in with your Atlassian OnDemand administrator username, the '' screen will appear. This screen summarises your user basesSetting up the user integration with your Google Apps Domain

after migration. It is divided into four areas:

ScreenArea

Function

Existinguser(s)to belinked

Where existing Google Apps and Atlassian OnDemand users have different email addresses associated with theiruser name, select ' ' to confirm that these users can access Atlassian OnDemand with their Google Apps Log In.Link

Externaluser(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 GoogleCalendar, GMail, Google Docs, or Google Site.* Under the column, select to provide these users with Atlassian OnDemand log in access.Make External Enable* If some of these users are Google users but they yet haven't been created in your Google Apps Domain, you canselect the link: to download a CSV export file, which you can'Export these users to your Google Apps domain'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 functionto help prepare your user base before fully migrating to Google Apps. The CSV export facility will also appear as anoption during the migration if the automatic merging process detects any problems when matching user names.

Newuser(s)

These are any new users which you have added to your Google Apps account since integrating with AtlassianOnDemand. They will be imported into Atlassian OnDemand.

Linkeduser(s)

These are existing users which are already linked to a Google Apps account. Atlassian OnDemand will use theirdetails for 'first name', 'last name', and 'email address'.

Review the screen and determine if you need to either link any Google Apps and Atlassian OnDemand email addresses, or makeany users external:

To link email addresses, under , select the 'Link' checkbox.Existing users(s) to be linkedTo make users external, under , select the 'Enable' checkbox.External user(s)

Under the drop-down labelled with your log in name, select . In the administration console, select the tab,Administration Generalthen select .Google ManagementUnder , click to select the required access level — Developer, Collaborator, or No Access –Set default access level for new usersthen click ' 'Save


54

4.

5.

1.

2. 3. 4.

5.

6.

1. 2.

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 pagedefault applicationrevoke the application access from a particular user

Under ' ', click ' ' to immediately Synchronise Users Start Synchronisation synchronise your Atlassian OnDemand and Google user. Your migration and merging of user bases is now complete.databases

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 area of the External user(s) Setting screen, along with the option to create a export of your user database. up the user integration with your Google Apps Domain CSV

To merge your Atlassian OnDemand and Google Apps user bases using the CSV export:

On the screen, under , click the Setting up the user integration with your Google Apps Domain External Users 'Export these link.users to your Google Apps domain'

Export your user database from Atlassian OnDemand by clicking ' '.SaveDelete any external users and inactive users from the CSV file.For all remaining users in the CSV file modify the 'first name', 'last name' and 'password' as necessary. The username must remainthe same.Re-import your user database into Google Apps by clicking through to the appropriate page in the Google Apps administrator pagesand uploading the CSV file. This will allow a smooth merging of the user databases, by creating Google Apps accounts for anyAtlassian 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 completeNow, go to the Atlassian OnDemand administrator screen, set the default access level for new users, and click 'Start

'. Your migration and merging of user bases is now complete.Synchronisation

End user actions

End users will need to carry out the following actions after the migration:

Log in to Atlassian OnDemand, using the password the administrator provides.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 basesOngoing synchronisation of large user basesMitigation 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 thesystem adds users after their initial login. Administrators cannot modify any user's access rights, i.e. application access, until the user haslogged 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 begranted 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 . Instead,enabled itusers 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 . Our supportAtlassian supportengineers will be happy to assist you with this process.

http://en.wikipedia.org/wiki/Comma-separated_values



55

1.

2. 3.

4. 5.

6.

Synchronising Atlassian OnDemand and Google Apps Users

User data is regularly synchronised between Atlassian OnDemand and Google Apps. You can change the synchronisation settings asneeded at any time.

Enable and disable automatic user synchronisationSpecify the synchronisation intervalSynchronise your user data on an 'as required' basis


Configuring synchronisation of user data with Google Apps

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click .Google ManagementConfigure the default application access for new users as needed. To edit the setting, click the link. This takes you to the defaultEditapplication access page.Configure the default user groups as needed. To edit the setting, select one or more groups and click the button.SaveSelect whether is enabled, and how often your user data is synchronised, then click 'Google Apps user Synchronization Save

'.Synchronization SettingsTo start synchronising users, click . An example system log from the most recent user data synchronisation isStart Synchronizationshown below. You can also click to download a text file of this synchronisation log.'Download full log'

You can configure these settings:

Setting Description AllowedValues

Default

Set Default AccessLevel for NewUsers

This sets the default access level for new users the first time they log in to OnDemand. 'NoAccess'

Default UserGroups for NewUsers

This sets the default group that new users are added to after their initial login. 'Users'

Google Apps UserSynchronization

This switches automatic synchronisation on or off. 'Enabled'

'Disabled'

'Enabled'

SynchronizationInterval

Adjusts how often the synchronisation process runs. Anyvalue inminutes

60minutes

Google AppsDomain

This is a link to the administration interface on your Google Apps domain. Click this linkto visit your Google Apps Domain and manage users or Google-specific settings.

Cannotbechanged

Link isalwaysshown

Synchronize Users Enables you to immediately synchronise user bases. You can also download the log asa 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.



56

1.

2.

If your site has

multiple OnDemand applications, refer to .Managing Users and GroupsConfluence 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 OnDemandAdding users in Confluence OnDemandManaging groups in Confluence OnDemand


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 iscreated.

All new users are added to the ' ' group.confluence-users


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 allnewly signed-up users of Confluence.

administrators This is a group of 'super-users' who can access the 'Administration Console' and perform site-wideadministration. 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 group automatically.'confluence-users'


Procedure

To create users:

Log in as an administrator, and go to the Confluence 'Administration Console' by clicking > .Browse Confluence Admin


57

2. 3. 4.

5. 6.

1. 2. 3. 4. 5.

1. 2. 3.

4.

Under the section, select .Security Manage UsersClick at the top of the page.Add UserEnter the user's details, for example:

Username: jwongFull Name: James WongPassword and Confirm Password: 1234Email: [email protected]

Click the button to create the user.CreateConfluence does not send the username and password to a new user automatically, so you will need to send those details to yourusers 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 tochange their password at the first login.

Related topics


Default groups in Confluence OnDemand

Configuring Default Space Permissions


Groups are handy when multiple users have the same application permission settings. Instead of having to configure application permissionsfor each user individually, you can configure permissions at the group level.


Procedure

1. Create groups

Log in as an administrator, and go to the Confluence 'Administration Console' by clicking > .Browse Confluence AdminUnder the section, select . You will see a list of default groups.Security Manage GroupsClick the link at the top of the page.Add GroupEnter a name for the group, for example: .The group name must be in lower case.department managersClick . The group is created and you will see the list of all existing groups.Save

You are now ready to start adding users to the group.

2. Add members to groups

Click the group name you just created in the group list.Click the link at the top of the page.Add MembersThe page appears. Type in the usernames of the people you want to add to the group. You can also search for andAdd Members

select users by clicking the icon.After you have added the required usernames, click the button to add the members to the group.Add

Next: After setting up users and groups, you can continue to configure permissions.

Related topics

Adding users in Confluence OnDemandDefault groups in Confluence OnDemand


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 FormatChanging your Account LanguageRequesting supportChanging your Account NameEnabling Public Signup and CAPTCHAViewing your user countChanging your Welcome MessageIntegrating OnDemand with Google Apps

Changing your OnDemand 'From' Email Header Format


58

1.

2. 3. 4. 5.

6.

1.

2. 3.

4.

The 'From' header is the email address that outgoing mails will appear to have come from.

To change your OnDemand 'From' Email Header Format:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues administration console will display.IssuesIn the left-hand menu, click the option. Your account settings will display.General ConfigurationClick the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode.Update the ' ' field to your desired email header. This will set the format in notification emails. You can use the followingEmail from: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) <[email protected]>

Please note that this field only sets the 'From' Email Header, not the email address itself.

Click the button to change your account settings.Update

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 project at . If you doOnDemand https://support.atlassian.comnot 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 processesyour request.

You can also ask questions at to get help from the community.https://answers.atlassian.com/

Changing your Account Name

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues administration console will display.IssuesIn the left-hand menu, click the option that displays below it. Your account settings will display (seeGeneral Configurationscreenshot below).


https://answers.atlassian.com/


59

4. 5. 6.

1.

2. 3.

4. 5.

Click the link at the bottom of the page. The page will display in editable mode.Edit ConfigurationUpdate the field as desired. You would typically set this to the name of your company or organisation.Application TitleClick the button to change your account settings.Update

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 createnew user accounts.

As with users created by administrators, new user accounts created via public signup are granted with the default application access andadded to the groups that have the global permission in the same way.JIRA Users


To enable public signup and CAPTCHA:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues administration console will display.IssuesIn the left-menu, click the option that displays below it. Your account settings will display (see screenshotGeneral Configurationbelow).Click the link at the bottom of the page. The page will display in editable mode.Edit ConfigurationUpdate the signup mode to be public. To do this, update the field to 'Public'. This will allow any users to sign up and then postMode issues.


60

5.

6. 7.

1.

2. 3.

Please note, OnDemand is priced based on the number of users in your installation. Enabling public signup maycause you to exceed your user limit.

To enable (i.e. validation by image) on signup, set the field to .CAPTCHA CAPTCHA on signup ONClick the button to save your account settings.Update

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:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, go to > . User Management Application AccessAt the top of the page, you will see the OnDemand applications that your site has. Below each application, the number of remaininguser licenses is displayed.

Bamboo OnDemand has the unlimited license because it is licensed based on the number of elastic agents your site utilises instead ofthe 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.


61

1.

2. 3.

4.

5.

1. 2.

3.

Changing your Welcome Message

The welcome message appears in the gadget, overwriting the default text of the gadget . By default, users of your site can seeIntroductionthe 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 gadget.Introduction


To change your welcome message:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues administration console will display.IssuesIn the left-hand menu, click the option. At the bottom of the the displayed page, click the General Configuration Edit

link. The page will display in editable mode.ConfigurationIn the section, find the field and update it to your desired welcome message. Setting Introduction

You can use HTML in your welcome message, but it must be correctly formatted (e.g. ensure all HTML tags areclosed).Click the button to change your account settings.Update

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.


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 email addresses. For example,notthe Google username pictured in the following screenshot is ' ', not ' '.george [email protected]

Migrating to Google Apps

1. Adding Google Apps integration to your Atlassian OnDemand instance

To do this:

Go to the and add Atlassian OnDemand.Google Apps MarketplaceEnter your My Atlassian credentials in the order form that is displayed. You must use the same My Atlassian credentials that youpurchased Atlassian OnDemand with.Choose to enable Google Apps when prompted. A support ticket for your migration will then be created, and our technical support

http://www.google.com/enterprise/marketplace/viewListing?productListingId=3421+6389312883797462351


62

3.

1. 2. 3. 4.

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 bydefault.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:

Log in to your Google Apps account as administrator.Go to Advanced toolsIn the section, click .Authentication Federated Login using OpenIDSelect the check box .Allow users to sign in to third party websites using OpenID

Next: Merging OnDemand and Google Apps user bases


Overview

There are two aspects to the permission management in Atlassian OnDemand.

Licensing and authentication via . Application access controls the applications that users can log in and is forapplication accesslicensing purposes only. Giving a user access to an application means that the user will count towards that application's license.Authorisation via . Application permissions control what users can do and what data they can see within aapplication permissionsparticular application.


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 thenotifications they receive are determined by the permissions granted at the application level.

To configure what applications a user can access, i.e. licenses:


For example, user Kate Watson ( ) is a business analyst and only uses JIRA and Confluence. Grant her access tokwatsonthese two applications and then she will be able to start using them.

To configure what functions a user can use in applications:


For example, if you want to restrict user Kate Watson ( ) from creating spaces in Confluence, revoke the 'Create Space'kwatsonglobal permission from her and the groups she's in in Confluence.


63

1. 2.

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 group and this group has the read'users'access to everything. The other two default groups, i.e. and have varying permissions on top of that for the 'developers' 'administrators'

group.'users'


Default groups and permissions in Atlassian OnDemandDefault groups in Confluence OnDemand

If some users should not be able to see certain projects, then you need to:

Create groups for each separate set of users, e.g. a group for each company, or perhaps a group for each project.Edit JIRA role memberships, Confluence space permissions and Subversion permissions to use the new groups instead of thedefault groups.

For instance, say there are some contractors who should only be able to view project ' '. In this case it makes sense toTimesheet Mobile Appsplit users by company, e.g. by creating two new groups and . Add the relevant users to these groupsmycompany-users contractors(keeping all of them in the default group too). Then redesign the permissions in each application:users

JIRA — In JIRA, we want to make most projects visible only to , and one project visible to mycompany-users mycompany-usersand . For every project listed in the administration section, click the project name, find the section andcontractors Project Rolesclick "View members" and edit the "Users" role groups. Remove the group and add either or users mycompany-users

as needed.contractorsConfluence — In the application, i.e. the 'Wiki' tab ( in the administration console), go through the spaces one byConfluence notone. Click the "Browse" dropdown arrow, select "Space Admin", and then click "Permissions" to show the space permissions. Youwill see the "users" group has view permissions. Grant the group the same permissions, then delete the mycompany-users usersgroup entry. For the ' ' project, grant the group view permissions.Timesheet Mobile App contractorsSource — Manage your Subversion and FishEye permissions as described in . Go through theConfiguring repository permissionsprojects replacing instances of the group with , and in the ' ' project, users mycompany-users Timesheet Mobile App

.contractorsReviews — Project review permissions are inherited from Crucible's default permission schemes. However, they are modifiedaccording to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissionsthat 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 aproject. See in the Bamboo documentation for further details.Granting Plan Permissions to Users or Groups

It is important that you go through projects, to the group with a more specific group. The reason is that all users belong toall replace usersthe group, and any project visible to will remain visible to everyone.users users

Note that newly created users, being only in the group (the only group given the ' JIRA global permission), will not beusers JIRA Users'able to see any projects until added to or .mycompany-users contractors

Notes on restricting visibility

New users are automatically added to groups that have the global permission. By default, this is the group. Hence, in'JIRA Users' usersthe example, you cannot simply add the group to the permission. The reason is that this setting would meancontractors 'JIRA Users'that newly added contractors would be added to the group (not desired, since can see all content) and newly addedusers usersemployees would be in the group (also not desired, since they are not contractors).contractors


You can change the appearance of your Atlassian OnDemand site by using the "Look and Feel" administration page. Refer to the followinginformation 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: (Confluence documentation)Customising Look and Feel OverviewRestrictions: Note that you cannot customise the layout for Confluence OnDemand. See Restricted Functions in

for details.Atlassian OnDemand


64

1.

2. 3. 4.

5.

JIRA only

Instructions: (JIRA documentation)Customising the Look and FeelRestrictions: Note that you cannot customise the layout for Confluence OnDemand. See Restricted Functions in

for details.Atlassian OnDemand

Multiple OnDemand applications

Global customisation:

Changing the LogoConfiguring Global and Default Application TabsEditing 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 (Confluence documentation)Customising the Look and Feel

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 list of might help you select a proper image format.Wikipedia browser support for imagesThe 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 sizesautomatically.

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the option in the left menu. The look and feel configuration page will display.Look and FeelClick the link at the bottom of the page. The logo and favicon configuration page will display.Edit ConfigurationSpecify the images to be used as the logo and favicon.

To upload an image, click the icon and browse to the image.UploadTo use an existing image on the web, click the icon and enter the URL to the image.URL

Click the button to save the new image settings. Your logo will now appear on your site and the favicon will take effect asUpdatewell.

Screenshot: Changing the Logo

http://en.wikipedia.org/wiki/Favicon#Browser_support


65

1.

2. 3.

1.

2. 3. 4. 5.

Configuring Global and Default Application Tabs

You can for each of your projects. You can also configure the global tabs and default tabs for applicationscustomise the application tabstabs.

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 assignedto all new projects.


Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click the option.TabsConfigure tabs under the ' ' section and the ' ' section as needed.Global tabs Project default tabs

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.


To change your date and time formats for 'Issues' (JIRA):

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the option in the left-hand menu. The look and feel configuration page will display.Look and FeelClick the link at the bottom of the page. The page will display in editable mode.Edit ConfigurationIn the section, update the values for each of the fields you wish to change.Date/Time FormatsClick the button at the bottom of the page to save your changes. For details and examples of date and time configuration,Updaterefer to the page (JIRA documentation).Date/Time Formats

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


66

1.

2. 3. 4. 5.

6. 7.

Editing the colour scheme

You can change the colour scheme to suit your needs with the settings in the administration console. You can change theLook and Feelcolour of the header and menu (e.g. subheader) of the projects toolbar. The colour of headings and links in the 'Issues' application can becustomised as well.

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the left-hand menu, click . The look and feel configuration page will display.Look and FeelAt the bottom of the page, click the link. The logo and favicon configuration page will display.Edit ConfigurationClick to expand the look and feel configuration options.Customize Colours And DateIn the section, update the colours for the page elements by using one of the following methods. To find out where the colourColoursoptions 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.

Click the button at the bottom of the page to save your changes.UpdateRefresh the page in the browser to see the changes.

Colour scheme elements

The provides explanations for each of the colour scheme elements.JIRA documentation

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. alight-coloured arrow for dark backgrounds or a dark-coloured arrow for light backgrounds):

The , and elements only affect the appearance of pages within the Link Colour Link Archive Colour Heading Colour 'Issues'application, i.e. JIRA. They affect the other applications (e.g. 'Wiki').do not

OnDemand Cookies

OnDemand uses , an open source framework, for .Seraph HTTP cookie authentication

Authentication CookiesThe 'Remember Me' Cookie

Cookie Key and ValueUse of Cookie for AuthenticationLife of 'Remember Me' Cookies

Other cookie usage

Authentication Cookies

http://docs.atlassian.com/atlassian-seraph


67

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 userselects the checkbox on the login page.Remember me

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. OnDemandgenerates this cookie when the user selects the checkbox on the login page.Remember me

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 willmatch 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 . This is the system default value and is not configurable.14 days

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, whichtab was previously selected etc. They are:

Cookie Key Purpose Cookie Contents Expiry

atlassian.xsrf.token Prevents XSRF attacks. Ensures that during auser's session, browser requests sent to aOnDemand server originated from that OnDemandserver instance. For more information about XSRFchecking by JIRA, see onForm Token Checkingthe Atlassian Developers site.

Your OnDemand server's ServerID, a securely-generated randomstring (i.e. token) and a flag thatindicates whether or not the userwas logged in at the time thetoken was generated.

At theend ofeverysessionor whenthebrowserisclosed.

studio.project.rec.used.cookie Stores the most recently used projects. Used byOnDemand to track recently viewed projects for theuser.

The project keys of all the recentlyviewed projects. (seperated by'-_-')

Oneyearfrom thedate it isset orwas lastupdated.

AJS.conglomerate.cookie Tracks which general tabs were last used orexpansion elements were last opened or closed.

One or more key-value stringsthat indicate the states of your lastgeneral tab views or expansionelements.

Oneyearfrom thedate it isset orwas lastupdated.

Using Atlassian OnDemand

Creating LinksCreating your own dashboardManaging your profileWorking with ActivitiesWorking with Google Apps Integration

Creating Links

http://en.wikipedia.org/wiki/HTTP_cookie

https://developer.atlassian.com/display/JIRADEV/Form+Token+Handling


68

You can create links to your , , and . Once created, links enable you to quickly jump to related information.issues wiki source reviews

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 thesource file name in a text field of the issue (e.g. the 'Description' or 'Comment' field) prefixed with . The link to the source file willsource: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 forWiki Style Rendererthe 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 inpage

the same project

[<Page Name>] [My Draft Page]

a wikipage in adifferent project

[<Space Key>:<Page Name>] [TEST:My Draft Page]

a changeset

revision:<Changeset Number>

rev:<Changeset Number>

r<Changeset Number>

revision:98765

rev:98765

r98765

a sourcefile

source:<Filename> orsource:/<Filename>

The difference between the twoformats is the slash */* before the

. The slash */*<Filename>indicates that the is<Filename>an absolute path and the link willpoint to the file specified by thepath. Without the slash before

, the <Filename> <Filename>is treated as a relative path andinstead of pointing to thespecified file, OnDemandsearches for the path within aproject.

When using relative paths, i.e.without the slash, do not includethe 1st level directory in the

, for example use <Filename> insteadsource:src/Foo.java

of source:trunk/src/Foo.java. The reason is that FishEyeindexes files without the 1st leveldirectory and including the 1stlevel directory in relative pathswill lead to zero search results.

source:pom.xm

source:webapps/pom.xml

source:/branches/webapps/pom.xml

source:src/main/java/com/atlassian/util/concurrent/BlockingReference.java

source:/trunk/src/main/java/com/atlassian/util/concurrent/BlockingReference.java

a review <Review Key> CR-TEST-34567

Screenshot: Creating Links in JIRA


69

1. 2. 3.

1. 2. 3. 4.

1. 2. 3.

Related topics

Configuring cross-application linking in JIRA OnDemand

Creating your own dashboardThe Dashboard is the first screen you see when you log in to Atlassian OnDemand. Each of OnDemand applications also contains adashboard. 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:

From the main screen, select the .Dashboards > Manage DashboardsIn the top right corner of the displayed screen, select .'Manage Dashboards' Create New DashboardIn the screen, fill in the fields to create your dashboard.'Create New Dashboard'You can then continue to customise your dashboard.

To customise your dashboard:

Choose adashboard layout

At the top right corner of the dashboard, click the link. Select your required layout from the layout'Edit Layout'options presented.

Add a gadget To add a gadget:

At the top right of the dashboard, click the link.'Add Gadget'Click the button beneath your chosen gadget.'Add it now'Click the button to return to your dashboard.'Finished'If the gadget you have selected requires configuration, you will be presented with the gadget'sconfiguration 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 newposition.

Remove a gadget To remove a gadget:

Hold your mouse over the top right corner of the gadget. A down-arrow appears.Click the down-arrow to display an options menu.Click .'Delete'

Related topics

Workspace


70

1. 2. 3.

4.

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 aschanging your password. You can also set your personal preferences for individual applications.

To edit your user profile:

Click the menu labelled with your user name in the header.In the drop-down menu, click in the drop-down menu that displays. The summary for your user profile will appear.ProfileTo edit cross-application settings such as your password and timezone: click the pencil icon in the or area asDetails Preferencesneeded.To edit application-specific settings: in the top-right corner of the profile summary page, click and you will see the options forToolsthe individual applications. Note that not all options in the referenced documentation are available in OnDemand.

Issues preferencesWiki preferencesSource 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 OnDemandIn 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 thelogin 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 ' administration page. User'

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 GoogleApps and Atlassian OnDemand, and the other one is a secondary 'OnDemand' password that is used to access Subversion, RSS feeds andfor use with the Atlassian IDE Connectors. New users will be asked to set this secondary password when they first log in to AtlassianOnDemand.

These two passwords need to be changed separately as described below.

Changing your Google password as a user


71

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 gadget displays the combined activities of the applications available in Atlassian OnDemand. Example activities are theActivity Streamclosing of a Crucible review and the creation of a JIRA issue. Activity streams are also interactive information sources and provide a numberof links which you can action on, for instance you can vote on, comment on or watch issues, create reviews for changesets, and comment onConfluence pages. Depending on what the activity is about, your action will be reflected in the appropriate object (issue, changeset or wikipage/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 thedefault 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 gadgetFiltering activitiesSubscribing to activitiesCondensing 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 page ( section) of the JIRACustomising the Dashboard Adding a Gadgetdocumentation.To add a gadget to wiki pages or blog posts, refer to the page (Gadget Macro Inserting Gadgets into a Confluence Page or Blog

section ) of the Confluence documentation.Post

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

http://support.google.com/a/bin/answer.py?hl=en&answer=33319

http://support.google.com/a/bin/answer.py?hl=en&answer=33319


72

1. 2.

1. 2.

display specific events.

Before you beginYou can only filter activities for the Activity Stream gadgets that are added by yourself.

Procedure

Click the button in the top right corner of the activity stream area.FilterModify the settings as needed, for example specifying the title that you want to display on your gadget, enter the maximum ofactivities 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 certainapplication 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 examplefor and filters, directly enter the value or multiple values separated by commas. For the filters whoseusername issue keyvalues are available in the form of lists such as and filters, just select a value or multiple values by holdingProject Activitydown 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:

Click the symbol in the top right corner of the activity stream area.RSSSelect 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 optionssuch 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:

OverviewLogging InLogging Out

Audience: Users


73

1. 2. 3.

Overview

When you use Atlassian OnDemand with Google Apps Integration, you need to manage your login status in both of these systems. Whenyou log in to Google Apps, you access your Google email, calendar, and documents. The Google Apps Marketplace offers products andservices designed to integrate with your Google Apps. As a separately licensed product, Atlassian OnDemand integrates with Google Appsand you can access Google products such as via the ), but has a different login to your Google Apps.Activity Bar

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 needto log in with the login details provided by your OnDemand administrator.

To log in without a Google Apps account:

From the ' ' drop-down, select the option.Log In Log in directlyAt the dialog, enter the login details provided by your administrator.Log in using your Atlassian OnDemandClick the button to start using Atlassian OnDemand.Log In

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 Subversionpassword. These two passwords are managed separately in Google Apps and OnDemand respectively.

However, you can access Subversion with the same Google Apps password.The you log in via Google Apps, you will be promptedfirst timeto set your password for and RSS feeds. Just specify the same password as your Google credentials and then you will be able toSubversionuse 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 stilllogged in to Google Apps, you can return to OnDemand without entering your password. As a security measure, the system will prompt youto 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


74

1. 2.

3.

4.

Click ' ' from the Google Apps interface.Log out

2. Log out of Atlassian OnDemand

Click ' ' from the Atlassian OnDemand.Log Out

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 BarAttaching Google Docs to issuesAttaching Google Docs to wiki pagesAttaching 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:

Create or open the desired JIRA issue.Click the ' ' link. The ' window appears. Type text into the ' ' field to searchAttach Google Docs Google Docs Picker' Title Containsfor a document, and you can restrict the documents displayed by selecting an option from the ' ' drop-down menu.Doc TypeTo select the document(s) you want to attach, check the box next to the document file name and click 'Attach Selected Documents'.You will be returned to the view issue page. The attached documents will appear as a list in the ' ' section.Google Documents

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 willonly 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 JIRAissue.

Screenshot: Google Docs Picker


75

1. 2. 3. 4. 5.

6.

1. 2.

Attaching Google Docs to wiki pages

To do this:

In the editing mode of a page, place the text cursor where you would like to insert the Google Document.In the toolbar, click > . The 'Select Macro' dialog appears.Insert Other MacrosIn the search box at the top right of the dialog, type . The Google Docs macros will appear in the list.GoogleSelect 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, themacro will appear in the editor window looking like the following:

{gdocument:docid=0AV1fqMj98CsNZGhodHN6NXhfNGR3bmZ4cGY1|height=100%}

Click on the wiki page. After the page is saved, you will be able to read the document in the wiki page. An ' ' link will appearSave Editbeneath 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

In the editing mode of a page, use the ' ' macro to display a list of Google documents on a wiki page. Google Documents ListAfter saving the page, you will see the document list in the wiki page.

Screenshot: List of Google Docs in a Confluence wiki page


76

2.

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 OnDemandAdding a Google Calendar event from OnDemandRemoving an event from Google CalendarRelated topics

Viewing upcoming Google Calendar events from OnDemand

Clicking the Google Calendar button on the Activity Bar will show a list of upcoming events. Click any link to open the event in GoogleCalendar.

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 in the cornerof the dialog. A form field opens, where you can simply type the event details in then click ' ', as in this example:Create

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: Adding a Google Calendar event from the Activity Bar


77

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 on the Activity Bar, then clicking ' '. GoogleSee MoreCalendar will launch in a new browser window.

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 . ThisActivity Barfeature 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. ) will only see and be able to access OnDemand features:external users

Recent ActivityRecent IssuesFavourite PagesRecent BuildsOutstanding 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 ActivityRecent IssuesFavourite PagesRecent BuildsOutstanding ReviewsGmail MessagesGoogle Calendar EventsGoogle DocsGoogle Sites

Screenshot: The Activity Bar


78

1.

1.

1.

2.

1.

Viewing Recent Activity with the Activity Bar

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

Click the issues button on the Activity Bar.

Screenshot: Recent Issues in the Activity Bar

To add an issue via the Activity Bar:

Click the issues button on the Activity Bar.

Click the plus sign icon in the corner of the dialogue. A dialogue box will be displayed.

See for more information about JIRA issues.Working with Issues

Viewing Favourite Pages with the Activity Bar

Click the wiki favourite button on the Activity Bar. A short list of Confluence wiki pages that you have selected as favouriteswill be displayed.

Screenshot: Favourite pages in the Activity Bar

See for more information about using Confluence wiki pages.Working with the Wiki


79

1.

1.

1.

Viewing Recent Builds with the Activity Ba

Click builds button on the Activity Bar.

Screenshot: List of recent build activity on the Activity Bar

See for more information about using Bamboo builds in OnDemand.Working with Builds

Viewing Outstanding Reviews with the Activity Bar

Click the reviews button on the Activity Bar. A list of outstanding reviews that you are involved in will be displayed. A number

in a red star superimposed over the button shows how many new reviews you have.

Screenshot: List of outstanding reviews on the Activity Bar

See for more information about using Crucible reviews.Working with Reviews

Viewing Gmail Messages with the Activity Bar

Click the Gmail button on the Activity Bar. A red number on the chatbar icon shows how many unread messages arewaiting in Gmail.

Screenshot: List of unread Gmail messages on the Activity Bar


80

1.

1.

Viewing Upcoming Google Calendar Events with the Activity Bar

Click the Google Calendar button on the Activity Bar. A list of upcoming events will be displayed.


See for more detail on how Google Calendar integrates with OnDemand.Using Google Calendar with Google Apps Integration

Viewing Google Docs with the Activity Bar

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 for more detail on how Google Docs integrates with OnDemand.Using Google Docs with Google Apps Integration

Launching Google Sites from the Activity Bar


81

1.

To launch Google Sites from the Activity Bar:

Click the Google Sites button on the Activity Bar. Google Sites will be launched in a new web browser window. You will beautomatically logged in with your Google ID.

Screenshot: Google Sites, launched by the Activity Bar

JIRA OnDemandJIRA 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 OnDemandapplications, 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


Important information

Please note the following important information before you begin using JIRA OnDemand:

Some functions in JIRA OnDemand are for security reasons. Read more about restricted 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 provided by Atlassian. See the commercial add-ons Atlassian for instructions on how to order these add-ons. The following add-ons are available:OnDemand Plugin Policy

GreenHopper is an agile project management tool that helps you manage JIRA issues in an agile environment.

http://www.atlassian.com/software/jira/



82

Check out the Got GreenHopper? GreenHopper documentation.Bonfire is an agile testing tool that allows you to report JIRA bugs directly from the web application being tested.

Check out the Got Bonfire? 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 toreturn to the OnDemand documentation, if you are directed to the documentation for downloadable JIRA.

Key topics

Administering IssuesAdministration console differencesJIRA Administrator's GuideEnabling sub-tasks for a projectConfiguring JIRA PluginsLinking a bitbucket or GitHub repository with JIRA OnDemandIntegrating Flowdock with JIRA OnDemandConnecting Zephyr with JIRA OnDemandConfiguring Cloud Connectors in JIRA OnDemand

Working with IssuesJIRA User's GuideCreating an issueManaging agile projectsCreating issue comments via emails

Administering IssuesJIRA OnDemand, i.e. the application, is based on JIRA. The administration of JIRA OnDemand is mostly the same as that ofIssuesdownloadable JIRA except the functions specific to JIRA OnDemand indicated below and certain restrictions due to security considerations.

An can represent whatever you need it to: a software bug, a development task, a documentation task, etc.issue

Every issue belongs to a .JIRA project


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 page.navigation differences between JIRA OnDemand and JIRA

http://www.atlassian.com/en/software/bonfire


83

1.

2.

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 ' administration tab in the administration console.'Issues

To access the Issues tab in the administration console:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues administration console will display (see screenshot on the right).Issues

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 administrationsection above.

Screenshot: Administering Issues (click to view larger image)

Appendix – Administration options in the Issues applicationThe following table lists the administration options in the application.Issues

Category Functions

GeneralConfiguration

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 * — Manage system-wide permissions (granted to groups of users).Global Permissions* — Manage the default settings for user profiles.User Preferences* — Define and assign project roles.Roles


84

Issue Types * — Add, edit and delete issue types as well as configure issue type schemes and translationsIssue Types(internationalisation).* — Manage sub-task settings for issues.Sub-Tasks

Workflows * — Manage workflows for your projects.Workflows* — Manage workflow schemes for your projects.Workflow Schemes

Screens * — Configure screens, i.e. which fields are displayed on a screen.Screens* — Configure screen schemes to determine which screen is displayed to a user for a particular issueScreen Schemesoperation.* — Manage the screen schemes that apply to issue types.Issue Type Screen Schemes

Fields * — Add, configure and delete your custom fields.Custom Fields* — Configure field behaviour, such as field description, visibility, whether it is enabled, etc.Field Configurations* — Manage field configuration schemes to apply field configurations to issue types.Field Configuration Schemes

IssueAttributes

* — Add, edit and delete issue statuses (used on workflows) as well as configure translationsStatuses(internationalisation) for statuses. * — Add, edit and delete issue resolutions as well as configure translations (internationalisation) forResolutionsresolutions.* — Add, edit and delete issue priorities as well as configure translations (internationalisation) for priorities.Priorities

IssueFeatures

* — Manage time tracking (i.e. logging work) settings for issues. Time Tracking is by default. Read Time Tracking ON (JIRA documentation) about how to configure the settings.Configuring Time Tracking

* — Manage issue links (e.g. an issue may on another issue). This is separate to .Issue Linking depend creating links

GreenHopper * — Configure general GreenHopper settings.General Configuration* — Manage project templates, e.g. editing a template or creating a new one. Project Templates* — Enable or disable a project to use GreenHopper.Enabled Projects* — Manage the license for the GreenHopper plugin.License Details

System Info Display the system information for your JIRA application.

UserInterfaces

* — Configure the default dashboard for your site.System Dashboard* — Configure the navigator columns (used to display results when searching for issues)Navigator Columns* — Set an HTML announcement that will appear as a system-wide banner.Announcement Banner

Mail * — Manage the JIRA event queue. You have the option of flushing the mail queue to send mailsMail Queueimmediately. * — Send an email to selected JIRA user groups or project roles.Send E-mail

Misc.Schemes

* — Manage issue security levels and schemes for your projects (i.e. who can individualIssue Security Schemesissues in a project).* — Manage notification schemes for your projects (i.e. emails notifications for events during anNotification Schemesissue lifecycle).* — Manage permission schemes for each of your projects.Permission Schemes

Advanced * — Re-index the JIRA application.Indexing* — Configure file attachment settings.Attachments* — Add, remove and configure events as well as the notification schemes and workflows that they apply to.Events* — Use scheme tools evolve your schemes from user-based to role-base, and rationalise yourScheme Toolsschemes.

Tempo Disable and enable Tempo, manage the license and configure the various settings.

Plugins * — Enable, disable and configure JIRA plugins. For instructions of how to do this, refer to the Plugins Configuring JIRA page. Plugins

* — Configure the OAuth settings if you associate private GitHub repositories with JIRAGitHub OAuth Settingsprojects. * — Associate GitHub repositories with JIRA OnDemand or manage existingBulk Configure GitHub Repositoriesones. * — Associate Bitbucket repositories with JIRA OnDemand or manage existing ones. Bitbucket* — Manage the license for the Gliffy plugin.Gliffy JIRA Plugin* — Manage the license for Balsamiq. Balsamiq Mockups License

CloudConnectors

Manage the license and configure the various settings. For instructions of how to configure them, refer to Configuring.CustomWare connectors in JIRA OnDemand

http://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking


85

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 , please note that the instructions on how to navigate to a specific administrationJIRA Administrator's Guideoption 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 anywhere in Atlassian OnDemand to bring upg + gthe box, in which you can search for menus you want to work with. Administration Search

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


86

Related topics


JIRA Administrator's Guide

Atlassian OnDemand includes for issue tracking. Use the search or click any of the links below to view the relevant page in theJIRA 5.0JIRA 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 FeelChoosing a Default LanguageConfiguring the Default Issue NavigatorConfiguring the Default Dashboard

Using Dashboard GadgetsConfiguring an Announcement BannerEnabling Logout Confirmation

User and Group Management

Managing UsersManaging GroupsManaging Project RolesMigrating User Groups to Project RolesClearing 'Remember my login' Tokens

http://confluence.atlassian.com/display/JIRA/Getting+Help

http://confluence.atlassian.com/display/JIRA/Configuring+the+Layout+and+Design

http://confluence.atlassian.com/display/JIRA/Customising+the+Look+and+Feel

http://confluence.atlassian.com/display/JIRA/Choosing+a+Default+Language

http://confluence.atlassian.com/display/JIRA/Configuring+the+Default+Issue+Navigator

http://confluence.atlassian.com/display/JIRA/Configuring+the+Default+Dashboard

http://confluence.atlassian.com/display/JIRA/Using+Dashboard+Gadgets

http://confluence.atlassian.com/display/JIRA/Configuring+an+Announcement+Banner

http://confluence.atlassian.com/display/JIRA/Enabling+Logout+Confirmation

http://confluence.atlassian.com/display/JIRA/User+and+Group+Management

http://confluence.atlassian.com/display/JIRA/Managing+Users

http://confluence.atlassian.com/display/JIRA/Managing+Groups

http://confluence.atlassian.com/display/JIRA/Managing+Project+Roles

http://confluence.atlassian.com/display/JIRA/Migrating+User+Groups+to+Project+Roles

http://confluence.atlassian.com/display/JIRA/Clearing+%27Remember+my+login%27+Tokens


87

Disabling Remember My Login on this ComputerEnabling Public Signup and CAPTCHA

Project Management

Defining a ProjectManaging Project Role MembershipDefining a ComponentManaging Versions

Running a Bamboo Build when Releasing a VersionCreating Release Notes

Configuring Project Keys

Configuring Security

Configuring Issue Level SecurityManaging Project PermissionsManaging Global Permissions

Configuring Fields and Screens

Configuring Built-in FieldsDefining 'Issue Type' Field Values

Associating Issue Types with ProjectsDefining 'Priority' Field ValuesDefining 'Resolution' Field ValuesDefining 'Status' Field Values

Adding a Custom FieldConfiguring a Custom FieldCreating Help for a Custom Field

Specifying Field BehaviourAssociating Field Behaviour with Issue TypesConfiguring Renderers

Defining a ScreenAssociating a Screen with an Issue OperationAssociating a Screen with an Issue Type

Configuring Workflow

Activating WorkflowAdding a Custom EventConfiguring the Initial StatusWorkflow Properties

Configuring Email

Configuring Email NotificationsCreating a Notification SchemeCustomising Email Content

Creating Issues and Comments from Email — JIRA OnDemand includes a mail service configured to create issue comments fromreplies to JIRA notifications. Setting up a JIRA service to create issues and comments from an external POP/IMAP server is notcurrently supported.

Moving or Archiving Individual Projects

Archiving a Project — For offline archiving, Atlassian support will assist with generating a usable XML backups for downloadableJIRA, 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 TrackingConfiguring JIRA Options — gzip is always set to off.Setting Properties and Options on Startup

Recognized System Properties for JIRAConfiguring File Attachments — Attachments enabled by default, maximum size set to 100MB.Configuring Issue CloningConfiguring Issue LinkingConfiguring Sub-tasksManaging Shared FiltersManaging Shared Dashboards

Server Administration

http://confluence.atlassian.com/display/JIRA/Disabling+Remember+My+Login+on+this+Computer

http://confluence.atlassian.com/display/JIRA/Enabling+Public+Signup+and+CAPTCHA

http://confluence.atlassian.com/display/JIRA/Project+Management

http://confluence.atlassian.com/display/JIRA/Defining+a+Project

http://confluence.atlassian.com/display/JIRA/Managing+Project+Role+Membership

http://confluence.atlassian.com/display/JIRA/Defining+a+Component

http://confluence.atlassian.com/display/JIRA/Managing+Versions

http://confluence.atlassian.com/display/JIRA/Running+a+Bamboo+Build+when+Releasing+a+Version

http://confluence.atlassian.com/display/JIRA/Creating+Release+Notes

http://confluence.atlassian.com/display/JIRA/Configuring+Project+Keys

http://confluence.atlassian.com/display/JIRA/Configuring+Security

http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Level+Security

http://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

http://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions

http://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens

http://confluence.atlassian.com/display/JIRA/Configuring+Built-in+Fields

http://confluence.atlassian.com/display/JIRA/Defining+%27Issue+Type%27+Field+Values

http://confluence.atlassian.com/display/JIRA/Associating+Issue+Types+with+Projects

http://confluence.atlassian.com/display/JIRA/Defining+%27Priority%27+Field+Values

http://confluence.atlassian.com/display/JIRA/Defining+%27Resolution%27+Field+Values

http://confluence.atlassian.com/display/JIRA/Defining+%27Status%27+Field+Values

http://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Field

http://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Field

http://confluence.atlassian.com/display/JIRA/Creating+Help+for+a+Custom+Field

http://confluence.atlassian.com/display/JIRA/Specifying+Field+Behaviour

http://confluence.atlassian.com/display/JIRA/Associating+Field+Behaviour+with+Issue+Types

http://confluence.atlassian.com/display/JIRA/Configuring+Renderers

http://confluence.atlassian.com/display/JIRA/Defining+a+Screen

http://confluence.atlassian.com/display/JIRA/Associating+a+Screen+with+an+Issue+Operation

http://confluence.atlassian.com/display/JIRA/Associating+a+Screen+with+an+Issue+Type

http://confluence.atlassian.com/display/JIRA/Configuring+Workflow

http://confluence.atlassian.com/display/JIRA/Activating+Workflow

http://confluence.atlassian.com/display/JIRA/Adding+a+Custom+Event

http://confluence.atlassian.com/display/JIRA/Configuring+the+Initial+Status

http://confluence.atlassian.com/display/JIRA/Workflow+Properties

http://confluence.atlassian.com/display/JIRA/Configuring+Email

http://confluence.atlassian.com/display/JIRA/Configuring+Email+Notifications

http://confluence.atlassian.com/display/JIRA/Creating+a+Notification+Scheme

http://confluence.atlassian.com/display/JIRA/Customising+Email+Content

http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+to+Receive+Email+from+a+POP+or+IMAP+Mail+Server

http://confluence.atlassian.com/display/JIRA/Moving+or+Archiving+Individual+Projects

http://confluence.atlassian.com/display/JIRA/Archiving+a+Project

https://support.atlassian.com/

http://confluence.atlassian.com/display/JIRA/Integrating+with+a+Build+Management+System

http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Bamboo

http://confluence.atlassian.com/display/JIRA/Configuring+Global+Settings

http://confluence.atlassian.com/display/JIRA/Configuring+Time+Tracking

http://confluence.atlassian.com/display/JIRA/Configuring+JIRA+Options

http://confluence.atlassian.com/display/JIRA/Setting+Properties+and+Options+on+Startup

http://confluence.atlassian.com/display/JIRA/Recognized+System+Properties+for+JIRA

http://confluence.atlassian.com/display/JIRA/Configuring+File+Attachments

http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Cloning

http://confluence.atlassian.com/display/JIRA/Configuring+Issue+Linking

http://confluence.atlassian.com/display/JIRA/Configuring+Sub-tasks

http://confluence.atlassian.com/display/JIRA/Managing+Shared+Filters

http://confluence.atlassian.com/display/JIRA/Managing+Shared+Dashboards

http://confluence.atlassian.com/display/JIRA/Server+Administration


88

1.

1. 2. 3. 4.

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:

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 that yourissue type schemeproject is associated with.

To do this:

In the administration console, go to > > .The 'Manage Issue Types' page displays.Issues Issue Types Issue TypesGo to the tab and locate your project.Issue Types SchemeIn the column of your project, click the link.Operations EditAdd 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 thatoffer configuration options.

Restriction: You can only enable or disable the bundled plugins in Atlassian OnDemand and cannot install or remove any plugins. Formore information, please read the .Atlassian OnDemand Plugin Policy


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. Theseplugins 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 AtlassianOnDemand. 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.

http://confluence.atlassian.com/display/JIRA/Search+Indexing

http://confluence.atlassian.com/display/JIRA/Viewing+your+System+Information

http://confluence.atlassian.com/display/JIRA/Appendix+A+-+Extending+JIRA

http://confluence.atlassian.com/display/JIRA/Managing+JIRA%27s+Plugins


89

1.

2. 3.

1. 2. 3. 4.

1.

2. 3.

1. 2. 3. 4.

1.

2. 3.

1.

Related topics

Configuring Confluence Plugins


You can enable and disable JIRA plugins in your Atlassian OnDemand site. With the Safe Mode, you can disable all user-installed plugins inyour site with one click, which might help you diagnose plugin-related problems more easily.


On this page:

Disabling a pluginEnabling a pluginDisabling 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:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Issues (JIRA) administration console will display.IssuesIn the left-hand menu, click . The will appear and display the plugins installed.Plugins > Plugins Universal Plugin Manager

To disable a JIRA plugin:

Click the tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon: Manage ExistingLocate the plugin that you want to disable and click the title to expand the plugin details section.Click the button.DisableOnce a plugin has been disabled, you need to restart your application for your change to take effect. If so, you will see amaymessage for the plugin, .Disabled, requires restartOnce the plugin is fully disabled, you will see an link for the plugin.Enable

Enabling a plugin



To enable a JIRA plugin:

Click the tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon: Manage ExistingLocate the plugin that you want to enable and click the title to expand the plugin details section.Click the button.EnableOnce a plugin has been enabled, you need to restart your application for your change to take effect. If so, you will see amaymessage for the plugin, .Enabled, requires restartOnce the plugin is fully disabled, you will see a link for the plugin.Disable

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 youentered Safe Mode will be re-enabled when you exit Safe Mode.



To enable Safe Mode:

Click the tab. Manage Existing


90

1.

2. 3.

4.

5.

1.

2. 3.

The system displays a list the installed plugins.Click the link.Enable Safe ModeClick the button in the confirmation window. ContinueAll user installed plugins will be disabled and your application will now be running in safe mode.Make changes to your installed plugins as desired. For example, you may want to enable/disable specific plugins or plugin modules.Exit safe mode by clicking one of the links in the Safe Mode banner:

Click to restore your plugin configuration to its state before youExit Safe Mode and restore the previous configurationentered Safe Mode.Click to keep all changes made to your plugin configuration duringExit Safe Mode and keep the current configurationSafe Mode.

Viewing your JIRA Plugins

This page explains how to view the JIRA plugins and their details in Atlassian OnDemand.


Viewing JIRA plugins



To view JIRA plugins:

Click the tab to list the plugins installed in your application. The application groups plugins into andManage Existing User-installed Plugins. The are hidden by default. Use the following actions when working with the plugin list:System Plugins System Plugins

Enter keywords in the text box to filter the list.Filter visible pluginsClick the link to see the hidden system plugins.Show System PluginsClick the name of a plugin to view the plugins details.Click to run your application in safe mode. This mode disables all user installed plugins.Enable Safe Mode

Enabled plugins have this icon , and this icon indicates disabled plugins.



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 theplugin 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 theplugin. This link will only appear if the plugin has modules. If you want to enable or disable a plugin module, hover your mouse overthe module and click the ' '/' ' button for that module.Enable DisablePlugin details – Click this link to display the plugin information on the .Atlassian Plugin ExchangeConfigure – Click this link to display the configuration settings for the plugin in the Universal Plugin Manager. This link will bedisabled if the plugin is disabled. Please note that not all plugins have settings that can be configured through the Universal PluginManager.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

http://plugins.atlassian.com


91

1.

2. 3.

1.

2. 3.


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 pluginsand the users who made the changes.



To view the plugin audit log:

Click the tab. Audit LogThe plugin audit log appears with a list of the 25 most recent entries.Use the arrows if you want to view older entries.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 pluginidentifies DVCS commit messages that reference a specific JIRA issue key and records the commit in JIRA. The information appears in theissue's and section. The plugin records the commit message, the list of changed files, and provides links to view theActivity Commitschange set.

JIRA requires that a connected repository provide a POST service. The POST service allows JIRA to hook into a source code commit andobtain 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 withadministrative access to the repository.

On this page:

Prequisite for GitHub private repositoriesProceduresExample of how commit information appears in a projectUsing with Force Sync operations to troubleshoot


92

1. 2.

3. 4.

1. 2.

3.

1. 2.

3.

4.

5.

6.

Prequisite for GitHub private repositories

If you are planning on connecting to GitHub repositories, you must configure OAuth settings for GitHub before connecting to yourprivaterepos. To configure the OAuth settings, do the following:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.AdministratorOpen the tab and click .Issues Source Control > GitHub OAuth SettingsFollow 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:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.AdministratorOpen the tab and click . Issues Source Control > Bitbucket and and GitHub RepositoriesThe page appears. The page lists . Each repository entry includes theBulk Configure Repositories Existing Linked Repositoriesrepository URL and its corresponding project key.

To add a repository to this list, scroll down past the list to the blue form.

Click and select the JIRA project you want to link the repository to.Choose projectEnter the URL of the hosted repository.JIRA uses the HTTPS protocol to connect to the repository.Click the button.Add Repository JIRA verifies it can connect to the repository. If the repository you specified is private, JIRA prompts you for a valid username/password to connect to the repository.

Check .Install postcommit service

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.

If you do not enable the postcommit serviceat this point, you must ensure that the service is enabledthrough thehosted service. For information on enablinga post service on bitbucket, see Setting Up the bitbucket

.POST Service



The system informs prompts you to authorize the connection:

Press .Allow

Your repository appears in the the page.Bulk Configure Repositories

Ensure your project users have the correct permissions

Project users must all have permissions. Without the proper permissions, users can not see the View Version Control tab even on linked projects.Bitbucket

Automatic synchronisation


93

After you link a repository, JIRA automatically starts looking for commits that reference issue keys for the associated JIRA project. Thesummary 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 tab of the DVCS-2 issueActivity


Using with Force Sync operations to troubleshoot


94

1. 2.

3.

4. 5.

1. 2.

3.

4.

1.

2. 3.

If you see inconsistencies between the displayed commits in JIRA and the actual activity in your repository, you should run a Force Syncoperation. The operation compares the existing commit data in JIRA with that in the linked repository. The system restores anyForce Syncmissing commit data to JIRA. A forced synchronization does not affect the commits in hosted DVCS. You should run operationsForce Syncwhen:

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, youmust wait for service to send the data.

To run a Force Sync operation:

Log in a user with access to your JIRA instance.administratorChoose > from the dashboard menu.username AdministrationThe page appears.AdministratorOpen the Issues tab and click . Source Control > Bitbucket and and GitHub RepositoriesThe page appears. The page lists .Bulk Configure Repositories Existing Linked RepositoriesLocate the repository that you want to synchronise.Click the link. Force SyncA synchronisation starts. After the synchronisation is complete, a summary for the synchronisation displays under the repositorylisting in JIRA.

Related topics

Setting Up the bitbucket POST Service

Post-Receive Hooks

Integrating Flowdock with JIRA OnDemand

You can integrate with JIRA OnDemand and issues from your JIRA projects will be included in your Flowdock flows.Flowdock

Procedure

Before you begin:

If you link a JIRA project to a Flowdock flow, regardless of the restriction level that isall JIRA comments will appear on FlowDockset when creating the comment. Please ensure that you only link JIRA projects to Flowdock flows when it is acceptable for all JIRAcomments to be visible.

To integrate Flowdock:

Log in as an administrator, and go to tab on the left menu.Administration > Issues > PluginsIn the section, click . Then locate , and click . The FlowdockSystem Plugins Show System Plugins Flowdock for JIRA Configureintegration page will display all JIRA projects set up in OnDemand.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 page. Your API key will beIntegrating with variety of issue trackersdisplayed in the JIRA instructions.Click . The API key information will be saved and the Flowdock integration page will refresh.Save

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:

Log in as an administrator, and go to tab . The plugin section is expanded and you will see theAdministration >Issues > Pluginslist of user-installed plugins.Near the bottom of the page, locate the and click it to display the available options.Zephyr RPC JIRA PluginClick . The Zephyr plugin will be enabled. Enable

Related topics

http://www.getzephyr.com/buy/index.phphttps://plugins.atlassian.com/plugin/details/18715

http://help.github.com/post-receive-hooks/

https://www.flowdock.com/

https://www.flowdock.com/help/issue_trackers

http://www.getzephyr.com/buy/index.php

https://plugins.atlassian.com/plugin/details/18715


95

1. 2. 3.

Configuring Cloud Connectors in JIRA OnDemandBefore you being

Make sure that the is set to .This setting is ON by default.Accept Remote API calls ON

To locate the option:

Go to . The General Configuration page displays.Administration > Issues > General ConfigurationAt the bottom of the page, click . The fields on the General Configuration page become editable.Edit ConfigurationFind the setting In the section.Accept Remote API calls Options

Configuring the connectors

Accessing the Connectors configuration settings:

JIRA OnDemand only: Administration > PluginsMultiple 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+GuideSalesforce.com: http://wiki.customware.net/repository/display/SFJIRA4/Administrators+GuideSource Labs: http://wiki.customware.net/repository/display/SLJIRA/Administrators+GuideuTest: http://wiki.customware.net/repository/display/UTJIRA/Administrators+Guide#AdministratorsGuide-ConfigurationZendesk: 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 installationinstructions in the referenced documentation are for downloadable JIRA. Similarly, you do not need to configure application links either.

Working with IssuesJIRA OnDemand, i.e. the application, is based on JIRA. Besides the functionality that is available in downloadable JIRA, JIRAIssuesOnDemand offers functions that are specific in OnDemand.



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 additionalfeatures:

http://wiki.customware.net/repository/display/GSJIRA/Administrators+Guide

http://wiki.customware.net/repository/display/SFJIRA4/Administrators+Guide

http://wiki.customware.net/repository/display/SLJIRA/Administrators+Guide

http://wiki.customware.net/repository/display/UTJIRA/Administrators+Guide#AdministratorsGuide-Configuration

http://wiki.customware.net/repository/display/ZDJIRA/Home


96

1.

GreenHopper User's GuideBonfire User GuideBalsamiq Mockups for JIRA User Guide

Accessing the Issues application

To work on issues, e.g. creating issues and searching for issues, use the ' application. This is also the place for using JIRA add-ons’Issuessuch as GreenHopper and Bonfire.

To access the Issues application:

Click the ' ' tab in the navigation bar. This takes you to JIRA.Issues

Screenshot: Example Issues dashboard (click to enlarge image)

JIRA User's Guide

Atlassian OnDemand includes for issue tracking. Use the search or click any of the links below to view the relevant page in theJIRA 5.0JIRA 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 ProjectWhat is WorkflowWhat is an Issue

Getting Started

Logging in to JIRAExploring the JIRA WorkspaceUsing Keyboard Shortcuts

http://support.balsamiq.com/customer/portal/articles/113842-mockups-for-jira-user-guide

http://confluence.atlassian.com/display/JIRA/JIRA+Concepts

http://confluence.atlassian.com/display/JIRA/What+is+a+Project

http://confluence.atlassian.com/display/JIRA/What+is+Workflow

http://confluence.atlassian.com/display/JIRA/What+is+an+Issue

http://confluence.atlassian.com/display/JIRA/Getting+Started

http://confluence.atlassian.com/display/JIRA/Logging+in+to+JIRA

http://confluence.atlassian.com/display/JIRA/Exploring+the+JIRA+Workspace

http://confluence.atlassian.com/display/JIRA/Using+Keyboard+Shortcuts


97

Working with Issues

Attaching a FileAttaching a ScreenshotCloning an IssueCommenting on an IssueCreating an IssueCreating a Sub-TaskEditing an IssueEditing Rich-Text FieldsEmailing an IssueLabelling an IssueLinking IssuesLogging Work on an IssueModifying Multiple ('Bulk') IssuesMoving an IssueScheduling an IssueSetting Security on an IssueViewing an Issue's Change HistoryViewing an Issue's Crucible ReviewsViewing an Issue's FishEye ChangesetsViewing the Bamboo Builds related to an IssueWatching and Voting on an Issue

Searching for Issues

Using Quick SearchPerforming Text SearchesAdvanced SearchingUsing the Issue NavigatorCustomising your Issue NavigatorSaving Searches ('Issue Filters')Receiving Search Results as an RSS FeedExporting Search Results to Microsoft WordExporting Search Results to Microsoft ExcelDisplaying Search Results as a ChartDisplaying Search Results in XMLReceiving Search Results via EmailEmailing a Search Result

Generating Reports

Workload Pie Chart ReportUser Workload ReportVersion Workload ReportTime Tracking ReportSingle Level Group By ReportCreated vs Resolved Issues ReportResolution Time ReportPie Chart ReportAverage Age ReportRecently Created Issues ReportTime Since Issues Report

Browsing a Project

Browsing a Project's SummaryBrowsing a Project's IssuesBrowsing a Project's Road MapBrowsing a Project's Change LogBrowsing a Project's Popular IssuesBrowsing a Project's Versions

Browsing a Version's SummaryBrowsing a Version's IssuesBrowsing a Version's Popular IssuesBrowsing a Version's Bamboo Builds

Browsing a Project's ComponentsBrowsing a Component's SummaryBrowsing a Component's IssuesBrowsing a Component's Road MapBrowsing a Component's Change LogBrowsing a Component's Popular Issues

Browsing a Project's LabelsBrowsing a Project's Bamboo BuildsBrowsing a Project's FishEye ChangesetsBrowsing a Project's Crucible ReviewsViewing a Project's Burndown Chart

Customising the Dashboard

http://confluence.atlassian.com/display/JIRA/Working+with+Issues

http://confluence.atlassian.com/display/JIRA/Attaching+a+File

http://confluence.atlassian.com/display/JIRA/Attaching+a+Screenshot

http://confluence.atlassian.com/display/JIRA/Cloning+an+Issue

http://confluence.atlassian.com/display/JIRA/Commenting+on+an+Issue

http://confluence.atlassian.com/display/JIRA/Creating+an+Issue

http://confluence.atlassian.com/display/JIRA/Creating+a+Sub-Task

http://confluence.atlassian.com/display/JIRA/Editing+an+Issue

http://confluence.atlassian.com/display/JIRA/Editing+Rich-Text+Fields

http://confluence.atlassian.com/display/JIRA/Emailing+an+Issue

http://confluence.atlassian.com/display/JIRA/Labelling+an+Issue

http://confluence.atlassian.com/display/JIRA/Linking+Issues

http://confluence.atlassian.com/display/JIRA/Logging+Work+on+an+Issue

http://confluence.atlassian.com/display/JIRA/Modifying+Multiple+%28%27Bulk%27%29+Issues

http://confluence.atlassian.com/display/JIRA/Moving+an+Issue

http://confluence.atlassian.com/display/JIRA/Scheduling+an+Issue

http://confluence.atlassian.com/display/JIRA/Setting+Security+on+an+Issue

http://confluence.atlassian.com/display/JIRA/Viewing+an+Issue%27s+Change+History

http://confluence.atlassian.com/display/JIRA/Viewing+an+Issue%27s+Crucible+Reviews

http://confluence.atlassian.com/display/JIRA/Viewing+an+Issue%27s+FishEye+Changesets

http://confluence.atlassian.com/display/JIRA/Viewing+the+Bamboo+Builds+related+to+an+Issue

http://confluence.atlassian.com/display/JIRA/Watching+and+Voting+on+an+Issue

http://confluence.atlassian.com/display/JIRA/Searching+for+Issues

http://confluence.atlassian.com/display/JIRA/Using+Quick+Search

http://confluence.atlassian.com/display/JIRA/Performing+Text+Searches

http://confluence.atlassian.com/display/JIRA/Advanced+Searching

http://confluence.atlassian.com/display/JIRA/Using+the+Issue+Navigator

http://confluence.atlassian.com/display/JIRA/Customising+your+Issue+Navigator

http://confluence.atlassian.com/pages/viewpage.action?pageId=185729481

http://confluence.atlassian.com/display/JIRA/Receiving+Search+Results+as+an+RSS+Feed

http://confluence.atlassian.com/display/JIRA/Exporting+Search+Results+to+Microsoft+Word

http://confluence.atlassian.com/display/JIRA/Exporting+Search+Results+to+Microsoft+Excel

http://confluence.atlassian.com/display/JIRA/Displaying+Search+Results+as+a+Chart

http://confluence.atlassian.com/display/JIRA/Displaying+Search+Results+in+XML

http://confluence.atlassian.com/display/JIRA/Receiving+Search+Results+via+Email

http://confluence.atlassian.com/display/JIRA/Emailing+a+Search+Result

http://confluence.atlassian.com/display/JIRA/Generating+Reports

http://confluence.atlassian.com/display/JIRA/Workload+Pie+Chart+Report

http://confluence.atlassian.com/display/JIRA/User+Workload+Report

http://confluence.atlassian.com/display/JIRA/Version+Workload+Report

http://confluence.atlassian.com/display/JIRA/Time+Tracking+Report

http://confluence.atlassian.com/display/JIRA/Single+Level+Group+By+Report

http://confluence.atlassian.com/display/JIRA/Created+vs+Resolved+Issues+Report

http://confluence.atlassian.com/display/JIRA/Resolution+Time+Report

http://confluence.atlassian.com/display/JIRA/Pie+Chart+Report

http://confluence.atlassian.com/display/JIRA/Average+Age+Report

http://confluence.atlassian.com/display/JIRA/Recently+Created+Issues+Report

http://confluence.atlassian.com/display/JIRA/Time+Since+Issues+Report

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Summary

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Road+Map

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Change+Log

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Popular+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Versions

http://confluence.atlassian.com/display/JIRA/Browsing+a+Version%27s+Summary

http://confluence.atlassian.com/display/JIRA/Browsing+a+Version%27s+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Version%27s+Popular+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Version%27s+Bamboo+Builds

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Components

http://confluence.atlassian.com/display/JIRA/Browsing+a+Component%27s+Summary

http://confluence.atlassian.com/display/JIRA/Browsing+a+Component%27s+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Component%27s+Road+Map

http://confluence.atlassian.com/display/JIRA/Browsing+a+Component%27s+Change+Log

http://confluence.atlassian.com/display/JIRA/Browsing+a+Component%27s+Popular+Issues

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Labels

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Bamboo+Builds

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+FishEye+Changesets

http://confluence.atlassian.com/display/JIRA/Browsing+a+Project%27s+Crucible+Reviews

http://confluence.atlassian.com/display/JIRA/Viewing+a+Project%27s+Burndown+Chart

http://confluence.atlassian.com/display/JIRA/Customising+the+Dashboard


98

1. 2.

3.

4.

Managing Multiple Dashboard PagesChanging the Look and Behaviour of a GadgetAdding the Activity Stream GadgetAdding the Administration GadgetAdding the Assigned To Me GadgetAdding the Average Age GadgetAdding the Bamboo Charts GadgetAdding the Bamboo Plan Summary Chart GadgetAdding the Bamboo Plans GadgetAdding the Bugzilla ID Search GadgetAdding the Calendar GadgetAdding the Clover Coverage GadgetAdding the Created vs Resolved GadgetAdding the Crucible Charts GadgetAdding the Favourite Filters GadgetAdding the Filter Results GadgetAdding the FishEye Charts GadgetAdding the FishEye Recent Changesets GadgetAdding the In Progress GadgetAdding the Introduction GadgetAdding the Issue Statistics GadgetAdding the JIRA News GadgetAdding the Pie Chart GadgetAdding the Projects GadgetAdding the Quick Links GadgetAdding the Recently Created Issues GadgetAdding the Resolution Time GadgetAdding the Road Map GadgetAdding the Text GadgetAdding the Time Since Issues GadgetAdding the Two-Dimensional Filter Statistics GadgetAdding the Voted Issues GadgetAdding the Watched Issues GadgetAdding the Heat Map GadgetAdding the Labels Gadget

Managing your User Profile

Adding a User AvatarAllowing OAuth AccessChanging your PasswordChoosing a LanguageUsing Hover ProfileChoosing a Time Zone

Creating an issue

Issues can only be created when there is at least one project.

Procedure

Go to the tab in the top navigation bar.IssuesClick , or type . Issues >Create Issue cIn the displayed dialog, fill in the issue details.'Create Issue'Optional: Customise the dialog to display only the fields you use most often. To do this, click the button andConfigure Fieldsremove or add fields as you wish. Your settings are saved for future usage automatically.Click the button.Create

Tip: If you want to create multiple issues with similar field values, click the check box before clicking the button.Create another CreateJIRA will then create your issue and automatically pre-populate a new dialog box with your previous field values. The Create Issue

field and attachments are not carried across.Summary

http://confluence.atlassian.com/display/JIRA/Managing+Multiple+Dashboard+Pages

http://confluence.atlassian.com/display/JIRA/Changing+the+Look+and+Behaviour+of+a+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Activity+Stream+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Administration+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Assigned+To+Me+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Average+Age+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Bamboo+Charts+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Bamboo+Plan+Summary+Chart+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Bamboo+Plans+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Bugzilla+ID+Search+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Calendar+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Clover+Coverage+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Created+vs+Resolved+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Crucible+Charts+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Favourite+Filters+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Filter+Results+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+FishEye+Charts+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+FishEye+Recent+Changesets+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+In+Progress+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Introduction+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Issue+Statistics+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+JIRA+News+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Pie+Chart+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Projects+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Quick+Links+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Recently+Created+Issues+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Resolution+Time+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Road+Map+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Text+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Time+Since+Issues+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Two-Dimensional+Filter+Statistics+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Voted+Issues+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Watched+Issues+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Heat+Map+Gadget

http://confluence.atlassian.com/display/JIRA/Adding+the+Labels+Gadget

http://confluence.atlassian.com/display/JIRA/Managing+your+User+Profile

http://confluence.atlassian.com/display/JIRA/Adding+a+User+Avatar

http://confluence.atlassian.com/display/JIRA/Allowing+OAuth+Access

http://confluence.atlassian.com/display/JIRA/Changing+your+Password

http://confluence.atlassian.com/display/JIRA/Choosing+a+Language

http://confluence.atlassian.com/display/JIRA/Using+Hover+Profile

http://confluence.atlassian.com/display/JIRA/Choosing+a+Time+Zone


99

1. 2.

3. 4. 5.

Related topics

Creating new projectsCreating 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:

Go to the tab in the top navigation bar.IssuesClick .Issues > Create Issue

In the screen, select the relevant project and issue type, and then click the button.'Create Issue' 'Next'Complete the issue details as required.Click the button.'Create'

Related topics

Creating new projectsCreating 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 purchasedseparately from JIRA OnDemand.

Here's how you can use GreenHopper:

Planning Board – where you plan your sprint and organise issues for a sprintTask Board – the task board typically shows all the work you're undertaking in a sprintChart Board – a graphical representation of the progress of ongoing versionsReleased Board – gives you access to charts and release notes for the released versions of your projects

http://confluence.atlassian.com/display/GH/Using+the+Planning+Board

http://confluence.atlassian.com/display/GH/Using+the+Task+Board

http://confluence.atlassian.com/display/GH/Using+the+Chart+Board

http://confluence.atlassian.com/display/GH/Using+the+Released+Board


100

1. 2. 3. 4. 5. 6. 7.

The use of the functionality introduced on this page depends on the purchase of GreenHopper.

On this page:

Moving issues into a sprintRelating the task board to the default workflowTransitioning 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.

Click the drop-down menu in the top navigation bar and select .'Agile' 'Planning Board'In the field, select the required project.'Planning Board'In the column at the right of the screen, click the link. The pop-up will appear.'Add' 'Add Version'In the field, type the name of your new sprint version (e.g. 'Sprint 1').'Version Name'In the field, select your major version (e.g. 'Version 1').'Parent'Enter the , and for your new sprint version.'Start Date' 'Release Date' 'Description'Click the button to create the version, then click the button to create the version and return to the'Create' 'Create and Close'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 andmonitor the progress of your workflow.

Screenshot: The Task Board displaying issue status in columns


101

1. 2. 3. 4. 5.

6.

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.

Select your project, click the drop-down menu in the top navigation bar and select .'Agile' Task BoardIn the field, select the required project. The will refresh with information for your project.'Planning Board' 'Task Board'In the dropdown, select the version which contains issues that you want to transition.'Version'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 thistransition.The issue status will update when you drop in into the destination column.

See also:

Transitioning Issues in GreenHopperScheduling 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 OnDemandWith , your team can manage and share information online easily. Confluence

Confluence OnDemand, i.e. the Wiki application, is the hosted offering of Confluence. If you are using Confluence OnDemand together withother OnDemand applications, you will be able to take advantage of a number of preconfigured integration features, such as linking between

.applications

http://www.atlassian.com/software/confluence


102

New to Confluence OnDemand?

Administrators

Getting Started Guide - Confluence

Getting Started Guide - Confluence OnDemand only

Users



Please note the following important information before you begin using Confluence OnDemand:

Some functions in Confluence OnDemand are for security reasons. Read more about restricted 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 provided by Atlassian. See the commercial add-ons Atlassian for instructions on how to order these add-ons. The following add-ons are available:OnDemand Plugin Policy

Team Calendars lets you set up and manage calendars for your teams in Confluence. Check out the Team Calendars documentation?Got Team Calendars?


The Confluence OnDemand documentation links to the documentation for downloadable Confluence extensively. Use the back button onyour browser to return to the OnDemand documentation, if you are directed to the documentation for downloadable Confluence.

Key topics

Administering the WikiConfiguring Default Space PermissionsConfiguring Confluence PluginsApplying a Theme to a SpaceCreating Confluence templatesConfluence Administrator's Guide

Working with the WikiConfluence User's GuideViewing drafts

Administering the WikiConfluence OnDemand, i.e. the application, is based on Confluence. The administration of Confluence OnDemand is mostly the sameWikias that of downloadable Confluence except the functions specific to Confluence OnDemand as indicated below and certain restrictions due tosecurity considerations.

The is a collection of online documents, i.e. .wiki pages


Administration specific to Confluence OnDemand

Page: Configuring Default Space Permissions

http://www.atlassian.com/en/software/confluence-team-calendars


103

1.

2.

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 administration console.Wiki

To go to the Wiki administration console:

Log in as an , click the menu labelled with your user name in the header, and select . Theadministrator Administrationadministration console appears with the tab active.GeneralClick the tab. The Wiki (Confluence) administration console will display.Wiki

Please note, the wiki administration console described above is used for administering the global settings for your wikiapplication. If you would like to administer a space, e.g. , , editing the space details changing the space theme configuring the space

, etc, you need to use the ' ' console. This is accessed by navigating to the desired space and selecting 'permissions Space Admin' from the ' ' menu.Space Admin Browse

Screenshot: Administering Wiki (click to enlarge the image)

Appendix - Administration options in the Wiki application

Category Functions

ConfigurationGlobal 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 otherwebsites 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 foruse by default. Import these page templates by using this option, and these templates will be available for useacross 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.


104

1.

2. 3.

1. 2.

PermissionsGlobal 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 (forexample, the wiki for each project). You can also set the for new spaces.default space permissions

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

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Wiki administration console will appear.WikiIn the left-hand menu, click > . The ' screen will appear. The table under thePermissions Space Permissions 'Space Permissions'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

Click the button below the table to edit the default space permissions. The table will display in editable mode.Edit PermissionsUpdate the default space permissions as needed and click the button to save the changes.Save

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 nothave the permission. A user group must have the permission before it can be granted with other permissions. ToView Viewgrant the permission to the user group not listed in the table, enter the name of the user group in the 'View Grant browse

' textbox and click the button. You can then grant additional permissions to that group by selecting checkpermission to Addboxes in the user group's row.

Tip: Click the magnifying glass icon to open the dialog and search for user groups.Group Search

Screenshot 2: Editing default space permissions


105

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 thatoffer configuration options.



Configuring a Confluence Plugin

Disabling or Enabling a Confluence Plugin

Viewing the Confluence Plugin Audit Log

Viewing your Confluence Plugins



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 updatethese configuration options.


Procedure


106

1.

2. 3.

1. 2.

3.

4.

1.


Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the ' ' tab. The Wiki (Confluence) administration console will display.WikiIn the left-hand menu, click . The will appear and display the plugins installed.Configuration > Plugins Universal Plugin Manager

To configure a Confluence plugin:

Click the tab.Manage ExistingLocate the plugin that you want to configure and click its title. The plugin details section expands.Click the button for that plugin.ConfigureThe advanced configuration options appear.

If the plugin is disable, you cannot configure it and so the Configure does not appear. If there are nobuttonadvanced configuration options for the plugin, there is no button.Configure

Update the configuration settings as desired and save your changes. The plugin itself provides advanced configuration options. If you encounter any problems after you click the button,Note: Configure

the plugin is responsible for the issue, not the UPM.

Screenshot: Configuring a plugin

Related topics



You can enable and disable Confluence plugins in your Atlassian OnDemand site. With the Safe Mode, you can disable all user-installedplugins in your site with one click, which might help you diagnose plugin-related problems more easily.



On this page:

Disabling a pluginEnabling a pluginDisabling and enabling all user-installed plugins (Safe Mode)

Disabling a plugin



107

1.

2. 3.

1. 2. 3. 4.

1.

2. 3.

1. 2. 3. 4.


To disable a Confluence plugin:

Click the tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon: Manage ExistingLocate the plugin that you want to disable and click the title to expand the plugin details section.Click the button.DisableOnce a plugin has been disabled, you need to restart your application for your change to take effect. If so, you will see amaymessage for the plugin, .Disabled, requires restartOnce the plugin is fully disabled, you will see an link for the plugin.Enable

Screenshot 1: Disabling a plugin

Enabling a plugin



To enable a Confluence plugin:

Click the tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon: Manage ExistingLocate the plugin that you want to enable and click the title to expand the plugin details section.Click the button.EnableOnce a plugin has been enabled, you need to restart your application for your change to take effect. If so, you will see amaymessage for the plugin, .Enabled, requires restartOnce the plugin is fully disabled, you will see a link for the plugin.Disable

Screenshot 2: Enabling a Plugin


108

1.

2. 3.

1.

2. 3.

4.

5.

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 youentered Safe Mode will be re-enabled when you exit Safe Mode.



To enable Safe Mode:

Click the tab. Manage ExistingThe system displays a list the installed plugins.Click the link.Enable Safe ModeClick the button in the confirmation window. ContinueAll user installed plugins will be disabled and your application will now be running in safe mode.Make changes to your installed plugins as desired. For example, you may want to enable/disable specific plugins or plugin modules.Exit safe mode by clicking one of the links in the Safe Mode banner:

Click to restore your plugin configuration to its state before youExit Safe Mode and restore the previous configurationentered Safe Mode.Click to keep all changes made to your plugin configuration duringExit Safe Mode and keep the current configurationSafe Mode.

Screenshot 3: Running Confluence in Safe mode

The Safe Mode is enabled The Enable Safe Mode link


109

1.

2. 3.

1.

2. 3.

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 pluginsand the users who made the changes.


Procedure



To view the plugin audit log:

Click the tab. Audit LogThe plugin audit log appears with a list of the 25 most recent entries.Use the arrows if you want to view older entries.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.



110

1.

2. 3.

On this page:

Viewing Confluence pluginsViewing a plugin's detailsRelated topics

Viewing Confluence plugins



To view Confluence plugins:

Click the tab to list the plugins installed in your application. The application groups plugins into andManage Existing User-installed Plugins. The are hidden by default. Use the following actions when working with the plugin list:System Plugins System Plugins

Enter keywords in the text box to filter the list.Filter visible pluginsClick the link to see the hidden system plugins.Show System PluginsClick the name of a plugin to view the plugins details.Click to run your application in safe mode. This mode disables all user installed plugins.Enable Safe Mode

Enabled plugins have this icon , and this icon indicates disabled plugins.



Screenshot 1: Viewing plugins (Confluence)


111

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 shortdescription of the plugin as well as buttons and links for plugin operations and related information.

Screenshot 2: Viewing a plugin's details


112

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 theplugin. This link will only appear if the plugin has modules. If you want to enable or disable a plugin module, hover your mouse overthe module and click the ' '/' ' button for that module.Enable DisablePlugin details – Click this link to display the plugin information on the .Atlassian Plugin ExchangeConfigure – Click this link to display the configuration settings for the plugin in the Universal Plugin Manager. This link will bedisabled if the plugin is disabled. Please note that not all plugins have settings that can be configured through the Universal PluginManager.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 PluginDisabling 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 aspecific theme to provide specific functionality or to significantly alter the appearance of your wiki.

You need to be a to edit the look and feel of a space.space administrator

On this page:

Themes in Confluence OnDemandApplying a theme to a spaceCustomising the Atlassian OnDemand Documentation ThemeRelated topics

Themes in Confluence OnDemand

Confluence OnDemand comes with a selection of themes:

Theme Features

http://plugins.atlassian.com

http://confluence.atlassian.com/display/DOC/Confluence+Glossary


113

1. 2. 3. 4. 5.

1. 2. 3. 4. 5.

6.

Default Theme This is the default look and feel of all OnDemand spaces. Using this theme enables you to customise the colourscheme and layout for individual spaces.

AtlassianOnDemandTheme

This theme features a cross-application navigation bar, which contains tabs for easy access to your , , Issues Wiki, , and functionality.Source Reviews Builds

AtlassianOnDemandDocumentationTheme

You can configure this theme to include a collapsible left navigation sidebar, custom sidebar links, and header andfooter text. The sidebar contains a collapsible navigation tree that can be used to browse through the space. Your wikiwill retain the Atlassian OnDemand header, along with any custom logos you have uploaded.

Please see below for instructions and examples of howCustomising the Atlassian OnDemand Documentation Themeto tailor this theme to your needs.

Applying a theme to a space

Procedure

Log into as an . In the navigation bar, click the tab. The wiki dashboard appears.administrator WikiSelect your desired space. The homepage for the space will display.In the top right corner of the wiki, click > . The 'Space Administration' console for your space will display.Browse Space AdminIn the area of the left-hand menu, select . The current theme and themes available for selection will display.Look and Feel ThemesClick the radio button next to your required theme, and then click the button to select this theme.Confirm

Customising the Atlassian OnDemand Documentation Theme

Procedure

Log in as an . In the navigation bar, click the tab. The wiki dashboard appears.administrator WikiSelect your desired space. The homepage for the space will display.In the top right corner of the wiki, click > . The 'Space Administration' console for your space will display.Browse Space AdminIn the area of the left-hand menu, select . The current theme and themes available for selection will display.Look and Feel ThemesSelect the , and then click the button to select this theme. This theme willAtlassian OnDemand Documentation Theme Confirmbe displayed as the current theme and you will see the option under the theme.Configure themeSelect to customise the theme, for example, by providing header and footer messages, or links.Configure Theme

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 is a Confluence page with predefined content and can be used as a prototype when creating new pages. Templates are handy totemplate


114

1.

2.

3.

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 spaceadministrators can create space templates.

Procedure

Go to the 'Create Template' page.To add space templates, go to > in any place of your space. Then, in the left-hand panel, click Browse Advanced

and then click the link.Templates Add New Space TemplateTo add global templates, go to > . Then, under the section of the left-handBrowse Confluence Admin Configurationpanel, click and then click the link.Global Templates Add New Space Template

The 'Create Template' page appears. Enter a name for your template in the field and an optional description in the Name field.Description

Using regular and (if you are using forms), enter content in the text-entry box as you would in anyWiki Markup form field markupother page.

Related topics

Global Templates (Confluence)

Confluence Administrator's Guide

Atlassian OnDemand includes for its wiki. Use the search or click any of the links below to view the relevant page in theConfluence 4.1Confluence Administrator's Guide. You will need to use the 'Back' button on your browser to return to the Confluence OnDemanddocumentation.

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 ConfigurationConfiguring the Site Home PageConfiguring the Administrator Contact Page Editing the Site Title

Editing the Global Logo Customising Default Space ContentConfiguring the Destination of View Space LinksEditing the Site Welcome MessageConfiguring the What's New Dialog

Optional Settings

Configuring a WebDAV client for Confluence Enabling OpenSearchEnabling the Did You Mean FeatureEnabling the Remote API — Enabled by defaultEnabling Threaded CommentsEnabling Trackback

Other SettingsConfiguring Attachment SizeConfiguring Character EncodingConfiguring HTTP Timeout SettingsConfiguring Indexing LanguageConfiguring Number FormatsConfiguring Shortcut LinksConfiguring Time and Date Formats

Configuring Confluence Security

Enabling or Disabling Public Signup Managing External Referrers

Excluding external referrersHiding external referrersIgnoring 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


115

Design and Layout

Customising Look and Feel Overview — Custom layouts are not permitted.

Customising Colour Schemes Global TemplatesImporting TemplatesCustomising PDF or HTML Content

Themes OverviewApplying a Theme to a SiteCustomising 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 PluginDisabling or Enabling a PluginViewing the Plugin Audit LogViewing 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 UserAdding a Group

Adding or Removing Users in Groups Changing UsernamesEditing User DetailsGlobal Groups Overview

Global Permissions Overview Removing a Group

Removing or Deactivating a User Setting up Anonymous AccessViewing members of a group

Resetting the Login Count for a User

Working with the WikiConfluence OnDemand, i.e. the Wiki application, is based on Confluence.

The is a collection of online documents, i.e. . A is a group of within the . You can think of each space as awiki pages space pages wikisub-site, or mini-site, each with its own home page.

In Atlassian OnDemand, a space can be associated with a . This allows links to be automatically created on your wiki pages, pointingprojectto associated , , and .issues source files changesets code reviews

Audience: Users

A few things to get started

Add a pageAdd a blog postAdd 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 additionalfeatures:

Team CalendarsBalsamiq Mockups for JIRA User GuideGliffy

http://confluence.atlassian.com/display/DOC/Creating+a+Page

http://confluence.atlassian.com/display/DOC/Adding+Blog+Posts

http://confluence.atlassian.com/display/DOC/Working+with+Spaces

http://support.balsamiq.com/customer/portal/articles/113842-mockups-for-jira-user-guide


116

1.

Accessing the Wiki application

To access the Wiki application and work with pages:

Click the tab in the navigation bar. This takes you to Confluence.Wiki

Confluence User's Guide

Atlassian OnDemand includes for its wiki. Use the search or click any of the links below to view the relevant page in theConfluence 4.1Confluence 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

DashboardPage in View ModeConfluence GlossaryConfluence IconsKeyboard Shortcuts

Creating Content

Using the EditorWorking with Text EffectsWorking with Links

Linking to Personal Spaces and User ProfilesLinking from an ImageUsing a Link to Create a New Email MessageLinking to AttachmentsWorking with AnchorsLinking to Confluence Pages from Outside ConfluenceTrackbackEditing and Removing LinksLinking to PagesLinking to Blog PostsLinking to Images

Working with DraftsConfiguring the Time Interval at which Drafts are SavedConcurrent Editing and Merging ChangesResuming the Editing of a DraftRecording Change Comments

Using ImagesDisplaying ImagesImage File Formats

Using AutocompleteUsing Special Characters

Inserting Emoticons and IconsInserting Symbols

Working with the Macro BrowserInserting JIRA Issues

Adding a PageAdding a Blog PostWorking with TablesWorking with Templates

Adding a TemplateCreating a Page using a TemplateEditing a templateRemoving a TemplateConfluence Wiki MarkupForm Field Markup for Templates

Working with the Office Connector Office Connector PrerequisitesDisplaying Office Files in ConfluenceImporting an Office Document into ConfluenceEditing an Office Document from ConfluenceEditing an Office Spreadsheet from ConfluenceEditing an Office Presentation from ConfluenceInstalling the Firefox Add-On for the Office Connector


117

Sharing Content

Network OverviewSubscribing to a Network RSS Feed

User Status UpdatesUsing Mentions

Watching Changes

Tracking Updates to Confluence Pages and SpacesSubscribing to Email Notifications of Updates to Confluence ContentWatching a Page or Blog PostWatching a SpaceManaging WatchersSubscribing to RSS Feeds within Confluence

Using pre-specified RSS feedsUsing the RSS Feed Builder

Working with RSS FeedsRSS Readers Compatibility

Searching Confluence

Confluence Search FieldsConfluence Search SyntaxRanking of Search ResultsSearching the People DirectoryText Tokenisation and Filtering

Organising Content

Working with PagesMoving a PageWorking with Page Families

Viewing a Page's FamilySetting a Page Family to Alphabetical Order

Using the Documentation ThemeSequential Order of PagesViewing Page InformationCopying a PageWorking with Comments

Adding a CommentDeleting CommentsEditing a CommentLinking to Comments

Recently Viewed ContentE-mailing a PageRenaming a PageDeleting a Page

Purging Deleted PagesRestoring a Deleted Page

Page History and Page Comparison ViewsRestoring an Older Version of a PageViewing an Older Version of a Page

Using a WebDAV Client to Work with PagesWorking with Blog Posts

Deleting Blog PostsEditing Blog PostsViewing Blog Posts

Working with SpacesViewing Space ActivityViewing All Confluence SpacesAdministering SpacesDeleting a SpaceSetting up a New Global SpaceSetting up your Personal SpaceExporting Confluence Pages and Spaces to Other Formats

Exporting Confluence Pages and Spaces to HTMLExporting Confluence Pages and Spaces to PDF

Customising Exports to PDFAdvanced PDF Export Customisations

Creating PDF in Another LanguageExporting to a Word documentExporting Confluence Pages and Spaces to XML

Browsing a spaceEditing Space DetailsManaging Orphaned PagesManaging Undefined PagesViewing Hierarchy of Pages within a Space


118

Viewing Pages AlphabeticallyViewing Recently Updated ContentViewing Space Details

Space Backup and RestoreArchiving Mail Overview

Adding a Mail AccountDeleting MailFetching MailImporting MailManaging Mail AccountsRestoring MailViewing Mail

Working with LabelsAdding a Global LabelAdding a Personal LabelUsing Labels to Categorise SpacesNavigating Pages by LabelRemoving a Label from a PageUsing Label Macros to Categorise Wiki Content

Content by Label MacroLabels List MacroNavigation Map MacroPopular Labels MacroRecently Used Labels MacroRelated Labels Macro

Viewing Global LabelsViewing labelled pagesViewing personal labelsViewing Popular Labels

Working with FavouritesAdding FavouritesRemoving FavouritesViewing Favourites

Working with AttachmentsUsing Drag-and-Drop in ConfluenceAttaching Files to a PageAttachment VersionsDeleting an AttachmentDisplaying a List of Attachments in a PageDownloading AttachmentsEditing Attachment PropertiesEmbedding Multimedia ContentEmbedding PowerPoint Presentations in a PageFinding an AttachmentMoving an Attachment

Choose a PageViewing Attachment Details

Customising Confluence

Personal Customisations User Profile Overview — Note, user profile configuration is available under Profile -> Wiki Profile

Changing PasswordEditing User SettingsEditing Your User ProfileEmail Address PrivacyUpdating Email AddressChoosing a Profile Picture

Deleting a Profile PictureViewing User ProfileViewing and Revoking OAuth Access Tokens

Choosing Your HomepageCustomising your Personal Dashboard

Customising Look and FeelApplying a Theme to a Space

Configuring the Documentation ThemeConfiguring the Easy Reader Theme

Changing a Space's LogoChanging the Confluence Browser Icon, aka faviconChoosing Your HomepageCustomising Space LayoutsEditing a Space's Colour SchemeStyling Confluence with CSS

Basic Styling TutorialStyling Fonts in ConfluenceStyling Tabs in ConfluenceUsing CSS to Customise the Easy Reader Theme

Customising your Personal DashboardPermissions Overview

Page Restrictions

http://confluence.atlassian.com/display/DOC/Personal+Customisations

http://confluence.atlassian.com/display/DOC/User+Profile+Overview

http://confluence.atlassian.com/display/DOC/Changing+Password

http://confluence.atlassian.com/display/DOC/Editing+User+Settings

http://confluence.atlassian.com/display/DOC/Editing+Your+User+Profile

http://confluence.atlassian.com/display/DOC/Email+Address+Privacy

http://confluence.atlassian.com/display/DOC/Updating+Email+Address

http://confluence.atlassian.com/display/DOC/Choosing+a+Profile+Picture

http://confluence.atlassian.com/display/DOC/Deleting+a+Profile+Picture

http://confluence.atlassian.com/display/DOC/Viewing+User+Profile

http://confluence.atlassian.com/display/DOC/Viewing+and+Revoking+OAuth+Access+Tokens

http://confluence.atlassian.com/display/DOC/Choosing+Your+Homepage

http://confluence.atlassian.com/display/DOC/Customising+your+Personal+Dashboard


119

Inaccessible PageSetting a Page's RestrictionsViewing a Page's Restrictions

Site Administrators and their PermissionsContacting Confluence Administrators

Space Administrators and their PermissionsSpace Permissions Overview

Assigning Space PermissionsRevoking Space PermissionsViewing Space Permissions

Users and GroupsSearching for Users

Viewing Restricted PagesWorking with Confluence Gadgets

Adding a Confluence Gadget to a JIRA DashboardConfiguring Confluence Gadgets for Use in Other ApplicationsConfluence Gadgets

Activity Stream GadgetConfluence News GadgetConfluence Page GadgetConfluence Quicknav Gadget

Adding JIRA Gadgets to a Confluence PageWorking with Macros

Anchor MacroAttachments MacroBlog Posts MacroChange-History MacroChart MacroCheese MacroChildren Display MacroCode Block MacroColumn MacroContent by User MacroContributors MacroContributors Summary MacroCreate Space Button MacroExcerpt Include MacroExcerpt MacroExpand MacroFavourite Pages MacroGadget MacroGallery MacroGlobal Reports MacroHTML Include MacroHTML MacroIM Presence MacroInclude Page MacroInfo MacroJIRA Issues MacroJIRA MacroJIRA Portlet MacroJUnit Report MacroLivesearch MacroLoremipsum MacroMetadata MacroDetailssummary MacroMultimedia MacroNetwork MacroNoformat MacroNote MacroPage Index MacroPage Tree MacroPage Tree Search MacroPanel MacroUser Profile MacroRecently Updated Dashboard MacroRecently Updated MacroRSS Feed MacroSearch Results MacroSection MacroSpace Details MacroSpace Jump MacroSpaces List MacroStatus MacroTable of Contents MacroTable of Content Zone MacroTasklist MacroTip MacroUser List MacroUser Status List Macro


120

1. 2. 3.

View File MacroWarning MacroWidget Connector Macro

Widget Connector ExamplesGuides to Specific Uses of Confluence

Developing Technical Documentation on Confluence WikiCreating your Technical Documentation SpaceUsing Templates in Technical DocumentationRe-using Content in Technical DocumentationManaging the Life Cycle of your Technical DocumentationProviding PDF Versions of your Technical DocumentationExporting and Printing Technical DocumentationEssential Confluence Features for Technical DocumentationConfluence Plugins for Technical DocumentationFurther Reading about Developing Technical Documentation on Confluence

Developing a Knowledge Base on Confluence WikiCreating Your Knowledge Base SpaceUsing Templates and Formatting Macros in a Knowledge BaseProactive Communications in a Knowledge BaseAdditional 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

Log in to your site.On the tab, go to .Wiki Browse > User SettingsOn the displayed page, go to the tab to see your draft pages.Drafts

Screenshot: Navigating to User Settings in the Wiki tab

Source and Review BundleThe Source and Review bundle consists of , and the integrated Subversion. FishEye and Crucible provide source repositoryFishEye Cruciblebrowsing 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 FishEyeand Crucible. If you are using Fisheye OnDemand and Crucible OnDemand together with other OnDemand applications, you will be able totake advantage of a number of preconfigured integration features, such as linking between applications

New to FishEye OnDemand/Crucible OnDemand?

Administrators


Users



http://www.atlassian.com/software/fisheye/

http://www.atlassian.com/software/crucible/

http://confluence.atlassian.com/display/JIRASTUDIO/Creating+Links


121

1.

2.

Please note the following important information before you begin using FishEye OnDemand/Crucible OnDemand:

Some functions in FishEye OnDemand and Crucible OnDemand are for security reasons. Read more about restricted Restricted.Functions in Atlassian OnDemand

To find out which FishEye version and Crucible version is running in Atlassian OnDemand, see Atlassian OnDemand Application.Versions


The FishEye OnDemand/Crucible OnDemand documentation link to the documentation for downloadable FishEye/Crucible extensively. Usethe back button on your browser to return to the OnDemand documentation, if you are directed to the documentation for downloadableFishEye/Crucible.

Key topics

Administering ReviewsAdministering Source

Configuring commits to require a JIRA issue keyConfiguring repository permissions

Working with ReviewsCrucible User's Guide

Working with SourceFishEye User's GuideChecking changesets committed against an issue

Working with the Repository

.

Administering ReviewsThe permissions of the application, inherit that of the application. This means that the same read and commitCrucible, i.e. Reviews Sourcepermissions that apply to a project's source also apply to that project's reviews.

About reviews: Your can go through a (sometimes called , or ) either before or aftersource review code review peer review quality assurancebeing committed to a repository.


For information on how to set up permissions for your source, refer to .Administering Source


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 Reviewsadministration area and select the appropriate setting:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Reviews administration console will appear. Each of the administration options for your 'Reviews'Reviewsapplication are divided into the categories listed below.

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


122

2.

1.

2.

Defect Classifications Customise the defect classifications for your reviews.

Screenshot: Administering Reviews

Administering SourceThe application is based on FishEye and includes the integrated Subversion. There is no configuration required on the part ofSourceadministrations for your team to start using the Source application. The administration options help you control access to your source andprovides additional integration functionality with JIRA OnDemand.


Administering Source

Configuring commits to require a JIRA issue keyConfiguring repository permissions

Accessing the Source administration area

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will appear. Source

Screenshot: Administering Source (Click to enlarge)

Related topics


http://confluence.atlassian.com/display/CRUCIBLE025/Customising+the+Defect+Classifications


123

1.

2. 3. 4. 5.

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 willnot 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:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will display.'Source'Click the option in the left menu. The page will display.'SVN Commit Hooks' 'SVN Commit Hooks'Select the checkbox, .'Require JIRA issue key for a successful commit'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 aparticular user, you need to add the user to a user group with the desired permission.


Permission management in other apps:Managing application permissions

Permissions levels

There are two levels of repository permissions: and .read commit

In your source – FishEye and Subversion:

The permissions controls if a user group can view the source code in a directoryreadThe permission controls if a user group can commit changes to the directory, i.e. .commit 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 permission to the ' group and permission to the 'read 'users commit' and ' ' groups. For more information about the default permission settings, refer to developers administrators Managing Users and

.Groups


124

1.

2. 3.

4.

5.

How to configure

Project-specific permissions overwrite the default permissions.

Configuring repository permissions for a projectConfiguring default repository permissionsEnabling 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. Subversionpermissions can be assigned to user groups only, but not to individual users. If you want to assign a repository permission to a particularuser, you can add the user to a user group with the desired permission.


On this page:

Configuring repository permissions at the project levelConfiguring repository permissions at the path levelMore options on the SVN Permission Manager pageRelated topics

Configuring repository permissions at the project level

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will display.SourceClick the option in the left menu. The ' ' page will display, listing all projects that youProject Permissions SVN Permission Managerhave permission to administer.Click the link next to the project that you wish to update the permissions for.The ' ' page will displayConfigure Manage Repository(see screenshot below).The ' ' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The ' 'Read Commitpanel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository.

Configure permissions as needed.

To grant permissions to a group, select the group in the drop-down list under the appropriate panel, and click the Group button. Note that a user group does not need to have the 'Read' permission, if it has been granted the 'Commit'Add

permission.To remove a permission from a user group, click the link next to the user group. Note that removing the 'Commit'removepermission from a user group will remove both read and write access from the user group. If you want to retain the group'sread access, you will need to grant the 'Read' permission to the group.

Anonymous access to a project's repository is by default. You can enable anonymous access to a repository via thedisabledadministration console. For instructions on how to do this, refer to .Enabling Anonymous Access to a Repository

Screenshot 1: Subversion Permission Manager


125

1.

2.

3.

4.

a.

b.

a. b.

a. b.

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/privateand then create a branch of that path (e.g. ), the branch inherit the/DOM/branches/branch1/private will notpath-level permissions. You must set up the path-level permissions for the branch separately.

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralGo to > . The ' ' page will display, listing all projects that you have theSource Project Permissions SVN Permission Managerpermission to administer.In the text box, enter the path of the directory that you want to configureModify commit permissions for an arbitrary pathpermissions for, and click .AddThe ' ' page will display (see screenshot 2 below). The permissions shown will be inherited from theManage Permissions for Pathparent or project in the repository hierarchy, unless explicitly overridden.

If a user group has the ' ' permission, users in the group can access the path but not commit to the path. ReadRead Onlyonly permission may have been inherited from the parent or project in the repository hierarchy, or explicitlygranted/overridden.If a user group has the ' ' permission, users in the group will be able to commit to the path.Commit

Modify the path permissions as needed.To to a user group,add path permissions

In section, select the desired user group in the first drop-down list and the permission in theAdd Permissionsecond drop-down list.Click the button. The path permissions will be added.Add

To for a user group,change the existing path permissions In the section, locate the group and select the path permission under the column.Permissions ActualClick the button. The path permissions will be updated.Save

To for a user group,remove an existing path permission In the section, locate the group and select the check box under the column.Permissions RemoveClick the button. The path permissions will be removed.Save

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 ' ' page also contains two other links as shown in the following screenshot:SVN Permission Manager

Synchronise FishEye permissions— this link will set your FishEye permissions to be the same as your Subversion permissions.You have to use this function, except on advice from the Atlassian Support team.should notModify settings applied to new projects — this link takes you to the page.Configuring default repository permissions

Screenshot 3 : Managing repository permissions for a path


126

1.

2. 3.

4.

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 moreabout .configuring repository permissions for a project


Overview of repository permissions:Configuring repository permissions

Procedure

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will appear.SourceIn the left-hand menu, click the option. The ' ' page will display (seeDefault Permissions Manage Default Repository Permissionsscreenshot below). The ' ' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The ' 'Read Commitpanel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository.Configure permissions as needed.

To grant permissions to a group, select the group in the drop-down list under the appropriate panel, and click the Group. Note, that a user group does not need to be the 'Read' permission, if it has been granted the 'Commit'Add button

permission.To remove a permission from a user group, click the link next to the user group. Note, that removing the 'Commit'removepermission 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 by default. You can enable anonymous access to your repository by followingdisabledinstructions in the page.Enabling Anonymous Access to a Repository

Screenshot: Manage Default Repository Permissions


127

1.

2. 3.

4.

5.

1.

2. 3. 4.

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 . If anonymousdisabledaccess 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 tab in your site.Source

Anonymous repository access can be enabled for each individual project. You can also enable anonymous repository access for all newprojects created.


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

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will appear.SourceClick the option in the left menu. The 'SVN Permission Manager' page will display, listing all projects that youProject Permissionshave permission to administer.Click the link next to the project that you wish to enable anonymous repository access for. The ' 'Configure Manage Repositorypage will display.Click to enable anonymous access to the project. This will override your global preferences forEnable anonymous accessanonymous repository access.

Enabling anonymous repository access for all new projects

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Source administration console will appear.SourceClick the option in the left menu.Default PermissionsClick to enable anonymous access for all new project repositories.Enable anonymous access

Related topics


128

1.

Managing anonymous access

Working with ReviewsYour can go through a (sometimes called , or ) either before or after beingsource review code review peer review quality assurancecommitted 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 ' application. ’Reviews

To access the Reviews application:

Click the tab in the navigation bar. This takes you to Crucible.Reviews

Crucible User's Guide

Atlassian OnDemand includes for code reviews. Use the search or click any of the links below to view the relevant page in theCrucible 2.7Crucible 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 ReviewsBrowsing Source FilesUsing the Dashboard

Browsing Your ReviewsBrowsing Reviews, Source and Issues ActivityViewing Your Favourites

Crucible IconsSearching in CrucibleViewing People's StatisticsBrowsing Projects

Viewing Project StatisticsViewing Reports

Review Coverage ReportChangeset Discussions

Changing your User Profile

Roles and Status Classifications

Conducting a Review

Creating a ReviewCreating a Patch ReviewCreating a Review within CrucibleCreating a Review from FishEyeCreating a Review from JIRACreating a Review from a URLCreating a Snippet Review

Selecting the Files for the ReviewIterative Reviews

Adding ReviewersIssuing a Review


129

1.

Performing the ReviewAdding CommentsFlagging DefectsCompleting your ReviewSending a Review's Comments via EmailUsing JIRA Integration in Crucible ReviewsUsing the Review History DialogTracking Crucible Review Metrics

Using Progress TrackingUsing Time Tracking

Summarising and Closing the ReviewMoving a Review to Another ProjectDeleting 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 SourceThe application is based on FishEye and includes the integrated Subversion. With FishEye, you can easily browse and search yourSourcesource repository.

Audience: Users

Using FishEye

FishEye User's GuideChecking changesets committed against an issue

Accessing the Source application

To access the Source application and work with your source code:

Click the tab in the navigation bar. This takes you to FishEye.Source

FishEye User's Guide

Atlassian OnDemand includes for browsing source code. Use the search or click any of the links below to view the relevantFishEye 2.7page in the FishEye User's Guide. You will need to use the 'Back' button on your browser to return to the FishEye OnDemanddocumentation.

Please note, some FishEye functionality is .restricted in FishEye OnDemand

Search the FishEye 2.7 documentation:

Using the FishEye Screens

Browsing through a RepositorySearching the RepositoryViewing a File

Viewing File ContentUsing Side by Side Diff View

Viewing a File HistoryViewing the ChangelogCopying and Pasting Code from FishEye

FishEye ChartsUsing FavouritesChangeset DiscussionsViewing People's Statistics


130

1. 2.

1. 2.

3.

1. 2.

3.

Changing your User Profile

Antglob Reference Guide

Date Expressions Reference Guide

EyeQL Reference Guide

Checking changesets committed against an issueYou can view changesets committed against a particular issue in JIRA if the commit messages have included the JIRA issue key.

Procedure

Locate the issue.In the area of the issue, go to the . You will see the changesets committed against the issue:Activity Source

who committed the codewhat changes were madecomments associated with the change

Related topics

Using Smart Commits

Working with the RepositoryThe Subversion in the Source and Review bundle contains your code. To work with the repository, you can either accessrepository sourcethe files directly using the or use an (integrated development environment).Subversion command-line client IDE

On this page:

Using the Subversion command-line clientUsing 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 morecommonly 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 onyour machine.

To check out a working copy

Open a Subversion command-line client.Enter the following command:svn checkout /svn/<project_key>/trunkhttps://<account_name>.atlassian.netwhere is the account name that you provided at signup and is the key of the project that you defined<account> <project_key>at project creation.

Enter the username only, i.e. if your Google Apps login is ' ', then simply supply the username '[email protected]'.fred

If you wish, you can check out a particular Subversion directory in your project (e.g. a branch of code), by specifying instead of .<project_key>/<directory_name> <project_name>/trunk

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 otherusers (with access to the repository) may have committed.

To update your working copy

Open a Subversion command-line client.Enter the following command:svn updateA confirmation message will be displayed at the end of a successful update, e.g. 'Updated to revision 2442.', as well as the list offiles updated in your working copy.


131

1. 2.

3.

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 commitcommand.

To commit changes to your Subversion project

Open a Subversion command-line client.Enter the following command:svn commit -m "<commit_message>"where is the description of your changes for this commit. This description will be recorded against the commit<commit_message>in the repository.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.

svndelete

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.

svnstatus

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 theoriginal).

svnrevert

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 thefollowing repository details when configuring the IDE:

Location of your repository — that is, , where is the account name thathttps://<account_name>.atlassian.net <account>you provided at signupThe and that you use to access your source repository — these will be the same details that you use toUsername Passwordaccess 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 OnDemandBamboo OnDemand, i.e. the Builds application, is the hosted offering of Bamboo. If you are using Bamboo OnDemand together with otherOnDemand applications, you will be able to take advantage of a number of preconfigured integration features, such as linking between

.applications

http://svnbook.red-bean.com/en/1.0/index.html

http://creativecommons.org/licenses/by/2.0/


132

New to Bamboo OnDemand?

Administrators


Users



Please note the following important information before you begin using Bamboo OnDemand:

Some functions in Bamboo OnDemand are for security reasons. Read more about restricted Restricted Functions in Atlassian.OnDemand

To find out which Bamboo version is running in Atlassian OnDemand, see .Atlassian OnDemand Application Versions


The Bamboo OnDemand documentation links to the documentation for downloadable Bamboo extensively. Use the back button on yourbrowser to return to the OnDemand documentation, if you are directed to the documentation for downloadable Bamboo.

Key topics

Administering BuildsIntegrating Builds with your Issues WorkflowBamboo Administrator's Guide

Working with BuildsBamboo User's GuideActioning Issues via Builds

Administering BuildsThe in your can be built by the 'Builds' application (Bamboo).source repository

and, you must have an Amazon account and input your account information in Bamboo.

New to 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: adeveloper commits a code change to SVN repository to resolve a JIRA issue; Bamboo detects this change and as a result, a build plan istriggered 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 "buildagents".Bamboo OnDemand utilises the Amazon Elastic Compute Cloud (EC2) to get these "build agents"; i.e. Bamboo OnDemand does notrun builds locally; instead, builds are run on EC2 .

Administering Builds


133

1.

2.

Bamboo Administrator's Guide

To administer the Builds application, use the administration tab in the administration console.'Builds'

To access the Builds tab in the administration console:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick the tab. The Builds administration console will display.Builds

For an overview of the administration options for the 'Builds' application, refer to the following appendix.

Appendix

Category Functions

BuildResources

* — View and manage running (elastic) agents. Agents* — View which active Bamboo agents can execute which plans (depending on plan requirements andAgent Matrixagent capabilities). * — Define global variables that can be used across all build plans.Global Variables

Elastic Bamboo * — Configure Elastic Bamboo settings. Configuration* — View and manage elastic instances. Instances* — Manage elastic image configurations, including , , instanceImage Configurations custom images EBS volumestype and availability zone. * — Schedule the startup and shutdown of instances of a particular elastic image. Instance Schedule* — View the history of elastic agents.Agent History

Plans * — Enable and disable concurrent builds, and configure the default number of concurrent builds.Concurrent Builds

* — Schedule when build results and/or artifacts will be deleted. Build Expiry* — Modify multiple plans at once, e.g. add notifications, etc. Bulk Action* — Configure build monitoring, including hung build and build queue timeout events. Build Monitoring* — Delete build plans. Remove Plans* — Move build plans between projects. Move Plans* — Apply permissions to multiple build plans at once.Bulk Edit Plan Permissions

Security * — Manage Bamboo global plan permissions.Global Permissions

The permission in Bamboo OnDemand is the restricted permission in downloadable'Restricted Admin' 'Admin' Bamboo. The restrictions are:

Local agents cannot be created because Bamboo OnDemand uses .Elastic AgentsUsers and groups are managed by JIRA OnDemand.

Communication * — Configure the instant messaging server for Bamboo.IM Server

System * — Configure general settings, such as the name of the Bamboo instance (displayed on theGeneral Configuration'Builds' dashboard), compression of artifacts, enabling the remote API (not the REST API which is enabled bydefault). * — View system information about Bamboo. System Information* — Configure runtime logging settings. Log Settings* — View Bamboo system errors.System Errors

Plugins * — Enable/Disable the Auto-Favourite Plugin.Auto-Favourite Plugin

Integrating Builds with your Issues Workflow

You can configure a workflow in the issues application, so that the workflow can be by the completion of a build. For example, youactionedcan configure a workflow to automatically progress an issue from 'Building' to 'Resolved' status when an build related to that issue (i.e. JIRAissue key added to commit message) has successfully completed. Alternatively, you can configure the same workflow to progress an issuefrom 'Building' to 'Build Broken' status if a build related to that issue fails.

http://confluence.atlassian.com/display/BAMBOO/Working+with+Elastic+Bamboo


134

On this page:

Understanding the 'Builds Workflow'Using the 'Builds Workflow' in your projectsModifying the 'Builds Workflow'Integrating build transitions into your custom workflow

A exists in JIRA and it incorporates the common statuses and transitions (see the Builds Workflow Understanding the 'Builds Workflow'section below).

If you are new to JIRA and Bamboo, we recommend that you as modifying an existing workflow is not ause the 'Builds Workflow'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 itIf you want to integrate Bamboo transitions into your existing workflow, you can . Weedit your workflow to add the transitionsrecommend that you avoid doing unless you have a good understanding of JIRA workflows.

Understanding the 'Builds Workflow'

Diagram: Builds Workflow

# 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


135

1.

2. 3. 4. 5.

6. 7.

1.

2.

3.

The , and transitions are Bamboo-specific transitions:'Wait for Build' 'Build Passed' 'Build Failed'

'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build. Note, you must manually enter the commit command in your commit message to trigger the transition, ascommit command #build

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 ' ', and then associate the workflowBuilds Workflowscheme with a project. If you want to add the 'Builds Workflow' to an existing workflow scheme, ignore steps 4-6 below and assign theworkflow to your existing workflow scheme instead.

Procedure

1. Creating a workflow scheme that uses the Builds Workflow

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralGo to the tab in the administration console. The ' ' administration console will display.Issues IssuesIn the left-hand menu, go to . The ' ' page will display.Workflows >Workflow Schemes Workflow SchemesClick . The 'Add Workflow Scheme' page will display.Add workflow schemeEnter a and ' for your workflow scheme and click the button. Your workflow scheme will be created and youName Description Addwill see the page for editing the workflow.Click the link. The 'Add Workflow to Scheme' page will display.Assign a workflowIn the dropdown, select the issue types that you want the 'Builds Workflow' to apply to. In the drop-down list,Issue Type Workflowselect . Click The 'Builds Workflow' to your new workflow scheme for the selected issue types.Builds Workflow Add.

2. Associating the workflow scheme with your project

In left-hand menu of the tab, go to and select the project you wish to use the 'Builds Workflow' with. The projectIssues Projectssummary page appears.Locate the section and click .Workflows More

In the top right corner of the displayed page, click > . The 'Associate Workflow Scheme to Project' screenActions Select a scheme


136

3.

4. 5.

1.

2. 3. 4. 5. 6.

7.

will display.In the drop-down list, select the newly created workflow scheme, and click the button.AssociateSelect any statuses to migrate from the old workflow scheme to the new one (if any) and click the ' ' button. The 'BuildsAssociateWorkflow' 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 thecommit 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 'BuildsWorkflow' doesn't suit the needs of your project. You can then activate the new (copied) workflow by adding it to a workflow scheme and thenassociating that scheme with your projects.

Copying and editing the 'Builds Workflow'

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralIn the displayed administration console, go to the ' ' tab .IssuesIn the left menu, go to ' ' > ' '. The ' ' page will display.Schemes Workflow Schemes Workflow SchemesClick the link. The 'View Workflows' page will display.View all workflowsLocate the and click in the column.Builds Workflow Copy OperationsEnter a and for the new (copied) workflow scheme and click the button. The new workflow will be createdName Description Copyand displayed on the 'View Workflows' page.You can now edit and activate your new workflow as needed. See and in the JIRAConfiguring Workflow Activating Workflowdocumentation 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 includethe 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 issuetransitions 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 aJIRA 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 codewithout successful builds resolving the issue. Hence, an intermediate state (e.g. 'Building') is required which a developer will only transitionthe issue into (i.e. using the commit command), if they want the issue to be resolved from that particular build.#build

Configuring your issue transitions

Automatic issue transitioning via builds is controlled by both commit commands and Bamboo-specific transition properties in JIRA, asdescribed below:

Commit Command — The is mapped to the 'Waiting for Build' transition. Hence, if you add the 'Waiting#build commit commandfor Build' transition to your workflow, your users will be able to automatically trigger the transition by using the commit#buildcommand in their commit messages.Bamboo-specific transition properties— The Bamboo-specific transition properties on the transitions that you want to be triggeredwhen 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 issuepasses, 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 issuefails, and the transition is available to the issue in its current state.

build.passed.resolution any validresolution, e.g.'Fixed'

The issue resolution will be set as specified by this property, if the transitionwith 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 propertyon each transition that you want it added to.


137

Bamboo Administrator's Guide

Atlassian OnDemand includes , its continuous integration build server. Use the search or click any of the links below to viewBamboo 3.0the relevant page in the Bamboo Administrator's Guide. You will need to use the 'Back' button on your browser to return to the BambooOnDemand 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 PlanCreating a Plan

Creating a New PlanEditing a Plan

Configuring a Plan's NotificationsConfiguring a Plan's PermissionsConfiguring Expiry of a Plan's Job Build ResultsRenaming a Plan, its Project or changing the Plan's Description

Disabling or Deleting a PlanDeleting the Results of a Plan BuildStopping an Active Plan Build

Configuring Concurrent BuildsModifying Multiple (Bulk) PlansMoving Plans to a Different ProjectSetting up Build Dependencies

Dependency Blocking StrategiesConfiguring a Stage

Creating a StageDeleting a StageEditing a Stage

Configuring a JobCreating a JobEditing a Job

Configuring a Job's RequirementsRenaming a Job or changing the Job's DescriptionConfiguring Automatic Labelling of Job Build ResultsConfiguring a Job's Build Artifacts

Configuring Artifact Sharing between JobsConfiguring Miscellaneous Settings for a Job

Disabling or Deleting a JobDeleting a Job's Current Working FilesStopping an Active Job Build

Specifying a BuilderAntCustom Command Builderdevenv.comGrailsMavenNAntPHPUnitScript BuilderUsing Global or Build-specific Variables

Defining Global Variables

Configuring Agents and Capabilities

Bamboo OnDemand only uses elastic agents.

Configuring CapabilitiesEditing a CapabilityRenaming a CapabilityViewing a Capability's Agents and Jobs

Working with Builds

Triggering a Plan BuildTriggering a Plan Build when Code is Updated

Polling the Repository for ChangesRepository Triggers the Build when Changes are Committed

Triggering a Plan Build Based on a ScheduleCron Based SchedulingSingle Daily Build


138

Triggering a Plan Build ManuallyReordering Jobs in the Build QueueMonitoring Job Builds

Configuring the Hanging Job Build EventConfiguring the Job Build Queue Timeout EventDisabling Build Monitoring

Working with Elastic Bamboo

About Elastic BambooElastic Bamboo Costs

Getting Started with Elastic BambooConfiguring Elastic Bamboo

Generating your AWS Private Key File and Certificate FileConfiguring Elastic Instances to use the EBS

Populating your EBS volumeManaging Elastic Bamboo

Managing your Elastic ImagesViewing an Elastic ImageManaging your Elastic Image ConfigurationsUpdating Elastic Images for Bamboo Upgrades

Managing your Elastic InstancesViewing an Elastic InstanceAccessing an Elastic InstanceStarting an Elastic InstanceScheduling your Elastic InstancesShutting Down an Elastic Instance

Managing your Elastic AgentsViewing your Elastic AgentsViewing your Elastic Agent Usage HistoryConfiguring Elastic Agent CapabilitiesDisabling an Elastic Agent

Running Job Builds using Elastic BambooDisabling Elastic Bamboo

Configuring Email and Instant Messaging Notifications

Configuring Notifications for a Plan and its JobsConfiguring Bamboo to use Instant Messaging

Configuring Bamboo to use Google Talk for Instant Messaging

Managing Users and Permissions

Managing Permissions for Users and GroupsGranting Plan Permissions to Users or GroupsGranting Global Permissions to Users or GroupsAllowing Anonymous Users to access Bamboo

Global Security and Permission PropertiesEnabling or Disabling Public SignupEnabling or Disabling Contact Details DisplayEnabling or Disabling Captcha for Failed Logins

Configuring System Settings

Viewing Bamboo's System InformationSpecifying Bamboo's TitleLogging in BambooEnabling GZIP CompressionEnabling Bamboo's Remote API

Working with Builds

A build is the execution of either a or a . The execution of a Plan is referred to as a 'Plan build' and that of a Job is a 'Job build'.Plan Job

A defines everything about your entire build process. Plans:Plan

consist of one or more , which are organised into one or more ;Jobs Stagescontains a single 'Default Job' in a single Stage, after ;creating a new Plandefine default settings for what gets built by Jobs in the Plan (i.e. the 'default source repository');define how the is ;Plan's build triggereddefine who will be of the Job's ;notified build resultdefine who has to view and perform various actions on the Plan and its Jobs.permission

Every plan belongs to a .Project

Projects and plans can only be configured by Bamboo administrators (see ).Creating a Plan

http://confluence.atlassian.com/display/BAMBOO030/Managing+Users+and+Permissions

http://confluence.atlassian.com/display/BAMBOO030/Managing+Permissions+for+Users+and+Groups

http://confluence.atlassian.com/display/BAMBOO030/Granting+Plan+Permissions+to+Users+or+Groups

http://confluence.atlassian.com/display/BAMBOO030/Granting+Global+Permissions+to+Users+or+Groups

http://confluence.atlassian.com/display/BAMBOO030/Allowing+Anonymous+Users+to+access+Bamboo

http://confluence.atlassian.com/display/BAMBOO030/Global+Security+and+Permission+Properties

http://confluence.atlassian.com/display/BAMBOO030/Enabling+or+Disabling+Public+Signup

http://confluence.atlassian.com/display/BAMBOO030/Enabling+or+Disabling+Contact+Details+Display

http://confluence.atlassian.com/display/BAMBOO030/Enabling+or+Disabling+Captcha+for+Failed+Logins


139

1.

Working with Builds


Bamboo User's Guide

Actioning Issues via Builds

Accessing the Builds application

Click the tab in the header. This takes you to Bamboo.Build

Bamboo User's Guide

Atlassian OnDemand includes for its continuous integration build server. Use the search or click any of the links below to viewBamboo 3.0the relevant page in the Bamboo User's Guide. You will need to use the 'Back' button on your browser to return to the Bamboo OnDemanddocumentation.

Please note, some Bamboo functionality is .restricted in Bamboo OnDemand

Search the Bamboo 3.0 documentation:

Getting Started

Using the Bamboo DashboardViewing Bamboo's Current ActivityViewing your Latest Build ResultsWorking with Favourites

Adding a Plan to your FavouritesRemoving a Plan from your Favourites

Displaying the WallboardViewing Bamboo's Agents

Working with Projects, Stages, Plans and Jobs

Working with PlansViewing a Plan's DetailsViewing the JIRA Issues linked to the Builds in a Build Plan

Working with StagesWorking with Jobs

Viewing a JobViewing a Job's Maven DependenciesViewing the Clover Coverage Summary for a Job

Working with Build Results

Viewing a Build ResultViewing the Code Changes that Triggered a BuildViewing a Build's ArtifactsViewing a Build LogViewing the Metadata for a Build ResultViewing the Clover Code-Coverage for a Build ResultViewing the JIRA Issues for a Build ResultLinking JIRA Issues to a Build

Working with Tests

Viewing Test Results for a BuildViewing a Test's HistoryViewing Test Statistics for a Job

Reporting on Plan Trends

Viewing Build Statistics for a PlanGenerating 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


140

'Time to Fix' Report'Number of Tests' Report

Reporting on Author Trends

Viewing Build Statistics for all AuthorsViewing Build Results for an AuthorGenerating 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 ResultViewing Comments about a Build ResultViewing Code Check-in Comments

Working with Labels

Labelling a Build ResultRemoving a Label from a Build ResultViewing Labelled Build ResultsViewing Popular Labels

Subscribing to RSS Feeds

Subscribing to an RSS Feed for All Build Results for All PlansSubscribing to an RSS Feed for All Build Results for a Particular PlanSubscribing to an RSS Feed for Failed Builds for All PlansSubscribing to an RSS Feed for Failed Builds for a Particular PlanSubscribing to an RSS Feed for Labelled Build Results

Working with Instant Messenger (IM) Notifications

Labelling a Build Result via IMCommenting about a Build Result via IM

Actioning Issues via Builds

If your administrator has , you will be able to action issues via builds. If the default 'Builds Workflow' is beingintegrated builds with issuesused 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

# Transition

1 Start Progress

2 Stop Progress

3 Resolve Issue

4 Close Issue

5 Reopen Issue

6 Wait for Build

7 Build Passed


141

8 Build Failed

The , and transitions are Bamboo-specific transitions:'Wait for Build' 'Build Passed' 'Build Failed'

'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build. Note, you must manually enter the commit command in your commit message to trigger the transition, ascommit command #build

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 , you can add the commit command to your commit message. Ifresolve an issue via a particular (successful) build #buildthe 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 commit command from your#buildcommit message.

Glossary

changelog

changeset

external user

issue

JIRA project

page

project

repository

review

source

space


142

user

wiki

changelog

A is a chronological list of the that were committed to a . changelog changesets repository

For more information, please see .Working with Source

changeset

A is a collection of that are committed to the at the same time. A changeset can be associated with one orchangeset source files repositorymore .In Atlassian OnDemand, a repository can be associated with , and therefore, a changeset can automatically link to anyreviews projectsassociated and .issues wiki pages

For more information, please see . Working with Source

external user

An is a user who does not have access to your company email domain, but who you allow to access your Atlassian OnDemandexternal usersite, 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 IntegrationManaging Users and Groups

issue



For more information, please see .Working with Issues

JIRA project

See in JIRA documentation.What is a Project

See also:

project

page

A is an online document within the . Each page belongs to a .page wiki space

For more information, please see .Working with the Wiki

project

In Atlassian OnDemand, a is like a container and includes the following objects if the corresponding application is available in yourprojectsite:

a JIRA projecta wiki spacea build projecta source repository

The association between these objects in a project makes it possible to automatically link between , , , ,issues wiki documents source files plan, and .changesets code reviews build result


143

For more information, please see .Creating new projects

repository

A (e.g. Subversion, Perforce or CVS) contains your . repository source code

Note: In Atlassian OnDemand, a source repository can be associated with one or more . projects


reviewYour can go through a (sometimes called , or ) either before or after beingsource review code review peer review quality assurancecommitted to a repository.

For more information, please see .Working with Reviews

See also: repository

source

Your (e.g. your source code) resides in a such as Subversion, Perforce or CVS. source repository


space

A is a group of within the . You can think of each space as a sub-site, or mini-site, each with its own home page.space pages wiki

In Atlassian OnDemand, a space can be associated with a . This allows links to be automatically created on your wiki pages, pointingprojectto associated , , and .For more information, see .issues source files changesets code reviews Working with the Wiki

user

A is the account for an individual who accesses your Atlassian OnDemand site.user

See also .External user

wiki

The is a collection of online documents, i.e. . Wikis are useful for collaboration, information sharing and documentation.wiki pages

For more information, see .Working with the Wiki

Atlassian OnDemand release summary

20 February 2012

Changes in this week:

Accessing administration menus fasterGreenHopper upgradeBonfire upgradeNew JIRA OnDemand features

Sharing issuesMentioning usersCreating and editing issues rapidlySearching for issues based on their history

Accessing administration menus faster

Type from anywhere in your Atlassian OnDemand site to bring up the box and start typing the name of the 'g' + 'g' Administration Searchadministration menus you want to work with.

Please be aware of the following limitations:


144

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 thesearch 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 thehighly 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


145

Have you been sharing pages in Confluence with the button? Now you can share JIRA issues with other people in the same way.Share

When viewing an issue on the 'view issue' page or a search result on the issue navigator, type or click the button at the top-right,s Shareand specify OnDemand users or any email address of people you want to share the issues with. Recipients will receive an email with the linkto 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 emailnotifications about the issue automatically.

To do this, type '@' in an issue's or field, then start typing the user's name, and then select the user from theDescription Commentsuggested 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 . Therefore, your pages are not reloadedseparate formany more when you start creating or editing an issue or sub-task.Customise what fields you want to seeYou can customise the / dialog boxes to display only the fields you use most often. To do this, click the Create Issue Edit Issue

button and remove or add fields as you wish. Your settings are saved for future usage automatically.Configure FieldsCreating a series of issues with similar optionsIf you want to create multiple issues with similar field values, use the check box before clicking the button.Create another CreateJIRA will then create your issue and automatically pre-populate a new dialog box with your previous field values. The Create Issue

field and attachments are not carried across.Summary

Tip: The keyboard shortcut for creating issues is and that for editing issues is . 'c' 'e'


146

Searching for issues based on their history

'CHANGED' operator introduced

You can use the operator to search for issues with specific field changes. This operator accepts the optional predicates , CHANGED FROM, , , , and , and TO ON DURING BEFORE AFTER BY can be used on the , , , , and Status Assignee Priority Reporter Resolution 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 field was changed to . You can see it in real use via .Fix Version "5.0" this link

The following example is a more complex JQL query. It will find any issues whose field value was at some point butStatus "In QA Review"changed to , by user between the start and end of the current week."QA Rejected" freddo

status changed FROM "In QA Review" TO "QA Rejected" BY freddo AFTER startOfWeek() BEFOREendOfWeek()

'WAS' operator enhanced

You can now use the operator to work with the field. For example, the following JQL query:WAS Fix Version

fixVersion WAS 4.4

Will find any issues whose field was at some point (or currently is) set to .Fix Version 4.4

Known Issues and Workarounds

Search previous features:

https://jira.atlassian.com/secure/IssueNavigator.jspa?reset=true&jqlQuery=project+%3D+JIRA+AND+fixVersion+changed+TO+%225.0%22


147

February 2012 — Commit commands changes; Improved FishEye and Crucible search; Repo commit graph; JIRAtransitions 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; UpdatedGitHub/Bitbucket connector;November 2011 — Changes of notification email prefixes; Domain name changes;The launchKnown Issues and Workarounds

February 2012

This week:

Commit commands changes; Improved FishEye and Crucible search; Repo commit graph; JIRA transitions in Crucible; andmore.

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 willmatch 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 CommandsImproved FishEye/Crucible quick search with pattern matches against CamelCase strings for files and directories, and an improvedlook 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 revisionspage 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 appearwhen 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:


148

JIRA transitions in Crucible:

Review reminders:

February 2012 - FishEye Crucible 2.7 upgrade notes


149

On this page:

Summary of FishEye and Crucible releasesFishEye 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 . See below.OnDemand commit commands Changes to Commit CommandsJIRA FishEye Plugin ImprovementsSmall 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 is selected).All

Does not apply to FishEye OnDemand:

Managed Git RepositoriesWeb HooksSmall Improvements

FishEye can now run on Java 7Improved user interface for the administration screensImproved plugin points for developers

FishEye 2.6 — 6 June 2011 ( )release notes

Applies to FishEye OnDemand:

Repository Commit GraphImproved Quick Search – Please note, this only applies to the quick search in FishEye OnDemand, not the Atlassian OnDemandquick search available in the navigation bar.Redesigned HTML Emails

Dashboard and Navigation Improvements

Does not apply to FishEye OnDemand:

User Management via JIRAImproved Support for Git BranchesGit Commit Authors include Email AddressMercurial Indexing Improvements

Crucible 2.7 — 7 September 2011 ( )release notes

Applies to Crucible OnDemand:

JIRA Transitions in CrucibleReview 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 SearchHTML Emails for ReviewsDashboard and Navigation ImprovementsReview Creation without Metadata ChangesImproved Patch Anchoring

Does not apply to Crucible OnDemand:

SQL Server SupportOracle Support

Changes to Commit Commands

http://confluence.atlassian.com/display/FISHEYE/FishEye+2.7+Release+Notes


http://confluence.atlassian.com/display/CRUCIBLE/Crucible+2.7+Release+Notes







150

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 inthe 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 workflowtransitions. Commit commands for custom workflow transitionshad to be manually configured.

FishEye will automatically find and match the prefix for an issuetransition, regardless of whether it is a default or custom JIRAtransition.For example, if you have transition name with spaces, such as

then specifying is sufficient. Hyphensfinish work #finishreplace spaces: #finish-work

Commit commands allowed the resolution to be set whenresolving an issue.

Smart commits do not allow the resolution to be set when resolvingan issue.

Logging work – a work log description can be saved whenlogging work.

Smart commits currently do not allow a work log description to besaved when logging work.

FE-3757 - to see issue detailsAuthenticate

Logging work – work can be logged with multiple timeparameters (e.g. 4d 2h).

Smart commits currently only allows a single time parameter. If morethan one time parameter is entered, then only the first is recorded.

FE-3885 - to see issue detailsAuthenticate

Triggering builds – builds can be triggered via commitcommands.

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 tab as well as the tab for the referenced issue.Commits ActivityThere used to be separate tabs for bitbucket and GitHub. The UI has been improved as well.



https://jira.atlassian.com/browse/FE-3757

http://confluence.atlassian.com/plugins/servlet/applinks/oauth/login-dance/authorize?applicationLinkID=144880e9-a353-312f-9412-ed028e8166fa

https://jira.atlassian.com/browse/FE-3885

http://confluence.atlassian.com/plugins/servlet/applinks/oauth/login-dance/authorize?applicationLinkID=144880e9-a353-312f-9412-ed028e8166fa


151

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 thefollowing release notes for an overview of the new features:

Bonfire 1.7.1 Release NotesBonfire 1.6.2 Release NotesBonfire 1.5.1 Release NotesBonfire 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 thoseapplications. The most common cause of this is when the Atlassian IDE Connector is set up to use incorrect credentials, for example due tothe 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 FAQ.Users are locked out of FishEye and Crucible REST APIs

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:


152

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 beconverted into a Confluence widget displaying the video.Find-and-replace feature in the editor. Use Ctrl + F to try itNew 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: This will?i18ntranslate=onallow you to see the key name for each UI element to aid translations. Turn it off by appending ?i18ntranslate=offOther improvements, including new icons, improved UI for favourites, a global plugin and macro timeout setting, and the ability touse 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 notethat 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 bothBitbucket and GitHub repositories via the same administration screen. We've simplified the setup process as well.

For instructions on how to use this, see and .Integrating Bitbucket with JIRA OnDemand 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 ; the prefix is used for repository watches and for[JIRA] [FishEye] [Crucible]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

http://confluence.atlassian.com/display/AOD/Integrating+Bitbucket+with+JIRA+OnDemand

http://confluence.atlassian.com/display/AOD/Integrating+GitHub+with+JIRA+OnDemand


153

your business requirements change. For a brief introduction of these applications and what they can do for your team, see:

Overview from www.atlassian.comOverview in this documentationChoosing 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 AtlassianOnDemand.

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 and Working with Google Apps Integration 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 relatedinformation. Creating links is as simple as inserting text into your application. For example, you can link a source file with a JIRA issueby 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 andJIRA Studio will be phased out, however we have a migration plan for existing customers that allows you to continue using the serviceand 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 andissues.

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 Googleintegration 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 box by typing from anywhere in your Atlassian OnDemand siteAdministration Search 'g' + 'g'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 thesearch box, but searching does not work.

Users continue receiving email notifications from applications for which access has been revoked

http://www.atlassian.com/software/ondemand/overview

http://www.atlassian.com


http://www.atlassian.com/software/confluence/tour/

http://www.atlassian.com/licensing/ondemand-faq-existing-customers



154

After you revoke a user's access to an application in the Application Access page of the administration console, the user will still be receivingnotifications 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 allgroups, continues to receive notifications until the user is removed from the notification groups. That's the way JIRA works, so we'rerespecting that.

Workaround: N/A.

Support

Restricted Functions in Atlassian OnDemand

Supported browsers


Atlassian OnDemand licensing

Support Policies

Atlassian OnDemand Plugin Policy

About Your Data

Maintenance windows

Restricted Functions in Atlassian OnDemandAtlassian OnDemand contains fully functional versions of JIRA, Confluence, FishEye, Crucible, Subversion and Bamboo. However, in orderto securely integrate these applications in a hosted environment, some of the functions that are available in the installable versions of theproducts are restricted in Atlassian OnDemand. This means,

The function is pre-configured and , or,cannot be altered by anyoneThe function can only be — changes can be requested byconfigured by Atlassian OnDemand Technical Supportfiling a ticket at under the 'OnDemand' project.https://support.atlassian.com

The functions that are restricted in Atlassian OnDemand are listed below.

On this page:

Atlassian OnDemand GeneralJIRAConfluenceFishEye and CrucibleBambooSubversion

Atlassian OnDemand General

Imports — Please read for information on supported imports for Atlassian OnDemand.Importing DataThemes — 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 for theAtlassian OnDemand Plugin Policylist of supported plugins. Requests for additional plugins should be created as a feature request at underhttps://studio.atlassian.comthe Atlassian OnDemand project.Alternate Languages —There's no full support for alternate languages except English (US) at the moment. Please follow JST-801for updates on this feature.Backups — Refer to our policy.Data BackupsCustom Domains — Your instance will be accessible at , where https://<account_name>.atlassian.net <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

https://support.atlassian.com/browse/JST

https://studio.atlassian.com



155

Generally speaking, all functions performed by the in download JIRA are restricted in Atlassian OnDemand. The'JIRA System Administrator'following table lists all of the functions that are restricted in Atlassian OnDemand, even to users with . The tableadministrator permissionsbelow also lists whether the function can be configured by Atlassian OnDemand Technical Support on request. If not, then it is unavailablefor configuration in Atlassian OnDemand.

RestrictedFunction

Configurableon Request?

Notes

GeneralConfiguration

Advancedsettings

NO

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 prefix is not configurable.[JIRA]

POP/IMAP Mailservers

NO Atlassian OnDemand includes a mail service configured to create issue comments from replies toJIRA notifications. Setting up a JIRA service to create issues and comments from an externalPOP/IMAP server is not currently supported.

Configure a CVSsource coderepository

NO CVS repositories are not supported.

Configurelisteners

NO

Configureservices

NO

Customisingsource files

NO

Customising emailcontent

NO The procedure for sent in notification messages requires editing Velocitycustomising email contentfiles within the JIRA webapp. This makes it a special case of "customising source files". See

and for feature requests to allow customisation of email contents through theJST-1791 JRA-7266web UI.

Change the indexpath

NO

Run the integritychecker

NO

Configure loggingand profilinginformation

NO

Access thescheduler

NO

Export/backupJIRA 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 OnDemandaccount. Commercial customers can request an export by filing a ticket at

.https://support.atlassian.com

Import data fromexternal systems (CSV / Excel)

NO Please read for information on supported imports for Atlassian OnDemand.Importing Data


http://jira.atlassian.com/browse/JRA-7266



156

Import XMLworkflows intoJIRA

NO

Plugins NO Only default plugins are allowed. Please see for the list ofAtlassian OnDemand Plugin Policysupported plugins.

Plugin Repository NO Only default plugins are allowed. Please see for the list ofAtlassian OnDemand Plugin Policysupported plugins.

Disableattachments, Set theattachment pathor size limit

NO Attachments enabled by default, maximum size set to 100MB.

Run Jelly scripts NO Please see on the status.JST-1439

Configure LDAPintegration

NO

Configure trustedapplications

NO

Configureapplication links

NO

Configure issuelinks

NO

Access licensedetails

NO

Modify SysAdminusers & 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 in download Confluence are restricted in AtlassianConfluence 'System Administrator'OnDemand. The following table lists all of the functions that are restricted in Atlassian OnDemand, even to users with administrator

. The table also lists whether the function can be configured by Atlassian OnDemand Technical Support on request. If not, then itpermissionsis unavailable for configuration in Atlassian OnDemand.

Restricted Function Configurable onRequest?

Notes

Permissions NO Confluence 'System Administrator' permission is not available in AtlassianOnDemand.

General Configuration

Server Base URLExternal usermanagementPublic Signup

NO Public signup is managed via JIRA.

Daily Backup Admin NO Backups are managed globally.


https://developer.atlassian.com/display/JIRADEV/JIRA+Remote+API+Reference


157

Plugins NO Only default plugins are allowed. Please see forAtlassian OnDemand Plugin Policythe list of supported plugins.

Plugin Repository NO Only default plugins are allowed. Please see forAtlassian OnDemand Plugin Policythe list of supported plugins.

Mail Servers NO Atlassian OnDemand comes with an internal SMTP server configured to sendnotifications.The prefix is not configurable.[Confluence]

Mail Archiving (at thespace level)

NO

User Macros NO

Attachment Storage NO Attachments enabled by default, maximum size set to 10MB.

Look and Feel

LayoutsCustom CSS

NO As Confluence uses a custom theme, it is not possible to .customise the layout

It is also not possible to .style Confluence with CSS

Custom HTML NO

Backup & Restore Backup - YESRestore - NO

Confluence exports can be requested by filing a ticket at .https://support.atlassian.com

SnipSnap Import NO

Logging and Profiling NO

Cluster Configuration NO

Remote API (XML-RPC,SOAP)

YES This is already enabled by default. For more information, see Confluence Remote.API

External Gadgets NO

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. Wehave configured the administration options for these applications to offer the greatest flexibility and security for our customers. To requestchanges to the default FishEye/Crucible configuration, please file a feature request at under the Atlassianhttps://studio.atlassian.comOnDemand 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 . Theadministrator permissionstable also lists whether the function can be configured by Atlassian OnDemand Technical Support on request (if not, then it is unavailable forconfiguration in Atlassian OnDemand).

RestrictedFunction


Notes

Configurebuilders

NO Bamboo OnDemand only runs builds using elastic agents. Hence, capabilities can only be configuredby .using a custom image

http://confluence.atlassian.com/display/DOC/Customising+Site+and+Space+Layouts


https://developer.atlassian.com/display/CONFDEV/Confluence+Remote+API+Reference



https://developer.atlassian.com/display/FECRUDEV/FishEye+and+Crucible+Remote+API+Reference


158

ConfigureJDKs


ConfigureServerCapabilities


SupportCustomElasticImages

NO Due to its wide scope, support of customised elastic images is not provided. We recommend using thedefault image with an instead. You can customise the default image via scripts stored onEBS volumeyour EBS snapshot during startup.

PluginInstallation

NO

ConfigureUsers

NO Bamboo users are managed via Atlassian OnDemand's users and groups.

ConfigureGroups

NO Bamboo user groups are managed via Atlassian OnDemand's users and groups.

ConfigureSecuritySettings

NO

ConfigureMail Server

NO Atlassian OnDemand comes with an internal SMTP server configured to send notifications.The prefix is not configurable.[Bamboo]

IM settings NO This feature can be discussed .here

DatabaseConfiguration

NO

LicenseDetails

NO

Indexing NO

ScheduledBackups

NO

Export Data NO

Import Data NO

Create/DeleteProjects

NO JIRA OnDemand manages the projects for all applications. To create or delete projects, go to the page.Administration > General > Projects

Clover plugin NO Clover is not included by Bamboo OnDemand, and the integration of Clover with Bamboo OnDemand isnot supported. The screen captures in the referenced Bamboo documentation might display Cloverinterfaces and they only apply to the download Bamboo.

Subversion

While you can access many of the Subversion functions via the , access to the administration console in Subversion iscommand line clientunavailable, meaning that functions like and cannot be used.svnadmin dump svnadmin load

RestrictedFunction


Notes



159

1. 2.

CustomHooks

NO A pre-commit hook is available that requires a JIRA issue key. Custom hooks are not available at themoment due to reasons listed . If you have suggestions on hooks you'd like to see in the future,hereplease request the feature .here

Backups Full - Yes Subversion full exports can be requested by filing a ticket at . It's alsohttps://support.atlassian.compossible to use to mirror the repository.svnsync

Supported browsers

This page describes the supported browsers for Atlassian OnDemand.

Key: = Supported; = Not Supported; = Supported but not recommended or with restrictions;

Your site's applications Microsoft InternetExplorer

Mozilla Firefox Safari Chrome

Confluence only 9.0

8.0

Latest stableversion



JIRA 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

8.0

3.6.x [1]

3.5.x

3.0.xJIRA + Confluence + FishEye/Crucible/SVN+ Bamboo

Notes

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.0Mobiles 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 benecessary right now.

Atlassian OnDemand is composed of individual applications that are integrated in a hosted environment. As such, the support for webbrowsers 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 Versionspage.

The following section lists the End of Support pages for the individual applications.

BambooCrucibleConfluenceFishEyeJIRA


https://studio.atlassian.com/secure/CreateIssue.jspa?pid=10073&issuetype=4


http://confluence.atlassian.com/pages/viewpage.action?pageId=203393680

http://confluence.atlassian.com/pages/editpage.action?pageId=253231682#SupportedBrowsers-1


160


The following tables display the current versions of the applications running in Atlassian OnDemand.

Please also see for information on functions that are restricted in Atlassian OnDemand.Restricted Functions 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 2011Confluence 4.1 Release NotesConfluence 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

(effectively the same as Bamboo 3.0)

October 2011 Bamboo 3.0 Release Notes

Repository (Subversion) Subversion 1.6.11 October 2011 Subversion Project Home

Single Sign-on (Crowd) Crowd 2.2

(effectively the same as Crowd 2.2)

October 2011 Crowd 2.2.2 Release Notes

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 theequivalent version of the downloadable product is released. However, it might take a few weeks for the application versionto become available to you, as each application version must undergo rigorous testing first before we apply it to AtlassianOnDemand. 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 to keepOnDemand on Twitterup-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

under the 'OnDemand' project.our support system

Atlassian OnDemand licensingAtlassian OnDemand licensing is user-based. This means that the pricing for your site is determined by the number of users that you want tohave 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/pricingOrdering FAQ: http://www.atlassian.com/licensing/ondemand

http://subversion.tigris.org/



http://www.atlassian.com/software/ondemand/pricing



161

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 administration console. For detailed instructions, see Application Access 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 accessUpgrade your account — if you do not want to remove access from users, you may wish to consider upgrading your account to addmore 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 touchwith our helpful support engineers. Please choose the relevant page below to find out more.

Bug Fixing PolicyHow to Report a Security IssueNew Features PolicySecurity Advisory Publishing PolicySecurity Update PolicySeverity Levels for Security IssuesUpdate Policy

To request support from Atlassian, please raise a support issue in our online support system. To do this, visit , log insupport.atlassian.com(creating an account if need be) and create an issue under the OnDemand project. Our friendly support engineers will get right back to youwith an answer.

See for an overview of the scope of support, operation hours and more.How to Get Legendary Support from Atlassian

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 systemproviding as much information as possible about how to replicate the problem you are experiencing. We will replicate the bug to verify, thenlodge 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.comfor the stand-alone products and for JIRA Studio and Atlassian OnDemand.http://studio.atlassian.com

When raising a new bug, you should rate the priority of a bug according to our . Customers a filed bug inJIRA usage guidelines should watchorder 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 ourcustomers. 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 toperform 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:


http://confluence.atlassian.com/display/Support/How+to+Get+Legendary+Support+from+Atlassian

http://jira.atlassian.com



http://studio.atlassian.com/browse/JST


162

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 providefeedback 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 thebug from the customer's perspective, how prevalent the bug is and whether roadmap features may render the bug obsolete. We combine thiswith 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 for more support-related information.How to Get Legendary Support from Atlassian

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 in the relevant project.http://jira.atlassian.com

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 patchout as soon as possible.

If you discover a security vulnerability, please attempt to create a test case that proves this vulnerability locally beforeopening either a bug or a support issue. When creating an issue, please include information on how the vulnerability can bereproduced; see our for general bug reporting guidelines. We will prioritise fixing the reported vulnerabilityBug Fixing Policyif your report has information on how the vulnerability can be exploited.

Further reading


New Features Policy

Summary

We encourage and display customer comments and votes openly in our issue tracking systems, and http://jira.atlassian.com.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 is distinct from our Feature Request process.Atlassian Bug Fixing PolicyAtlassian 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 upcomingrelease only. We maintain roadmaps for more distant releases internally, but because these roadmaps are often pre-empted by changingcustomer demands, we do not publish them.

How Atlassian Chooses What to Implement

In every we to implement highly requested features, but it is not the only determining factor. Other factors include:major release aim

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 the requested feature is (some issues gain in popularity rapidly, allowing little time to plan their implementation).well definedOur long-term for the product.strategic vision

How to Contribute to Feature Development

Influencing Atlassian's release cycleWe encourage our customers to vote on feature requests in JIRA. The current tally of votes is available online in our issue tracking systems,



http://studio.atlassian.com


163

and . Find out if your improvement request . If it does, please vote for it. Ifhttp://jira.atlassian.com http://studio.atlassian.com already existsyou do not find it, online.create a new feature or improvement request

Extending Atlassian ProductsAtlassian products have powerful and flexible extension APIs. If you would like to see a particular feature implemented, it may be possible todevelop the feature as a plugin. Documentation regarding the is available. Advice on extending either product may be availableplugin APIson the user mailing-lists, or at .Atlassian Answers

If you require significant customisations, you may wish to get in touch with our . They specialise in extending Atlassian products andpartnerscan do this work for you. If you are interested, please .contact us

Further reading


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 followingmechanisms:

We will post a security advisory in the latest documentation of the affected product at the same time as releasing a fix for thevulnerability. 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 for the product concerned.'Technical Alerts' mailing list

To manage your email subscriptions and ensure you are on this list, please go to and click 'Email Prefs' nearNote: my.atlassian.comthe top right of the page.If the person who reported the vulnerability wants to publish an advisory through some other agency, such as , we will assist inCERTthe 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 ) we will send an early warning to the 'Technical Alerts'severity levelsmailing list approximately one week before releasing the fix. This early warning is in addition to the security advisory itself, describedabove.However, if the vulnerability is publicly known or being exploited, we will release the security advisory and patches as soon aspossible, potentially without early warning.

Further reading


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 as well.Atlassian OnDemand Update Policy

The development of Atlassian OnDemand can be followed on .our bug tracking system

Further reading

See for more support-related information.Atlassian Support Offerings

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 specificvulnerability. CVSS is an industry standard vulnerability metric. You can learn more about CVSS at web site.FIRST.org

CVSS scores are mapped into the following severity ratings:

CriticalHighMediumLow

An approximate mapping guideline is as follows:

CVSS score range Severity in advisory


http://studio.atlassian.com

https://developer.atlassian.com/display/DOCS/Developing your Plugin using the Atlassian Plugin SDK

https://answers.atlassian.com

http://www.atlassian.com/about/partners/

http://my.atlassian.com

http://www.cert.org/

https://studio.atlassian.com/browse/JST/

http://www.first.org/cvss/cvss-guide.html


164

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 mindthat 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 orknowledge about individual victims, and does not need to persuade a target user, for example via social engineering, into performingany special functions.

For critical vulnerabilities, is advised that you patch or upgrade as soon as possible, unless you have other mitigating measures in place. Forexample, 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 usuallyrequires local or physical system access.

Further reading


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, Atlassianwill 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 toincorporate 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 unableto perform their normal functions).An update is technically feasible (i.e. it doesn't require a major architectural change).ORThe 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

https://studio.atlassian.com/browse/JST/


165

See for more support-related information.Atlassian Support Offerings

Atlassian OnDemand Plugin Policy

Atlassian OnDemand comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existingplugins. The commercial and bundled plugins listed below are included with the service, and can be enabled, disabled and/or configured viayour OnDemand administration console.

On this page:

Plugin BundlingAdd-Ons in the Future

Commercial PluginsHosted Commercial PluginsDirect Purchase Commercial Plugins

Bundled PluginsIssues (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 integratetheir instances. We are currently working on ways to provide add-ons independent of the current in-process plugin framework. In this way, wewill provide hosted add-ons that are stable, secure, and can be developed and maintained by their contributors. As these efforts begin toyield 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 informationon what's coming and how they can participate.

Commercial Plugins

The following third-party plugins are available in Atlassian OnDemand under . This means that the plugins are installedcommercial licensesin 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 bylogging into your account at .http://my.atlassian.com

Family / Base product Add-ons

ConfluenceGliffyTeam Calendars

JIRABonfireGliffyGreenHopper

Direct Purchase Commercial Plugins

Licenses for the following products must be purchased directly from the plugin vendor. See the individual products below for moreinformation.

The . This plugin enables you to track time using JIRA. A 30-day trial for Tempo is enabled as part of theTempo Plugin for JIRA30-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 FAQThe Balsamiq Mockups for JIRA and Confluence plugins. A 30-day trial for Balsamiq (JIRA and Confluence) is available if you wantto 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 pluginBalsamiq 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 as needed. disable or enable a JIRA plugin

Flowdock for JIRAGreenHopperCustomWare Get Satisfaction Connector PluginCustomWare Sauce Labs Connector Plugin





http://www.customware.net/products/connectors/jira_and_salesforce.html




http://wiki.customware.net/repository/display/AtlassianPlugins/CustomWare+Sauce+Labs+Connector+Plugin


166

1.

2.

3.

4.

CustomWare uTest Connector PluginCustomWare Zendesk Connector PluginDVCS Connector PluginJIRA Bamboo PluginJIRA Calendar PluginJIRA Charting PluginJIRA FishEye PluginJIRA Miscellaneous Workflow Extensions PluginJIRA Suite Utilities PluginJIRA Toolkit PluginJIRA Timesheet Report and Portlet PluginJIRA Wallboards PluginZephyr Test Management Plugin

Wiki (Confluence)

The following plugins are installed on Confluence OnDemand. You can as needed.disable or enable a Confluence plugin

Content Formatting MacrosTable Plugin

Builds (Bamboo)

The is bundled with Bamboo and enabled by default.Auto-Favourite Plugin

Reviews (Crucible)

While Crucible , we do not currently offer any plugins for Crucible.boasts a plugin API

Third-Party Plugin Process

JIRA Studio comes with . Customers are not permitted to install new plugins or remove existing plugins.a set of pre-defined plugins

Requests for additional plugins should be created as feature requests in the 'JIRA Studio' project on . Plugins willhttps://studio.atlassian.combe 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 theJIRA 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,

Create a feature request in the 'JIRA Studio' project on , if one doesn't already exist. Thishttps://studio.atlassian.comwill notify the team and product manager of the desire to bundle the plugin. Please include a link to the plugin's pageon plugins.atlassian.com.Create a support request in the 'JIRA Studio' project on to have the plugin installed on the http://support.atlassian.com

instance, and have a user created with administrative access so you can test the plugin withStudio Plugin TestingJIRA Studio.Once you verify that the plugin works with JIRA Studio, update the feature request on to note that the pluginStACappears compatible.The feature request will then be placed into the feature backlog for JIRA Studio development. We can not guaranteethat any given plugin will be certified and bundled with a future release, but will prioritise bundling of future pluginsbased on customer interest. Plugin vendors who are seeing interest from customers should encourage thesecustomers to vote on the feature request at .StAC

Unless otherwise stated, bundled third-party plugins are not considered "supported" by Atlassian, and support and futureversion 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 websiteor order form.

About Your Data

This page contains information on the deletion policy for Atlassian OnDemand.

On this page:

Data backupsData deletion policy

What happens if I want to delete my Atlassian OnDemand instance?

http://wiki.customware.net/repository/display/AtlassianPlugins/CustomWare+uTest+Connector+Plugin

http://wiki.customware.net/repository/display/AtlassianPlugins/Zendesk+Connector+Plugin














https://studio.atlassian.com/browse/JST



http://plugintesting.jira.com/




167

1. 2. 3.

4.

Data retentionRequesting a data exportHow to claim accountsHow 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 ourOnDemand platform backups are stored at a location separate from the data center. Use of backup data to roll back changes to applicationdata 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:

Cancel your subscription. Your OnDemand instance will remain active until the end of your final subscription period.Once your subscription period is finished, your instance will be deactivated shortly afterward.Once your instance is deactivated, Atlassian will retain your image and its data for 15 days. During this time, you can have yourinstance reactivated by renewing your subscription.Once 15 days has elapsed after deactivation, Atlassian will delete the system image and all of its data. Once this is done, the datacannot be recovered.

Atlassian will not delete any of your data stored in Google Apps Marketplace, such as users or information in your GoogleApps 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 isdone, 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 isworking on a customer-facing backup manager and will release it shortly. The issue is tracked here: JST-5677. Pleasewatch 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-timeexport 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 ofyour final subscription period. You can request this by submitting a .support request

If you are in need of a Confluence backup, you can and the assistance of our support team is notproduce a space backup at any timeneeded, 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 instancereactivated 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. YourOnDemand 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 doesnot 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




168

at the times listed below.maintenance windows

Your region Window

APAC every Monday at 20:00 - 22:00, Sydney time

EMEA

(including India)

every Monday at 00:00 - 02:00, Geneva time

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 we need to deviate from the weeklyunlessschedule.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.comFollow us on Twitter: We will tweet any maintenance scheduled outside of the weekly regular windows as well as any outages withthe account ( ).@OnDemandStatus 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 . To requestAnswers from the communitysupport, .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

http://my.atlassian.com/

http://twitter.com/ondemandstatus

https://answers.atlassian.com/tags/jira-studio/



169

Configuration and Administration

Can I use a custom Elastic Bamboo image?Subversion is constantly asking users to re-authenticate and failing with the correct credentialsCan 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 APIsI cannot log in using my Google Apps accountI cannot find my applications after adding themDo 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 browsersAbout Your DataAtlassian OnDemand Application VersionsRestricted Functions in Atlassian OnDemandAtlassian OnDemand licensingAtlassian OnDemand Plugin PolicySupport 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?


170

1.

2. 3.

1. 2.

3.

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 byediting the JIRA workflow and removing the flag from the step:jira.issue.editable Closed

If you are using the default workflow, copy the workflow and edit the copy. If you are already using a customised workflow,jiracreate a draft of it and edit the draft.In the workflow, remove the flag as described in the .jira.issue.editable JIRA workflow documentationActivate the workflow by creating a Workflow Scheme that uses your edited workflow, and associating the workflow scheme with therelevant projects.

You will now be able to edit or the issues.bulk edit

How can I prevent certain users seeing certain content?

You can use the following options to restrict access:

Restrict application access, i.e. licenses. Users without the access to a particular application cannot log in to it.Restrict issue visibility to just the reporter and some group. For instance you may wish to let end users raise issues, and not seeissues raised by other users. This can be achieved by creating an and applying it to the project.issue security schemeDivide users into groups, and restrict which projects a group can see. For instance one might have a Finance project that only

people should be able to see. This can be achieved by defining a new group for the finance department and configuringfinancepermissions for the new group in each application as needed. For details, see the page.Managing application permissions

How do I access my Subversion repository?

Accessing the Subversion repository

You may view your repository and code activity via the ' ' tab.Source

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 is the account name that you provided at signup.<account_name>

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 " " online Subversion reference containsVersion Control with Subversion (Pilato, Collins-Sussman, Fitzpatrick; 2004 O'Reilly)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 in Serf withbugreverse 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 under the OnDemand project. You may need to if you do not have one already.https://studio.atlassian.com create an account

Please also see ' ' for further details on how we handle feature requests and bugs.How we choose what to implement

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

http://www.atlassian.com/software/jira/docs/latest/workflow.html#uneditable_steps

http://www.atlassian.com/software/jira/docs/v3.13/activating_workflow.html

http://www.atlassian.com/software/jira/docs/v3.13/bulkoperations.html

http://svnbook.red-bean.com/

http://subversion.tigris.org/issues/show_bug.cgi?id=3979


https://studio.atlassian.com/secure/Signup%21default.jspa


171

1. 2.

a.

b.

c.

1. 2.

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 maintainany issues that are related to the code you are changing. See for more details .Using Smart Commits

This functionality is currently only available for Subversion repositories and does not work with Bitbucket or GitHub integration. If you'd like tosee 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 separatefrom the main codebase. These modules are often not large enough to warrant their own JIRA project or Confluence space. In this case it isdesirable to have just a FishEye module (under the 'Source' tab) for viewing the source, with no other references to the module in the projectlist 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 theprojects that use the common module.

To set the JIRA project and Confluence space invisible:

Create an OnDemand project (eg. ) and go to the JIRA project configuration page.COMMONIn the new project's admin section:

In the People section, find the row, click and remove the groups from all roles. ThisProject Roles View memberseffectively makes the JIRA project invisible everywhere except in the admin section.Click , then , and revoke the 'View' permission from all groups. This makes the ConfluenceSpace Admin Permissionsspace invisible to everyone except the user who created the project.Click and hide the Issues and Wiki tabs.Manage Project Tabs

The project will now be invisible except for within the 'Source' tab.

Now for each project that uses the common module:

Go to that project's OnDemand administration page and on the 'Subversion Repository' line and click SelectFor 'FishEye repository key', enter the module name (eg. ) and add it as a non-primary association.COMMON

Now any commits in the codebase that reference an issue key will appear on the referenced issue's 'Source' tab.COMMON

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.

/wikihttps://<account_name>.atlassian.netwhere is the account name of your OnDemand site.<account_name>

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 is the account name you provided at sign-up.account_name

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 automaticallycreated 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 automaticallycreated 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 existingprojects.

See the page for information about what an OnDemand project is.project

Configuration and Administration FAQ

https://studio.atlassian.com/browse/BBC-123


172

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 credentialsCan 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 APIsI cannot log in using my Google Apps accountI cannot find my applications after adding themDo you support SSL?

Other FAQs?

Don't know how to use something in OnDemand? Try the .Usage FAQHave a question about Google Apps integration? Try the .Google Apps Integration FAQ

Can I use a custom Elastic Bamboo image?

The Atlassian is used to create elastic agents for your Bamboo OnDemand. This means that all elastic agents will inheritdefault imagecapabilities from the default image.

If you want to use a custom Elastic Bamboo image, you can create one by following the instructions in the . However,Bamboo documentationplease note that we custom elastic images in OnDemand.do not support

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 agentversion. 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 OnDemandon the page.Atlassian OnDemand Application Versions

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 owncustom image, as creating a custom image is not a trivial process. You do not need to update your image each timeBamboo OnDemand is upgraded if you use this method. You can read about EBS volumes and reasons for using them inthe .Bamboo documentation

Subversion is constantly asking users to re-authenticate and failing with the correctcredentials

Certains user groups of Subversion may experience authentication issues such as this:

Authentication realm: <https://example.jira.com:443> Subversion RepositoryPassword for 'jturner':Authentication realm: <https://example.jira.com:443> Subversion RepositoryUsername: jturnerPassword for 'jturner':Authentication realm: <https://example.jira.com:443> Subversion RepositoryUsername: svn: PROPFIND of '/svntest': authorization failed (https://example.jira.com)

This may be due to a configuration issue on your Subversion permissions. Subversion clients require access on the rootunnecessary readpath.

http://subversion.tigris.org/issues/show_bug.cgi?id=3242


173

To workaround this problem, ensure that a group which all Subversion users belong to (such as ) has access to the root path. Theusers readpermission from the root path will be inherited by your project folders. You can then the permission under each project. See alsorevoke readhow to set permissions for new projects.default

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 yoursite. See for further details.Configuring the look and feel

If your site has multiple OnDemand applications, changes may not apply to all applications, e.g. the colours of the links and headers incontent 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 for the list of installed plugins and instructions on how to request plugins.Atlassian OnDemand Plugin Policy

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 supportedlanguage. Please follow for updates.JST-801

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 thedownloadable version of these products.

JIRA — XML-RPC and SOAP APIs. Read more about the .JIRA Remote APIConfluence — XML-RPC and SOAP APIs. Read more about the . Confluence Remote APIFishEye — 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 under the OnDemandhttps://support.atlassian.comproject.

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 provides 'EBS volumes' which can attach to EC2 instances. EBS volumes (and the 'EBS snapshots'Elastic Block Store (EBS)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 repositoryartifacts), you can add these to an EBS volume. From this volume, you can create an EBS snapshot, which effectively records the 'state' ofan 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 . You will also need to Bamboo documentation and attach your private key and certificate file. Our support team will copy these files to the EC2 directory of yourcreate a support ticket

OnDemand instance and configure Bamboo to use those files.

Related topics


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 command.svnsync




https://developer.atlassian.com/display/JIRADEV/JIRA+Remote+API+Reference


https://developer.atlassian.com/display/FECRUDEV/FishEye+and+Crucible+Remote+API+Reference


http://aws.amazon.com/ebs/



174

For example:

$ mkdir backupsvn$ svnadmin create backupsvn$ cat > backupsvn/hooks/pre-revprop-change << EOF#!/bin/shEOF$ 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`/backupsvnCommitted revision 1.Copied properties for revision 1.Committed revision 2.Copied properties for revision 2.Committed revision 3.Copied properties for revision 3....

See for a full overview of the process.this write-up

If you find your sync is timing out after an hour or so, you may need to adjust the setting in your SVN client http-timeout 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 customersHow 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, orwho 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 and enjoy Google Apps integration as soon as your OnDemand site is live.Marketplace

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 willdepend on Google for user account management.

See for more information.Integrating OnDemand with Google Apps

How do you evaluate OnDemand with Google Apps integration?

This can be done via the OnDemand listing on .Google Apps Marketplace

http://blogs.collab.net/subversion/2007/08/mirroring-repos/

http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.1

http://svnbook.red-bean.com/en/1.1/ch07.html#svn-ch-7-sect-1.3.1

https://www.google.com/enterprise/marketplace/viewListing?productListingId=3421+6389312883797462351




175

1. 2.

3. 4.

1. 2.

Can existing OnDemand evaluators enable Google Apps integration?

No. Existing evaluators can sign up for a new evaluation from if desired.Google Apps Marketplace

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 justfor 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 beautomatically 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. However, users who don't have a Google ID will not be able to access Google-specificManaging Users with Google Apps Integration

features of the , e.g. Google Docs.Google Apps Activity Bar

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 existingrepository.

If you want to import Subversion data for a single project without losing existing data in OnDemand, use the following process:

Clone the existing OnDemand SVN data locally by following the instructions on .Mirror your Subversion repository locallyMerge 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/

Create a new dump of the new data set in the repository.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:

Export your data from Visual SourceSafe in the Subversion format.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 and then download the Connector at the .documentation download page

Related topics

Requesting supportHow do I import Subversion data for a single project?

How are we notified of system maintenance?

Please see the page.Maintenance windows




176

1.

2. 3. 4.

1. 2. 3. 4.

Related topics

Requesting supportWhere 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 downloadableproduct is released. However, it might take a few weeks for the application version to become available to you, as each application versionmust 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 to keep up-to-date withOnDemand on Twittersystem maintenance and upgrades. If you suspect that an application upgrade will create problems for you, please contact our support stafffor assistance in mitigating any risks. You can contact our support staff by raising a ticket in under the 'OnDemand'our support systemproject.

Related topics

Atlassian OnDemand Application VersionsMaintenance windowsHow 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 to change the region setting.my.atlassian.com

Related topics

Maintenance windows

Users are locked out of FishEye and Crucible REST APIsUsers can become locked out of the FishEye and Crucible REST APIs as a result of attempting to use incorrect credentials to log in to thoseapplications. The most common cause of this is when the Atlassian IDE Connector is set up to use incorrect credentials, for example due tothe 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 afterfixing the credentials.

To reset the FishEye CAPTCHA for your users:

Log in as an administrator, click the menu labelled with your user name in the header, and select . TheAdministrationadministration console appears with the tab active.GeneralClick > .User Management UsersLocate the user name, and click the name to open the user details.Locate , and click .Reset FishEye CAPTCHA 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 yourGoogle 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:

Log in to your Google Apps account as administrator.Go to Advanced toolsIn the section, click .Authentication Federated Login using OpenIDSelect the check box .Allow users to sign in to third party websites using OpenID






177

4.

1.

2.

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 willnot 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:

Go to https://<account_name>.atlassian.net/secure/admin/user/ApplicationAccessConfig!default.jspaorhttps://<account_name>.jira.com/secure/admin/user/ApplicationAccessConfig!default.jspaConfigure 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 FAQDon'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 instructionson .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 continuereceiving 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.


178

1. 2. 3. 4. 5.

Related topics


Atlassian OnDemand licensing

How do I add a technical contact to my account?You can add a technical contact person to your account at by entering the person's email address in your hosted accountmy.atlassian.comdetails on the ' ' page.Licenses

To add a technical contact to your account:

Sign in at .my.atlassian.comIn the header, click .LicensesLocated the Atlassian OnDemand license, and click the plus ' ' sign to expand the options for the account.+Locate the field, enter your contact's email address, and click .Technical Contact AddIf the person has not yet signed up to my.atlassian.com, you will be prompted for more information. Enter the information and click '

'. SaveThe person will receive an email informing them that they have been automatically signed up at my.atlassian.com. The email willcontain 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 tocreate 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 notaffect the number of users in your account.

How do I get started with the Tempo Plugin?

The Tempo plugin requires to be enabled in JIRA. Time-tracking is enabled by default, but if you have disabled it, you will needtime-trackingto 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 DocumentationTempo User Documentation

How do I upgrade my account, renew my license, change credit card details, etc?

Accounts are managed through your account.My Atlassian

Go to to increase or decrease your account's user licenses, renew your license, change your credit card details,http://my.atlassian.comupdate 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 administration console. For detailed instructions, see Application Access 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 accessUpgrade your account — if you do not want to remove access from users, you may wish to consider upgrading your account to addmore 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 limitfee 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 database.PostgreSQL



http://www.tempoplugin.com/support/documentation/admin-doc

http://www.tempoplugin.com/support/documentation/user-doc



http://www.postgresql.org/


179

What domain name will my OnDemand service be on? Can I use my own domainname?

Your site is assigned a domain name of , where is the account name youhttps://<account_name>.atlassian.net account_nameprovided 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-1Pricing: 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, orwho 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 and enjoy Google Apps integration as soon as your OnDemand site is live.Marketplace

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 willdepend on Google for user account management.

See for more information.Integrating OnDemand with Google Apps

How do you evaluate OnDemand with Google Apps integration?

This can be done via the OnDemand listing on .Google Apps Marketplace


http://www.atlassian.com/licensing/ondemand#orderingatlassianondemand-1

http://www.atlassian.com/software/ondemand/pricing







180

Can existing OnDemand evaluators enable Google Apps integration?

No. Existing evaluators can sign up for a new evaluation from if desired.Google Apps Marketplace

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 justfor 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 beautomatically 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. However, users who don't have a Google ID will not be able to access Google-specificManaging Users with Google Apps Integration

features of the , e.g. Google Docs.Google Apps Activity Bar

Contributing to the Atlassian OnDemand DocumentationWould 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 LanguagesUpdating the Documentation Itself

Getting Permission to Update the DocumentationFollowing our Style GuideHow 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 willlink 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 usto 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 guidesto other frameworks) as well as product documentation (user's guides, administrator's guides and installation guides). The wiki permissionsare different for each type of documentation.

If you want to update the or other developer-focused wiki spaces, just sign up for a wiki username then log inDeveloper Networkand make the change.If you want to update the , we ask you to sign the Atlassian Contributor LicenseAtlassian OnDemand product documentationAgreement (ACLA) before we grant you wiki permissions to update the documentation space. Please read the to see theACLAterms of the agreement and the documentation it covers. Then sign and submit the agreement as described on the form attached tothat 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 RSSfeeds and watching the spaces. If someone makes an update that needs some attention from us, we will make the necessarychanges.Wiki permissions. We use wiki permissions to determine who can edit the documentation spaces. We ask people to sign the



181

(ACLA) and submit it to us. That allows us to verify that the applicant is a real person. ThenAtlassian Contributor License Agreementwe 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

. This means that anyone can copy, distribute and adapt our documentation provided theyCommons Attribution 2.5 Australia Licenseacknowledge the source of the documentation. The CC BY license is shown in the footer of every page, so that anyone whocontributes to our documentation knows that their contribution falls under the same copyright.

Related Topics:

Contributing to the JIRA DocumentationContributing to the Confluence DocumentationContributing to the FishEye DocumentationContributing to the Crucible DocumentationContributing to the Bamboo DocumentationAuthor GuidelinesAtlassian 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 atranslation 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 providesthese links because the information is useful and relevant at the time it was written. Please check carefully whether theinformation is still relevant when you read it. The information in the linked guides has not been tested or reviewed byAtlassian.

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 willinclude 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 websiteAtlassian blog

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

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

http://creativecommons.org/licenses/by/2.5/au/

http://creativecommons.org/licenses/by/2.5/au/

http://www.atlassian.com/hosted/studio/

http://blogs.atlassian.com


182

On this page:

Access level changes for your usersWhat are the changes?What does this mean in terms of licensing if you continue with the Studio pricing?What next?

Bamboo is enabledConfluence 4.1 - a new text editor

What are the changes?

Access level changes for your users


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

Table 1. How access level is mapped to application access

Access level forStudio users

OnDemand application access

Developer JIRA + Confluence + FishEye/Crucible + Bamboo + GreenHopper

Collaborator JIRA + Confluence + GreenHopper

Settings for thedefault accesslevel

non-Google Apps: JIRA + ConfluenceGoogle Apps: Your default access level preference for new Google Apps users will be preserved andmapped to OnDemand.e.g. If you configured new Google Apps users to be granted Collaborator access in JIRA Studio, then newGoogle 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 license you purchase, you get a user with access to all applications; for every Developer license, you get a new user for JIRA and Confluence. For example, you have 20 license and 10 Collaborator Developer Collaborator

license, you can have up to 30 users for JIRA, GreenHopper and Confluence each, up to 20 users for FishEye/Crucible and GreenHoppereach, and unlimited users for Bamboo.

What next?

After your service is migrated to Atlassian OnDemand, you can

change the default access level, or as it is called in OnDemandthe default application accessconfigure 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 page.Managing application access

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 Buildsin 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 introducedin Confluence 4, and this new editor has replaced the Wiki Markup editor.


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 UsersConfluence 4.0 Editor - What's Changed for Users of the Old Rich Text Editor


183

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

Confluence 4.1 Release NotesThere is also a video on the page that shows the 4.1 features relevant to Confluence OnDemand.December 2011Confluence 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 onwhat stage of Migration we are in. We can't anticipate all questions though, so please don't hesitate to leave a comment if wemissed something.

JIRA Studio Migration FAQWhat 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 FAQWhat 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 shouldbe 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

and configuring their OnDemand account.my.atlassian.com

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 OnDemandpricing and services. The rest of the users have customizations that we can not support have already been contacted regarding their options goingforward (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 , you can play around with different application and user tier options and see what the pricing would be:signup page

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 newpricing 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.comOnDemand is always on the latest version of Atlassian products, so first we will upgrade your instance to the latest versionOnce 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 and configure your service.my.atlassian.com

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.






184

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.