1. .bookmarks ...... 4 2. Glossary ...... 4 2.1 changelog ...... 4 2.2 changeset ...... 4 2.3 issue ...... 4 2.4 page ...... 5 2.5 project ...... 5 2.6 repository ...... 5 2.7 review ...... 5 2.8 source ...... 5 2.9 space ...... 5 2.10 wiki ...... 6 3. JIRA Studio Documentation ...... 6 3.1 JIRA Studio 101 ...... 6 3.2 JIRA Studio Administrator's Guide ...... 22 3.2.1 Administering Applications ...... 23 3.2.1.1 Administering Issues ...... 24 3.2.1.1.1 Configuring Commit Commands for Issues ...... 26 3.2.1.1.2 JIRA Administrator's Guide ...... 29 3.2.1.1.3 GreenHopper Administrator's Guide ...... 31 3.2.1.1.4 Configuring Zendesk to Work with JIRA Studio ...... 32 3.2.1.1.5 Configuring JIRA Plugins in JIRA Studio ...... 33 3.2.1.2 Administering the Wiki ...... 36 3.2.1.2.1 Configuring Default Space Permissions ...... 38 3.2.1.2.2 Confluence Administrator's Guide ...... 39 3.2.1.2.3 Applying a Theme to a Space ...... 43 3.2.1.2.4 Configuring Confluence Plugins in JIRA Studio ...... 45 3.2.1.3 Administering Source ...... 51 3.2.1.3.1 Configuring Repository Permissions for a Project ...... 53 3.2.1.3.2 Configuring Default Repository Permissions ...... 56 3.2.1.3.3 Enabling Anonymous Access to a Repository ...... 58 3.2.1.3.4 Configure Commits to Require a JIRA Issue Key ...... 59 3.2.1.4 Administering Reviews ...... 60 3.2.1.5 Administering Builds ...... 61 3.2.1.5.1 Getting Started with Bamboo in JIRA Studio ...... 64 3.2.1.5.2 Integrating Builds with your Issues Workflow ...... 67 3.2.1.5.3 Bamboo Administrator's Guide ...... 70 3.2.2 Administering Projects ...... 72 3.2.2.1 Adding New Projects ...... 72 3.2.2.2 Configuring the Home Page for your Project ...... 74 3.2.2.3 Deleting a Project ...... 76 3.2.2.4 Customising Application Tabs for your Project ...... 78 3.2.3 Managing Users and Groups ...... 80 3.2.3.1 Managing User Access Levels ...... 84 3.2.3.1.1 Managing User Access Levels in JIRA Studio ...... 84 3.2.4 Configuring the Appearance of JIRA Studio ...... 87 3.2.4.1 Changing the Logo ...... 87 3.2.4.2 Configuring Global and Default Application Tabs ...... 88 3.2.4.3 Editing the Date and Time Formats for 'Issues' (JIRA) ...... 89 3.2.4.4 Editing the Colour Scheme ...... 90 3.2.5 Administering your Account ...... 92 3.2.5.1 Viewing your Account Information ...... 92 3.2.5.2 Changing your Account Name ...... 93 3.2.5.3 Changing your JIRA Studio Welcome Message ...... 94 3.2.5.4 Enabling Public Signup and CAPTCHA ...... 95 3.2.5.5 Changing your JIRA Studio 'From' Email Header Format ...... 97 3.2.5.6 Changing your Account Language ...... 98 3.2.5.7 Creating a Support Request ...... 99 3.2.5.8 Viewing Web Statistics for your Account ...... 100 3.2.6 Administering Google Apps Integration ...... 100 3.2.6.1 Migrating to Google Apps ...... 101 3.2.6.2 Merging your JIRA Studio and Google Apps user bases ...... 102 3.2.6.2.1 Converting Google Apps Users to External Users ...... 105 3.2.6.3 Managing Username Conflicts ...... 106 3.2.6.4 Managing Large User Databases with Google Apps Integration ...... 107 3.2.6.5 Synchronising JIRA Studio and Google Apps Users ...... 108 3.2.6.6 Managing Users with Google Apps Integration ...... 109 3.2.6.7 Managing External Users with Google Apps Integration ...... 112 3.2.6.8 Managing Groups with Google Apps Integration ...... 118 3.2.6.9 Disabling User Access with Google Apps Integration ...... 119 3.2.7 Managing Data ...... 120 3.2.7.1 Data Backups ...... 120 3.2.7.2 Importing Data ...... 121 3.2.7.2.1 Importing Unversioned Data into Subversion ...... 123 3.2.7.2.2 Importing Versioned Data into Subversion ...... 124 3.2.7.3 Uploading Data via WebDAV ...... 126 3.3 JIRA Studio User's Guide ...... 128 3.3.1 Using the Projects Toolbar ...... 129 3.3.2 Searching in Studio ...... 131 3.3.3 Working with Issues ...... 132 3.3.3.1 JIRA User's Guide ...... 133 3.3.3.2 GreenHopper User's Guide ...... 135 3.3.3.3 Actioning Issues via Commit Messages ...... 136 3.3.4 Working with the Wiki ...... 137 3.3.4.1 Confluence User's Guide ...... 138 3.3.5 Working with Source ...... 144 3.3.5.1 FishEye User's Guide ...... 145 3.3.6 Working with Reviews ...... 145 3.3.6.1 Crucible User's Guide ...... 146 3.3.7 Working with Builds ...... 147 3.3.7.1 Bamboo User's Guide ...... 148 3.3.7.2 Actioning Issues via Builds ...... 150 3.3.8 Working with Streams ...... 150 3.3.8.1 Viewing the Activity Stream ...... 151 3.3.8.2 Configuring the Activity Stream ...... 152 3.3.8.3 Adding Comments via the Activity Stream ...... 153 3.3.9 Working with the Repository ...... 155 3.3.10 Working with Google Apps Integration ...... 157 3.3.10.1 Logging In and Out With Google Apps Integration ...... 157 3.3.10.2 Using the Activity Bar ...... 159 3.3.10.2.1 Using Google Calendar with Google Apps Integration ...... 164 3.3.10.2.2 Using Google Docs with Google Apps Integration ...... 166 3.3.11 Creating Links ...... 171 3.3.12 Managing Your Profile ...... 171 3.3.12.1 Changing Your Password in JIRA Studio ...... 172 3.4 JIRA Studio FAQ ...... 173 3.4.1 Usage FAQ ...... 175 3.4.1.1 How are we notified in case of system maintenance or outage? ...... 176 3.4.1.2 How can I edit or reassign closed issues? ...... 176 3.4.1.3 How can I prevent certain users seeing certain content? ...... 176 3.4.1.4 How do I access my Subversion repository? ...... 176 3.4.1.5 How do I create issues or issue comments via email? ...... 177 3.4.1.6 How do I file bugs or log feature requests? ...... 177 3.4.1.7 How do I request support? ...... 177 3.4.1.8 How should Studio be configured for a shared code module? ...... 177 3.4.1.9 What is the activity stream in JIRA Studio? ...... 177 3.4.1.10 What is the URL for my installation of JIRA Studio? ...... 177 3.4.1.11 Why can't I find the documentation for a particular JIRA Studio function? ...... 178 3.4.2 Configuration and Administration FAQ ...... 178 3.4.2.1 How do I associate a JIRA Project with multiple FishEye Repositories? ...... 178 3.4.2.2 Can I import my existing JIRA data, Confluence data, Subversion data, etc? ...... 179 3.4.2.3 How do I enable issue and issue comment creation via email? ...... 179 3.4.2.4 How can I migrate my content to and from other Atlassian applications? ...... 179 3.4.2.5 Can I use a custom Elastic Bamboo image? ...... 179 3.4.2.6 When will my JIRA Studio applications be upgraded? ...... 180 3.4.2.7 Subversion is constantly asking users to re-authenticate and failing with the correct credentials ...... 180 3.4.2.8 Can I change the look and feel of JIRA Studio? ...... 180 3.4.2.9 Can I install my own plugins? ...... 180 3.4.2.10 Are alternative languages available for JIRA Studio? ...... 180 3.4.2.11 Do you support SSL? ...... 180 3.4.2.12 How do I request installation modifications? ...... 181 3.4.2.13 How do I enable Bamboo for JIRA Studio? ...... 181 3.4.2.14 Can I use JIRA Studio with Confluence Hosted? ...... 181 3.4.2.15 What remote APIs are supported in JIRA Studio? ...... 182 3.4.2.16 How do I update JIRA issues via subversion commit messages? ...... 182 3.4.2.17 How are commit messages defined (for actioning issues)? ...... 182 3.4.2.18 Can I import my existing data from an external system (Bugzilla, Trac)? ...... 183 3.4.2.19 Can I use EBS volumes with Elastic Bamboo? ...... 183 3.4.2.20 How do I create a backup copy of my Subversion repository? ...... 183 3.4.2.21 Can I change the global theme for the look and feel? ...... 184 3.4.2.22 How do I add Google Apps to JIRA Studio? ...... 184 3.4.2.23 Can I use Clover with JIRA Studio? ...... 185 3.4.2.24 How do I import Subversion data for a single JIRA Studio project? ...... 185 3.4.2.25 How do I migrate from Visual SourceSafe to JIRA Studio? ...... 185 3.4.3 Subscription and Account FAQ ...... 186 3.4.3.1 Can I disable a user without deleting them? ...... 186 3.4.3.2 Can I import external data into JIRA Studio? ...... 186 3.4.3.3 How do I add a technical contact to my account? ...... 186 3.4.3.4 How do I end my subscription or evaluation? ...... 187 3.4.3.5 How do I get started with the Tempo Plugin? ...... 187 3.4.3.6 How do I upgrade my account, renew my license, change credit card details, etc? ...... 187 3.4.3.7 How is JIRA Studio licensed? ...... 188 3.4.3.8 How is the user count of my account calculated? How do I reduce my user count? ...... 188 3.4.3.9 How long will it take to receive my JIRA Studio installation after placing the order? ...... 189 3.4.3.10 I would like to try Studio out before buying. How do I do that? ...... 189 3.4.3.11 What are the storage and bandwidth limits? ...... 189 3.4.3.12 What database will the JIRA Studio instance use? ...... 189 3.4.3.13 What domain name will my JIRA Studio service be on? Can I use my own domain name? ...... 189 3.4.3.14 What happens to my JIRA Studio instance when my account is cancelled? ...... 189 3.4.3.15 What is the minimum number of users allowable in an upgrade? ...... 190 3.4.3.16 What is the minimum term of service? ...... 190 3.4.3.17 What level of customization and control will I have over my JIRA Studio instance? ...... 190 3.4.4 Google Apps Integration FAQ ...... 190 3.4.5 Deletion Policy for User Data ...... 191 3.4.6 JIRA Studio Application Versions ...... 192 3.4.7 JIRA Studio Licensing ...... 193 3.4.8 JIRA Studio Plugin Policy ...... 194 3.4.8.1 Third-Party Plugin Process ...... 196 3.4.9 Restricted Functions in JIRA Studio ...... 196 3.4.10 Support Policies ...... 200 3.4.10.1 Bug Fixing Policy ...... 200 3.4.10.2 How to Report a Security Issue ...... 201 3.4.10.3 New Features Policy ...... 201 3.4.10.4 Security Advisory Publishing Policy ...... 202 3.4.10.5 Security Update Policy ...... 202 3.4.10.6 Severity Levels for Security Issues ...... 202 3.4.10.7 Update Policy ...... 203 3.4.11 Supported Platforms ...... 204 3.4.11.1 End of Support Announcements for JIRA Studio ...... 204 3.5 JIRA Studio Resources ...... 204 3.6 JIRA Studio Release Notes ...... 205 3.6.1 JIRA Studio Release Summary ...... 205 3.6.2 JIRA Studio May 2011 Release Notes ...... 207 3.6.3 JIRA Studio April 2011 Release Notes ...... 212 3.6.4 JIRA Studio 2.4 Release Notes ...... 212 3.6.5 JIRA Studio 2.3.1 Release Notes ...... 219 3.6.6 JIRA Studio 2.3 Release Notes ...... 220 3.6.7 JIRA Studio 2.2 Release Notes ...... 224 3.6.8 JIRA Studio 2.1 Release Notes ...... 229 3.6.9 JIRA Studio 2.0 Release Notes ...... 233 3.6.10 JIRA Studio 1.8 Release Notes ...... 237 3.6.11 JIRA Studio 1.7 Release Notes ...... 239 3.6.12 JIRA Studio 1.6 Release Notes ...... 242 3.6.13 JIRA Studio 1.5 Release Notes ...... 245 3.6.14 JIRA Studio 1.4 Release Notes ...... 247 3.6.15 JIRA Studio 1.3 Release Notes ...... 250 3.6.16 JIRA Studio 1.2 Release Notes ...... 252 3.6.17 JIRA Studio 1.1 Release Notes ...... 253 3.6.18 JIRA Studio 1.0 Release Notes ...... 254 3.7 Contributing to the JIRA Studio Documentation ...... 256 3.7.1 JIRA Studio Documentation in Other Languages ...... 257 .bookmarks
JIRA Studio Beta Bookmarks This page is a container for all the bookmarks in this space. Do not delete or move it or you will lose all your bookmarks. Bookmarks in JIRA Studio Beta | Links for JIRA Studio Beta
The 15 most recent bookmarks in JIRA Studio There are no bookmarks to display.
Glossary changelog changeset issue page project repository review source space wiki changelog
A changelog is a chronological list of the changesets that were committed to a repository.
For more information, please see Working with Source. changeset
A changeset is a collection of source files that were committed to the repository at the same time. A changeset can be associated with one or more reviews.
In JIRA Studio, because a repository can be associated with projects, a changeset can automatically link to any associated issues and or wiki pages.
For more information, please see Working with Source.
issue An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a project.
For more information, please see Working with Issues. page
A page is an online document within the wiki. Each page belongs to a space.
For more information, please see Working with the Wiki. project
A project is a collection of issues.
In JIRA Studio, a project can be associated with a wiki space, build project and/or a source repository. This allows the project's issues to automatically link to (and be linked from) their associated wiki documents, source files, plan, changesets, code reviews and (if Bamboo enabled) build result.
For more information, please see Adding New Projects. repository
A repository (e.g. Subversion, Perforce or CVS) contains your source code. Note: In JIRA Studio, a source repository can be associated with one or more projects.
For more information, please see Working with Source. review
Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being committed to a repository.
For more information, please see Working with Reviews. source
Your source (e.g. your source code) resides in a repository such as Subversion, Perforce or CVS.
A changeset is a collection of source files that were committed to the repository at the same time. A changeset can be associated with one or more reviews.
In JIRA Studio, because a repository can be associated with projects, a changeset can automatically link to any associated issues and or wiki pages.
For more information, please see Working with Source. space
A space is a collection of pages within the wiki.
In JIRA Studio, a space can be associated with a project. This allows links to be automatically created on your wiki pages, pointing to associated issues, source files, changesets and/or code reviews.
For more information, please see Working with the Wiki. wiki
The wiki is a collection of pages (online documents). The wiki is useful for collaboration, information sharing and documentation.
For more information, please see Working with the Wiki.
JIRA Studio Documentation
JIRA Studio
User's Guide
The JIRA Studio User's Guide is for project managers, developers, testers – anyone who uses JIRA Studio. New to JIRA Studio? Start by learning about the Projects Toolbar and how to navigate around in JIRA Studio. Try creating issues, drafting wiki pages, browsing the source repository, performing a code review and (if enabled) running a build. You can also create links between issues, wiki pages, source files, reviews and builds that you create.
Administrator's Guide
The JIRA Studio Administrator's Guide is for people with JIRA Studio administration rights. It will help you set up users and groups, applications and projects. You may want to customise the look and feel of your JIRA Studio instance. Account administration is also covered. You may also find the FAQs and JIRA Studio Forum useful.
Evaluator's Guide
If you would like to try out JIRA Studio, you can take the tour or try it out yourself by signing up for a free trial. The JIRA Studio 101 guide will help you get started using JIRA Studio.
Stay in Touch
Read the latest JIRA Studio news and keep track of the status of JIRA Studio. You can receive more news, product information and code tips via our newsletter and forums (JIRA Studio forum and JIRA Studio Announcements forum).
Have feedback regarding your JIRA Studio service? Please submit your feedback under the 'JIRA Studio' project here. Alternatively, you may submit feedback via email to [email protected].
Important Information
JIRA Studio Security Statement JIRA Studio Terms of Use JIRA Studio Privacy Policy JIRA Studio Plugin Policy JIRA Studio Application Versions Restricted Functions in JIRA Studio
Looking for information on our other hosted offerings? Find it here: JIRA and Confluence Enterprise Hosting and Bitbucket code hosting.
JIRA Studio 101
JIRA Studio 101
Thank you for choosing JIRA Studio. To help you get up and running quickly, we've compiled some easy instructions for configuring and using JIRA Studio.
Getting Started with JIRA Studio
1. Importing Your Own Data
Importing issues and source? Follow this procedure: (http://confluence.atlassian.com/x/yIAoC) 2. Adding Users For each of your JIRA Studio users, you will need to do the following (click to expand):
1. Click the menu labelled with your user name in the JIRA Studio header, and select the 'Administration' link. 2. Click 'User Browser' in the left navigation column, then click 'Add User'. 3. Enter the 'Username', 'Password', 'Full Name' and 'Email Address' and (optionally) tick the 'Send Password Email' checkbox to send the user an email containing their account details, then click the 'Create' button. 4. The 'User Browser' will display. Locate the new user and click the 'Groups' link in the 'Operations' column. When your JIRA Studio account is created, three groups are automatically set up – Users, Developers, and Administrators. Each of these groups can have access. 5. If the user is going to need to work on issues, select the 'Developers' access level and click the 'Create' button. If the user is only going to log issues, and not work on them, then they don't need to have 'Developer' access level. Adding a user with 'Developer' access will automatically put them into the 'developers' group if it exists, which will grant them some standard developer permissions.
See also:
Managing Users and Groups
If you are a Google Apps customer, you can add your Google Apps users to JIRA Studio:
1. Visit the Google Apps Dashboard for your domain and log in as administrator. 2. On the Google Apps toolbar, click 'Organization & Users'. 3. Click the 'Create a new user' button. Fill out the new user details as required. A temporary password is shown on screen; make a note of that or set an alternate initial password. 4. Click 'Create new user'. The account will be created and the user's details displayed, including their new email address. You can now click to print or email the access instructions for the new user. 5. Next, select 'Google Management' and click 'Start Synchronisation' to synchronise your users between JIRA Studio and Google. This will ensure that any new users added to your Google domain are quickly made available to JIRA Studio and can be added to groups. 6. At this stage, visit the JIRA Studio admin pages to configure the correct access to Atlassian applications. To do this, open the 'User Menu' in JIRA Studio (labelled with your user name), click 'Administration', then click the 'User Browser' link under 'General', 'JIRA Studio'. 7. Find the desired user and edit the user's privileges. Choose the desired access to Atlassian applications and click 'Save'.
See also:
Migrating to Google Apps. Managing Users and Groups
3. Creating a Project In JIRA Studio, Projects are like 'containers'. So get started by creating a project to store issues in:
1. Click the menu labelled with your user name in the JIRA Studio header, and select the 'Administration' link. 2. Click 'Projects' in the left navigation column, then click 'Add Project'. 3. In the 'Name' field, type a descriptive name for your project (typically two or three words, e.g. 'Purchase Orders'). 4. In the 'Key' field, type a meaningful prefix for issues in your project (typically three or four characters, e.g.'ORD'). Please note, that this cannot be changed later. 5. In the 'Project Lead' field, select the user to whom issues should be assigned by default. 6. If you want JIRA Studio to automatically send emails to appropriate people when particular events occur (e.g. 'Issue Created', 'Issue Resolved'), change the 'Notification Scheme' field from 'None' to 'Default Notification Scheme'. Your JIRA Studio account is pre-configured to send email notifications from jira@}}accountname{{.jira.com, where accountname is the name of your JIRA Studio account. 7. Leave the fields for 'Permission Scheme', and 'Issue Security Scheme' at default, then click the 'Add' button. If required, you can revisit the project and edit these parameters later.
See also:
How do I enable issue and issue comment creation via email? Configuring email Notifications Defining a Project
4. Going Agile? Apply the Scrum template Apply a Scrum template to a project: Scrum is an agile development methodology where work is completed iteratively over a number of discrete time periods (sprints). If you set your agile projects to use the 'Scrum' template, your projects will automatically be configured to use Stories, Epics, Story Points, Ranking and Flagging. To apply the Scrum template,
1. Click the menu labelled with your user name in the JIRA Studio header, and select the 'Administration' link. 2. Select the 'Issues' tab, and then from the 'GreenHopper' section, select 'Project Templates'. 3. In the 'Project Templates' screen, from the 'Create a new project' dropdown list, select 'Scrum'. Your template selection is saved automatically. When you set up JIRA Studio to use the 'Scrum' project template, the system will automatically create the appropriate data fields and issue types, and configure the card styles.
JIRA 'Scrum' Fields
Flagged' — flag issues to provide visual notification of any impediments 'Rank' — prioritise issues
JIRA 'Scrum' Issue Types
'Epic' – Epics are typically used to capture large and complex items. 'Story' – A story is a software system requirement that is expressed in a few short sentences
'Technical Task' – A task that needs to be done
Card Styles
Your issues are presented in either detailed or summary card views
Screenshot: Detailed card view
See also:
Specifying your Project Templates Setting Up Epics for your Project Configuring your Card Styles Using Planning Board Views
Create versions and hierarchy in GreenHopper's scrum template: GreenHopper in JIRA Studio enables you to create parent-child relationships between versions. For example, you may wish to group your sprints as milestone versions (e.g. "Version 1 m1", "Version 1 m2", etc) under the version for the major release (e.g. "Version 1"). In GreenHopper, you can set up the major version as the "parent" version for the milestone versions. This allows you to view and track all of the issues assigned to the milestone releases under the umbrella of the major release. All issues under the child version are considered to be a subset of the parent version. These version hierarchies are useful for managing Releases/Sprints/Teams.
1. From the 'Agile' drop-down list, select 'Planning Board'. 2. In the Planning Board screen which displays, select your project from the project dropdown in the top navigation bar. 3. Change the viewing mode to 'Version' mode. 4. Locate the box for the version that you want to be the child version in the right-hand column. 5. Edit the 'Parent' ( ) field by clicking the icon which will appear when you hover over the field. 6. Select the version that you want to be the parent version from the dropdown. The Planning Board will refresh and display your version under its new parent version (see screenshot below). The child version will also have an icon display( ) in its header. Screenshot: A parent and child version in GreenHopper
See also:
Adding a Version
Add source to your SVN repository: 1. Click the menu labelled with your user name in the JIRA Studio header, and select the 'Administration' link. 2. The administration console will display with the 'General' tab active. 3. Click the 'Source' tab. The Source (FishEye/Subversion) administration console will display. 4. To link your code to an issue, and see relevant code when looking at an issue: a. Enter the key of the JIRA issue (that you want to link your code to) in the commit message, when committing your code. b. Commit your code. The link from your code to the JIRA issue will be created. c. Open your issue in JIRA Studio. d. Click the 'Source' tab under the 'Description'. The code that you linked from will display.
Mastering the Basics — Issues
5. Creating an Issue Create a new Issue in JIRA Studio:
1. Click on the 'Issues' tab in the top navigation bar 2. From the 'Issues' drop-down list, select the 'Create Issue' option. 3. In the 'Create Issue' screen, select the relevant Project and Issue Type, then click the 'Next' button. 4. Complete the issue details in the 'Priority', 'Environment' and 'Description' fields, etc. as required. 5. Click the 'Create' button.
See also:
Creating an Issue
6. Assigning an Issue Assign an Issue in JIRA Studio:
You can configure the default assignee for an issue when you create a project. Issues are usually either assigned to the project lead, or left unassigned by default.
To assign an issue to yourself during the process of issue creation, simply click the 'Assign to Me' link. To assign an issue after an issue has been created, open the required issue and select 'Assign', then from the Assignee drop-down, select the required assignee and click the 'Assign' button.
See also:
Defining a Project Configuring JIRA Options
7. Progressing an Issue Through a Workflow Progress an issue through a workflow: JIRA Studio ships with a default workflow. The default workflow cannot be edited, but you can customise the issue lifecycle by creating additional workflows. Each workflow can be associated with particular projects and (optionally) particular issue type(s).
To progress an issue through the default workflow, Screenshot: Default Workflow for an Issue
Button Action
Edit Click to make changes to the issue, including the title, issue type, priority, description, time estimate, and attachments.
Assign Click to assign the issue to another person.
Comment Click to add a comment to the issue. Comments display chronologically.
More Click to perform other actions, including: to work with the issue in the Planning or Task Board, to log work, Actions watch the issue, convert to a sub-task of another issue, to move the issue to another project, or to delete the issue.
Stop By default, issues display as 'In Progress'. Click to stop progress on the issue. Its status will display now Progress display as 'Open'.
Resolve Click to resolve the issue and assign a resolution criteria such as: 'Fixed', 'Won't Fix', 'Duplicate', Issue 'Incomplete', or 'Cannot Reproduce'.
Workflow Click to close the issue and assign a resolution criteria and any required documentation or summary description.
View Click to view the issue in XML, MS Word, or in printable format.
See also:
What is an Issue? Configuring Workflow
8. Using Keyboard Shortcuts to Navigate Issues Use keyboard shortcuts to navigate through Issues:
JIRA Studio enable you to quickly navigate through issues. You can use keyboard shortcuts to navigate and perform tasks in Issues.
Keyboard shortcuts in Issues
Action Keyboard Shortcut
Create issue 'c'
Edit issue 'e'
View selected issue 'o' or 'enter'
Next issue 'j'
Previous issue 'k'
Assign issue 'a'
Comment on issue 'm'
See also:
JIRA Keyboard Shortcuts
Mastering the Basics — Agile Planning
9. Using JIRA Studio's Agile Features The basics of Agile Planning: JIRA Studio incorporates agile project methodologies, so it's well suited for rapid development teams. A sprint (also known as an iteration) is a short (two to four week) period in which the development team implements and delivers a discrete product increment (e.g. a working milestone version).
Planning Board – where you plan your sprint and organise issues into a plan of work for a sprint Task Board – the task board typically shows all the work you're undertaking a sprint. Chart Board – a graphical representation of the progress of ongoing versions Released Board – gives you access to charts and release notes for the released versions of your projects
10. Moving Issues into a Sprint Move Issues into a Sprint:
The Planning Board is where you plan your sprint and organise issues into a plan of work for a sprint.
1. Click the 'Agile' drop-down menu in the top navigation bar and select 'Planning Board'. 2. In the 'Planning Board' field, select the required project. 3. In the column at the right of the screen, click the 'Add' link. The 'Add Version' pop-up will appear. 4. In the 'Version Name' field, type the name of your new sprint version (e.g. 'Sprint 1'). 5. In the 'Parent' field, select your major version (e.g. 'Version 1'). 6. Enter the 'Start Date', 'Release Date' and 'Description' for your new sprint version. 7. Click the 'Create' button to create the version, then click the 'Create and Close' button to create the version and return to the Planning Board. Screenshot: JIRA Studio 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.
Task Board Columns To Do In Progress Done
Issues Open In Progress Resolved
Reopened Closed
For Kanban practitioners, JIRA Studio enables you to set multiple constraints on each of the Task Board columns so that your team can easily visualise and monitor the progress of your workflow. Screenshot: The Task Board displaying issue status in columns
See also:
Creating an Issue Adding Constraints to Your Task Board Columns (Kanban) Working with Issues in GreenHopper
Drag and Drop Issues in to a Workflow:
The task board allows you to easily transition issues along a workflow by dragging and dropping cards between workflow statuses.
1. Click the 'Agile' drop-down menu in the top navigation bar and select 'Planning Board'. 2. In the 'Planning Board' field, select the required project. The 'Task Board' will refresh with information for your project. 3. In the 'Version' dropdown, select the version which contains issues that you want to transition. 4. Transition an issue by dragging and dropping the card between the columns on your Task Board. 5. Complete the transition card, if it displays. Select the desired workflow action. You can also optionally add a comment for this transition. 6. The issue status will update when you drop in into the destination column.
See also:
Transitioning Issues in GreenHopper Scheduling and Assigning Issues in GreenHopper
Mastering the Basics — Source 11. Committing Source with an Issue Key Commit Source with an Issue Key:
JIRA Studio enables you to require commits be associated with an Issue Key. This allows you to enforce the inclusion of an open Issue, or a ticket number in a commit. To set up Source to ensure commits are associated with an Issue Key,
1. While you are logged in as an Administrator, click the menu labelled with your user name in the JIRA Studio header, and select the 'Administration' link. 2. The administration console will display with the 'General' tab active. 3. Click the 'Source' tab. The 'Source' administration console will display. 4. Click the 'SVN Commit Hooks' option in the left menu. The 'SVN Commit Hooks' page will display. 5. Select the checkbox, 'Require JIRA issue key for a successful commit'. 6. Click 'Save'.
See also:
Configure Commits to Require a JIRA Issue Key
12. Checking out Source Code Check out a Working Copy of Source:
1. Open a Subversion command-line client. 2. Enter the following command: svn checkout https://
See also:
Working with the Repository Working with Source
13. Changing a File Change a File:
1. Open a Subversion command-line client. 2. Enter the following command:svn commit -m "
See also:
Working with the Repository
14. Checking Differences in Committed Code View the Issue Source Tab to Check Code Differences: The Source tab of an Issue shows all the code changes committed against this issue.
1. From the default JIRA Studio dashboard, select the required issue. For example, you can navigate to the 'Assigned to Me' dashboard portlet and select an issue. 2. In the Activity area of the issue, click to select the 'Source' tab and display any source code commits associated with this issue. (See screenshot below) 3. You can click individual commits, or select to:
— View differences to previous commit
— View full source
— View file history
— Download the raw file
Screenshot: View Source from an Issue
15. Commenting on Issues when Committing Code Update Issues with Commit Comments:
If you are working with code, you can action issues in JIRA Studio via Subversion commit messages. By using particular keywords in your commit message, you can log work, add comments or change the status of an issue. This makes it easy for you to maintain any issues that are related to the code you are changing. The basic command line syntax for your commit comment is:
Command Command Description Example Parameters
#comment
#time
#start This command transitions #start — this command executes the 'Start Progress' an issue to a particular workflow transition for an Issue in the default JIRA Studio workflow state. Here, work workflow is started on the issue.
See also:
Actioning Issues via Commit Messages
16. Viewing a Changeset from the Source Tab View a Changeset from the Source Tab: A changeset is a collection of source files that were committed to the repository at the same time. A changeset can be associated with one or more reviews.
To view a changeset from the 'Source' tab,
1. From the JIRA Studio dashboard, select the required project from the project list drop-down 2. In the project screen that appears, select the 'Source' tab from the left-hand side. 3. The Source screen displays changesets that you can browse; from the changeset id number you can drill down into branches to view: who committed the code what changes were made comments associated with the change
Mastering the Basics — Reviews
17. Creating a Review from the Source Tab Create a Review from the Source Tab:
1. From the JIRA Studio dashboard, select the 'Source' tab. 2. From the left panel, click 'Create Review', then in the 'Select Project for New Review' dialog, select the required project from the drop-down list. 3. Click the 'Create Review' button. 4. In the 'Add Content to Review' dialog, select the required review components. Click the 'Add More Content' button to add changesets, attachments, patches, or files to your review. 5. Click 'Start Review' when you are ready to begin the review. Screenshot: The Add Content to Review Dialog
Mastering the Basics — Wiki
18. Creating a Wiki Page Create a Wiki Page: 1. Select your project from the 'Projects' dropdown in the top navigation bar (if you are not already in your project) and click the 'Wiki' tab. The home page for your project will display. 2. Click the 'Add' menu and select 'Page' from the dropdown. 3. Write content in a simple markup language or using the Rich Text editor. 4. You can add links from your wiki page to other wiki pages, issues, source and reviews. 5. Click the 'Save' button to create your page.
See also:
Working with Pages Overview
19. Creating a Blog Post Create a Blog Post:
1. Select your project from the 'Projects' dropdown in the top navigation bar (if you are not already in your project) and click the 'Wiki' tab. The home page for your project will display. 2. Click the 'Add' menu and select 'Blog Post' from the dropdown. 3. Write content in a simple markup language or using the Rich Text editor. 4. You can add links from your wiki page to other wiki pages, issues, source and reviews. 5. Click the 'Save' button to create your blog post. Your blog post will now appear: In the Activity Steam of your project In the Activity Stream of the default JIRA Studio dashboard In the Recently Updated area of your project Wiki
See also:
[Working with Blog Posts Overview]
20. Linking your Wiki Page to an Issue Link your Wiki Page to an Issue:
To link your issue from within a wiki page so you can quickly jump to it,
1. Access the required wiki page, 2. Then, simply type the issue key to create a direct link to an issue. For example, typing "TEST-123" will create a direct link to issue TEST-123.
See also:
Creating Links
21. Linking to and Between Wiki Pages, Source Files, Reviews, or Build Plans Link to and Between Wiki Pages, Source Files, Reviews, or Build Plans:
You can link between your wiki pages, and to your source file, review, or build plans. This means you can easily jump to related content from any wiki page.
To link to… Type this Examples
a wiki page in the same project [
a wiki page in a different project [
a changeset revision:
a source file source:
a review
a build plan
a build result
See also:
Creating Links
Mastering the Basics — Streams 22. Viewing JIRA Studio Activity using Streams View JIRA Studio Activity using Streams:
The activity stream is available in a number of places in JIRA Studio. Each view provides a different set of activities depending on whether you are in the context of a user, single project or multiple projects.
The Activity Stream feature allows you to view the combined activity of your 'Issues', 'Wiki', 'Source', 'Reviews' and (if Bamboo is enabled) 'Builds'. You can view the activity for a single project or across all of your projects in JIRA Studio. Your Studio instance will be set up to display an activity stream portlet on your dashboard by default. By default, it will display the recent activity for all projects and all users in your Studio instance. You can configure the stream display. Every project in JIRA Studio has an 'Activity Stream' tab. This activity stream contains all of the recent activity by all users, for the project. RSS feeds enable you to subscribe to activity steam updates and have these updates available as an RSS feed. The link for the RSS feed of an activity stream is available via the RSS symbol ( ) in the top right corner of each activity stream view.
To view the activity stream,
1. To view the Activity Stream for a project: At the top left of your JIRA Studio instance, click to select the required project from the 'Project' drop-down. 2. To view the Activity Stream across all projects in your JIRA Studio instance, click to select the 'Dashboards' drop-down. 3. Click the RSS icon ( ) to subscribe to the RSS Feed.
See also:
Configuring the Activity Stream
Mastering the Basics — Dashboards
23. Creating a Dashboard in JIRA Studio Create a Dashboard in JIRA Studio: The Dashboard is the first screen you see when you log in to JIRA Studio. Each of JIRA Studio's components also contains a dashboard. Administrators can configure component dashboards. Individual users can customise the dashboard for their personal space. The navigation bar (at the top of the screen) is the same on every screen in JIRA Studio. It features a Cross-Application Navigation Bar to give you quick access to: Issues, the Wiki, Source., and Reviews. The white area of the screen, below the top navigation bar, can be customised to display 'gadgets' showing many different types of information, depending on your areas of interest. If you are anywhere else in JIRA Studio, you can access your Dashboards view by clicking the 'Dashboards' link in the top left corner of the JIRA Studio interface. The information boxes on the dashboard are called Gadgets.
To create a dashboard in JIRA Studio,
1. From the main screen, select the 'Dashboards' drop-down, and then click 'Manage Dashboards'.
2. In the 'Manage Dashboards' screen which appears, select 'Create New Dashboard'. 3. In the 'Create New Dashboard' screen, fill in the fields to create your dashboard.
Note that you can select either 'Create Dashboard' to create a blank dashboard, or 'Copy Dashboard' to create a dashboard that is based on the default dashboard. 4. From the 'Add Shares' drop-down, select either Everyone, Group, or Project. Note that the Groups or Projects will be dynamically enabled according to the groups you belong to, and any projects you have created. 5. Click the 'Add' button to create your dashboard. 6. You can now select your newly created Dashboard from the 'Dashboards' drop-down.
24. Customising your JIRA Studio Dashboard Customise your JIRA Studio Dashboard: You can customise your dashboard as follows:
Choose a Dashboard Layout At the top right of the Dashboard, click the 'Edit Layout' link. Select your required layout from the layout options presented.
Add a Gadget 1. At the top right of the Dashboard, click the 'Add Gadget' link. 2. Click the 'Add it now' button beneath your chosen gadget. 3. Click the 'Finished' button to return to your Dashboard. 4. If the gadget you have selected requires configuration, you will be presented with the gadget's configuration page. Configure as required, and click 'Save'.
Move a Gadget To move a gadget to a different position on your dashboard, just click the gadget and drag it into its new position.
Remove a Gadget 1. Hold your mouse over the top right corner of the gadget, until a down-arrow appears. 2. Click the down-arrow to display an options menu. 3. Click 'Delete'.
Trying the Advanced Features
25. Enabling Builds Enable Builds in JIRA Studio:
The Builds application (Bamboo) is disabled by default in JIRA Studio. If you want to use Bamboo in JIRA Studio, you must request for it to be enabled for your JIRA Studio account by raising a support ticket. An Amazon Web Services account is also required to use Bamboo in JIRA Studio because all builds are run using computing resources from the Amazon Elastic Compute Cloud (EC2). To set up and start using Bamboo in JIRA Studio, read Getting Started with Bamboo in JIRA Studio.
26. Integrating Builds with your Workflow Integrate Builds with your Issues Workflow: 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. The administration console will display with the 'General' tab active. 2. Click the 'Issues' tab in the administration console (not the JIRA Studio header). The 'Issues' administration console will display. 3. Click the 'Schemes' link in the left menu and click the 'Workflow Schemes' link in the menu that displays. The 'Workflow Schemes' page will display. 4. Click the 'Add' link. The 'Workflow Schemes' page will display. 5. Click the 'Add workflow scheme' link. The 'Add Workflow Scheme' page will display. 6. Enter a 'Name' and 'Description' for your workflow scheme and click the 'Add' button. Your workflow scheme will be created and the 'Edit Workflows for
See also:
Integrating Builds with your Issues Workflow
27. Enabling sub-tasks Enable Sub-Tasks:
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. 2. Select the 'Issues' tab, and then from the 'Global Settings' section, select 'Sub-Tasks'. 3. In the 'Sub-Tasks' screen, click the 'Enable sub-tasks' link. This will enable the default JIRA sub-task types, which include: Technical Task Bug Epic Improvement New Feature Story Task
See also:
Configuring Sub-tasks Creating a Sub-Task
28. Configuring a Workflow Configure a Workflow JIRA ships with a default workflow. The default workflow cannot be edited, but you can customise the issue lifecycle by creating additional workflows. Each workflow can be associated with particular projects and, optionally, particular issue types.
Depending on how your organisation uses JIRA Studio, you might need to add a new 'Status', e.g. a new step in the issue ' workflow. You can configure the Issue to meet this requirement. For example, if you are using JIRA to track purchase orders, you might add a new Status called 'Purchase Approved'.
To add a new Status called 'Purchase Approved', and create a new workflow that has an extra step between 'Open' and 'In Progress':
1. Click the menu labelled with your user name in the the JIRA Studio header, and select 'Administration'. 2. Click the 'Issues' tab in the Administration Console (not in the JIRA Studio header). 3. Click 'Issue Settings' in the left navigation column, and then click 'Statuses'. 4. In the 'Add New Status' form at the bottom of the page, type 'Purchase Approved' in the 'Name' field. Then click the 'Add' button. 5. Click 'Global Settings' in the left navigation column, and then click 'Workflows'. 6. Click the 'Copy' link next to 'JIRA (Read-only System Workflow)'. 7. In the 'Workflow Name' field, type 'Purchase Order Workflow'. Then click the 'Add' button'. 8. Click the 'Steps' link next to 'Purchase Order Workflow'. 9. In the 'Add New Step' form: a. in the 'Name' field, type 'Purchase Approved'. b. in the 'Linked Status' field, select 'Purchase Approved'. c. click the 'Add' button. 10. Click the 'Add Transition' link next to 'Open': a. in the 'Name' field, type 'Approve Purchase'. b. in the 'Destination Step' field, select 'Purchase Approved'. c. click the 'Add' button. 11. Click the 'Add Transition' link next to 'Purchase Approved': a. in the 'Name' field, type 'Start Progress'. b. in the 'Destination Step' field, select 'In Progress'. c. click the 'Add' button. 12. Click the 'Delete Transitions' link next to 'Open'. Select 'Start Progress' and click the 'Delete' button. 13. Click 'Workflow Schemes' in the left navigation column (under 'Issue Fields'). Then click 'Add Workflow Scheme'. 14. In the 'Name' field, type 'Purchase Order Workflow Scheme'. In the 'Default Screen' field, select 'Purchase Order Screen'. Then click the 'Add' button. 15. Click the 'Workflows' link next to 'Purchase Order Workflow Scheme', click 'Assign Workflow' and select 'Purchase Order Workflow'. Then click the 'Add' button. 16. Click the 'General' tab, then click 'Projects' in the left navigation column. Then in the 'Name' column, click 'Purchase Orders'. The project details will be displayed. 17. Click the 'Select' link next to the 'Workflow Scheme' field, select 'Purchase Order Workflow Scheme' and click the 'Associate' button.
To test your new configuration, create an issue in the 'Purchase Orders' project. After you save the issue, the left column should contain a link called 'Approve Purchase', but not a link called 'Start Progress'.
See also:
Defining 'Status' Field Values Configuring Workflow Activating Workflow
Visiting JIRA Studio's Component Products
Visit the in-depth guides:
JIRA 101 GreenHopper 101 Confluence 101 FishEye 101 Crucible 101 Bamboo 101
Thank you for using JIRA Studio.
Thanks for choosing JIRA Studio. We're always happy to help. Feel free to email or call us with any questions you have.
JIRA Studio Administrator's Guide
The JIRA Studio administration console enables you to administer your JIRA Studio applications, and your JIRA Studio-wide configuration options from one place. The configuration settings for JIRA Studio are grouped into tabs. There is a tab for the configuration settings for each of the applications as well as a general tab for global settings. Clicking on a tab will display the configuration settings in an menu on the left of the page (see screenshot below).
A triangle ( ) next to a menu option means that the menu option has sub-options that will display when you click the menu option. A square ( ) next to a menu option means that the menu item does not have any sub-options.
Read more about the administration options available to you in the pages listed below:
Administering Applications Administering Projects Managing Users and Groups Configuring the Appearance of JIRA Studio Administering your Account Administering Google Apps Integration Managing Data
Administering Applications
Administering Applications
Administering Issues Configuring Commit Commands for Issues JIRA Administrator's Guide GreenHopper Administrator's Guide Configuring Zendesk to Work with JIRA Studio Configuring JIRA Plugins in JIRA Studio Disabling or Enabling a JIRA Plugin in JIRA Studio Viewing your JIRA Plugins in JIRA Studio Viewing the JIRA Plugin Audit Log in JIRA Studio Administering the Wiki Configuring Default Space Permissions Confluence Administrator's Guide Applying a Theme to a Space Configuring Confluence Plugins in JIRA Studio Configuring a Confluence Plugin in JIRA Studio Disabling or Enabling a Confluence Plugin in JIRA Studio Viewing the Confluence Plugin Audit Log in JIRA Studio Viewing your Confluence Plugins in JIRA Studio Administering Source Configuring Repository Permissions for a Project Configuring Default Repository Permissions Enabling Anonymous Access to a Repository Configure Commits to Require a JIRA Issue Key Administering Reviews Administering Builds Getting Started with Bamboo in JIRA Studio Integrating Builds with your Issues Workflow Bamboo Administrator's Guide Administering Issues
An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a project. In JIRA Studio, a project can be associated with a wiki space, build project and/or a source repository. This allows the project's issues to automatically link to (and be linked from) their associated wiki documents, source files, plan, changesets, code reviews and (if Bamboo enabled) build result.
JIRA in JIRA Studio Please note the following important information regarding your issues application (JIRA) in JIRA Studio:
The versions of JIRA and GreenHopper running in JIRA Studio may differ slightly from the latest released versions of standalone JIRA and GreenHopper. Please refer to JIRA Studio Application Versions for that latest version information. Some functions in JIRA are restricted for security reasons. Read more about Restricted Functions in JIRA Studio.
On this page:
Administering Issues JIRA and GreenHopper Administration Documentation JIRA Studio-specific Documentation
Administering Issues
To administer issues,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active. 2. Click the 'Issues' tab. The Issues (JIRA/GreenHopper) administration console will display (see screenshot below). Each of the administration options for your 'Issues' application are divided into the categories listed below. For details about administering JIRA and GreenHopper, please see the 'JIRA and GreenHopper Administration Documentation' section below.
Category Functions
Permissions * Global Permissions — Manage system-wide permissions (granted to groups of users).
Global * Attachments — Configure file attachment settings. Settings * Project Role Browser — Define and assign project roles. * Project Categories — Define the categories used to group projects. * Default Dashboard — Configure the default dashboard for your JIRA Studio instance. * Events — Add, remove and configure events as well as the notification schemes and workflows that they apply to. * General Configuration — Configure general issue settings, such as internationalisation, the ability of customers to vote on and watch issues, visibility of comments and user emails, auto-completion on issue picker and user pickers, etc. * Issue Linking — Manage issue links (e.g. an issue may depend on another issue). This is separate to creating links. * Sub-Tasks — Manage sub-task settings for issues. * Time Tracking — Manage time tracking (i.e. logging work) settings for issues. Time Tracking is OFF by default in JIRA Studio. Read Configuring Time Tracking in the JIRA documentation about how to enable this feature. * User Defaults — Manage the default settings for user profiles. * Workflows — Manage workflows and workflow schemes for your projects. * GreenHopper — Configure the global settings for GreenHopper. Read Configuring your GreenHopper Global Settings in the GreenHopper documentation for more information. You can also configure project-wide settings for GreenHopper. Read Configuring your GreenHopper Project Settings in the GreenHopper documentation for more information. * Bamboo Server — Configure the settings for your Bamboo server (if you are using a hosted Bamboo server with JIRA Studio). Read more about configuring your Bamboo server in the Bamboo documentation.
Schemes * Issue Security Schemes — Manage issue security levels and schemes for your projects (i.e. who can individual issues in a project). * Notification Schemes — Manage notification schemes for your projects (i.e. emails notifications for events during an issue lifecycle). * Permission Schemes — Manage permission schemes for each of your projects. * Workflow Schemes — Manage workflow schemes for your projects. * Scheme Tools — Use scheme tools evolve your schemes from user-based to role-base, and rationalise your schemes.
Issue Fields * Custom Fields — Add, configure and delete your custom fields. * Field Configurations — Configure field behaviour, such as field description, visibility, whether it is enabled, etc. * Field Configuration Schemes — Manage field configuration schemes to apply field configurations to issue types. * Navigator Columns — Configure the navigator columns (used to display results when searching for issues) * Screens — Configure screens, i.e. which fields are displayed on a screen. * Screen Schemes — Configure screen schemes to determine which screen is displayed to a user for a particular issue operation. * Issue Type Screen Schemes — Manage the screen schemes that apply to issue types.
Issue * Issue Types — Add, edit and delete issue types as well as configure issue type schemes and Settings translations (internationalisation). * Priorities — Add, edit and delete issue priorities as well as configure translations (internationalisation) for priorities. * Resolutions — Add, edit and delete issue resolutions as well as configure translations (internationalisation) for resolutions. * Statuses — Add, edit and delete issue statuses (used on workflows) as well as configure translations (internationalisation) for statuses.
System * Send E-mail — Send an email to selected JIRA users in JIRA Studio. * Announcement Banner — Set an HTML announcement that will appear as a system-wide banner in JIRA Studio. * Indexing — Re-index your JIRA application in JIRA Studio. * Mail Queue — Manage the JIRA events queue in JIRA Studio (that may trigger notifications). * Plugins — This is a restricted function in JIRA Studio. * System Info — Display the system information for your JIRA application in JIRA Studio.
Screenshot: 'JIRA Studio — Administering Issues' (click to view larger image) JIRA and GreenHopper Administration Documentation
The guides listed below contain information on how to administer JIRA and GreenHopper. Please note, these guides do not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone JIRA/GreenHopper). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
JIRA Administrator's Guide GreenHopper Administrator's Guide
JIRA Studio-specific Documentation
The following JIRA or GreenHopper functions are specific to JIRA Studio and cannot be found in standalone JIRA/GreenHopper:
Configuring Commit Commands for Issues Configuring Zendesk to Work with JIRA Studio
Configuring Commit Commands for Issues
JIRA Studio allows users to action issues via commit commands. These issue actions include workflow transitions. The default JIRA workflow transitions are mapped to commit commands with equivalent names:
Start Progress — #start Stop Progress — #stop Close Issue — #close Resolve Issue — #resolve Re-open Issue — #reopen
However, if you are using a custom workflow you may wish to add commit commands for any custom workflow transitions, and/or edit the commit commands for the existing workflow transitions.
Note, changes to commit commands are independent of the workflow itself. Hence, you do not need to create a draft workflow when editing the commit commands for an active workflow.
To add a new commit command, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Commit Commands' option in the left menu. The 'Commit Notification Command Mappings' page will display (see screenshot below).
4. Click the 'Add workflow command mapping' link. The 'Edit workflow command mapping details' page will display. 5. Enter the following details: Command — the text that is entered into the commit message, (with a preceding hash symbol), to call this command. Transition — the workflow transition that this command triggers System Transition — system transitions are built-in transitions from the default workflow. These cannot be added or removed from command mappings.
To edit an existing commit command, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab.The Source administration console will display. 3. Click the 'Commit Commands' option in the left menu. The 'Commit Notification Command Mappings' page will display (see screenshot below).
4. Click the 'Edit' link for the commit command that you wish to edit. The 'Edit workflow command mapping details' page will display. 5. Update the following details, as desired: Command — the text that is entered into the commit message, (with a preceding hash symbol), to call this command. Transition — the workflow transition that this command triggers System Transition — system transitions are built-in transitions from the default workflow. These cannot be added or removed from command mappings.
To delete an existing commit command, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Commit Commands' option in the left menu. The 'Commit Notification Command Mappings' page will display (see screenshot below).
4. Click the 'Delete' link for the commit command that you wish to delete.
JIRA Administrator's Guide
JIRA Studio May 2011 includes JIRA 4.3.1 for issue tracking. Use the search or click any of the links below to view the relevant page in the JIRA Administrator's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some JIRA functionality is restricted in JIRA Studio.
Search the JIRA 4.3.1 documentation only:
Getting Help Configuring the Layout and Design
Customising the Look and Feel Choosing a Default Language Configuring the Default Issue Navigator Configuring the Default Dashboard Using Dashboard Gadgets Adding a Gadget to the Directory Subscribing to Another Application's Gadgets Configuring an Announcement Banner Enabling Logout Confirmation
User and Group Management
Configuring User Directories Configuring the Internal Directory Connecting to an LDAP Directory Connecting to an Internal Directory with LDAP Authentication Connecting to Crowd or Another JIRA Server for User Management Managing Multiple Directories Synchronising Data from External Directories Managing Nested Groups Diagrams of Possible Configurations for User Management User Management Limitations and Recommendations Allowing Other Applications to Connect to JIRA for User Management Enabling Public Signup and CAPTCHA Managing Users Managing Groups Managing Project Roles Migrating User Groups to Project Roles Viewing User Sessions User access logging Clearing 'Remember my login' Tokens Disabling Remember My Login on this Computer
Project Management
Defining a Project Managing Project Role Membership Defining a Component Managing Versions Creating Release Notes Configuring Project Keys
Configuring Security
Configuring Issue Level Security Preventing Security Attacks Managing Project Permissions Managing Global Permissions Configuring Secure Administrator Sessions
Configuring Fields and Screens
Configuring Built-in Fields Defining 'Issue Type' Field Values Defining 'Priority' Field Values Defining 'Resolution' Field Values Defining 'Status' Field Values Translating Resolutions, Priorities, Statuses and Issue Types Adding a Custom Field Configuring a Custom Field Creating Help for a Custom Field Specifying Field Behaviour Associating Field Behaviour with Issue Types Configuring Renderers Defining a Screen Associating a Screen with an Issue Operation Associating a Screen with an Issue Type
Configuring Workflow
Activating Workflow Adding a Custom Event
Configuring Email Notifications
Creating a Notification Scheme Customising Email Content Creating Issues and Comments from Email Configuring JIRA to Send SMTP Mail Using Gmail as a JIRA Mail Server Configuring JIRA to Receive POP or IMAP Mail
Migrating from Other Issue Trackers
Importing Data from Bugzilla Importing Data From CSV Commonly Asked CSV Questions and Known Issues How to Import CSV Data with PVCS Command Importing Data From FogBugz Importing Data From Mantis Importing Data From Pivotal Tracker
Moving or Archiving Individual Projects
Archiving a Project Splitting a JIRA instance Integrating with a Source Control System
Integrating JIRA with FishEye Integrating JIRA with CVS and ViewCVS Integrating JIRA with Subversion Integrating JIRA with Perforce Integrating JIRA with ClearCase
Integrating with a Build Management System
Integrating JIRA with Bamboo
Configuring Global Settings
Configuring JIRA Options Setting Properties and Options on Startup Recognized System Properties for JIRA Advanced JIRA configuration with jira-application.properties Configuring File Attachments Configuring Sub-tasks Configuring Issue Linking Enabling Trackback Configuring Time Tracking Configuring the Whitelist Configuring Application Links Adding an Application Link Configuring Authentication for an Application Link Editing an Application Link Making an Application Link the Primary Link Relocating an Application Link Upgrading an Application Link Deleting an Application Link Configuring Entity Links for an Application Link
Server Administration
Increasing JIRA Memory Using the Database Integrity Checker Precompiling JSP pages Database Indexing Logging and Profiling Logging email protocol details Restoring Data Restoring a Project from Backup Optimising Performance Backing Up Data Automating JIRA Backups Preventing users from accessing JIRA during backups Search Indexing Re-Indexing after Major Configuration Changes Using robots.txt to hide from Search Engines Updating your JIRA License Details Viewing your System Information Generating a Thread Dump Performance Testing Scripts Finding the JIRA Support Entitlement Number (SEN)
Appendix A - Extending JIRA
Managing JIRA's Plugins Listeners Services Jelly Tags JIRA Toolkit (Customer Support Extensions) Developer Guides Building JIRA from Source How to Make a JIRA Patch API Documentation
GreenHopper Administrator's Guide
JIRA Studio May 2011 includes GreenHopper 5.6.1 for issue tracking. Use the search or click any of the links below to view the relevant page in the GreenHopper Administrator's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation. Search the GreenHopper 5.6.1 documentation:
Configuring your GreenHopper Global Settings
Restricting GreenHopper to Selected Projects Specifying your Project Templates Specifying your General Configuration Specifying your License Details
Configuring your GreenHopper Project Settings
Setting Up Epics for your Project Configuring your Card Styles Configuring your General Project Settings Configuring your Task Board Settings
Configuring Statistics Optimising Performance Backing Up and Restoring Data Configuring Versions and Components
Adding a Version Releasing a Version Setting Up a Component Hierarchy Setting Up a Version Hierarchy Synchronising Versions and Components for your Issues
Updating your GreenHopper License Details
Configuring Zendesk to Work with JIRA Studio
The Zendesk Support site contains instructions on how to integrate Zendesk with JIRA. These instructions will also work if you would like to integrate Zendesk with JIRA Studio, although you will need to make a few additional changes. Follow the steps below to configure Zendesk to work with JIRA Studio.
On this page:
1. Enable Remote API Calls in JIRA 2. Following the JIRA Integration Guide 3. Request Support to Configure the Zendesk Notifier Plugin
1. Enable Remote API Calls in JIRA
1. Navigate to the Issues administration console in JIRA Studio, as described on Administering Issues. 2. Click 'General Configuration' in the 'Global Settings' section. 3. Click 'Edit Configuration' at the bottom of the page. 4. In the 'Options' section, set 'Accept Remote API calls' to 'ON'. 5. Click 'Update'.
2. Following the JIRA Integration Guide
Read the JIRA Integration guide on the Zendesk Support site.
Note,
You do not have to perform the "Configure JIRA to communicate via SSL with Zendesk" step. In the "Configure the JIRA target and trigger" step, the 'Ticket update via' setting should be 'Is not' – 'Web Service (API)'. You will need to request help from our Support team to configure the Zendesk notifier plugin (in the "Configure the Zendesk Notifier plugin" step). This is described in Step 3 below.
3. Request Support to Configure the Zendesk Notifier Plugin
Once you have followed the JIRA Integration guide linked in Step 2 and can create JIRA issues from Zendesk tickets, the final step is performed by our support team. Please raise a support request to ask for your Zendesk Notifier plugin to be configured with the following information:
The URL of your Zendesk account (e.g. "http://yoursubdomain.zendesk.com") The username (email address) of the Zendesk agent account that is designated for adding comments to Zendesk from JIRA, e.g. "[email protected]". The password for the Zendesk username provided. The name of the custom field you configured earlier, ZendeskID in our example. The JIRA username that will be configured in Zendesk for creating issues and issue comments in JIRA. This must exactly match the username used by the Zendesk widget and target. For example, if the Zendesk target's JIRA username is '[email protected]', the value should be configured as '[email protected]' in the listener configuration. Important: Any comments made on Zendesk-linked issues by this user will be suppressed by the Listener plugin to prevent comment looping. Allow/disallow public comments. If you specify Allow, JIRA comments will be visible to end users in Zendesk. If you specify Disallow, comments will only be visible to agents and admins. Allow/disallow attachments. Specifying Allow Attachments if you'd like JIRA Studio to upload attachments to Zendesk, if not specify Disallow Attachments.
Configuring JIRA Plugins in JIRA Studio
JIRA plugins in JIRA Studio are managed via the Universal Plugin Manager (UPM). This page provides information about the Universal Plugin Manager (UPM) and links to topics on how to work with JIRA plugins by using the UPM.
Prerequisite: You must have administrator permissions in order to work with plugins.
The Universal Plugin Manager (UPM) provides you with a powerful and user-friendly interface to manage your plugins. The Universal Plugin Manager itself is a plugin, which contains a number of modules that are implementations of the Atlassian REST plugin module type. With the Universal Plugin Manager, you can perform the common plugin tasks such as:
Enabling and disabling plugins and their plugin modules. Configuring advanced plugin options. Viewing the audit log for plugin activity.
Restriction: The Universal Plugin Manager in JIRA Studio does not allow you to install or remove plugins. You can only enable or disable the bundled plugins in JIRA Studio as needed. For more information, please read the JIRA Studio Plugin Policy.
Read more about the Universal Plugin Manager in the topics linked below:
Disabling or Enabling a JIRA Plugin in JIRA Studio Viewing your JIRA Plugins in JIRA Studio Viewing the JIRA Plugin Audit Log in JIRA Studio
Having problems with the Universal Plugin Manager? Try the Universal Plugin Manager FAQ. The link will redirect you to the Universal Plugin Manager documentation. Use the back button on your browser to return to this page.
Disabling or Enabling a JIRA Plugin in JIRA Studio
The Universal Plugin Manager (UPM) allows you to enable and disable a JIRA plugin on your JIRA Studio instance. You can also disable all user-installed plugins in your application with one single click by enabling Safe Mode, which might help you diagnose a plugin-related problem more easily.
Restriction: You cannot install new plugins nor remove existing plugins in JIRA Studio as per the JIRA Studio Plugin Policy.
On this page:
Disabling a Plugin Enabling a Plugin Disabling and Enabling all User-Installed Plugins (Safe Mode)
Disabling a Plugin
To access the JIRA Universal Plugin Manager in JIRA Studio:
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues (JIRA) administration console will display. 3. In the left menu, click System > Plugins. The Universal Plugin Manager will display, showing the plugins installed in JIRA on your JIRA Studio instance.
To disable a JIRA plugin in JIRA Studio:
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon: 2. Locate the plugin that you want to disable and click the title to expand the plugin details section. 3. Click the 'Disable' button. 4. Once a plugin has been disabled, you may need to restart your application for your change to take effect. If so, you will see a 4. message for the plugin, 'Disabled, requires restart'. Once the plugin is fully disabled, you will see an 'Enable' link for the plugin.
Enabling a Plugin
To access the JIRA Universal Plugin Manager in JIRA Studio:
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues (JIRA) administration console will display. 3. In the left menu, click System > Plugins. The Universal Plugin Manager will display, showing the plugins installed in JIRA on your JIRA Studio instance.
To enable a JIRA plugin in JIRA Studio:
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon: 2. Locate the plugin that you want to enable and click the title to expand the plugin details section. 3. Click the 'Enable' button. 4. Once a plugin has been enabled, you may need to restart your application for your change to take effect. If so, you will see a message for the plugin, 'Enabled, requires restart'. Once the plugin is fully disabled, you will see a 'Disable' link for the plugin.
Disabling and Enabling all User-Installed Plugins (Safe Mode)
Running your application in Safe Mode disables all user-installed (i.e. non-system) plugins at once. All plugins that were disabled when you entered Safe Mode will be re-enabled when you exit Safe Mode.
To access the JIRA Universal Plugin Manager in JIRA Studio:
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues (JIRA) administration console will display. 3. In the left menu, click System > Plugins. The Universal Plugin Manager will display, showing the plugins installed in JIRA on your JIRA Studio instance.
To enable Safe Mode,
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. 2. Click the 'Enable Safe Mode' button. 3. Click the 'Continue' button in the confirmation window. All user installed plugins will be disabled and your application will now be running in 'Safe Mode'. 4. You can now make changes to your installed plugins as desired. For example, you may want to enable/disable specific plugins or plugin modules. 5. Exit safe mode by clicking one of the links in the Safe Mode banner: Click 'Exit Safe Mode and restore the previous configuration' to restore your plugin configuration to its state before you entered Safe Mode. Click 'Exit Safe Mode and keep the current configuration' to keep all changes made to your plugin configuration during Safe Mode.
Viewing your JIRA Plugins in JIRA Studio The Universal Plugin Manager (UPM) allows you to easily view all the JIRA plugins bundled in your JIRA Studio instance.
On this page:
Viewing the JIRA Bundled Plugins Viewing a Plugin's Details
Viewing the JIRA Bundled Plugins
To access the JIRA Universal Plugin Manager in JIRA Studio:
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues (JIRA) administration console will display. 3. In the left menu, click System > Plugins. The Universal Plugin Manager will display, showing the plugins installed in JIRA on your JIRA Studio instance.
To view the JIRA bundled plugins:
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. The plugins are grouped into 'User-installed Plugins' and 'System Plugins'. You can filter your list by entering keywords in the 'Filter visible plugins' text box. The list of 'System Plugins' will be hidden by default. Click the 'Show System Plugins' link to see them.
Enabled plugins will have this icon: Disabled plugins will have this icon: Click the name of a plugin to view the plugin's details. Click 'Enable Safe Mode' to run your application in safe mode. This mode disables all user installed plugins.
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that shipped with the stand-alone version of the product and included in JIRA Studio. These plugins are integral to the functioning of the system and cannot be disabled. User-installed plugins are not included with the stand-alone version of the product and have been bundled with JIRA Studio. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well, although modules that are integral to the functioning of the plugin cannot be disabled.
Viewing a Plugin's Details
You can view the details for a plugin when you click the plugin name in the installed plugins list. The details contain a short description of the plugin as well as buttons and links for plugin operations.
Unable to render {include} Couldn't find a page to include called: UPM:_viewPluginDetailsStudio
Related Topics
Disabling or Enabling a JIRA Plugin in JIRA Studio
Viewing the JIRA Plugin Audit Log in JIRA Studio
The Universal Plugin Manager (UPM) keeps a log of all the plugin activities in your JIRA Studio instance, for example enabling plugins and disabling plugins.
To access the JIRA Universal Plugin Manager in JIRA Studio: 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues (JIRA) administration console will display. 3. In the left menu, click System > Plugins. The Universal Plugin Manager will display, showing the plugins installed in JIRA on your JIRA Studio instance.
To view the plugin audit log:
1. Click the 'Audit Log' tab. The plugin audit log will appear, showing the 25 most recent entries. 2. Use the arrows if you want to view older entries. 3. Click the orange RSS icon if you want to receive the audit log activity in an RSS feed.
Screenshot: Viewing the plugins audit log
Administering the Wiki
The wiki is a collection of pages (online documents). The wiki is useful for collaboration, information sharing and documentation.
Confluence in JIRA Studio Please note the following important information regarding your wiki application (Confluence) in JIRA Studio:
The version of Confluence running in JIRA Studio may differ slightly from the latest released version of standalone Confluence. Please refer to JIRA Studio Application Versions for that latest version information. Some functions in Confluence are restricted for security reasons. Read more about Restricted Functions in JIRA Studio.
On this page:
Administering the Wiki Confluence Administration Documentation JIRA Studio-specific Documentation
Administering the Wiki
To administer the wiki,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display (see screenshot below). Each of the administration options for your 'Wiki' application are divided into the categories listed below. For details about administering Confluence, please see the 'Confluence Administration Documentation' section below.
Category Functions
Configuration * Global Configuration — Configure your global wiki settings including feature settings, security and privacy, formatting and international settings, attachment settings and connection timeouts. * Manage Referrers — Manage external referrers for your wiki. * Shortcut Links — Add, edit and delete your custom shortcut links. * External Gadgets — Add Atlassian gadgets from applications such as Confluence, JIRA and others, or add gadgets from other websites such as iGoogle. * Global Templates — Set up predefined page templates for use across your wiki. * JIRA Issues Icon Mapping — Associate icons to any custom issue types, priorities or workflow statuses for the JIRA Issues macro. * Spam Prevention — Adjust spam prevention settings, such as Captcha. * Default Space Content — Customise the default content of the home page of a new space. * Configure Whitelist — Manage whitelist for your wiki to restrict access to specified websites (e.g. via {html-include} and {rss} macros). * WebDAV Configuration — Configure WebDAV (file management) for your wiki. * Plugins — Configure, enable and disable plugins for your wiki.
Permissions * Manage Users & Manage Groups — see Managing Users and Groups * Global Permissions — Manage the permissions assigned to user groups for your wiki. * Space Permissions — Manage the permissions assigned to user groups for your wiki spaces (for example, the wiki for each JIRA Studio project). You can also set the default space permissions.
Please note, the wiki administration console described above is used for administering your wiki application. If you would like to administer a space, e.g. edit the space details, change the theme, configure the space permissions, etc, you need to use the 'Space Admin' console. This is accessed by navigating to the desired space and selecting 'Space Admin' from the 'Browse' menu.
Screenshot: 'JIRA Studio — Administering the Wiki' (click to view larger image)
Confluence Administration Documentation The guide listed below contains information on how to administer Confluence. Please note, this guide does not contain documentation on JIRA Studio-specific functions (for example, functions that cannot be found in standalone Confluence). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
Confluence Administrator's Guide
JIRA Studio-specific Documentation
The following Confluence functions are specific to JIRA Studio and cannot be found in standalone Confluence:
Configuring Default Space Permissions
Configuring Default Space Permissions
Every space in your JIRA Studio wiki has its own unique set of permissions for user groups. These space permissions can be configured separately, as described in Space Permissions Overview. JIRA Studio also allows you to configure a set of default permissions for user groups that are applied to all newly created spaces in your wiki.
To configure the default space permissions,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki administration console will display. 3. Click the 'Permissions' option in the left menu, then click the 'Space Permissions' option that appears below it. The ' Space Permissions' screen will display (see first screenshot below). The table under the 'Default Space Permissions' header shows the permissions assigned to user groups by default when a space is created. 4. Click the 'Edit Permissions' button to edit the default space permissions. The table will display in editable mode (see second screenshot below). Update the default space permissions as follows: Check the desired checkbox to grant the permission for a function (column) to a user group (row). Uncheck the desired checkbox to remove the permission for a function (column) from a user group (row). Enter the name of the user group in the 'Grant browse permission to' textbox and click the 'Add' button to grant the 'View' permission to a user group not listed in the table. You can then grant additional permissions to that group by checking more checkboxes in the user group's row. Tip: if you are not sure of the name of a user group, you can click the magnifying glass icon search for the user group. 5. Click the 'Save' button to save your changes.
Screenshot: 'Viewing Space Permissions'
Screenshot: 'Editing Default Space Permissions'
Confluence Administrator's Guide
JIRA Studio May 2011 includes Confluence 3.5.3 for its wiki. Use the search or click any of the links below to view the relevant page in the Confluence Administrator's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some Confluence functionality is restricted in JIRA Studio.
Search the Confluence 3.5.3 documentation:
Administration
Cache Statistics Confluence Data Directory Configuration Content Index Administration Finding Unused Spaces Important Directories and Files Confluence Home Directory Confluence Installation Directory Installing a Language Pack Configuring Backups User Submitted Backup & Restore Scripts Manually Backing Up The Site Migrating Confluence Between Servers Restoring a Site Restoring a Space Changing the version of a space backup Restoring a Test Instance from Production Restoring Data from other Backups Restoring Data from the Administration Console Retrieve file attachments from a backup Troubleshooting failed XML site backups Troubleshooting XML backups that fail on restore Migrating from HSQLDB to MySQL Rebuilding the Ancestor Table Viewing and Editing License Details Viewing System Information Live Monitoring Using the JMX Interface Tracking Customisations Made to your Confluence Installation Viewing Site Statistics Viewing System Properties Installing Patched Class Files Finding Your Confluence Support Entitlement Number (SEN)
Configuring Confluence
Site Configuration Configuring the Site Home Page Configuring the Administrator Contact Page Editing the Site Title Showing Link Icons Editing the Global Logo Configuring the Server Base URL Customising Default Space Content Configuring the Destination of View Space Links Editing the Site Welcome Message Configuring the Site Support Address Configuring the What's New Dialog Configuring Encoding Character encodings in Confluence Troubleshooting Character Encodings Configuring Mail Configuring a Server for Outgoing Mail Enabling the 'Mail Page' plugin The Mail Queue Optional Settings Attachment Storage Configuration Configuring a WebDAV client for Confluence Configuring Quick Navigation Enabling CamelCase Linking Enabling OpenSearch Enabling Rich Text Editing Option Enabling the Did You Mean Feature Enabling the Remote API Enabling Threaded Comments Enabling Trackback Making Rich Text Editing default Other Settings Configuring Attachment Size Configuring Character Encoding Configuring HTTP Timeout Settings Configuring Indexing Language Configuring Number Formats Configuring Shortcut Links Configuring Time and Date Formats Number of Ancestors to Show in Breadcrumbs Thumbnail Settings Configuring System Properties Recognised System Properties Configuring a Large Confluence Installation Configuring Logging External Gadgets
Confluence Clustering Overview
Technical Overview of Clustering in Confluence Cluster safety mechanism Changing Datasources Manually in a Cluster Cluster Troubleshooting Cluster Panic triggers Multicast Test Clustering for Scalability vs Clustering for High Availability (HA) Recommended network topology Cluster Administration page Cluster Checklist
Confluence Security
Confluence Community Security Advisory 2006-01-19 Confluence Security Advisory 2005-02-09 Confluence Security Advisory 2005-12-05 Confluence Security Advisory 2006-01-20 Confluence Security Advisory 2006-01-23 Confluence Security Advisory 2006-06-14 Confluence Security Advisory 2007-07-26 Confluence Security Advisory 2007-08-08 Confluence Security Advisory 2007-11-19 Confluence Security Advisory 2007-11-27 Confluence Security Advisory 2007-12-14 Confluence Security Advisory 2008-01-24 Confluence Security Advisory 2008-03-06 Confluence Security Advisory 2008-03-19 Confluence Security Advisory 2008-05-21 Confluence Security Advisory 2008-07-03 Confluence Security Advisory 2008-09-08 Confluence Security Advisory 2008-10-14 Confluence Security Advisory 2008-12-03 Confluence Security Advisory 2009-01-07 Confluence Security Advisory 2009-02-18 Confluence Security Advisory 2009-04-15 Confluence Security Advisory 2009-06-01 Confluence Security Advisory 2009-06-16 Confluence Security Advisory 2009-08-20 Confluence Security Advisory 2009-10-06 Confluence Security Advisory 2009-12-08 Confluence Security Advisory 2010-05-04 Confluence Security Advisory 2010-06-02 Confluence Security Advisory 2010-07-06 Confluence Security Advisory 2010-08-17 Confluence Security Advisory 2010-09-21 Confluence Security Advisory 2010-10-12 Confluence Security Advisory 2010-11-15 Confluence Security Advisory 2011-01-18 Confluence Security Advisory 2011-03-24
Configuring Confluence Security
Confluence Cookies Configuring Secure Administrator Sessions Using Fail2Ban to limit login attempts Securing Confluence with Apache Using Apache to limit access to the Confluence administration interface Enabling or Disabling Public Signup Managing External Referrers Excluding external referrers Hiding external referrers Ignoring External Referrers Best Practices for Configuring Confluence Security Hiding the People Directory Configuring Captcha for Spam Prevention Hiding External Links From Search Engines Configuring Captcha for Failed Logins Configuring XSRF Protection User Email Visibility Anonymous Access to Remote API Running Confluence Over SSL or HTTPS Connecting to LDAP or JIRA or Other Services via SSL Configuring the Maximum Size of RSS Feeds
Design and Layout
Choosing a Default Language Custom Decorator Templates Customising Look and Feel Overview Customising Colour Schemes Customising Layouts Global Templates Importing Templates Modify Confluence Interface Text Working With Decorator Macros Customising a Specific Page Customising PDF or HTML Content Customising the Dashboard Customising the eMail Templates Customising the Login Page Themes Overview Applying a Theme to a Site Customising the Left Navigation Theme Modifying Look and Feel (for themes) Creating a Theme
Importing Data
Importing Content from another Wiki Snip Snap Import
Installing Plugins and Macros
Installing and Configuring Plugins using the Universal Plugin Manager Checking Plugin Compatibility for Confluence Upgrades Configuring a Plugin Disabling or Enabling a Plugin Installing a Plugin Uninstalling a Plugin Upgrading your Existing Plugins Viewing the Plugin Audit Log Viewing your Installed Plugins Plugin loading strategies in Confluence Removing Malfunctioning Plugins Enabling and Configuring Macros Configuring a URL Whitelist Configuring the userlister Macro Enabling HTML macros Troubleshooting the Gallery Macro Adding, Editing and Removing User Macros Writing User Macros Configuring the Office Connector
Operating Large or Mission-Critical Confluence Installations Performance Tuning
Cache Performance Tuning Cache Performance Tuning for Specific Problems Confluence Cache Schemes Memory usage and requirements Requesting Performance Support Access Log Scripts Troubleshooting Slow Performance Using Page Request Profiling Compressing an HTTP Response within Confluence Performance Testing Scripts Garbage Collector Performance Issues
Scheduled Jobs Search
Setup Confluence To Index External Sites Setup External Search Tool To Index Confluence
Working with Confluence Logs
log4j Logging Levels
User Management
Understanding User Management in Confluence Configuring User Directories Configuring the Internal Directory Connecting to an LDAP Directory Connecting to an Internal Directory with LDAP Authentication Connecting to Crowd or JIRA for User Management Connecting to JIRA 4.2 or Earlier for User Management Managing Multiple Directories Managing Nested Groups Synchronising Data from External Directories Diagrams of Possible Configurations for User Management User Management Limitations and Recommendations Requesting Support for External User Management Confluence User Management Searching For and Managing Users Adding a New User Adding a Group Adding or Removing Users in Groups Changing Usernames Editing User Details Global Groups Overview Global Permissions Overview Removing a Group Removing or Deactivating a User Setting up Anonymous Access Viewing members of a group Restoring Passwords To Recover Admin User Rights Resetting the Login Count for a User Disabling the Built-In User Management
Integrating Confluence with Other Applications
Configuring Application Links Adding an Application Link Configuring Authentication for an Application Link Editing an Application Link Making an Application Link the Primary Link Relocating an Application Link Upgrading an Application Link Deleting an Application Link Configuring Project Links across Applications Configuring OAuth Confluence and JIRA Installing Confluence and JIRA Together Integrating JIRA and Confluence Setting Up Trusted Communication between JIRA and Confluence
Applying a Theme to a Space
On this page:
What's a theme? Themes in JIRA Studio Applying a Theme to a Space Customising the JIRA Studio Documentation Theme
What's a theme?
Themes allow you to personalise the 'look and feel' of JIRA Studio. You can apply a theme to each of your JIRA Studio wiki spaces. Choose a specific theme to provide specific functionality or to significantly alter the appearance of your wiki.
Further information is available in the Confluence documentation for Customising Look and Feel.
Themes in JIRA Studio
JIRA Studio comes with a selection of themes:
Theme Features
Default Theme This is the default look and feel of all JIRA Studio wiki spaces. Using this theme enables you to customise the colour scheme and layout for individual spaces.
JIRA Studio This theme features a Cross-Application Navigation Bar, which contains tabs for easy access to your Issues,Wiki, Theme Source, Reviews, and Build functionality.
JIRA Studio You can configure this theme to include a collapsible left navigation sidebar, custom sidebar links, and header and Documentation footer text. The sidebar contains a collapsible navigation tree that can be used to browse through the space. Your wiki Theme will retain the JIRA Studio header, along with any custom logos you have uploaded.
Please see Customising the JIRA Studio Documentation Theme below for instructions and examples of how to tailor this theme to your needs.
Applying a Theme to a Space
Applying a theme to a space,
1. Log into JIRA Studio as an administrator. 2. Select your desired project from the 'Projects' dropdown in the top left of your page. The Issues dashboard for your project will display. 3. Click the 'Wiki' tab. The homepage for your project will display. 4. Click the 'Browse' dropdown menu in the top right of your page and select the 'Space Admin' option. The 'Space Administration' console for your space will display. 5. From the 'Look and Feel', area of the left options, select 'Themes'. The current theme and themes available for selection will display (see screenshots below). 6. Click the radio button next to your required theme, then click the 'Confirm' button to select this theme. Screenshot: 'Selecting a theme'
Customising the JIRA Studio Documentation Theme
Customising the JIRA Studio Documentation Theme,
1. Log into JIRA Studio as an administrator. 2. Select your desired project from the 'Projects' dropdown in the top left of your page. The Issues dashboard for your project will display. 3. Click the 'Wiki' tab. The homepage for your project will display. 4. Click the 'Browse' dropdown menu in the top right of your page and select the 'Space Admin' option. The 'Space Administration' console for your space will display. 5. From the 'Look and Feel', area of the left options, select 'Themes'. The current theme and themes available for selection will display (see screenshot below). 6. Click the radio button next to the JIRA Studio Documentation Theme, then click the 'Confirm' button to select this theme. 7. Select 'Configure Theme' to further customise the theme, for example, by providing header and footer messages, or links.
Screenshot: Configuring your JIRA Studio Documentation Theme (click to view fullsize image)
1. Customising the JIRA Studio Documentation Theme 2. Customising the JIRA Studio Documentation Theme
Configuring Confluence Plugins in JIRA Studio
Conflunce plugins in JIRA Studio are managed via the Universal Plugin Manager (UPM). This page provides information about the Universal Plugin Manager (UPM) and links to topics on how to configure plugins using the UPM. Note that you must have administrator permissions in order to configure plugins.
The Universal Plugin Manager (UPM) provides you with a powerful and user-friendly interface to manage your plugins. The Universal Plugin Manager itself is a plugin, which contains a number of modules that are implementations of the Atlassian REST plugin module type. With the Universal Plugin Manager, you can perform the common plugin tasks such as:
Enabling and disabling plugins and their plugin modules. Configuring advanced plugin options. Viewing the audit log for plugin activity.
Restriction: The Universal Plugin Manager in JIRA Studio does not allow you to install or remove plugins. You can only enable or disable the bundled plugins in JIRA Studio as needed. For more information, please read the JIRA Studio Plugin Policy.
Read more about the Universal Plugin Manager in the topics linked below:
Configuring a Confluence Plugin in JIRA Studio Disabling or Enabling a Confluence Plugin in JIRA Studio Viewing the Confluence Plugin Audit Log in JIRA Studio Viewing your Confluence Plugins in JIRA Studio
Having problems with the Universal Plugin Manager? Try the Universal Plugin Manager FAQ. The link will redirect you to the Universal Plugin Manager documentation. Use the back button on your browser to return to this page.
Configuring a Confluence Plugin in JIRA Studio
A number of Confluence plugins have advanced configuration options. If you have one of these plugins enabled on your JIRA Studio instance, you can view and update these configuration options via the Universal Plugin Manager (UPM).
To access the Confluence Universal Plugin Manager in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To configure a Confluence plugin in JIRA Studio via the UPM,
1. Click the 'Manage Existing' tab. 2. Locate the plugin that you want to configure and click its title. The plugin details section will expand. 3. Click the 'Configure' link for that plugin. The link will be disabled if the plugin is disabled. If there is no 'Configure' link, then there are no advanced configuration options available for that plugin. 4. The advanced configuration options for the plugin will appear. Update the configuration settings as desired and save your changes. Note: The advanced configuration screens are provided by the plugin. If you encounter any problems after you click the 'Configure' link, the plugin is responsible for the issue, not the Universal Plugin Manager.
Screenshot: Configuring a plugin Screenshot: Configuring a plugin example — WebDAV configuration
Related Topics
Disabling or Enabling a Confluence Plugin in JIRA Studio
Disabling or Enabling a Confluence Plugin in JIRA Studio
The Universal Plugin Manager (UPM) allows you to disable a plugin in Confluence on your JIRA Studio instance without permanently removing it. You can also enable any plugins that have been previously disabled, via the UPM. Please note, you cannot add new plugins nor remove existing plugins in JIRA Studio, as per the JIRA Studio Plugin Policy.
You can also disable all user installed plugins in your application, by enabling Safe Mode. This may help you to diagnose a plugin-related problem more easily.
On this page:
Disabling a Plugin Enabling a Plugin Disabling/Enabling all User Installed Plugins (Safe Mode)
Disabling a Plugin
To access the Confluence Universal Plugin Manager in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To disable a Confluence plugin in JIRA Studio, 1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. Enabled plugins will have this icon: 2. Locate the plugin that you want to disable and click the title to expand the plugin details section. 3. Click the 'Disable' button. 4. Once a plugin has been disabled, you may need to restart your application for your change to take effect. If so, you will see a message for the plugin, 'Disabled, requires restart'. Once the plugin is fully disabled, you will see an 'Enable' link for the plugin.
Screenshot: Disabling a Plugin
Enabling a Plugin
To access the Confluence Universal Plugin Manager in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To enable a Confluence plugin in JIRA Studio,
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. Disabled plugins will have this icon: 2. Locate the plugin that you want to enable and click the title to expand the plugin details section. 3. Click the 'Enable' button. 4. Once a plugin has been enabled, you may need to restart your application for your change to take effect. If so, you will see a message for the plugin, 'Enabled, requires restart'. Once the plugin is fully disabled, you will see a 'Disable' link for the plugin.
Screenshot: Enabling a Plugin
Disabling/Enabling all User Installed Plugins (Safe Mode)
Running your application in Safe Mode disables all user installed (i.e. non-system) plugins at once. All plugins that were disabled when you entered Safe Mode will be re-enabled when you exit Safe Mode.
To access the Confluence Universal Plugin Manager in JIRA Studio, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To enable Safe Mode in Confluence,
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. 2. Click the 'Enable Safe Mode' button. 3. Click the 'Continue' button in the confirmation window. All user installed plugins will be disabled and your application will now be running in 'Safe Mode'. 4. You can now make changes to your installed plugins as desired. For example, you may want to enable/disable specific plugins or plugin modules. 5. Exit safe mode by clicking one of the links in the Safe Mode banner: Click 'Exit Safe Mode and restore the previous configuration' to restore your plugin configuration to its state before you entered Safe Mode. Click 'Exit Safe Mode and keep the current configuration' to keep all changes made to your plugin configuration during Safe Mode.
Screenshot: Running Confluence in Safe mode in JIRA Studio
Viewing the Confluence Plugin Audit Log in JIRA Studio
The Universal Plugin Manager (UPM) keeps a log of all plugin activity for Confluence in your JIRA Studio instance, e.g. enabling plugins, disabling plugins, etc.
Viewing the Plugin Audit Log
To access the Confluence Universal Plugin Manager in JIRA Studio, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To view the plugin audit log,
1. Click the 'Audit Log' tab. The plugin audit log will appear, showing the 25 most recent entries. 2. Use the arrows if you want to view older entries. 3. Click the orange RSS icon if you want to receive the audit log activity in an RSS feed.
Screenshot: Viewing the plugins audit log
Viewing your Confluence Plugins in JIRA Studio
The Universal Plugin Manager (UPM) allows you to easily view the plugins bundled with Confluence in your JIRA Studio instance. This includes both enabled and disabled plugins.
On this page:
Viewing the Confluence Bundled Plugins Viewing a Plugin's Details
Viewing the Confluence Bundled Plugins
To access the Confluence Universal Plugin Manager in JIRA Studio, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Wiki' tab. The Wiki (Confluence) administration console will display. 3. Click the 'Plugins' link in the left menu to open the 'Universal Plugin Manager'. The 'Universal Plugin Manager' will be displayed, showing the plugins installed in Confluence on your JIRA Studio instance.
To view the Confluence bundled plugins,
1. Click the 'Manage Existing' tab. You will see a list of the plugins installed in your application. The plugins are grouped into 'User-installed Plugins' and 'System Plugins'. You can filter your list by entering keywords in the 'Filter visible plugins' text box. The list of 'System Plugins' will be hidden by default. Click the 'Show System Plugins' link to see them.
Enabled plugins will have this icon: Disabled plugins will have this icon: Click the name of a plugin to view the plugin's details. Click 'Enable Safe Mode' to run your application in safe mode. This mode disables all user installed plugins.
What is the difference between a 'System Plugin' and a 'User Installed Plugin'?
System plugins are those that shipped with the stand-alone version of the product and included in JIRA Studio. These plugins are integral to the functioning of the system and cannot be disabled. User-installed plugins are not included with the stand-alone version of the product and have been bundled with JIRA Studio. These plugins can be disabled or enabled. Some of the modules of these plugins can be disabled or enabled as well, although modules that are integral to the functioning of the plugin cannot be disabled.
Screenshot: Viewing Bundled Plugins (Confluence) 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 (as described above). The summary contains a short description of the plugin as well as buttons/links for plugin operations and related information.
Screenshot: Viewing a Plugin's Details (Confluence)
Unable to render {include} Couldn't find a page to include called: UPM:_viewPluginDetailsStudio
Related Topics
Configuring a Confluence Plugin in JIRA Studio Disabling or Enabling a Confluence Plugin in JIRA Studio
Administering Source
Your source (e.g. your source code) resides in a repository such as Subversion, Perforce or CVS. FishEye in JIRA Studio Please note the following important information regarding your source application (FishEye) in JIRA Studio:
The version of FishEye running in JIRA Studio may differ slightly from the latest released version of standalone FishEye. Please refer to JIRA Studio Application Versions for that latest version information. Many functions in FishEye are restricted for security reasons. Read more about Restricted Functions in JIRA Studio.
On this page:
Administering Source FishEye/Subversion Administration Documentation JIRA Studio-specific Documentation
Administering Source
To administer source,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source (FishEye/Subversion) administration console will display (see screenshot below). Each of the administration options for your 'Source' application are divided into the categories listed below. For details about administering FishEye/Subversion, please see the 'FishEye/Subversion Administration Documentation' section below.
Category Functions
Default Manage read/commit permissions for your repository, as well as enable/disable anonymous Permissions access.
Project Manage read/commit permissions for your projects. Project-level permissions will override the Permissions default permissions.
Commit Configure commit commands for your repository. Commands
SVN Commit Configure commits to require a JIRA Issue Key . Hooks
Screenshot: 'JIRA Studio — Administering Source'
FishEye/Subversion Administration Documentation
The FishEye/Subversion administration functions in JIRA Studio are JIRA Studio-specific (i.e. cannot be found in standalone FishEye). Please see 'JIRA Studio-specific Documentation' section on this page.
JIRA Studio-specific Documentation
The following FishEye/Subversion functions are specific to JIRA Studio and cannot be found in standalone FishEye/Subversion:
Configuring Repository Permissions for a Project Configuring Default Repository Permissions Enabling Anonymous Access to a Repository
Configuring Repository Permissions for a Project
JIRA Studio allows you to configure the permissions for a project's Subversion repository. You can also configure permissions (commit access only) for specific directories within a Subversion repository. Subversion permissions can be assigned to any user groups that exist in JIRA Studio, but not to individual users. If you want to assign a Subversion permission to a particular user, you can assign the user to a user group with the desired permission.
You can also configure a default set of permissions, which will be applied to the repositories of any new projects created.
Default repository permissions Default Subversion permissions are assigned to the 'users', 'developers' and 'administrators' groups when your JIRA Studio account is first set up. You may wish to change the default repository permissions that are assigned to any projects created in future.
Branches do not inherit path permissions If you have set up path-level permissions for a specific path in your Subversion repository (e.g. /DOM/trunk/private) and then create a branch of that path (e.g. /DOM/branches/branch1/private), the branch will not inherit the path-level permissions. You must set up the path-level permissions for the branch separately.
On this page:
Configuring Repository Permissions for a Project Configuring Commit Permissions for a Repository Directory
Configuring Repository Permissions for a Project
To configure repository permissions for a project, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Project Permissions' option in the left menu. The 'SVN Permission Manager' page will display (see screenshot below), listing all projects that you have permission to administer. 4. Click the 'Configure' link next to the project that you wish to update the Subversion permissions for.
The 'SVN Permission Manager' page also contains two other links: 'Synchronise FishEye permissions' — this link will set your FishEye permissions to be the same as your Subversion permissions. You should not have to use this function, except on advice from the Atlassian Support team. 'Modify settings applied to new projects' — this link takes you to the Configuring Default Repository Permissions page.
5. The 'Manage Repository' page will display (see screenshot below). The 'Read' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The 'Commit' panel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository. You can grant the 'Read' permission to a user group, by selecting the user group in the 'Group' dropdown under the 'Read' panel and clicking 'Add'. Similarly, you can grant the 'Commit' permission to a user group, by selecting the user group in the 'Group' dropdown under the 'Commit' panel and clicking 'Add'. Note, that a user group does not need to be granted the 'Read' permission, if it has been granted the 'Commit' permission. To remove a permission from a user group, click the 'remove' link next to the user group. Note, that removing the 'Commit' permission from a user group will remove read and write access from the user group. You will need to add the 'Read' permission to the user group, if you still wish the user group to retain read access to your repository.
Path permission changes may take a few minutes to take effect, due to caching. Anonymous access to a project's repository is disabled by default. You can enable anonymous access to a repository via the administration console in JIRA Studio. Read more about Enabling Anonymous Access to a Repository.
Screenshot: 'Subversion Permission Manager'
Removing a repository from FishEye will remove the directory from the SVN Permission Manager. You can still modify the SVN permissions by using the arbitrary path input box
Screenshot: 'Managing repository permissions for a project' Configuring Commit Permissions for a Repository Directory
To configure commit permissions for a repository directory, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Project Permissions' option in the left menu. The 'SVN Permission Manager' page will display (see screenshot below), listing all projects that you have permission to administer. 4. Enter the path of the directory that you wish to configure permissions for in the 'Modify commit permissions for an arbitrary path:' text box and click 'Add'. 5. The 'Manage Permissions for Path:' page will display (see screenshot below). The permissions shown will be inherited from the parent or project in the repository hierarchy, unless explicitly overridden. If a user group has the 'Read Only' permission (under the 'Actual' column), users in the group will be able to access the path but not commit to the path. Read only permission may have been inherited from the parent or project in the repository hierarchy, or explicitly granted/overridden. If a user group has the 'Commit' permission (under the 'Actual' column), users in the group will be able to commit to the path. The 'Commit' panel lists all of the user groups that have the 'Commit' permission for the path. Commit permission may have been inherited from the parent or project in the repository hierarchy, or explicitly granted/overridden. 6. To add, change or remove the path permissions for a user group, To add path permissions to a user group, a. Select the desired user group in the first dropdown under the 'Add Permission' section and select the desired path permission in the second dropdown. b. Click the 'Add' button. The path permissions will be added. To change the existing path permissions for a user group, a. Locate the group and select the desired path permission under the 'Actual' column. b. Click the 'Save' button. The path permissions will be updated. To remove an existing path permission for a user group, a. Locate the group and check the checkbox under the 'Remove' column. b. Click the 'Save' button. The path permissions will be removed.
Path permission changes may take a few minutes to take effect, due to caching.
Screenshot: 'Managing repository permissions for a path'
Configuring Default Repository Permissions
JIRA Studio allows you to configure a default set of permissions, which will be applied to the Subversion repositories of any new projects created. You can also set up permissions for the repositories of each your projects individually, to override the default permissions. Read more about configuring repository permissions for a project.
Subversion permissions can be assigned to any user groups that exist in JIRA Studio, but not to individual users. If you want to assign a Subversion permission to a particular user, you can assign the user to a user group with the desired permission.
Default Subversion permissions are assigned to the 'users', 'developers' and 'administrators' groups when your JIRA Studio account is first set up. You may wish to change these permissions for any projects you have already set up.
To configure default repository permissions,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Default Permissions' option in the left menu. 4. The 'Manage Default Repository Permissions' page will display (see screenshot below). The 'Read' panel lists all of the user groups that have the 'Read' permission for the project's Subversion repository. The 'Commit' panel lists all of the user groups that have the 'Commit' (i.e. read and write) permission for the project's Subversion repository. You can grant the 'Read' permission to a user group, by selecting the user group in the 'Group' dropdown under the 'Read' panel and clicking 'Add'. Similarly, you can grant the 'Commit' permission to a user group, by selecting the user group in the 'Group' dropdown under the 'Commit' panel and clicking 'Add'. Note, that a user group does not need to be the 'Read' permission, if it has been granted the 'Commit' permission. To remove a permission from a user group, click the 'remove' link next to the user group. Note, that removing the 'Commit' permission from a user group will remove read and write access from the user group. You will need to add the 'Read' permission to the user group, if you still wish the user group to retain read access to your repository.
Anonymous access to your project repository is disabled by default. You can enable anonymous access to your repository via the administration console in JIRA Studio. Read more about Enabling Anonymous Access to a Repository.
Screenshot: 'Manage Default Repository Permissions' Enabling Anonymous Access to a Repository
Anonymous access to project repositories can be enabled in JIRA Studio. This will allow anonymous users to access the 'Source' tab in Studio and grant them read-only access to the project repository (e.g. allowing code checkouts, exports, etc). Please carefully consider the security implications of allowing anonymous access to your project repositories before enabling this feature.
Anonymous repository access can be enabled for each individual project. You can also enable anonymous repository access for all new projects created. By default, anonymous access is disabled in your Studio instance.
Note, you cannot enable/disable anonymous access globally for all projects. You must change this setting for each project separately.
To enable anonymous repository access for a project in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Project Permissions' option in the left menu. The 'SVN Permission Manager' page will display, listing all projects that you have permission to administer. 4. Click the 'Configure' link next to the project that you wish to enable anonymous repository access for. The 'Manage Repository' page will display (see screenshot below). 5. Click 'Enable anonymous access' to enable anonymous access to for the project. This will override your global preferences for anonymous repository access in JIRA Studio.
Screenshot: Enable anonymous repository access for a project repository
To enable anonymous repository access for all new projects created in JIRA Studio, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'Default Permissions' option in the left menu. The 'Manage Default Repository Permissions' page will display (see screenshot below). 4. Click 'Enable anonymous access' to enable anonymous access to all project repositories in your JIRA Studio instance.
Screenshot: Enable anonymous repository access for all new projects
Configure Commits to Require a JIRA Issue Key
JIRA Studio enables users to require commits be associated with a JIRA Issue Key. This functionality allows you to enforce the inclusion of an open JIRA issue, or a JIRA ticket number in a commit.
To require commits to include a JIRA issue, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Source' tab. The Source administration console will display. 3. Click the 'SVN Commit Hooks' option in the left menu. The 'SVN Commit Hooks' page will display (see screenshot below). Screenshot: Configuring SVN Commit Hooks
4. Select the checkbox, 'Require JIRA issue key for a successful commit'. 5. Click 'Save'.
Administering Reviews
Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being committed to a repository.
Crucible in JIRA Studio Please note the following important information regarding your reviews application (Crucible) in JIRA Studio:
The version of Crucible running in JIRA Studio may differ slightly from the latest released version of standalone Crucible. Please refer to JIRA Studio Application Versions for that latest version information. Many functions in Crucible are restricted for security reasons. Read more about Restricted Functions in JIRA Studio.
On this page:
Administering Reviews JIRA Studio-specific Documentation
Administering Reviews
To administer reviews, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
Project review permissions are inherited from Crucible's default permission schemes. However, they are modified according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions that apply to a project's source also apply to that project's reviews. You configure the default project permissions that apply to the repositories of any new projects in the Default Permissions area. You configure the permissions for a project's repository in the Project Permissions area.
2. Click the 'Source' tab, then select either Default Permissions or Project Permissions as required (see Source Tab screenshot below). 3. Click the 'Reviews' tab. The Reviews administration console will display (see Reviews Tab screenshot below). Each of the administration options for your 'Reviews' application are divided into the categories listed below. Clicking the links in the table below will redirect you to the Crucible documentation. Use the 'Back' button on your browser to return to the JIRA Studio documentation.
Category Functions
Review Defaults Configure the default settings for new reviews for each of your projects.
New Project Defaults Select the default review period, and specify if a moderator is required
Defect Classifications Customise the defect classifications for your reviews.
Screenshot: 'JIRA Studio — Administering Reviews' (click to view larger image)
1. Source Tab 2. Reviews Tab
JIRA Studio-specific Documentation
Project review permissions are inherited from Crucible's default permission schemes. However, they are modified according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions that apply to a project's source also apply to that project's reviews.
Note that changes to your project default repository permissions only apply to future projects. Projects created previously retain their permissions scheme.
Administering Builds
The source in your repository can be built by the 'Builds' application (Bamboo) in JIRA Studio.
First time using Bamboo in JIRA Studio? If you haven't used Bamboo in JIRA Studio before, please read Getting Started with Bamboo in JIRA Studio first. Bamboo in JIRA Studio Please note the following important information regarding your Builds application (Bamboo) in JIRA Studio:
The version of Bamboo running in JIRA Studio may differ slightly from the latest released version of standalone Bamboo. Please refer to JIRA Studio Application Versions for that latest version information. Many functions in Bamboo are restricted for security reasons. Read more about Restricted Functions in JIRA Studio. Clover is not included by JIRA Studio, and the integration of Clover with Bamboo in JIRA Studio is not supported. The screen captures in the referenced Bamboo documentation might display Clover interfaces and they only apply to the standalone Bamboo.
On this page:
Administering Builds Bamboo Administrator's Documentation JIRA Studio-specific Documentation
Administering Builds
To administer builds, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab. The Builds administration console will display (see screenshot below). Each of the administration options for your 'Builds' application are divided into the categories listed below. For details about administering Bamboo, please see the 'Bamboo Administration Documentation' section below.
Category Functions
Build * Agents — View and manage running (elastic) agents. Resources * Agent Matrix — View which active Bamboo agents can execute which plans (depending on plan requirements and agent capabilities). * Global Variables — Define global variables that can be used across all build plans.
Elastic Bamboo * Configuration — Configure Elastic Bamboo settings. * Instances — View and manage elastic instances. * Image Configurations — Manage elastic image configurations, including custom images, EBS volumes, instance type and availability zone. * Instance Schedule — Schedule the startup and shutdown of instances of a particular elastic image. * Agent History — View the history of elastic agents.
Plans * Build Expiry — Schedule when build results and/or artifacts will be deleted. * Bulk Action — Modify multiple plans at once, e.g. add notifications, etc. * Build Monitoring — Configure build monitoring, including hung build and build queue timeout events. * Remove Plans — Delete build plans. * Move Plans — Move build plans between projects. * Bulk Edit Plan Permissions — Apply permissions to multiple build plans at once.
Security * Global Permissions — Manage Bamboo global plan permissions. Please note, the 'Admin' permission for standalone Bamboo has been renamed 'Restricted Admin' for Bamboo in JIRA Studio. The permission is essentially the same, i.e. grants access to 'Builds' administration, permission to delete plans and access to plan permissions for every plan.
Communication * IM Server — Configure the instant messaging server for Bamboo.
System * General Configuration — Configure general settings, such as the name of the Bamboo instance (displayed on the 'Builds' dashboard), compression of artifacts, enabling the remote API (not the REST API which is enabled by default). * System Information — View system information about Bamboo. * Log Settings — Configure runtime logging settings. * System Errors — View Bamboo system errors.
Favourites * Configure Auto-Favourite Plugin — Enable/Disable the Auto-Favourite Plugin.
Screenshot: 'JIRA Studio — Administering Builds' (click to view larger image)
Bamboo Administrator's Documentation
The guide listed below contains information on how to administer Bamboo. Please note, this guide does not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone Bamboo). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
Bamboo Administrator's Guide
JIRA Studio-specific Documentation
The following Bamboo functions are specific to JIRA Studio and cannot be found in standalone Bamboo:
Getting Started with Bamboo in JIRA Studio Integrating Builds with your Issues Workflow Bamboo Administrator's Guide
Integrating Builds with your Issues Workflow (this is administered on the 'Issues' tab of the administration console)
Getting Started with Bamboo in JIRA Studio
If you are administering Bamboo for the first time in JIRA Studio, you will need to complete a few setup tasks before your users can start running builds. Please follow the steps below to configure Bamboo and your build plans and agents.
On this page:
1. Enable Bamboo 2. Configure Elastic Bamboo 3. Start an Elastic Instance 4. Run a Build 5. Shut Down your Elastic Instance Further Information
1. Enable Bamboo
Bamboo is disabled by default in JIRA Studio. If you want to use Bamboo in JIRA Studio, you must first enable it by raising a support request. You can do this via the the JIRA Studio administration console.
To request Bamboo to be enabled,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab in the administration console (not the JIRA Studio header). The 'Builds' administration console will display. 3. Click the 'Enable Bamboo' button. A support request will be automatically submitted to have Bamboo enabled for your JIRA Studio instance and a confirmation message will display. You will also be sent an email with the support request details, so you can track the progress of your request.
Once we have enabled Bamboo for your JIRA Studio account, your existing JIRA Studio projects will have Bamboo projects created for them. Every new JIRA Studio project created while you have Bamboo enabled will also have a Bamboo project created for it.
2. Configure Elastic Bamboo
Bamboo in JIRA Studio only runs builds on elastic agents using Elastic Bamboo (i.e. you cannot create local or non-elastic remote agents). Elastic Bamboo is a Bamboo feature that utilises computing resources from the Amazon Elastic Compute Cloud (EC2) to run builds. You will need to configure Elastic Bamboo in your JIRA Studio installation before using Bamboo. Read more about Elastic Bamboo in the Bamboo documentation. Elastic Bamboo Costs You can use Elastic Bamboo to run agents on elastic instances in the Amazon Elastic Compute Cloud (EC2). If you choose to do this, you will be charged by Amazon for your EC2 compute usage. These charges will be billed to the AWS account that you provide separate to your JIRA Studio license cost. If you do not have an AWS account, you must register for one on the AWS registration page before you can set up and use Elastic Bamboo.
Full details on Amazon EC2 pricing is available on the Amazon EC2 pricing page. Please also note the following important information, which is relevant to EC2 usage by Elastic Bamboo:
You are responsible for all EC2 compute usage costs incurred on your AWS account. Elastic Bamboo creates "High-CPU Medium" Instances for Bamboo in JIRA Studio. This cannot be changed. You are responsible for creating and shutting down elastic instances to run agents in EC2. You can track your EC2 usage in near real-time on the AWS Account page. Your Elastic Bamboo compute usage will not be distinguishable from your non-Bamboo EC2 compute usage in your AWS billing.
To configure Elastic Bamboo,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab in the administration console (not the JIRA Studio header). The 'Builds' administration console will display. 3. Click the 'Elastic Bamboo' option in the left menu. The 'Configuration Details' page will display. 4. Before you enable Elastic Bamboo, you will need to read and accept the Atlassian Hosted Services Terms of Use. Click the 'Terms of Use' link to view the Terms of Use. When you have read them, click the 'I have read and agree to the Terms of Use' button to accept them. The 'Elastic Bamboo Configuration' page will refresh. 5. Click the 'Enable' button. The 'Elastic Bamboo Configuration' page will refresh, displaying fields to enter your Elastic Bamboo configuration details. 6. Fill out the Elastic Bamboo configuration fields. See Configuring Elastic Bamboo in the Bamboo documentation for more information on these fields. 7. Click the 'Save' button to finish setting up Elastic Bamboo.
3. Start an Elastic Instance
Once you have enabled and configured Elastic Bamboo, you can try running a build with Elastic Bamboo. You can manually start an elastic instance via the Bamboo administration console. Starting an elastic instance will automatically start an elastic agent process on it.
To start an elastic instance, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab in the administration console (not the JIRA Studio header). The 'Builds' administration console will display. 3. Click the 'Elastic Bamboo' option in the left menu, then click the 'Instances' link under it. The 'Manage Elastic Instances' page will display. 4. Click the 'Start New Elastic Instances' link. The 'Start New Elastic Instances' screen will display (see screenshot below). Enter the number of new elastic instances you would like to start in the 'Number of instances' field. The maximum number of elastic agents allowed by Bamboo in JIRA Studio is 25. One elastic agent runs in every elastic instance, hence you can only start a maximum of 25 elastic instances. The 'Elastic Image Configuration Name' will be set to 'Default'. This cannot be changed. Bamboo in JIRA Studio is configured with a default image supplied by Atlassian. To create your own, please read "Can I use a custom Elastic Bamboo image?." 5. Click the 'Submit' button. The 'Manage Elastic Instances' page will display, showing the startup of your new instance(s).
Read more about starting an elastic instance in the Bamboo documentation.
4. Run a Build
To run a build on your elastic agent, you must create a build plan with requirements that can be met by your elastic agent's capabilities. Elastic agents inherit the capabilities of the image that they are started from. Bamboo in JIRA Studio only uses the default image supplied by Atlassian. Read about the capabilities of the default image in the Bamboo documentation.
To create a new build plan,
1. Log into JIRA Studio as an administrator. 2. Click the 'Builds' tab in the JIRA Studio header. The 'Builds' dashboard will display. 3. Specify your build plan as desired. Please see Creating a Plan in the Bamboo documentation for more information on creating build plans. Please also note the following JIRA Studio specific information: The source repository will be defaulted to the Subversion repository of your JIRA Studio project and cannot be changed. The web repository URL is automatically preset to your Source (FishEye) application and is not visible nor editable. 4. Click the 'Save' button when you have finished specifying your build plan. Your plan will be created. When you return to the 'Builds' dashboard, your new plan will be displayed in the 'All Projects' tab.
Your build will be queued and run (provided that you set up the requirements of build plan to be met by an elastic agent). You will see the progress of your build on your 'Builds' dashboard and can view the build result when it has completed. See the Bamboo documentation for more information on viewing the progress of your build and viewing build results.
5. Shut Down your Elastic Instance
When your build has completed successfully, shut down your elastic instance. The bulk of your Elastic Bamboo costs are from instance uptime. Hence, we strongly recommend that you shut down your elastic instances when not in use.
Please ensure that the agent on an elastic instance is not running a build, before shutting down the instance. Any builds running on the agent will be abandoned when you shut down the elastic instance.
To shut down an elastic instance, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab in the administration console (not the JIRA Studio header). The 'Builds' administration console will display. 3. Click the 'Elastic Bamboo' option in the left menu, then click the 'Instances' link under it. The 'Manage Elastic Instances' page will display showing your running elastic instances. 4. Click the 'Shut Down' link in the 'Operations' column, next to the instance that you wish to shut down. The 'Shut Down Instance' screen will display. 5. Click the 'Confirm' button to shut down the elastic instance. The 'Manage Elastic Instances' screen will display again. The elastic instance that you have shut down will display a 'Shutting down' status for a few minutes, before it shuts down and disappears from this screen.
Read more about shutting down elastic instances in the Bamboo documentation.
Please note, that when you shut down an elastic instance, the agent process it is running is terminated. This means that elastic agents are not present on the 'Agents' page in Bamboo unless they are online. If you wish to view information about a terminated elastic agent, you can find the agent in the elastic agent usage history. Read about viewing your elastic agent usage history in the Bamboo documentation.
Congratulations! You successfully set up and ran a build with Bamboo in JIRA Studio.
Further Information
You may be interested in reading the following related topics to help you manage and improve your Bamboo builds:
Integrating Builds with your Issues Workflow — automatically transition issues through the JIRA Studio 'Builds Workflow' via builds. (Bamboo documentation) Managing your Elastic Instances / Managing your Elastic Agents — information hubs for managing Elastic Bamboo images, instances and agents. (Bamboo documentation) Running Job Builds using Elastic Bamboo — general questions about running builds using Elastic Bamboo. (Bamboo documentation) Updating Elastic Images for Bamboo Upgrades — guidelines for updating images when Bamboo is upgraded.
Integrating Builds with your Issues Workflow
JIRA Studio allows you to configure a workflow in your issues application, so that it can be actioned by the completion of a build. For example, you can configure a workflow to automatically progress an issue from 'Building' to 'Resolved' status when an build related to that issue (i.e. JIRA issue key added to commit message) has successfully completed. Alternatively, you can configure the same workflow to progress an issue from 'Building' to 'Build Broken' status if a build related to that issue fails.
A 'Builds Workflow' exists in JIRA Studio that incorporates these common statuses and transitions (see the Understanding the 'Builds Workflow' section below).
If you are new to JIRA and Bamboo, we recommend that you use the 'Builds Workflow' as modifying an existing workflow is not a trivial task. If you have an existing workflow that you would like to modify to include build statuses and transitions, we recommend that you take a copy of the 'Builds Workflow' and modify it. If you want to integrate Bamboo transitions into your existing workflow, you can edit your workflow to add the transitions. We recommend that you avoid doing unless you have a good understanding of JIRA workflows.
On this page:
Understanding the 'Builds Workflow' Using the 'Builds Workflow' Modifying a Copy of the 'Builds Workflow' Integrating Build Transitions into your Custom Workflow Configuring your Issue Statuses Configuring your Issue Transitions
Understanding the 'Builds Workflow' Diagram: 'Builds Workflow' in JIRA Studio
# 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
The 'Wait for Build', 'Build Passed' and 'Build Failed' transitions are Bamboo-specific transitions:
'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build commit command. Note, you must manually enter the #build commit command in your commit message to trigger the transition, as described in Actioning Issues via Commit Messages. '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'
The following instructions describe how to create a workflow scheme that uses the 'Builds Workflow', then associate the workflow scheme with your project. If you want to add the 'Builds Workflow' to an existing workflow scheme, you can ignore steps 4-6 below and assign the workflow to your existing workflow scheme instead. To use the 'Builds Workflow' in your project, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page will appear, listing all of the projects currently set up in JIRA Studio. Click the 'Issues' tab in the administration console (not the JIRA Studio header). The 'Issues' administration console will display. 3. Click the 'Schemes' link in the left menu and click the 'Workflow Schemes' link in the menu that displays. The ' Workflow Schemes' page will display. 4. Click the 'Add' link. The 'Workflow Schemes' page will display. 5. Click the 'Add workflow scheme' link. The 'Add Workflow Scheme' page will display. 6. Enter a 'Name' and 'Description' for your workflow scheme and click the 'Add' button. Your workflow scheme will be created and the 'Edit Workflows for
Issues (of the issue types specified in your workflow scheme) will now use the 'Builds Workflow'. If you add the issue key of an issue to the commit message when committing, the issue will be automatically transitioned along the workflow when the build starts/succeeds/fails.
Modifying a Copy of the 'Builds Workflow'
You cannot modify the 'Builds Workflow' itself as it is non-editable. However, you can copy it and edit the copy if the original 'Builds Workflow' doesn't quite suit the needs of your project. You can then activate your new (copied) workflow by adding it to a workflow scheme then associating that scheme with your project(s).
To copy and edit the 'Builds Workflow',
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page will appear, listing all of the projects currently set up in JIRA Studio. Click the 'Issues' tab in the administration console (not the JIRA Studio header). The 'Issues' administration console will display. 3. Click the 'Schemes' link in the left menu and click the 'Workflow Schemes' link in the menu that displays. The ' Workflow Schemes' page will display. 4. Click the 'View all workflows' link. The 'View Workflows' page will display. 5. Locate the 'Builds Workflow' and click the 'Copy' link in the 'Operations' column. 6. Enter a 'Name' and 'Description' for your new (copied) workflow scheme and click the 'Copy' button. Your workflow scheme will be created and display on the 'View Workflows' page. 7. You can now edit and activate your new workflow as desired. See Configuring Workflow and Activating Workflow in the JIRA documentation for more information on how to do this.
Integrating Build Transitions into your Custom Workflow If modifying a copy of the 'Builds Workflow' is not feasible for your project(s), it is possible to manually modify your existing workflow to include the Bamboo transitions. We recommend that you avoid doing so unless you have a good understanding of JIRA workflows.
To integrate build transitions into your existing custom workflow, you will need to edit your workflow and configure appropriate issue statuses and issue transitions, as described below.
Configuring your Issue Statuses
We recommend that you set up issue statuses for your workflow to indicate when a build related to an issue is building or the build is broken (e.g. 'Building', 'Build Broken'). There is no technical restriction preventing you from incorporating Bamboo-specific build transitions into a JIRA workflow without these intermediate states, however, in practice it will cause problems.
For example, a developer may work on an issue, and commit several times over the course of a few days for that issue. Even if earlier commits cause the build to pass, the developer may not have finished working on the issue and will need to commit more code without successful builds resolving the issue. Hence, an intermediate state (e.g. 'Building') is required which a developer will only transition the issue into (i.e. using the #build commit command), if they want the issue to be resolved from that particular build.
Configuring your Issue Transitions
Automatic issue transitioning via builds is controlled by both commit commands and Bamboo-specific transition properties in JIRA Studio, as described below:
Commit Command — The #build commit command is mapped to the 'Waiting for Build' transition. Hence, if you add the 'Waiting for Build' transition to your workflow, your users will be able to automatically trigger the transition by using the #build commit command in their commit messages. Bamboo-specific transition properties — The Bamboo-specific transition properties on the transitions that you want to be triggered when a Bamboo build passes or fails. The following properties are supported:
Property Value Description
build.passed.transition anything A transition with this property will be triggered when a build for this issue passes, and the transition is available to the issue in its current state.
build.failed.transition anything A transition with this property will be triggered when a build for this issue fails, and the transition is available to the issue in its current state.
build.passed.resolution any valid The issue resolution will be set as specified by this property, if the transition resolution, e.g. with this property is triggered by a build. 'Fixed'
Please note, you cannot set up common transition properties in JIRA. You will need to manually re-enter the transition property on each transition that you want it added to. Alternatively, you can copy and edit the XML file for the 'Builds Workflow', then import it as described in Configuring Workflow#xml in the JIRA documentation. You can find the 'Builds Workflow' XML at webapps/studio-jira/src/main/resources/builds-workflow.xml
Bamboo Administrator's Guide
JIRA Studio May 2011 includes Bamboo 2.6.5 its continuous integration build server. Use the search or click any of the links below to view the relevant page in the Bamboo Administrator's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some Bamboo functionality is restricted in JIRA Studio.
Search the Bamboo 2.6.5 documentation:
Configuring Projects and Plans
About Projects, Plans and Builds Creating a Plan Specifying a Plan's Details Specifying a Plan's Source Repository Specifying a Plan's Builder Specifying a Plan's Capability Requirements Specifying a Plan's Build Artifacts Specifying a Plan's Notifications Specifying a Plan's Post Actions Specifying a Plan's Permissions Editing a Plan Disabling or deleting a Plan Deleting a Build Result Deleting a Plan's Working Files Stopping an Active Build Moving a Plan to a different Project Renaming a Plan or Project Modifying Multiple (Bulk) Plans Importing a Plan from a pom.xml
Configuring Agents and Capabilities
About Agents and Capabilities Configuring Agents Creating a Local Agent Creating a Remote Agent Editing an Agent's Details Disabling or Deleting an Agent Viewing an Agent Monitoring Agent Status Configuring Capabilities Configuring a new Builder Configuring a new JDK Configuring a new Custom Capability Configuring a new Perforce Capability Editing a Capability Renaming a Capability Deleting a Capability Viewing a Capability's Agents and Plans
Working with Builds
Triggering a Build About Build Triggering Triggering a Build when Code is Updated Triggering a Build on Schedule Triggering a Build Manually Setting up Build Dependencies Reordering your Build Queue Monitoring Builds Configuring the Hanging Build Event Configuring the Build Queue Timeout Event Disabling Build Monitoring
Working with Elastic Bamboo
About Elastic Bamboo Elastic Bamboo Costs Getting Started with Elastic Bamboo Configuring Elastic Bamboo Generating your AWS Private Key File and Certificate File Configuring Elastic Instances to use the EBS Managing Elastic Bamboo Managing your Elastic Images Managing your Elastic Instances Managing your Elastic Agents Running Builds using Elastic Bamboo Disabling Elastic Bamboo
Configuring Email and Instant Messaging Notifications
Adding or Removing Notifications for a Plan Modifying Notification Templates Freemarker and Notification Templates Configuring Bamboo to send SMTP Email Configuring Bamboo to use Instant Messaging (IM) Configuring Bamboo to use Google Talk for Instant Messaging
Managing Users and Permissions
Managing Users Creating a User Changing a User's Password or Details Deleting or deactivating a User Granting Administration Rights to a User Managing Groups Creating a Group Deleting a Group Adding Users to and removing them from Groups Managing Permissions for Users and Groups Granting Plan Permissions to Users or Groups Granting Global Permissions to Users or Groups Allowing Anonymous Users to access Bamboo Global Security and Permission Properties Enabling or Disabling Public Signup Enabling or Disabling Contact Details Display Enabling or Disabling Captcha for Failed Logins Working with External User Repositories Integrating Bamboo with Crowd Integrating Bamboo with LDAP
Managing Data and Backups
Locating Important Directories and Files Specifying Bamboo's Working Directory Viewing your Database Connection Details Moving your Bamboo Data to a different Database Optimising or Re-indexing Data Enabling Expiry of Build Results Specifying a Backup Schedule Exporting Data for Backup Importing Data from Backup
Configuring System Settings
Viewing Bamboo's System Information Updating your Bamboo License Details Specifying Bamboo's Title Specifying Bamboo's URL Logging in Bamboo Enabling GZIP Compression Enabling Bamboo's Remote API Configuring System Properties
Managing Bamboo Security
Configuring OAuth Consumers Elastic Bamboo Security
Configuring Plugins
About Bamboo Plugins Enabling the 'Auto-Favourites' Plugin Enabling the Clover Plugin Installing a new Plugin
Using Bamboo with Other Applications
Embedding Bamboo into Other Applications Javascript Widgets Integrating Bamboo with Other Applications Integrating Bamboo with JIRA
Administering Projects
Administering Projects
Adding New Projects Configuring the Home Page for your Project Deleting a Project Customising Application Tabs for your Project
Adding New Projects
In JIRA Studio, a project can be associated with a wiki space, build project and/or a source repository. This allows the project's issues to automatically link to (and be linked from) their associated wiki documents, source files, plan, changesets, code reviews and (if Bamboo enabled) build result.
To add a new project, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page should appear, listing all of the projects currently set up in JIRA Studio. Click the 'Add Project' link. 3. The 'Add A New Project' page will display (see screenshot below). 4. In the 'Name' field, type the name of the new project. Please note that this name will be displayed on the Dashboard. 5. In the 'Key' field, type the key of the new project (e.g. 'JRA'). This unique project key will prefix the first letters of all issue keys in the project (e.g. 'JRA-1000'). 6. In the 'URL' field, you can type the URL to be associated with this project, if you wish. Please note that this is an optional field. 7. In the 'Project Lead' field, type the name of the user to be assigned as the project lead for the project. As you type, the field will display a list of matches against users currently set up in the system. Select the user you wish to assign as the project lead from the list. 8. In the 'Description' field, type your description for the new project. 9. (Optional) Select a notification scheme to be used for this project from the 'Notification Scheme' dropdown. This dropdown will list all the notification schemes currently set up in the system. Please note that by default, no notification scheme is assigned to the project. 10. Select a permission scheme to be used for this project from the 'Permission Scheme' dropdown. This dropdown will list all the permission schemes currently set up in the system. Please note that by default, the 'Default Permission Scheme' is assigned to the project. 11. (Optional) Select a issue security scheme to be used for this project from the 'Issue Security Scheme' dropdown. This dropdown will list all the issue security schemes currently set up in the system. Please note that by default, no issue security scheme is assigned to the project. 12. Click the 'Add' button to add the new project. 13. The JIRA project, Confluence space, Subversion repository, FishEye repository and (if Bamboo enabled) Bamboo project will be created and the Project Summary page for your project will be displayed.
Screenshot: 'Add A New Project' Configuring the Home Page for your Project
The home page for your project is almost identical to a custom application tab, except for a minor cosmetic difference — If you choose one of the default applications (Issues, Wiki, Source, Reviews or (if Bamboo enabled) Builds) as the URL for your custom application tab, then it will always highlight the default application tab (not the custom application tab) when you navigate to it. However, if you choose one of the default applications as your project home page, then the 'Home' tab (not the default application's tab), will remain highlighted when you navigate to it.
Please note, the project home page is not the same as the global home for Studio (i.e. the page that you navigate to, when you click the logo in Studio).
To configure a custom Home Page for your Project, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page should appear, listing all of the projects currently set up in JIRA Studio. Click the 'View' link next to the project you wish to customise. 3. The information page for the project will display. Click the 'Select' link next to the 'Project Home Page: No Home page selected' label. 4. The 'Project Home Page' page will display, as per the screenshot below.
Configure the home page for your project, as follows: If you wish to select one of the default applications (Issues, Wiki, Source, Reviews, Builds) for your home page, click the relevant link under 'URL' field and the 'URL' field will be populated with the application's URL. If you wish to use a custom URL as your home page, enter the URL in the 'URL' field (please see the note on Using an external URL for a Studio tab below). If you have previously set up a home page for your project and wish to remove it, delete the URL of your home page from the 'URL' field. If you wish to retain the URL of your home page, you can choose to hide your 'Home' tab instead. Read about hiding and showing application tabs on the Customising Application Tabs for your Project page. 5. Click the 'Update' button to save your changes.
Using an external URL for a Studio tab Please note that if you specify an URL for your home page which is external to JIRA Studio (e.g. http://www.youtube.com), the entire external page will be loaded without any Studio context when you click the 'Home' tab. Please ensure that your external page has links back into JIRA Studio, otherwise the user will only be able to navigate back to JIRA Studio by using the back button of their browser.
Deleting a Project
In JIRA Studio, a project can be associated with a wiki space, build project and/or a source repository. This allows the project's issues to automatically link to (and be linked from) their associated wiki documents, source files, plan, changesets, code reviews and (if Bamboo enabled) build result. Deleting a project will delete the project from JIRA, Confluence, FishEye, Crucible, Bamboo* and Subversion. Hence, the issues, wiki documents, source files, changesets, code reviews, build plans and build results associated with the project will be deleted.
* This only applies if you are using JIRA Studio's Bamboo application. Your Bamboo project will not be deleted if you are using your own hosted Bamboo instance with JIRA Studio.
To delete a project, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page should appear, listing all of the projects currently set up in JIRA Studio. Click the name of the project that you wish to delete. 3. The 'Project' information page will display. Click the 'Delete Project' link (see screenshot below). 4. The 'Delete studio project' page will display (see screenshot below). Click the 'Delete' button to delete the project. 5. The 'Delete studio project' confirmation page will display (see screenshot below). This page will should list the following successful deletions: JIRA project successfully deleted Confluence space successfully deleted Subversion repository successfully deleted (note, the Project Key will be displayed for the Subversion repository rather than the Project Name, as the Project Key is the primary identifier in Subversion) FishEye repository successfully deleted (note, FishEye and Crucible are treated as one application, hence if your FishEye repository is successfully deleted then your Crucible reviews will also be deleted) Bamboo project successfully deleted
Screenshot: 'Delete Project Link'
Screenshot: 'Delete Project' Screenshot: 'Delete Project Confirmation'
Customising Application Tabs for your Project
You can streamline the user experience for your JIRA Studio users by customising the application tabs in each project. For example, you may not require the 'Source' and 'Reviews' tabs on a Human Resources project.
Each of the default tabs in JIRA Studio (Home, Issues, Wiki, Source, Reviews, (if Bamboo enabled) Builds) can be hidden, shown or moved, as desired. The Home tab can be configured to display any of the JIRA Studio applications or an external URL. You can also add new custom tabs to display an external URL.
Screenshot:Example of a Projects Toolbar with Customised Tabs
On this page: Hiding, Showing and Moving Application Tabs for your Project Adding a Custom Application Tab to your Project Adding a Home tab for your Project
Hiding, Showing and Moving Application Tabs for your Project
To hide or show an Application Tab for your Project,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. The 'Administration' page will appear, listing all of the projects currently set up in JIRA Studio. Click the 'View' link next to the project you wish to customise. 3. The information page for the project will display. Click the 'Manage Project Tabs' link under the information panel.
4. The 'Project Tab Administration' page will display. To hide or show an application tab, click the 'Hide' or 'Show' links in the 'Actions' column for the tab, respectively. To move an application tab, click the up ( ) and down ( ) arrows in the 'Actions' column for the tab, as desired. If you wish to return to the default tab configuration, click the 'Reset Default Tab Configuration' link. Please note, that this will remove any custom tabs that you have added. If you wish to edit the default tab configuration, click the 'Edit Default Tab Configuration' link. Read more about default application tabs in Configuring Global and Default Application Tabs.
Adding a Custom Application Tab to your Project
To add a Custom Application Tab for your Project, 1. Navigate to 'Administration' -> 'Projects'. 2. The 'Projects' page will display. Click the 'View' link next to the project you wish to customise. 3. The information page for the project will display. Click the 'Manage Project Tabs' link under the information panel.
4. The 'Project Tab Administration' page will display. Click the 'Add Custom Tab' link.
5. The 'Edit Custom Tab Project Details' page will display. Enter the 'Display Name' (displayed in tab header) and 'URL' for your desired custom page.
6. Click the 'Save' button to add your custom tab.
Please note that if you specify a URL for your new tab which is external to JIRA Studio (e.g. www.youtube.com), the entire external page will be loaded without any Studio context when you click the new tab. Please ensure that your external page has links back into JIRA Studio, otherwise the user will only be able to navigate back to JIRA Studio by using the back button of their browser.
Adding a Home tab for your Project
You can also add a Home tab to your project, which is almost identical to a custom application tab. To set up a Home tab, read the instructions on configuring the home page for your project.
Managing Users and Groups
On this page: JIRA Studio's Default Groups User Access Levels in JIRA Studio Restricting Project Visibility Managing Anonymous Access in JIRA Studio
Users and Groups in JIRA Studio are managed by JIRA. That is, the users and groups set up in JIRA will be inherited across all the applications in JIRA Studio. However, please note that default groups for JIRA Studio differ from JIRA, as follows:
JIRA Studio's Default Groups
When your JIRA Studio account is created, three groups are automatically set up:
users — should contain every JIRA Studio user in your system. By default, this group: has the 'JIRA Users' and 'Bulk Change' global permissions in JIRA. 'JIRA Users' allows users to log in to JIRA, and and 'Bulk Change' allows users to bulk edit issues. is a member of the 'Users' project role in JIRA, which allows members to see all project issues (unless protected by a security level) and create new issues. has permission to create and view Confluence (wiki) content for the project. has non-administrator access to Bamboo. has read only access to Subversion. developers — typically contains people who perform work on issues. By default, this group: is a member of the 'Developers' project role in JIRA, allowing developers to edit, move, assign, be assigned, link, work on, resolve and close issues. has the 'Browse Users', 'Create Shared Filter' and 'Manage Group Filter Subscriptions' global permissions in JIRA. has the 'Personal Space' Confluence permissions only. has non-administrator access to Bamboo. has read/write access to Subversion. administrators — typically contains people who are JIRA Studio administrators. By default, this group: is a member of the 'Administrators' project role in JIRA, able to edit project versions and manage project content (delete issues, comments, manage watchers). has the 'JIRA Administrators' global permissions in JIRA. has the 'Attach Files to User Profile', 'Personal Space', 'Create Space' and 'Confluence Administrator' Confluence permissions. has administrator access to Bamboo and permission to create plans. has read/write access to Subversion.
Users will typically belong to more than one group, ie. users only, or users and developers, or users, developers and administrators. By default new users will be added to the users group, which is the only default group with the 'JIRA Users' global permission.
To manage users,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 3. Further instructions on managing users in JIRA can be found here.
To manage groups, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Group Browser' option in the left menu. The 'Group Browser' page will display. 3. Further instructions on managing groups in JIRA can be found here.
While user groups are managed by JIRA, Subversion permissions are assigned to user groups via the Subversion Repository Manager. Instructions on managing Subversion permissions can be found here.
User Access Levels in JIRA Studio
Users are also assigned a User Access Level in JIRA Studio, and the User Access Level setting is for license purposes only. For further information on User Access Levels, please read the JIRA Studio Licensing page.
To manage user types for users,
Instructions on managing user access levels can be found here.
Restricting Project Visibility
Studio's default permissions assume just one set of users who have read access to everything ("users"), and groups who have varying permissions beyond this ("developers", "administrators").
If some users should not be able to see certain projects, then you will need to:
Create groups for each separate set of users, eg. a group per 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 the old groups.
For instance, say there are some contractors who should only be able to view a particular project. In this case it makes sense to split users by company, so by creating two new groups, eg. mycompany-users and contractors. Add the relevant users to these groups (keeping all of them in the users group too). Then redesign the permissions in each application:
JIRA — In JIRA, we want to make most projects visible only to mycompany-users, and one project visible to mycompany-users and contractors. For every project listed in the administration section, click the project name, find the Project Roles: section and click "View members" and edit the "Users" role groups. Remove the users group and add either mycompany-users or contractors. Confluence — In the Confluence application, i.e. the 'Wiki' tab (not in the administration console), go through the spaces one by one. Click the "Browse" dropdown arrow, pick "Space Admin", and then click "Permissions" to show the space permissions. You will see the "users" group has view permissions. Grant the mycompany-users group the same permissions, then delete the users group entry. For the relevant project, also grant the contractors group view permissions. Source — Manage your Subversion and FishEye permissions as described in Administering Source. Go through the projects replacing instances of the users group with mycompany-users, and in the relevant project, contractors. Reviews — Project review permissions are inherited from Crucible's default permission schemes. However, they are modified according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions that apply to a project's source also apply to that project's reviews. Bamboo (if enabled) — You cannot restrict the visibility of a Bamboo project, however, you can restrict permissions for individual plans in a project. See Granting Plan Permissions to Users or Groups in the Bamboo documentation for further details.
It is important that you go through all projects, to replace the user group with a more specific group. Since all users will belong to the users group, any project visible to users will remain visible to everyone.
Note that newly created users, being only in the users group (the only group given the 'JIRA Users' JIRA global permission), will not be able to see any projects until added to mycompany-users or contractors.
Restricting Visibility Notes To prevent a group from seeing most projects, It is not possible to simply remove a group (e.g. contractors) from the users group and then add a contractors group with the permission to view just one project. JIRA requires that all users be in a group that has the 'JIRA Users' global permission. By default, this is the users group. Hence, everyone needs to be in the users group. Users that are not in a group with the 'JIRA Users' permission may be able to log in, but JIRA will behave unpredictably (e.g. redirecting to a login screen on certain operations). The 'JIRA Users' group is designed to be the default group that new users get added to. Hence, in the example in the bullet point above, you cannot simply add the contractors group to the 'JIRA Users' permission. This would mean that newly added contractors would be added to the users group (not desired, since users can see all content) and newly added employees would be in the contractors group (also not desired, since they are not contractors)._
Managing Anonymous Access in JIRA Studio
Anonymous access in JIRA Studio can only be enabled for JIRA and Confluence at this stage. If you wish to enable anonymous access for these applications, you will need to configure each application individually as follows:
To allow anonymous access in JIRA,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The 'Issues' administration options will display. 3. Click the 'Schemes' option in the left menu and then click the 'Permission Schemes' option that displays underneath it. 4. Grant the 'Browse Projects' permission to 'Anyone' for the 'Default Permission Scheme'. Further instructions on changing project permissions in JIRA can be found here.
To allow anonymous access in Confluence,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The 'Issues' administration options will display. 3. Click the 'Permissions' option in the left menu. The 'Permissions' settings for your wiki will display. 4. Change the 'Anonymous Access' setting to allow anonymous access to your project's wiki. Instructions on setting up anonymous access in Confluence can be found here.
To allow anonymous access in Subversion,
Anonymous access to your project repository is disabled by default. Enabling/disabling anonymous access to your repository is restricted in JIRA Studio. Read more about Enabling Anonymous Access to a Repository.
To allow anonymous access in Bamboo, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Builds' tab. The 'Builds' administration options will display. 3. Click the 'Security' option in the left menu. The 'Global Permissions' settings for your wiki will display. 4. Click the 'Edit Global Permissions' button. The 'Global Permissions' page will display with editable fields. 5. Locate 'Anonymous users' (under 'Other'). 6. Select the 'Access' check-box. 7. Click the 'Save' button.
Anonymous users will now be able to access your Bamboo system. However, they will only be able to view plans and build results for plans where the 'Access' plan permission has been granted to 'Anonymous users'.
Managing User Access Levels
JIRA Studio licensing is user-based. This means the pricing for JIRA Studio is determined by the number of users that you want to have access to it. We call this "Access Level". There are two different user access levels for licensing: Developer and Collaborator. Each of these access levels has a separate user count for your license and provides a different level of access to JIRA Studio functionality.
If you remove a user from all groups, the user will display in the User Browser as having "No Access" and will not be able to log in to JIRA Studio. For licensing purposes, this user is no longer included in your user count.
See the JIRA Studio Licensing page for further details.
The links below guide you through configuring, viewing, and editing the access levels for your users. Where you are using JIRA Studio, users are set up from within JIRA Studio. Where you are using Google Apps integration with JIRA Studio, users are set up from within your Google account.
Managing User Access Levels in JIRA Studio Managing Users with Google Apps Integration Managing External Users with Google Apps Integration
Managing User Access Levels in JIRA Studio
JIRA Studio licensing is user-based. This means the pricing for JIRA Studio is determined by the number of users that you want to have access to it. We call this "Access Level". There are two different user access levels for licensing: Developer and Collaborator. Each of these access levels has a separate user count for your license and provides a different level of access to JIRA Studio functionality.
If you remove a user from all groups, the user will display in the User Browser as having "No Access" and will not be able to log in to JIRA Studio. For licensing purposes, this user is no longer included in your user count.
See the JIRA Studio Licensing page for further details.
The sections below describe how to configure and view the user access levels for your users.
On this page:
Configuring the Access Level for a New User Configuring the Access Level for an Existing User Viewing the Access Level for User(s) Configuring the Access Level for a New User
To configure the Access Level for a New User,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 3. Create a new user, as described in the Managing Users instructions. The 'Access Level' field will display at the bottom of the 'Create New User' screen (see screenshot below). 4. Select either 'Developer' or 'Collaborator', as the 'Access Level' (default is 'Developer'). 5. Click the 'Create' button to create the user.
Screenshot: Creating a New User
Configuring the Access Level for an Existing User
To configure the Access Level for an Existing User, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 3. Edit an existing user, as described in the Managing Users instructions. The 'Access Level' field will display at the bottom of the 'Edit Profile' page (see screenshot below). 4. Change the 'Access Level' to 'Developer' or 'Collaborator', as desired. 5. Click the 'Update' button to create the user.
Screenshot: Editing an Existing User
Viewing the Access Level for User(s)
You can view the user access level when browsing users.
To view the User Access Level for multiple Users,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display with the 'Access Level' field shown in a column for the list of users (see screenshot below).
Screenshot: Browsing Users (click to view fullsize)
The Access Level is also displayed in the user profile of a user.
To view the Access Level for a User, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 3. View an existing user's profile by clicking the username of the user. The 'Access Level' field will display in the 'User Profile' page (see screenshot below).
Screenshot: Viewing an Existing User
Configuring the Appearance of JIRA Studio
Configuring the Appearance of Studio
You can change the appearance of Studio, by configuring different settings for the look and feel of your account. You can change the settings described below by following the linked instructions:
Changing the Logo Configuring Global and Default Application Tabs Editing the Date and Time Formats for 'Issues' (JIRA) Editing the Colour Scheme
Changing the Logo
To change your logo, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Look and Feel' option in the left menu. The look and feel configuration page will display. 3. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 4. In the 'Logo' section, enter the URL of your new logo and specify the image height and width. 5. To display your logo as a shortcut or bookmark icon, select the Use as Favicon checkbox. Note that not all browsers display all image types. To display as a favicon, your logo will need to be an image format supported by your browser. This list on Wikipedia list of browser support for images may help you select a workable image format. 6. Click the 'Update' button at the bottom of the page to save your changes. Your logo will now appear on every page within JIRA Studio.
Screenshot: Changing the Logo
Configuring Global and Default Application Tabs
JIRA Studio allows you to customise the application tabs for each of your projects. You can also configure the global tabs and default tabs for applications tabs in JIRA Studio.
Global tabs are the tabs that are displayed when no project is selected in JIRA Studio. Default tabs are the tabs that are displayed for projects which do not have a customised tab configuration. These tabs are assigned to all new projects.
To configure global tabs,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Tabs' option in the left menu. The 'JIRA Studio Tab Administration' screen will display. 3. Configure your global tabs (as described in Customising Application Tabs for your Project) under the 'Global tabs' section.
To configure project default tabs, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Tabs' option in the left menu. The 'JIRA Studio Tab Administration' screen will display. 3. Configure your global tabs (as described in Customising Application Tabs for your Project) under the 'Project default tabs' section.
Screenshot: 'Configuring global tabs and default tab settings'
Editing the Date and Time Formats for 'Issues' (JIRA)
To change your date and time formats for 'Issues' (JIRA), 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Look and Feel' option in the left menu. The look and feel configuration page will display. 3. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 4. In the 'Date/Time Formats' section, update the values for each of the fields you wish to change. 5. Click the 'Update' button at the bottom of the page to save your changes.
Please note, the date and time formats will apply to pages within 'Issues' (JIRA) only. They do not apply to the other applications within JIRA Studio (e.g. 'Wiki').
Screenshot: 'Change Date and Time Formats'
Editing the Colour Scheme
You can easily change the colour scheme in Studio to suit your needs. The 'Look and Feel' settings in the Administration interface allow you to customise the colour scheme of the Top Bar (e.g. header) and Menu Bar (e.g. subheader) of the projects toolbar. The colour of headings and links in the 'Issues' application can be customised as well.
Due to a known issue with cache settings in Studio, the colour scheme of your projects toolbar will not immediately refresh when you update it. You will need to perform a once-off force refresh to see your changes.
To change the colour scheme in Studio, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Look and Feel' option in the left menu. The look and feel configuration page will display. 3. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 4. In the 'Colours' section, the colour scheme for Studio will be displayed. The JIRA documentation provides explanations for each of the colour scheme elements.
Please take note of the following JIRA Studio-specific information when reading the JIRA documentation: 'Top Bar' in JIRA is equivalent to 'Header' in JIRA Studio 'Menu Bar' in JIRA is equivalent to 'Navigation Bar' in JIRA Studio (JIRA Studio only setting) 'Header Highlight Background Colour' — the background colour that is displayed when highlighting elements in the JIRA Studio header, e.g. background colour of a tab when you hover your mouse over it. (JIRA Studio only setting) 'Header Text Highlight Colour' — the text colour that is displayed when highlighting elements in the JIRA Studio header, e.g. colour of the text of a tab when you hover your mouse over it. (JIRA Studio only setting) 'Header Separator Colour' — this setting is currently not used in JIRA Studio. (JIRA Studio only setting) 'Header Menu Indicator Image' — the colour of the dropdown indicator on the menus in your JIRA Studio header (e.g. a light-coloured image for dark backgrounds or a dark-coloured image for light backgrounds):
The 'Link Colour', 'Link Colour' and 'Heading Colour' elements only affect the appearance of pages within 'Issues' (JIRA). They do not affect the other applications within JIRA Studio (e.g. 'Wiki').
You can update the colours for the page elements by either:
Specifying the hexadecimal RGB colour codes or, Clicking on the square colour sample and selecting the colour in the new window. 5. Click the 'Update' button at the bottom of the page to save your changes.
Screenshot: Look and Feel Configuration Administering your Account
Administering your Account
You can change a number of your account settings in JIRA Studio. Please note that the account settings described here are for your organisation's JIRA Studio account, not your personal user account.
Do not change the Base URL for your installation. Modifying this value will cause errors in your instance of JIRA Studio.
The following sections describe how to view and update a range of JIRA Studio settings:
Viewing your Account Information Changing your Account Name Changing your JIRA Studio Welcome Message Enabling Public Signup and CAPTCHA Changing your JIRA Studio 'From' Email Header Format Changing your Account Language Creating a Support Request Viewing Web Statistics for your Account
Viewing your Account Information
You can view your account information in JIRA Studio. Please note that the account information described here is for your JIRA Studio account (e.g. your instance of JIRA Studio), not your personal user account.
To view your account information,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Account' option in the left menu. 3. The 'Studio Administration' page will display with your account information (see screenshot below), including: Account Name — The name that is displayed on the login page and dashboard of your Studio installation. See the instructions on changing your Account Name, if you wish to change this. Service Type — The hosted service being provided to you, i.e. 'JIRA Studio' User Count — The user counts of Developers and Collaborators for your account. The number of each user account type purchased for your account is displayed, as well as the number currently being used. Logo — The logo that is displayed in the header of your JIRA Studio installation. See the instructions on changing the Logo, if you wish to change this.
Screenshot: Studio Administration Changing your Account Name
To change your account name,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues administration console will display. 3. Click the 'Global Settings' option in the left menu, then click the 'General Configuration' option that displays below it. Your account settings will display (see screenshot below). 4. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 5. Update the 'Application Title' field, as desired. You would typically set this to the name of your company or organisation. 6. Click the 'Update' button to change your account settings.
Screenshot: 'Changing your Account Name' Changing your JIRA Studio Welcome Message
To change your JIRA Studio Welcome Message,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues administration console will display. 3. Click the 'Global Settings' option in the left menu, then click the 'General Configuration' option that displays below it. Your account settings will display (see screenshot below). 4. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 5. Update the 'Introduction' field to your desired welcome message. This message will display on the Issues dashboard. You can use HTML in your welcome message, but it must be properly formatted (e.g. ensure all HTML tags are closed). 6. Click the 'Update' button to change your account settings.
Screenshot: 'Changing your JIRA Studio Welcome Message' Enabling Public Signup and CAPTCHA
To enable public signup and CAPTCHA, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues administration console will display. 3. Click the 'Global Settings' option in the left menu, then click the 'General Configuration' option that displays below it. Your account settings will display (see screenshot below). 4. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 5. Update the 'Public Signup' and 'CAPTCHA' settings, as desired: To enable 'Public Signup', you will need to update the 'Mode' field to 'Public'. This will allow any users to signup and then post issues. Setting 'Mode' to 'Private' will restrict user creation to administrators only.
Please note, JIRA Studio is priced based on the number of users in your installation. Enabling public signup may cause you to exceed your user limit.
To enable 'CAPTCHA' (i.e. validation by image) on signup, you will need to set the 'CAPTCHA on signup' field to 'ON'. 6. Click the 'Update' button to change your account settings.
Screenshot: 'Enable Public Signup and CAPTCHA' Changing your JIRA Studio 'From' Email Header Format
To change your JIRA Studio 'From' Email Header Format,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Issues' tab. The Issues administration console will display. 3. Click the 'Global Settings' option in the left menu, then click the 'General Configuration' option that displays below it. Your account settings will display (see screenshot below). 4. Click the 'Edit Configuration' link at the bottom of the page. The page will display in editable mode. 5. Update the 'Email from:' field to your desired email header. This will set the 'JIRA Studio 'From' Email Header Format' in notification emails. You can use the following variables in your email header:
${fullname}, ${email}, ${email.hostname}
For example, setting the header format to:
${fullname} (JIRA)
would result in notification emails with headers like this one: From: John Doe (JIRA)
6. Click the 'Update' button to change your account settings.
Screenshot: 'Changing your JIRA Studio 'From' Email Header Format' Changing your Account Language
Please note that although Internationalisation functionality is present in JIRA Studio, only English language packs are available at this point in time.
Screenshot: 'Changing your Account Language' Creating a Support Request
Support requests for JIRA Studio are managed in the 'JIRA Studio' project at https://support.atlassian.com. You can file a support request by visiting https://support.atlassian.com or creating the request in JIRA Studio itself.
To create a support request in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Support Request' option in the left menu. 3. The 'Support Request' page will display. Fill in the required fields and click the 'Submit' button at the bottom of the form to submit your request. Please provide as much detail as possible. This will help us to resolve your issue faster. You can view your issue https://support.atlassian.com after you have submitted it. There may be a small delay while the support system processes your request.
Screenshot: 'Creating a support request' Viewing Web Statistics for your Account
You can view the web statistics for your JIRA Studio account (not your personal account) in JIRA Studio. This summary lists web statistics about your JIRA Studio instance, such as number of visitors, duration of visit, search keyphrases, referrers, etc.
To view your account information,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Webstats' option in the left menu. 3. The web statistics page will display (see screenshot below). Navigate up and down the page using the left menu. Use the back button on your browser to return to JIRA Studio.
Screenshot: 'Viewing web statistics for a JIRA Studio account' Administering Google Apps Integration
This page links to documentation on administering the Google Apps Marketplace integration for JIRA Studio. You can also find additional information in the Google Apps Integration FAQ.
For information on using the features of the Google Apps Marketplace integration for JIRA Studio, see Working with Google Apps Integration.
Click the relevant document below to view it:
Migrating to Google Apps Merging your JIRA Studio and Google Apps user bases Managing Username Conflicts Managing Large User Databases with Google Apps Integration Synchronising JIRA Studio and Google Apps Users Managing Users with Google Apps Integration Managing External Users with Google Apps Integration Managing Groups with Google Apps Integration Disabling User Access with Google Apps Integration
Migrating to Google Apps
This page contains instructions for migrating a JIRA Studio instance to add Google Apps integration.
On this page:
Before You Start Migrating to Google Apps
Before You Start
Ensure that you have an administrator user whose username is identical in both JIRA Studio and in Google Apps. Ensure that you are matching usernames and not email addresses, when matching Google usernames to JIRA Studio. For example, the Google username pictured in the following screenshot is 'george', not '[email protected]'.
Migrating to Google Apps
To add Google Apps integration to your JIRA Studio instance, 1. Go to the Google Apps Marketplace and add JIRA Studio. 2. Enter your My Atlassian credentials in the order form that is displayed. You must use the same My Atlassian credentials that you purchased JIRA Studio with. 3. Choose to enable Google Apps when prompted. A support ticket for your migration will then be created, and our technical support staff will coordinate the migration with you. You will be notified when the migration is complete. 4. Log into your JIRA Studio instance after the migration has been completed. You (i.e. the administrator of the instance) will be presented with a migration report screen, where you can see the list of JIRA Studio users compared with Google users, and the automatic matches that have been made.
Once your JIRA Studio instance is enabled for Google Apps integration, your users can select to log into JIRA Studio with their Google ID or JIRA Studio login.
Merging your JIRA Studio and Google Apps user bases
This page guides administrators through the process of migrating a Google Apps user base into the JIRA Studio user base. This is typically done immediately after integrating Google Apps with JIRA Studio.
On this page:
Before You Start Merging User Databases Using the CSV Export to Merge User Databases End User Actions
Before You Start
When you migrate to Google Apps, JIRA Studio will automatically merge the user bases from JIRA Studio and Google Apps. To streamline the process, before you merge users from the two systems you should confirm that:
You have an administrator user whose username is identical in both JIRA Studio and in Google Apps. Each user has a username in both JIRA Studio and Google Apps. Each of these user names is identical. Each of these user's email addresses is identical You are matching usernames and not email addresses, when matching Google usernames to JIRA Studio. For example, the Google username pictured in the following screenshot is 'george', not '[email protected]'.
Merging User Databases
To merge your JIRA Studio and Google Apps user bases, 1. Follow the instructions for Migrating to Google Apps. 2. After migrating to Google Apps, when you first log in with your JIRA Studio Administration username, the 'Setting up the user integration with your Google Apps Domain' screen will appear (see screenshot below). This screen summarises your user bases after migration. It is divided into four areas:
Screen Function Area
Existing Where existing Google Apps and JIRA Studio users have different email addresses associated with their user(s) user name, select 'Link' to confirm that these users can access JIRA Studio with their Google Apps Log to be In. linked
External * These users do not have a Google Apps Log In and are identified in the system as 'external' to Google user(s) Apps users* These users can not access Google Apps-specific functionality of the Google Apps Activity Bar, such as Google Calendar, GMail, Google Docs, or Google Site. * Under the Make External column, select Enable to provide these users with JIRA Studio log in access. * If some of these users are Google users but they yet haven't been created in your Google Apps Domain, you can select the link: 'Export these users to your Google Apps domain' to download a CSV export file, which you can then upload to your Google Apps Domain to create these users in bulk. * If you encounter problems using the automatic user merging facility, you can choose to use the CSV export function to help prepare your user base before fully migrating to Google Apps. The CSV export facility will also appear as an option during the migration if the automatic merging process detects any problems when matching user names
New These are any new users which you have added to your Google Apps account since integrating with user(s) JIRA Studio. They will be imported into JIRA Studio.
Linked These are existing users which are already linked to a Google Apps account. JIRA Studio will use their user(s) details for: 'first name', 'last name', and 'email address'.
3. Review the screen and determine if you need to either link any Google Apps and JIRA Studio email addresses, or make any users external: To link email addresses, under Existing users(s) to be linked select the 'Link' checkbox. To make users external, under External user(s) select the 'Enable' checkbox. 4. Under the drop-down labelled with your log in name, select Administration; in the Administration screen, select the ' General' tab, then select 'Google Management'. 5. Under Set default access level for new users, click to select the required access level — Developer, Collaborator, or No Access – then click 'Save'
Note that new JIRA Studio users are automatically assigned the default access level you have set up in Administration > General Tab > User Browser. This default may be Developer, Collaborator or No Access.
Users with Collaborator access are not able to access areas of JIRA Studio that are restricted to Developers, such as the Source tab and Subversion. Please see JIRA Studio Licensing and Managing User Access Levels for further information.
Where you don't want new users to count towards your license, you can:
Set the default access to No Access, or Set the access level for a single user to No Access
6. Under 'Synchronise Users', click 'Start Synchronisation' to immediately synchronise your JIRA Studio and Google user databases. Your migration and merging of user bases is now complete.
Screenshot: Report from Matching User Databases in JIRA Studio Using the CSV Export to Merge User Databases
If any users cannot be matched exactly during your user base migration, these users will display in the External user(s) area of the Setting up the user integration with your Google Apps Domain screen, along with the option to create a CSV export of your user database. See: Importing Data from CSV for further information.
To merge your JIRA Studio and Google Apps user bases using the CSV export,
1. On the Setting up the user integration with your Google Apps Domain screen, under External Users, click the 'Export these users to your Google Apps domain' link. 2. Export your user database from JIRA Studio by clicking 'Save'. 3. Delete any external users and inactive users from the CSV file. 4. For all remaining users in the CSV file modify the: 'first name', 'last name' and 'password' as necessary. The username must remain the same. 5. Re-import your user database into Google Apps by clicking through to the appropriate page in the Google Apps administrator pages and uploading the CSV file. This will allow a smooth merging of the user databases, by creating Google Apps accounts for any JIRA Studio accounts that do not already have a corresponding Google Apps account. Once you're ready, click 'I have received confirmation from Google that the import is complete' (see screenshot below). 6. Now, go to the JIRA Studio administrator screen, set the default access level for new users, and click 'Start Synchronisation'. Your migration and merging of user bases is now complete.
Screenshot: CSV Export Dialog Window End User Actions
End users will need to carry out the following actions after the migration:
1. Log in to JIRA Studio, using the password the administrator provides. 2. Create a new password when prompted.
Note that new JIRA Studio users will be given the default access level, which may be Developer, Collaborator or No Access. If they are given No Access, they will not be able to log in without intervention from the administrator. If they are given Collaborator access, they will not be able to access some JIRA Studio developer functionality, such as the 'Source' tab and Subversion.
Users will not be able to check out files from Subversion until they have logged in to JIRA Studio.
Converting Google Apps Users to External Users
If you are using JIRA Studio with Google Apps integration there may be times when you need to convert one of your Google Apps users to an external user. An example is where an employee becomes a contractor.
To convert a Google Apps user to an external user,
1. First, note the groups that the user is assigned to in JIRA Studio. You can do this by accessing the 'User Browser', selecting the user and then writing down the groups listed under the Groups column (see screenshot below). 2. Then you will need to remove the user from your Google domain. 3. Next, synchronise your users between JIRA Studio and Google. This will disable the user you have removed from Google by removing the user from all groups with login permission. 4. Now you can manually re-enable the user as an external user by re-assigning the user to the groups you have removed it from. To do this: From within JIRA Studio, access the 'User Browser'. Select the user and click on their name. In the user information screen which opens, click 'Edit Groups'. In the 'Edit User Groups' screen, hold down the 'Ctrl' key, then click to select the groups the user was originally assigned to. Click 'Join' to re-assign the user to these groups. 5. Note that as JIRA Studio is unable to retrieve the password used in Google, the user's password will be randomised at this point. You will need to either reset the user's password via the admin console or have the user reset it logging in directly to JIRA Studio, and then clicking 'Can't access your account?' on the Google login form (see screenshots below). 6. You should now update the user's email address to change it from your Google domain.
Screenshot: Viewing JIRA Studio groups
Screenshot: Logging in directly to JIRA Studio
Screenshot: Re-setting a password at login Related Topics
Managing External Users with Google Apps Integration Managing Users with Google Apps Integration Disabling User Access with Google Apps Integration
Managing Username Conflicts
Quick guide to managing username conficts
A "username conflict" means the same user name exists in both your JIRA Studio and Google Apps user bases. If the system detects a username conflict when merging or synchronising your JIRA Studio and Google Apps userbases, it will send the Administrator an email. Administrators can then either: Link the user names if they are for the same user Delete or rename the username in Google Apps which is causing the conflict Where a user has no Issues associated with their name, you are able to delete the user and username. Where a user has Issues associated with their name, you are not able to delete the username. In this case, you can disable the username and assign the user a new username.
On This Page
Managing Username Conflicts
Managing Username Conflicts
To manage username conflicts, 1. If you receive a system email advising of a username conflict, you can either click the link to the Username Conflicts screen supplied in the email or navigate to the Username Conflicts screen manually (see screenshot below).
2. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
3. In the Username Conflicts screen, you can click the user email under JIRA Studio name (email) to preview the user's information, and: Edit the Properties, Groups, Project Roles, Details, Set the Password, or Delete the user, or Link the Google Apps and JIRA Studio passwords 4. Where you select to edit the user details or delete the user, follow the instructions in: Managing Users and Groups. 5. Where you select to link Google Apps and JIRA Studio user names, click Link to open the Confirm Link Usernames dialog. Screenshot: Confirm Link Usernames
6. Click Yes to link the user names and return to the Username Conflicts screen. The user will be removed from the list of username conflicts.
Screenshot: Username Conflicts
Managing Large User Databases with Google Apps Integration
This page contains information about migrating and ongoing synchronising of large user databases (over 10,000 users) with Google Apps integration.
On this page: How Google Apps Integration Migrates Large User Databases How Google Apps Integration Manages Ongoing Synchronisation of Large User Databases Mitigation Strategies
How Google Apps Integration Migrates Large User Databases
Where you migrate a large user database, JIRA Studio will synchronise your user base progressively. This means that the system will add users when they first log in. Administrators cannot modify any user's access rights until the user has logged in for the first time. When an end-user does their initial log in, the JIRA Studio account will be created, granting the user the default access level.
How Google Apps Integration Manages Ongoing Synchronisation of Large User Databases
Where you have a large number of users (containing more than 1000 users), JIRA Studio will not synchronise your entire user base periodically as per your user synchronisation settings. Instead, it will add users upon authentication (that is, when they first log in).
When JIRA Studio synchronises your Google Apps user base, it sets an upper limit to the users it synchronises to 1000 at one time.
Mitigation Strategies
Where you have an urgent need to carry out actions on a large user database, we recommend getting in touch with Atlassian support. Our support engineers will be happy to assist you with this process.
Synchronising JIRA Studio and Google Apps Users
User data is regularly synchronised between JIRA Studio and Google Apps. JIRA Studio data synchronisation settings enable you to:
Customise the default access for users – Collaborator, Developer, or No Access Select whether user data synchronisation is enabled or disabled Specify the synchronisation interval Synchronise your user data on an 'as required' basis
Configuring how your user data is synchronised with Google Apps
To configure how your user data is synchronised with Google Apps,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click 'Google Management' on the left navigation bar. 3. Select the required Default Access Level for new JIRA Studio users, then click 'Save'. 4. Select whether Google Apps user Synchronization is enabled, and how often your user data is synchronised, then click 'Save Synchronization Settings'. 5. If required, you can click 'Start Synchronization' to immediately synchronise your JIRA Studio and Google user databases. An example system log from the most recent user data synchronisation is shown below. You can also click 'Download full log' to download a text file of this synchronisation log.
You can configure these settings:
Setting Description Allowed Default Values
Set Default Access This sets the default access level for new users the first time they log in to JIRA Studio. 'No Access' 'No Level for New Users 'Collaborator Access' Access' 'Developer Access'
Google Apps User This switches automatic synchronisation on or off. 'Enabled' 'Enabled' Synchronization 'Disabled'
Synchronization Adjusts how often the synchronisation process runs. Any value in 60 Interval minutes minutes Google Apps This is a link to the administration interface on your Google Apps domain. Click this link Cannot be Link is Domain to visit your Google Apps Domain and manage users or Google-specific settings. changed always shown
Synchronize Users Enables you to immediately synchronise your JIRA Studio and Google Apps user bases. You can also download the log as a text file.
Screenshot: Google Management settings in JIRA Studio
Managing Users with Google Apps Integration
When you integrate Google Apps with JIRA Studio, administration functions are shared between Google and JIRA Studio. This is because you manage your users in Google, and you group your users, and manage how each group accesses features of JIRA Studio from within JIRA Studio. Access privileges for the groups you set up for JIRA in the Issues tab can be configured to apply across all your JIRA projects, or to apply on a project-by-project level.
On this page:
Creating a new user Deleting a user Renaming a User Resetting a user's password Granting administration rights
The following tasks are carried out in the Google Apps Dashboard for your domain.
Creating a new user
To Create a New User, 1. Visit the Google Apps Dashboard for your domain and log in as administrator. For example, the Google Apps Dashboard for the JIRA Studio test server (atl-paid-dev.com) is located at this address:
https://www.google.com/a/cpanel/atl-paid-dev.com/UserAction
2. On the Google Apps toolbar, click 'Organization & Users'. 3. Click the 'Create a new user' button. Fill out the new user details as required (see screenshot below). A temporary password is shown on screen; make a note of that or set an alternate initial password. 4. Click 'Create new user'. The account will be created and the user's details displayed, including their new email address. You can now click to print or email the access instructions for the new user. 5. Now, visit the JIRA Studio admin pages to configure the correct access to Atlassian applications. To do this, open the ' User Menu' in JIRA Studio (labelled with your user name), click 'Administration', then click on the 'User Browser' link under 'General', 'JIRA Studio'. 6. Find the desired user and edit the user's privileges. Choose the desired access to Atlassian applications and click Save.
Note that new JIRA Studio users will be given default access level: Developer, Collaborator or No Access. Users with No Access require Administrator intervention to log in. Users with Collaborator access have restricted access to JIRA Studio capability. Please see JIRA Studio Licensing and Managing User Access Levels details.
Screenshot: Creating a new user
Deleting a user
To Delete a User,
1. Visit the Google Apps Dashboard for your domain and log in as administrator. For example, the Google Apps Dashboard for the JIRA Studio test server (atl-paid-dev.com) is located at this address:
{https://www.google.com/a/cpanel/atl-paid-dev.com/UserAction}
2. On the Google Apps toolbar, click 'Organization & Users'. The Users and Groups page opens. 3. In the 'Users' tab, find the desired user(s) in the directory, then select the checkbox next to their name(s). 4. From the More Actions drop-down, select Delete Users (see screenshot below). 5. At the confirmation dialog, click OK to delete the selected user(s) and return to the 'Organization & Users' screen.
Screenshot: Selecting a user to delete Renaming a User
To Rename a User,
1. Visit the Google Apps Dashboard for your domain and log in as administrator. For example, the Google Apps Dashboard for the JIRA Studio test server (atl-paid-dev.com) is located at this address:
https://www.google.com/a/cpanel/atl-paid-dev.com/UserAction
2. On the Google Apps toolbar, click 'Organization & Users'. 3. From the Users and Groups directory, select the required user and click on their name to access their account summary. 4. Select Change Name and edit the details as required (see screenshot below). 5. Click the Save Changes button to return to the 'Organization & Users' screen.
Screenshot: Editing a user's details
Resetting a user's password
To Reset a User's Password, 1. Visit the Google Apps Dashboard for your domain and log in as administrator. For example, the Google Apps Dashboard for the JIRA Studio test server (atl-paid-dev.com) is located at this address:
{https://www.google.com/a/cpanel/atl-paid-dev.com/UserAction}
2. On the Google Apps toolbar, click 'Organization & Users'. 3. From the Users and Groups directory, select the required user and click on their name to access their account summary. 4. Select Change Password, and edit the details as required (see screenshots below). 5. Click the Save Changes button to return to the 'Organization & Users' screen.
Screenshot: User password details
Screenshot: Resetting a user's password
Granting administration rights
To Grant Administration Rights,
1. Visit the Google Apps Dashboard for your domain and log in as administrator. For example, the Google Apps Dashboard for the JIRA Studio test server (atl-paid-dev.com) is located at this address:
{https://www.google.com/a/cpanel/atl-paid-dev.com/UserAction}
2. On the Google Apps toolbar, click 'Organization & Users'. The Users and Groups page opens. 3. From the Users and Groups directory, select the required user and click on their name to access their account summary. 4. At the user account summary screen, select the 'Privileges' tab, then select the checkbox marked 'Allow USER to administer YOURDOMAIN' (see screenshot below). 5. Click 'Save changes' at the bottom of the screen. 6. At the confirmation dialog, click OK. 7. The user will be granted admin rights, returning you to the 'Organization & Users' screen.
_Screenshot: Confirming Admin Privileges-
Managing External Users with Google Apps Integration Quick guide to managing external users
'External' users are clients, contacts, or remote workers who do not have a Google ID, or have a different company email domain on Google. When using Google Apps integration with JIRA Studio, your administration is shared between Google and JIRA Studio. This is because you manage your users in Google, and you group your users, and manage how each group accesses features of JIRA Studio from within JIRA Studio. Access privileges for the groups you set up for JIRA in the Issues tab can be configured to apply across all your JIRA projects, or to apply on a project-by-project level.
On this page:
Adding a New External User for Google Apps Viewing Google Apps External Users in the User Browser Setting Developer or Collaborator Access Level for an External User Disabling the Access Level for External Users Viewing User Access Levels
Adding a New External User for Google Apps
To add a new user,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will be displayed. 3. Select the 'Add External User' (see screenshot below) option. 4. At the 'Create New External User' dialog, fill in the new user details as required, then select the 'Create' button. 5. Select the required user(s), using the 'Filter' fields at the top of the 'User Browser' if required. 6. Locate the user in the 'User Browser' and click the 'Groups' link in the 'Operations' column. 7. In the 'Edit User Groups' screen which appears, click to select the required group(s). (You can use Ctrl + click to select multiple groups). See Assigning a User to a Group in the JIRA documentation. 8. Select the required 'Developer' or 'Collaborator' Access Level (default is 'Developer'). 9. Now that an external user has been enabled in the system, the JIRA Studio login page will display both a 'Log in via Google' and 'Log in directly' Log in options.
Screenshots: Adding a New External User for Google Apps Viewing Google Apps External Users in the User Browser
The User Browser summarises a user's login details, access level and capabilities within JIRA Studio. When using JIRA Studio with Google Apps integration, the 'User Browser' enables you to see which of your users are external, and which have not yet activated their account. This means you can filter your user base against this criteria for account and licensing management purposes (see screenshot below).
Column Function Name
Username Displays a user's user name.
Email Displays the user's email address.
Full Name Displays the user's full name.
Access Displays a user's access level. See JIRA Studio Licensing for more information. Level 'Developer' — the user has 'developer' level access: 'Issues', 'Wiki', 'Source', 'Reviews', 'Builds', 'Repository'. 'Collaborator' — the user has 'collaborator' access: Restricted access to 'Issues', full access to 'Wiki'. 'No Access' — the user has been removed from all Groups and therefore has no access to JIRA Studio.
User Type 'Google User' — the user has a Google account and is able to access JIRA Studio functionality specific to Google account holders. 'Google User (needs activation)' — a Google user with a Google account who has never logged into JIRA Studio; this account will be activated when the user first logs in to JIRA Studio 'External User' — the user does not have a Google account and does not have access to Google Apps integration outside of JIRA Studio.
Groups Displays all Groups of which the user is a member. The JIRA instructions for Managing Users provide further detail.
Operations Displays the administration functions that can be performed for each user.
'Groups' — Opens the 'Edit User Groups*' screen, where you can view and administer the group memberships for a user. 'Project Roles' — Opens the 'Project Roles' screen, where you can view and administer the project roles for a user. 'Edit' — Opens the 'Edit Profile' screen, where you can view and edit the full name, email, and account type for a user. 'Delete' — Opens the 'Delete
Screenshot: Viewing Google Apps Users in the User Browser (click to view full-size image) Setting Developer or Collaborator Access Level for an External User
For licensing purposes, JIRA Studio assumes that setting Developer or Collaborator access occurs at individual user level.
To configure the access level for an external user,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. To set Developer or Collaborator access: 3. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 4. Select the required user, then under the 'Operations' column, click 'Edit'. 5. The 'Access Level' field will display at the bottom of the 'Edit Profile' page. 6. Change the 'Access Level' to 'Developer' or 'Collaborator. 7. Click the 'Update' button to provide the user with this updated access.
Screenshot: Setting Developer or Collaborator Access
Disabling the Access Level for External Users
For licensing purposes, JIRA Studio assumes that setting the access level to No Access is required for multiple users. You can use the JIRA Studio Bulk Edit tool to quickly manage the access level for many users in your database.
To disable the access level for external users, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'Bulk Edit Access Level' option in the left menu. 3. In the 'Bulk Edit Access Level' screen, select 'No Access' from the drop-down list (see screenshot below).
4. Then, click the icon ( ) to open the 'User Picker'. 5. The 'User Picker' enables you to apply filter selection criteria and then select many users by checking the box next to their names. 6. Once you've selected the users for whom you wish to disable access, click 'Select'. 7. The users you have selected will display in the 'Select the users' field. Click 'Submit' to disable JIRA Studio access for these users.
Screenshot: Setting the Access Level to "No Access"
Viewing User Access Levels
You can view the user account type for users, when browsing users.
To view the user access level for multiple users, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display with the 'Access Level' field shown in a column for the list of users (see screenshot below). The User Access Level is also displayed in the user profile of a user.
Screenshot: Browsing Users (click to view full-size image)
To view the user access level for a single user,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click the 'User Browser' option in the left menu. The 'User Browser' page will display. 3. View an existing user's profile by clicking the username of the user. The 'Access Level' field will display in the 'User Profile' page (see screenshot below).
Screenshot: Viewing an External User Related Topics
Managing User Access Levels Managing Groups with Google Apps Integration JIRA Studio Licensing
Managing Groups with Google Apps Integration
Quick guide to managing groups with Google Apps integration
When using Google Apps integration with JIRA Studio, your administration is shared between Google and JIRA Studio. This is because you manage your users in Google, and you group your users, and manage how each group accesses features of JIRA Studio from within JIRA Studio. Access privileges for the groups you set up for JIRA in the Issues tab can be configured to apply across all your JIRA projects, or to apply on a project-by-project level. If you remove a user from all groups, they will display in the User Browser as having "No Access". This means they have no access to JIRA Studio.
Google Administrator functions:
Create users Delete users Rename users Reset passwords
JIRA Studio Administrator functions:
Manage allocation of users to groups Manage how groups access JIRA Studio functionality
On this page:
Group Management in JIRA Studio Bulk Edit Group Members Removing a User's Access to JIRA Studio Related Topics
Group Management in JIRA Studio
Groups are used to control how individual users access project and parts of JIRA Studio. All other user management tasks are carried out in the Google interface (See the page on Managing Users with Google Apps Integration for more information).
Bulk Edit Group Members
You can use the JIRA Studio Bulk Edit tool to quickly manage the access level for many users in your database.
To open Bulk Edit, 1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Click 'Google Management' on the left navigation bar. 3. Click 'Bulk Edit User Access Level' on the left navigation bar. 4. From the Select access level to grant dropdown, select from: No Access, Collaborator Access, or Developer Access.
5. You can now Select the users for which you want to change the access level. Click the icon ( ) next to the form field to open the User Picker. 6. The User Picker enables you to select and add a range of users in bulk, by checking the box next to their names. You can also select the entire row by checking the box at the top of the column. To add specific users, you can control how many users are displayed per page, filter by full name, filter by email address and filter by group membership. Once you've selected the users to bulk change, click 'Select'. 7. The users you have selected will display in the Select the users field. Click 'Submit' to apply the access level to all these users.
Screenshot: Bulk User Editing Edit (click to view fullsize image)
1. Bulk User Access Level 2. Bulk User Picker
Removing a User's Access to JIRA Studio
If you remove a user's access, you can also remove them from the JIRA Users group.
To remove a user's access to JIRA Studio,
1. Click your user name in the the JIRA Studio header, and select the 'Administration'. 2. Select the 'Issues' tab, then select the 'Permissions' option. 3. From within the JIRA Permissions table, move to'JIRA Users', then click the view users link. 4. This opens the User Browser, from which you select and remove the user from the JIRA Users group. 5. Click 'Save'.
Related Topics
Managing Users and Groups Synchronising JIRA Studio and Google Apps Users
Disabling User Access with Google Apps Integration
If a Google user's account is suspended or deleted from your Google Apps domain, they may still be able to access JIRA Studio for up to an hour, or until user databases are synchronised. To prevent access, you can either immediately synchronise your user bases to prevent disabled users gaining access, or you can disable users by removing them from all groups in JIRA Studio.
Disabling User Access with Google Apps Integration To disable access to JIRA Studio by synchronising user bases,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Select 'Google Management' from the left navigation panel. 3. Under the 'Synchronise Users' area of the Google Management screen, click the 'Start Synchronisation' button. This will immediately begin a synchronisation of your user bases, which when complete, will prevent any user accounts that have been deleted or suspended in Google Apps from accessing JIRA Studio.
To disable users in JIRA Studio,
1. Click the menu labelled with your user name in the JIRA Studio header, and select 'Administration'. You will need to be logged in as an administrator to see this link.
The administration console will display with the 'General' tab active.
2. Select 'User Browser' from the left navigation panel. 3. Select the user, using the 'Filter' fields at the top of the User Browser if required. 4. For the selected user, click the "groups" link and then remove the user from all groups in JIRA Studio to disable access.
Related Topics:
Synchronising JIRA Studio and Google Apps Users Managing Users with Google Apps Integration Managing User Access Levels in JIRA Studio Managing Users and Groups
Managing Data
JIRA Studio provides mechanisms for handling data outside of the application user interface. You may need to use these to import data into JIRA Studio or provide us with large amounts of data for a support case.
Read more about managing data in the topics below:
Data Backups Importing Data Uploading Data via WebDAV
Data Backups
This page contains instructions on how to request backup data from JIRA Studio, how often the data is automatically backed up and the policies and procedures enabling this.
On this page:
Requesting Backup Data How We Protect Your Data Database Backups Off-Site Disaster Recovery Filesystem Hardware Redundancy Requesting Backup Data
If you require a backup of your data to be sent to you, the JIRA Studio support team can generate one for you. To request a backup, please raise a support ticket via your application or at http://support.atlassian.com.
Note that customers will not be able to restore a Studio backup into each individual application without assistance from Atlassian Support, who will process it so that it can be restored.
JIRA Studio is an integrated suite of applications that contains exclusive configuration data. Because of this, an XML backup generated from Studio can't be used by standalone instances of our products without data transformation. Atlassian support will assist with generating a usable XML backups for standalone instances, only if you have a pending cancellation of a paid-subscription JIRA Studio account. Please contact Atlassian Support to schedule an appointment for this backup, and let us know if you intend to use Crowd in your environment.
Please note that Atlassian will not export backup data for evaluation users or expired accounts. If you are cancelling your JIRA Studio license, please arrange a backup prior to account cancellation.
How We Protect Your Data
Database Backups
Database backups are taken every twelve hours, and the data is retained for seven days.
The following applications store data in the main database:
JIRA Confluence Bamboo Crowd
Off-Site Disaster Recovery
There is currently no off-site Disaster Recovery option for commercial hosted services. We are exploring options in this area and hope to offer a solution soon.
Filesystem Hardware Redundancy
Data is stored on highly redundant RAID-50 SAN. This also allows us to easily instantiate an instance if the physical server fails.
Filesystem Backups
The following applications store data in the filesystem:
Application Data storage details
JIRA file attachments Backed up daily, overwriting the prior day's attachment backup.
Confluence file attachments Backed up daily, overwriting the prior day's attachment backup.
Subversion Backed up once a week, overwriting the previous week's backup.
FishEye & Crucible Not backed up. An upgrade of FishEye which will allow database backups soon.
Bamboo home directory Not backed up, but the database is.
Importing Data
JIRA Studio has an Subversion importer that allows you to import versioned Subversion data. For more information, see the Source section below.
Other import functions, such as JIRA CSV imports, are currently disabled in JIRA Studio. However, you can request data to be imported into your instance of JIRA Studio by filing a ticket at https://support.atlassian.com in the 'JIRA Studio' project. Our support staff will schedule an appointment with you for an agreed upon time for your data to be imported. The data can be attached to the support case or (preferably) uploaded to the Studio WebDAV directory share.
Specific per-product restrictions on imports are listed below.
On this page:
Important Information Application-Specific Notes Issues Wiki Source Users Notes
Important Information
Imports for Evaluators: Only one import request is supported per evaluation. This request can include both a JIRA and Confluence import, which will be performed at the same time. While having a separate 'evaluation' and 'production' import is not recommended, we are able to perform one 'final' import for subscribers that wish to overwrite changes made to data imported during evaluation. We are not able to merge changes made during evaluation into a data set prior to final import. Supported Versions: We cannot import from a higher version of JIRA or Confluence than the version that is currently installed on JIRA Studio. Please see the JIRA Studio Application Versions page to view the current versions of JIRA and Confluence in Studio.
Application-Specific Notes
Issues
Importing Data from a JIRA Instance
We can import JIRA issues and attachments from an existing JIRA installation and JIRA Hosted instance using an XML backup and an archive of attachments on the filesystem.
Importing Data from Third-Party Issue Tracker
If you would like to import data from a third-party issue tracking system such as Bugzilla, Fogbugz, Mantis, you will need to do the following:
1. Create a CSV file that matches the format described in Importing Data From CSV (JIRA documentation). 2. Import the CSV file into a local instance of JIRA that is the same or earlier version than the version currently installed on JIRA Studio (4.2.2). You can download JIRA from the JIRA Archive Downloads and obtain an evaluation license for it from my.atlassian.com, if you don't already have a local instance of JIRA. 3. Create an XML backup using JIRA's XML backup utility, as described in Backing Up Data (JIRA documentation). 4. Raise a support request under the 'JIRA Studio Support' project at https://support.atlassian.com and attach your XML backup. Our support team will verify the file and import it for you.
Restrictions
Please note, the restrictions on the following import procedures:
Renaming Users — Renaming users is not supported during evaluation. For subscribers, user renaming is supported for matching Google Apps user names, or matching existing JIRA and Confluence users when both are being imported. Merging Instances — Merging multiple JIRA instances during import is not supported. If you have multiple JIRA instances, please file a support ticket advising us of this so we can provide guidance prior to proceeding. Project Imports — It is possible to import a single JIRA project from an XML backup of an existing instance. While we cannot do this for you during evaluation, you can do so locally using an evaluation copy of JIRA in order to provide us with an XML backup ready for Studio import. Details on restoring a single project from backup can be found here: Restoring a Project from Backup (JIRA documentation).
Wiki
Importing Data from a Confluence Instance
We can import Confluence site imports or space imports from on-premises Confluence installations and Confluence Hosted.
Importing Data from Third-Party Issue Wiki
If you would like to import data from a third-party wiki, you will need to do the following:
1. Use the Universal Wiki Converter to migrate the wiki pages to Confluence format. 2. Create space exports for the desired spaces in your wiki, as described in Exporting Confluence Pages and Spaces to XML (Confluence documentation). 3. Raise a support request under the 'JIRA Studio Support' project at https://support.atlassian.com and attach your zipped Confluence space exports. Our support team will verify the file and import it for you.
Restrictions
Please note, the restrictions on the following import procedures:
Versions prior to 2.7.4 — Confluence versions prior to 2.7.4 are not supported. If you have a version of Confluence older than that, we recommend upgrading to 2.7.4 locally then providing the supported version backup for import into Studio. Version Mismatches — For Confluence space imports, the version of Confluence the spaces were exported from must match the current version in JIRA Studio. Renaming Spaces — Renaming Confluence spaces to match JIRA issue keys is not supported. We are able to map existing Confluence spaces to their corresponding JIRA projects so the integration works properly, however they will not have matching names. Alternately, spaces can be renamed using a locally installed evaluation copy of Confluence. We can then import the renamed space(s) for you. See the following instructions for renaming Confluence spaces: Copy Or Rename A Space (Confluence documentation). Note, the space imports must be produced from a Confluence instance which matches the current version in JIRA Studio.
Source
If you have not previously used Subversion, you can import your content directly into JIRA Studio's Subversion using a Subversion Client, using the svn import command. Please see Importing Unversioned Data into Subversion for instructions.
However, if you want to import versioned Subversion data (preserving full history) into JIRA Studio, you can use the JIRA Studio Subversion importer. For instructions on how to use this, see Importing Versioned Data into Subversion.
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. For examples of the appropriate CSV format, please review the Crowd CSV Import document. There are some Studio specific groups to be aware of — to specify if a user should be a Developer or Collaborator, add the user to a group named developer. Users will likely need to be part of the users group in order to login to Studio. Please upload the CSV files to us via WEBDAV and submit a support request to import the users. If you are importing JIRA or Confluence data already, the user data is likely already there so generating CSV files to us will not be necessary.
If you would like assistance getting your data into an acceptable format for import to JIRA Studio, check out our Premium Hosted Services.
Notes
Related Topics
JIRA Studio Application Versions Importing Data From CSV (JIRA documentation) Backing Up Data (JIRA documentation) Universal Wiki Converter Importing Unversioned Data into Subversion Importing Versioned Data into Subversion
Importing Unversioned Data into Subversion
You can perform all of the commands available to you via Subversion Client Functions for JIRA Studio, including the svn import command. This command allows you to import a directory, which may contain further levels of directories and files, into a Subversion repository. However, the svn import command will only import an unversioned tree of files into Subversion (e.g. no history will be retained).
Access to the Subversion Administration Console is restricted, hence you will not be able to import full directories and history into Subversion. If you would like to import data into your Subversion repository, preserving full history, please see Importing Versioned Data into Subversion.
To import unversioned data into Subversion, 1. Open a Subversion console. 2. If you have already created your project in JIRA Studio, enter the following command to import your local directory into your project's Subversion directory:
svn import
where,
You can create directories in Subversion by using the svn create command. However, we strongly recommend that you create your
3. You will see a commit message on your console at the completion of a successful import (e.g. 'Committed revision 1'). You can check that your files were correctly imported by using the svn list command to display the files in your target directory, i.e. svn list https://
If you now wish to work with your imported files, you will need to check out a working version of the directory from Subversion first. Read more about working with your Repository.
Importing Versioned Data into Subversion
You can import a full Subversion (SVN) repository from a dump file. Importing the full repository preserves all historical information, whereas an svn import (see Importing Unversioned Data into Subversion) only stores the most recent state. Please note, the import process described below will overwrite any existing Subversion data for all projects in your JIRA Studio repository. If you want to import Subversion data for a single project, see this FAQ: How do I import Subversion data for a single JIRA Studio project?.
On this page:
1. Create an SVN Dump File 2. Alter the Structure of your Subversion Repository 3. Test the Integrity of the Dump File 4. Import the SVN Dump File into JIRA Studio Notes
1. Create an SVN Dump File
You can generate a Subversion dump file from the SVN host by using the svnadmin dump command, e.g.
$ svnadmin dump /path/to/svn/ > svn.dump
You need to ensure that the Subversion content in your dump file conforms to the Subversion layout used in JIRA Studio. Some functions in JIRA Studio assume that the content follows the standard layout (e.g. project creation/deletion). JIRA Studio also does not provide enough control to manage arbitrary mappings.
The standard Studio Subversion layout is described below:
Your JIRA Studio instance has a single Subversion repository, at https://
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 in JIRA Studio that do not have corresponding top-level directories in your existing Subversion repository, create the top-level directories in the repository. For example,
$ svn mkdir --parents -m "Created place-holder directories for MYPROJ project." file:///path/to/svn/MYPROJ/{trunk,tags,branches}
If the directories in your existing Subversion repository do not match your project names, do one the following: rename each top-level directory via Subversion, e.g. svn rename Plugins PL. However, only new commits made after the rename will appear in Studio's Source tab, alter the structure (including history) of the repository using Subversion tools (see below), or raise a support request (uploading your dump file) asking for the paths in Subversion to be rewritten across all revisions, e.g. transforming all references to /Plugins to /PL. This means that all commits will be visible within Studio. However, this also breaks Subversion's assumption that history is immutable and renders existing checkouts invalid. If you have a complex Subversion structure that cannot be rearranged, e.g. your build system relies on that structure, raise a support request. Upload your dump file and specify which Subversion paths map to which Studio projects in the support request. If you need both revision numbers and/or checkouts to be preserved, please state this in the support request and we will attempt to preserve them.
2. Alter 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 JIRA Studio (described above), you can alter it yourself.
First, export a subset of your repository while creating an SVN dump file using the svndumpfilter tool. In the following example, the resulting dump file will only contain the data under the 'PL' top-level directory. This rewrites the history, so 'PLE' and other top-level directories will not exist in this dump.
$ svnadmin dump /path/to/svn/ | svndumpfilter include --drop-empty-revs --renumber-revs PL/ > PL.dump
Next, download the third-party Perl script: svn-dump-reloc. Run the script to rename directories through the entire repository history. For example, to change all occurrences of the file/directory paths starting with 'Plugins/' to 'PL/' use the following command:
$ svnadmin dump /path/to/svn/ | svn-dump-reloc Plugins/ PL/ > svn.dump
3. Test the Integrity of the Dump File
You must test the integrity of your SVN dump file, particularly if you have altered the structure of the repository. To do this, create a new, blank repository and attempt to load the dump file into it. For example:
1. Create a test repository:
$ svnadmin create /tmp/test_repo
2. Load in the dump file using svnadmin load:
$ cat svn.dump | svnadmin load /tmp/test_repo
3. Verify the contents of your SVN repo by inspecting its directory hierarchy: 3.
$ 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. Import the SVN Dump File into JIRA Studio
Once you have created and verified your SVN dump file, follow the instructions below to import it into the Subversion repository of your JIRA Studio instance.
To import an SVN dump file into JIRA Studio,
1. Log into JIRA Studio as an administrator. 2. Upload the Subversion dump (preferably compressed) to the dump_files sub-directory in the WebDAV directory share on your Studio host. See Uploading Data via WebDAV for instructions. If your dump file is too big to upload, you can try compressing it first using gzip or bzip2. The importer can import the zipped files. 3. Click your username, select 'Administration' from the dropdown. The administration console will be displayed. 4. Navigate to 'Import SVN Repository' under the 'Source' tab of the administration console. 5. The SVN dump files that you have uploaded to dump-files will be displayed. Click 'Import' next to the file you want to import. The importer will make the following checks: If you have an existing SVN repository that is not empty (i.e. it contains files apart from the base "skeleton" structure), you will be asked to confirm whether you want to overwrite it. If you have users in the dump file that do not exist in your Studio instance, you will be asked to confirm whether you still want to do the import. You can still import your file, however, if you want to match all committers to users, you will need to create the missing users in JIRA Studio before doing the import. 6. The importer will back up your existing Studio repository (as a SVN dump file) in your WebDAV dump-files sub-directory. The import will then be completed. 7. If your import is successful, a confirmation message will be displayed. (optional) You can delete the SVN dump files (the imported file or the backup of your old data) from your WebDAV directory after the import, if you wish.
Please note, your Subversion users will need to check out a new copy of Subversion content after your repository is moved to Studio.
Screenshots: Importing a SVN dump file into JIRA Studio
There are no images attached to this page.
Notes
The files in your existing JIRA Studio repository may be associated with entities like code reviews. If you overwrite these files on import, you may experience errors when trying to access the files (e.g. via the code review). Raise a support request for assistance.
Related Topics
How do I import Subversion data for a single JIRA Studio project? Importing Unversioned Data into Subversion
Uploading Data via WebDAV
Your JIRA Studio instance includes a WebDAV (Web-based Distributed Authoring and Versioning) directory share, which can be used to send us large amounts of data related to your initial setup or a support case. The directory has a 1 gigabyte limit. You must also belong to the administrators group, and have an account type of Developer.
Please note, this directory share is not intended to be used for general file storage. It is also different from the Confluence WebDAV interface accessible at http://
On this page:
Supported WebDAV clients Accessing your WebDAV directory Accessing your WebDAV directory in OS X Accessing your WebDAV directory in Windows XP Accessing your WebDAV directory in Windows Vista Accessing your WebDAV directory in Linux Accessing your WebDAV directory using a client
Supported WebDAV clients
Depending on your operating system, you may need to install a client to access your web directory. Please refer to the matrix below for details:
Operating Studio WebDAV Directory compatibility Recommended Alternative Client System
OS X All versions of OS X should be compatible. We highly recommend Transmit, if you don't want to use the OS X WebDAV functionality.
Windows Windows XP may not work with the Studio WebDAV directory, as The BitKinex WebDAV Client is a free XP compatibility is highly dependant on the service packs and hotfixes that time-limited DAV are installed. client. Please note that this client has not been tested thoroughly with the Studio WebDAV directory.
Windows Windows Vista has a working redirector for DAV over HTTPS. Please note The BitKinex WebDAV Client is a free Vista that this has not been tested thoroughly with the Studio WebDAV time-limited DAV directory. client. Please note that this client has not been tested thoroughly with the Studio WebDAV directory.
Linux Cadaver is known to work well.
Accessing your WebDAV directory
Google Marketplace Users: If you signed up for Studio via Google Marketplace, you should have been prompted to provide a password for Subversion access the first time you logged into Studio. You'll need to use that password to access WebDAV, not your Google Apps password.
Accessing your WebDAV directory in OS X
To access your WebDAV directory in OS X,
1. Activate the Finder in OS X and select Connect to Server from the Go menu. 2. Enter the following URL: https://
Accessing your WebDAV directory in Windows XP
To access your WebDAV directory in Windows XP,
Note, there are a number of ways to set up WebDAV access in Windows XP. The method below will allow you to access your WebDAV directory from 'My Network Places.'
1. Navigate to 'My Network Places' and click 'Add a network place'. 2. The 'Add Network Place Wizard' will display. Click 'Next'. 3. A list of service providers will be displayed. Select 'Choose another network location' and click 'Next'. 4. You will be prompted to enter a URL in the 'Internet or network address' field on the next page. Enter the following URL and click Next: https://
Accessing your WebDAV directory in Windows Vista
To access your WebDAV directory in Windows Vista, Note, there are a number of ways to set up WebDAV access in Windows Vista. This is only one of the methods available.'
1. Open 'My Computer' and click 'Map Network Drive'. 2. The 'Map Network Drive' screen will display. Click 'Connect to a Web site that you can use to store your documents and pictures', and then click 'Next'. 3. Click 'Choose a custom network location', and then click 'Next'. 4. You will be prompted to enter a URL in the 'Internet or network address' field on the next page. Enter the following URL and click Next: https://
If you are getting the following error message when trying to map the web folder, 'The folder you entered does not appear to be valid', you may need to download and install the following Vista update — KB907306
Accessing your WebDAV directory in Linux
To access your WebDAV directory in Linux,
Note, there are a number of ways to set up WebDAV access in Linux. This is only one of the methods available.
1. Install a WebDAV client. For example, to install Cadaver on Debian/Ubuntu, run sudo apt-get install cadaver . 2. Connect to https://
$ cadaver https://
Accessing your WebDAV directory using a client
To access 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 that,
The URL of the WebDAV directory is: https://
JIRA Studio User's Guide
JIRA Studio User's Guide Using the Projects Toolbar Searching in Studio Working with Issues JIRA User's Guide GreenHopper User's Guide Actioning Issues via Commit Messages Working with the Wiki Confluence User's Guide Working with Source FishEye User's Guide Working with Reviews Crucible User's Guide Working with Builds Bamboo User's Guide Actioning Issues via Builds Working with Streams Viewing the Activity Stream Configuring the Activity Stream Adding Comments via the Activity Stream Working with the Repository Working with Google Apps Integration Logging In and Out With Google Apps Integration Using the Activity Bar Using Google Calendar with Google Apps Integration Using Google Docs with Google Apps Integration Creating Links Managing Your Profile Changing Your Password in JIRA Studio
Using the Projects Toolbar
The Projects Toolbar appears at the top of every page in JIRA Studio. The toolbar has two main parts:
The dark-blue header — this is displayed on every page in JIRA Studio. It contains tabs for the project you are currently viewing. The default tabs are the Issues, Wiki, Source and Reviews tabs, but you may see a different set of tabs depending on how your administrator has set up the project (e.g. the Builds tab). The light-blue subheader — this subheader appears for all of the default applications in Studio. The functions in this subheader change depending on whether you are currently working with Issues, Wiki, Source, Reviews or (if enabled) Builds. The main area of the screen, below the projects toolbar, will also change depending on whether you are currently working with Issues, Wiki, Source, Reviews or (if enabled) Builds.
Screenshot: 'Projects Toolbar'
Features of the Projects Toolbar
The projects toolbar has a number of key features that can help you navigate around Studio more easily:
The projects dropdown menu — This dropdown menu is labelled with the project you are currently viewing (e.g. 'JIRA Studio'). It allows you to easily switch between projects you have set up in JIRA Studio. Screenshot: 'Projects Dropdown' The user dropdown menu — this dropdown menu is labelled with your username (e.g. 'Administrator'). It allows you to access your user profile and (if you are an administrator) administration functions. Screenshot: 'User Dropdown'
The global history dropdown menu — your navigation history can be accessed via the 'History' dropdown menu and is saved even after you log out. The last twenty pages in Studio that you have visited will be displayed. Screenshot: 'Global History'
Please note, only the following types of pages are stored in your navigation history:
Issues — JIRA issue Wiki — Confluence page Reviews — Crucible review Source — FishEye file Source — FishEye path
The JIRA Studio search — the projects toolbar contains a powerful Studio-wide search. Read more about searching in Studio.
Searching in Studio
Tracking the information being produced by your development team can be a challenge, as documents are drafted, tasks are created and code is reviewed and committed. Streams can help you to keep up to date, as the information is produced, and application links provide an easy way to navigate through related information. The Studio-wide Search feature can also be useful, by helping you to find specific project information across applications in Studio.
The Studio-wide Search provides you with a birds-eye view of related information, by aggregating search results across applications and projects into a set of summary results. You can also drill down for more results from a specific application.
Build information not searchable Build information (e.g. build plans, build results) is currently not searchable in JIRA Studio. Build information is captured in the 'History' dropdown of the project toolbar and the activity stream though.
To search in Studio,
1. Enter your search criteria in the search box in the Projects Toolbar, which is available across applications.
2. As you enter your search criteria, the 'Search QuickNav' dropdown will appear under the search box and suggest possible matches for your criteria. If you wish to select one of the suggested results, simply click the entry in the dropdown. The QuickNav will return up to three suggestions for each of the following, issues, wikis/blogs and user profiles.
3. If the 'Search QuickNav' does not provide you with your desired search result, press 'Enter'/'Return' (on your keyboard) to execute your search. 4. The search results will display as seen in the 'Studio-wide Search Results' screenshot below. Click on any of the search results to navigate to that item in the relevant application. Other features of the search results page include: Refining results by project — If you wish to refine your results by project, select a project from the 'Project' dropdown and click the 'Search Again' button. The search results page will be reloaded with the results from the selected project only.
Grouped results — All results will be grouped by application (e.g. Issues, Wiki, Source, Reviews). Each application will display a maximum of 5 results. Results will be sorted by relevance in the application groups. Results totals — A summary line at the end of each application group will tell you how many results there are in total and how many were retrieved, e.g. 'Showing 5 of 7 results'. Drilldown for more search results — If you wish to see any further search results which are not retrieved, click on the summary line for the application group, e.g. 'Showing 3 of 7 results'. This will open the application's search page with the full search results for that application.
Screenshot: Studio-wide Search Results Working with Issues
An issue can represent whatever you need it to: a software bug, a development task, a documentation task, etc.
Every issue belongs to a project. In JIRA Studio, a project can be associated with a wiki space, build project and/or a source repository. This allows the project's issues to automatically link to (and be linked from) their associated wiki documents, source files, plan, changesets, code reviews and (if Bamboo enabled) build result.
Please note, the versions of JIRA and GreenHopper running in JIRA Studio may differ from the latest released versions of JIRA and GreenHopper. Please refer to JIRA Studio Application Versions for that latest version information.
On this page:
Working with Issues JIRA and GreenHopper User Documentation JIRA Studio-specific Documentation
Working with Issues
To work with issues,
1. Click the 'Issues' tab in the JIRA Studio header. 2. This takes you to JIRA. For details about using JIRA, please see the 'JIRA and GreenHopper Documentation' section below. Your issues application includes the GreenHopper agile project management tool. To work with GreenHopper, click the 'Agile' link/menu in the JIRA Studio header. For details about using GreenHopper, please see the the 'JIRA and GreenHopper User Documentation' section below. Your issues application may also include the following additional JIRA features, if the relevant third-party plugins have been enabled in your installation of JIRA Studio (check with your administrator): Balsamiq Mockups for JIRA Plugin — Integrated mockups.
Screenshot: 'JIRA Studio — Issues' (click to view larger image) JIRA and GreenHopper User Documentation
The guides listed below contain information on how to use JIRA and GreenHopper. Please note, these guides do not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone JIRA/GreenHopper). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
JIRA User's Guide GreenHopper User's Guide
JIRA Studio-specific Documentation
The following JIRA or GreenHopper functions are specific to JIRA Studio and cannot be found in standalone JIRA/GreenHopper:
Actioning Issues via Builds
JIRA User's Guide
JIRA Studio May 2011 includes JIRA 4.3.1 for issue tracking. Use the search or click any of the links below to view the relevant page in the JIRA User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some JIRA functionality is restricted in JIRA Studio.
Search the JIRA 4.3.1 documentation:
JIRA Concepts
What is an Issue What is a Project What is Workflow
Getting Started
Logging in to JIRA Exploring the JIRA Workspace Using Keyboard Shortcuts
Working with Issues
Attaching a File Attaching a Screenshot Cloning an Issue Commenting on an Issue Creating an Issue Creating a Sub-Task Editing Rich-Text Fields Labelling an Issue Linking Issues Logging Work on an Issue Modifying Multiple ('Bulk') Issues Moving an Issue Scheduling an Issue Setting Security on an Issue Viewing an Issue's Change History Viewing an Issue's Crucible Reviews Viewing an Issue's FishEye Changesets Viewing the Bamboo Builds related to an Issue Watching and Voting on an Issue
Searching for Issues
Receiving Search Results as an RSS Feed Using Quick Search Customising your Issue Navigator Exporting Search Results to Microsoft Word Exporting Search Results to Microsoft Excel Receiving Search Results via Email Displaying Search Results as a Chart Using the Issue Navigator Saving Searches ('Issue Filters') Performing Text Searches Advanced Searching Displaying Search Results in XML
Generating Reports
Workload Pie Chart Report User Workload Report Version Workload Report Time Tracking Report Single Level Group By Report Created vs Resolved Issues Report Resolution Time Report Pie Chart Report Average Age Report Recently Created Issues Report Time Since Issues Report
Browsing a Project
Browsing a Project's Summary Browsing a Project's Issues Browsing a Project's Road Map Browsing a Project's Change Log Browsing a Project's Popular Issues Browsing a Project's Versions Browsing a Version's Summary Browsing a Version's Issues Browsing a Version's Popular Issues Browsing a Version's Bamboo Builds Browsing a Project's Components Browsing a Component's Summary Browsing a Component's Issues Browsing a Component's Road Map Browsing a Component's Change Log Browsing a Component's Popular Issues Browsing a Project's Labels Browsing a Project's Bamboo Builds Browsing a Project's FishEye Changesets Browsing a Project's Crucible Reviews Viewing a Project's Burndown Chart
Customising the Dashboard
Changing the Look and Behaviour of a Gadget Managing Multiple Dashboard Pages Adding the Activity Stream Gadget Adding the Administration Gadget Adding the Assigned To Me Gadget Adding the Average Age Gadget Adding the Bamboo Charts Gadget Adding the Bamboo Plan Summary Chart Gadget Adding the Bamboo Plans Gadget Adding the Bugzilla ID Search Gadget Adding the Calendar Gadget Adding the Clover Coverage Gadget Adding the Created vs Resolved Gadget Adding the Crucible Charts Gadget Adding the Favourite Filters Gadget Adding the Filter Results Gadget Adding the FishEye Charts Gadget Adding the FishEye Recent Changesets Gadget Adding the In Progress Gadget Adding the Introduction Gadget Adding the Issue Statistics Gadget Adding the JIRA News Gadget Adding the Pie Chart Gadget Adding the Projects Gadget Adding the Quick Links Gadget Adding the Recently Created Issues Gadget Adding the Resolution Time Gadget Adding the Road Map Gadget Adding the Text Gadget Adding the Time Since Issues Gadget Adding the Two-Dimensional Filter Statistics Gadget Adding the Voted Issues Gadget Adding the Watched Issues Gadget Adding the Heat Map Gadget Adding the Labels Gadget
Managing your User Profile
Adding a User Avatar Allowing OAuth Access Changing your Password Choosing a Language Using Hover Profile
GreenHopper User's Guide
JIRA Studio May 2011 includes GreenHopper 5.6.1 for agile project management. Use the search or click any of the links below to view the relevant page in the GreenHopper User's Guide. Please note, you will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Search the GreenHopper 5.6.1 documentation:
Using the Planning Board
Using Planning Board Modes Using Planning Board Views Using Statistical Markers to Group Issues Working with Epics
Using the Task Board
Transitioning Issues in GreenHopper Adding Constraints to your Task Board Columns (Kanban) Using Task Board Modes Using Task Board Views
Using the Chart Board
Viewing the Cumulative Flow Chart Viewing the Hour Burndown Chart How Hour Burndown Charts Relate to Time Tracking in JIRA Viewing the Time-Tracking Analysis Viewing the Issue Burndown Chart Viewing the Statistics Burndown Chart Viewing the Statistics Burnup Chart Viewing the Value Chart
Using the Released Board
Working with Issues in GreenHopper
Scheduling and Assigning Issues in GreenHopper Creating an Issue in GreenHopper Ranking Issues in GreenHopper Flagging an Issue in GreenHopper Searching for Issues on a Board Using Contexts to Filter and Highlight Issues Printing Issues in Card Form Modfying Multiple ('Bulk') Issues
Managing your User Preferences
Using the GreenHopper Gadgets
Using the Agile Gadget Using the Card View Gadget Using the Cumulative Flow Chart Gadget Using the Days Remaining Gadget Using the Hour Burndown Chart Gadget Using the Project Progress Gadget Using the Statistics Burndown Chart Gadget Using the Task Board Gadget
Using Keyboard Shortcuts
Actioning Issues via Commit Messages
If you are working with code, you can action issues in JIRA Studio via Subversion commit messages. By using particular keywords in your commit message, you can log work, add comments or change the status of an issue. This makes it easy for you to maintain any issues that are related to the code you are changing.
On this page:
Basic Command Line Syntax Advanced command line syntax Commit Commands Error Handling
Basic Command Line Syntax
The basic command line syntax for your commit comment is:
For example, if you include the following text in your commit message, JIRA Studio will record 2 days and 5 hours of work against issue JRA-123, when you perform your commit: JRA-123 #time 2d 5h
Please see the section on commit commands below for further information on the command line parameters.
Advanced command line syntax
If you wish to perform multiple actions on issues, you can create composite commands by combining keywords, as described below.
To perform multiple actions on a single issue:
For example, if you include the following text in your commit message, JIRA Studio will log 2 days and 5 hours of work against issue JRA-123, add the comment 'Task completed ahead of schedule' and resolve the issue, when you perform your commit: JRA-123 #time 2d 5h #comment Task completed ahead of schedule #resolve
To perform a single action on multiple issues:
For example, if you include the following text in your commit message, JIRA Studio will resolve issues JRA-123, JRA-234 and JRA-345, when you perform your commit: JRA-123 JRA-234 JRA-345 #resolve
To perform multiple actions on multiple issues:
For example, if you include the following text in your commit message, JIRA Studio will log 2 days and 5 hours of work against issues JRA-123, JRA-234 and JRA-345, add the comment 'Task completed ahead of schedule' to all three issues, and resolve all three issues, when you perform your commit: JRA-123 JRA-234 JRA-345 #resolve #time 2d 5h #comment Task completed ahead of schedule Please see the section on commit commands below for further information on the command line parameters.
The commit message syntax allows you to do even more complicated actions, than the examples described above. If you would like to view the formal syntax for the commit message definition, it is available on this FAQ
Commit Commands
Command Command Description Example Parameters
#time
#comment
#
Please note, your JIRA Studio administrator may have set up a custom workflow or changed the default commit command for a particular transition. Please check with your JIRA Studio administrator for the commit commands available for you to use.
Error Handling
If you have specified a commit command incorrectly, your code changes will still be committed to the repository. However, the associated JIRA issue action(s) will not be executed and you will be notified via email.
Possible commit command errors include:
Issue key not found Workflow command not found, or not available for current status No valid parameters are specified for a command that requires parameters You do not have permissions to perform the specified action in JIRA, e.g. issue may be restricted by permissions
Working with the Wiki
The wiki is a collection of pages (online documents). The wiki is useful for collaboration, information sharing and documentation.
A space is a collection of pages within the wiki.
In JIRA Studio, a space can be associated with a project. This allows links to be automatically created on your wiki pages, pointing to associated issues, source files, changesets and/or code reviews.
Please note, the version of Confluence running in JIRA Studio may differ from the latest released version of Confluence. Please refer to JIRA Studio Application Versions for that latest version information.
On this page:
Working with the Wiki Confluence User Documentation JIRA Studio-specific Documentation Working with the Wiki
To work with the wiki,
1. Click the 'Wiki' tab in the header of JIRA Studio. 2. This takes you to Confluence. For details about using Confluence, please see the 'Confluence User Documentation' section below. 3. Your wiki may also include the following additional Confluence features, if the relevant third-party plugins have been enabled in your installation of JIRA Studio (check with your administrator): Balsamiq Mockups for Confluence Plugin — Integrated software mockups tool. Gliffy Plugin for Confluence — Draw diagrams in Confluence.
Personal space creation function missing Please note, the 'Create Personal Space' function is missing in the wiki user interface for JIRA Studio 1.8. You can manually access the 'Create Personal Space' function by using the following URL: https://
Screenshot: 'JIRA Studio — Wiki' (click to view larger image)
Confluence User Documentation
The guide listed below contains information on how to use Confluence. Please note, this guide does not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone Confluence). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
Confluence User's Guide
JIRA Studio-specific Documentation
There are currently no JIRA Studio-specific user functions for Confluence.
Confluence User's Guide
JIRA Studio May 2011 includes Confluence 3.5.3 for its wiki. Use the search or click any of the links below to view the relevant page in the Confluence User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some Confluence functionality is restricted in JIRA Studio.
Search the Confluence 3.5.3 documentation: Rich Text Editor Overview
Enabling Rich Text Editing Using the Context Menu in the Rich Text Editor Inserting Content in the Rich Text Editor Inserting Images in the Rich Text Editor Inserting Emoticons in the Rich Text Editor Inserting Symbols in the Rich Text Editor Adding and Removing Links in the Rich Text Editor Linking to Attachments in the Rich Text Editor Linking to Images in the Rich Text Editor Working with Tables in the Rich Text Editor Using Autocomplete in the Rich Text Editor Working with Text Effects in the Rich Text Editor Inserting JIRA Issues
Space Backup and Restore
Archiving Mail Overview
Adding a Mail Account Deleting Mail Fetching Mail Importing Mail Linking to Mail Managing Mail Accounts Restoring Mail Viewing Mail
Working with Bookmarks
Adding a bookmark Adding a Bookmark Icon to your Browser Adding a Bookmark Link to your Browser's Favorites Dragging a Bookmark Link to your Browser Editing or Commenting on a Bookmark Removing a Bookmark Subscribing to a Bookmarks RSS Feed Viewing Bookmarks
Working with Attachments
Using Drag-and-Drop in Confluence Attaching Files to a Page Attachment Versions Deleting an Attachment Displaying List of Attachments in a Page Downloading Attachments Editing Attachment Properties Embedding Multimedia Content Embedding PowerPoint Presentations in a Page Finding an Attachment Linking to Attachments Moving an Attachment Choose a Page Viewing Attachment Details
Customizing Look and Feel
Applying a Theme to a Space Configuring the Documentation Theme Configuring the Easy Reader Theme Changing a Space's Logo Changing the Confluence Browser Icon Customising Homepage Customising Layouts for a Space Editing a Space's Colour Scheme Styling Confluence with CSS Basic Styling Tutorial Styling Fonts in Confluence Styling Tabs in Confluence Using CSS to Customise the Easy Reader Theme
Working with the Office Connector
Office Connector Prerequisites Installing the Firefox Add-On for the Office Connector Editing a Confluence Page in an Office Application Importing an Office Document into Confluence Displaying Office Files in Confluence Editing an Office Document from Confluence Editing an Office Presentation from Confluence Editing an Office Spreadsheet from Confluence
Site Backup and Restore
Production Backup Strategy
Hover Profile Overview
Working with Templates Overview
Adding a Template Creating a Page using a Template Editing a template Removing a Template
Searching Confluence
Confluence Search Fields Confluence Search Syntax Ranking of Search Results Searching the People Directory Text Tokenisation and Filtering
Tracking Updates to Confluence Pages and Spaces
Subscribing to Email Notifications of Updates to Confluence Content Watching a Page or Blog Post Watching a Space Managing Watchers Subscribing to RSS Feeds within Confluence Using pre-specified RSS feeds Using the RSS Feed Builder Working with RSS Feeds Adding a username and password to Confluence RSS feeds RSS Readers Compatibility
Working with Confluence Gadgets
Adding a Confluence Gadget to a JIRA Dashboard Configuring Confluence Gadgets for Use in Other Applications Confluence Gadgets Activity Stream Gadget Confluence News Gadget Confluence Page Gadget Confluence Quicknav Gadget Adding JIRA Gadgets to a Confluence Page
Keyboard Shortcuts
Importing Content Into Confluence
Importing Pages from Disk
Confluence Glossary
User Profile Overview
Changing Password Editing User Settings Editing User Profile Viewing Status Updates Email Address Privacy Updating Email Address Choosing a Profile Picture Deleting a Profile Picture Viewing User Profile Viewing and Revoking OAuth Access Tokens
User Status Overview
Using the Confluence Screens Network Overview
Subscribing to a Network RSS Feed
Working with Spaces
Administering Spaces Browsing a space Editing Space Details Managing Orphaned Pages Managing Undefined Pages Tree View of Pages Viewing Pages Alphabetically Viewing Recently Updated Content Viewing Space Details Converting a Global Space to a Personal Space Deleting a Space Exporting a Confluence Pages and Spaces to Other Formats Exporting Confluence Pages and Spaces to HTML Exporting Confluence Pages and Spaces to PDF Exporting to a Word document Exporting Confluence Pages and Spaces to XML Moving Content from one Space to Another Moving a family of pages from one space to another Moving a Page from one Space to Another Moving Pages within a Space Setting up a New Global Space Setting up your Personal Space Viewing All Confluence Spaces Viewing Space Activity
Working with the Macro Browser
Working with Blog Posts
Adding Blog Posts Deleting Blog Posts Editing Blog Posts Linking to Blog Posts Viewing Blog Posts
Working with Images
Displaying an Image Image File Formats Displaying a Thumbnail Image Thumbnail and Gallery Example Viewing Images as a Slide Show
Working with Favourites
Adding Favourites Removing Favourites Viewing Favourites
Dashboard
Customising your Personal Dashboard
Working with Links
Linking to Pages Within the Same Space Linking to Pages in Another Space Linking to Web Pages Linking an Image Linking to Personal Spaces and User Profiles Linking to Confluence Pages from Outside Confluence Changing the Title of a Link Sample Release Notes Using a Link to Create a New Email Message Trackback Working with Anchors CamelCase linking CamelCasePage
Confluence Notation Guide Overview Adding Special Characters to your Wiki Page Confluence Emoticons Form Field Markup for Templates Working with Headings Working with Lists Working with Tables Working with Text Breaks Working with Text Effects
Working with Pages
Deleting a Page Purging Deleted Pages Restoring a Deleted Page Editing an Existing Page Choosing Rich Text or Wiki Markup Editing as your Default Concurrent Editing and Merging Changes Recording Change Comments Working with Drafts Overview Configuring the Time Interval at which Drafts are Saved Resuming the Editing of a Draft Viewing Drafts Page Layout in View Mode Page Layout in Edit Mode (Wiki Markup) Page Layout in Edit Mode (Rich Text) Moving a Page Commenting on a Page Adding a Comment Deleting Comments Editing a Comment Linking to Comments Viewing Comments Linking Pages Writing Confluence pages Recently Viewed Content Page History and Page Comparison Views Restoring an Older Version of a Page Viewing an Older Version of a Page Sequential Order of Pages Working with Page Families What is a Page Family? Breadcrumbs Viewing a Page's Family Viewing Children of a Page Viewing Hierarchy of Pages within a Space Viewing a Page's Location within a Space Changing Parent of a Page Creating a Child Page Setting a Page Family to Alphabetical Order Viewing Page Information Copying a Page Renaming a Page E-mailing a Page Using the Documentation Theme Using a WebDAV Client to Work with Pages Creating a New Page
Confluence Icons
Permissions Overview
Page Restrictions Setting a Page's Restrictions Viewing a Page's Restrictions Site Administrators and their Permissions Contacting Confluence Administrators Space Administrators and their Permissions Space Permissions Overview Assigning Space Permissions Revoking Space Permissions Viewing Space Permissions Users and Groups Searching for Users Viewing Restricted Pages
Working with Labels
Adding a Global Label Adding a Personal Label Using Labels to Categorise Spaces Navigating Pages by Label Removing a Label from a Page Using Label Macros to Categorise Wiki Content Content by Label Macro Labels List Macro Navmap Macro Popular Labels Macro Recently Used Labels Macro Related Labels Macro Viewing Global Labels Viewing labelled pages Viewing personal labels Viewing Popular Labels
Working with Macros
Anchor Macro Attachments Macro Blog Posts Macro Bookmarks Macro Change-History Macro Chart Macro Cheese Macro Children Display Macro Child Page 1 Child Page 2 Code Block Macro Color Text Macro Column Macro Content by User Macro Contributors Macro Contributors Summary Macro Create Space Button Macro Documentation Link Macro Edit in Word Link Macro Excerpt Include Macro Excerpt Macro Expand Macro Favourite Pages Macro Flowchart Macro Gadget Macro Gallery Macro Global Reports Macro HTML Include Macro HTML Macro IM Presence Macro Include Page Macro Sample Include Page Info Macro JIRA Issues Macro JIRA Macro JIRA Portlet Macro JUnit Report Macro Livesearch Macro Loremipsum Macro Metadata Macro Metadata Summary Macro Multimedia Macro Network Macro Noformat Macro Nolink and nl Macros Note Macro Page Index Macro Pagetree Macro Sample Page Tree Sample Page Tree 2 Pagetree Search Macro Panel Macro Profile Macro Quote Macro Recently Updated Dashboard Macro Recently Updated Macro RSS Feed Macro Search Macro Section Macro Space Details Macro Spacegraph Macro Space Jump Macro Spaces List Macro Status Macro Table of Contents Macro Table of Contents Zone Macro Tasklist Macro Tip Macro Userlister Macro User Status List Macro View File Macro Warning Macro Web-Widget Macro Welcome Message macro Widget Macro Widget Connector Examples
Guides to Specific Uses of Confluence
Developing Technical Documentation on Confluence Wiki Creating your Technical Documentation Space Using Templates in Technical Documentation Re-using Content in Technical Documentation Managing the Life Cycle of your Technical Documentation Providing PDF Versions of your Technical Documentation Exporting and Printing Technical Documentation Essential Confluence Features for Technical Documentation Confluence Plugins for Technical Documentation Further Reading about Developing Technical Documentation on Confluence Developing a Knowledge Base on Confluence Wiki Creating Your Knowledge Base Space Using Templates and Formatting Macros in a Knowledge Base Proactive Communications in a Knowledge Base Additional Plugins for a Knowledge Base
Working with Source
Your source (e.g. your source code) resides in a repository such as Subversion, Perforce or CVS.
A changeset is a collection of source files that were committed to the repository at the same time. A changeset can be associated with one or more reviews.
In JIRA Studio, because a repository can be associated with projects, a changeset can automatically link to any associated issues and or wiki pages.
Please note, the version of FishEye running in JIRA Studio may differ from the latest released version of FishEye. Please refer to JIRA Studio Application Versions for that latest version information.
On this page:
Working with Source FishEye User Documentation JIRA Studio-specific Documentation
Working with Source
To work with source,
1. Click the 'Source' tab in the top header of JIRA Studio. Only 'Developer' accounts have access to this tab. 2. This takes you to FishEye. For details about using FishEye, please see the 'FishEye User Documentation' section below.
Screenshot: 'JIRA Studio — Source' (click to view larger image) FishEye User Documentation
The guide listed below contains information on how to use FishEye. Please note, this guide does not contain documentation on JIRA Studio-specific functions (e.g. functions that cannot be found in standalone FishEye). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
FishEye User's Guide
JIRA Studio-specific Documentation
There are currently no JIRA Studio-specific user functions for FishEye.
FishEye User's Guide
JIRA Studio May 2011 includes FishEye 2.5.4 for browsing source code. Use the search or click any of the links below to view the relevant page in the FishEye User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some FishEye functionality is restricted in JIRA Studio.
Search the FishEye 2.5.4 documentation:
FishEye Quick Start Guide
Using the FishEye Screens
Browsing through a Repository Searching the Repository Viewing a File Viewing the Changelog Viewing a File History Viewing File Content FishEye Charts Using Favourites Copying and Pasting Code from FishEye Changeset Discussions Viewing People's Statistics
Changing your User Profile
Re-setting your Password
Antglob Reference Guide
Date Expressions Reference Guide
EyeQL Reference Guide
Working with Reviews
Your source can go through a review (sometimes called code review, peer review or quality assurance) either before or after being committed to a repository.
Please note, the version of Crucible running in JIRA Studio may differ from the latest released version of Crucible. Please refer to JIRA Studio Application Versions for that latest version information.
On this page:
Working with Reviews Crucible User Documentation JIRA Studio-specific Documentation
Working with Reviews
To work with reviews,
1. Click the 'Reviews' tab in the header of JIRA Studio. Only 'Developer' accounts have access to this tab. 2. This takes you to Crucible. For details about using Crucible, please see the 'Crucible User Documentation' section below.
Screenshot: 'JIRA Studio — Reviews' (click to view larger image)
Crucible User Documentation
The guide listed below contains information on how to use Crucible. Please note, this guide does not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone Crucible). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
Crucible User's Guide
JIRA Studio-specific Documentation
Project review permissions are inherited from Crucible's default permission schemes. However, they are modified according to the repository permission scheme set up in the 'Source' tab. This means that the same read and commit permissions that apply to a project's source also apply to that project's reviews.
Crucible User's Guide
JIRA Studio May 2011 includes Crucible 2.5.4 for code reviews. Use the search or click any of the links below to view the relevant page in the Crucible User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some Crucible functionality is restricted in JIRA Studio.
Search the Crucible 2.5.4 documentation:
Getting Started with Crucible
Using the Crucible Screens
Browsing Source Files Using the Dashboard Browsing Your Reviews Browsing Reviews, Source and Issues Activity Viewing Your Favourites Crucible Icons Viewing People's Statistics Browsing Projects Viewing Project Statistics Searching in Crucible Viewing Reports Review Coverage Report Browsing All Reviews
Changing your User Profile
Roles and Status Classifications
Conducting a Review
Creating a Review Creating a Patch Review Creating a Review within Crucible Creating a Review from FishEye Creating a Review from JIRA Creating a Review from a URL Creating a Snippet Review Selecting the Files for the Review Iterative Reviews Adding Reviewers Issuing a Review Performing the Review Adding Comments Flagging Defects Completing your Review Sending all of a Review's Comments via Email Using the Review History Dialog Tracking Crucible Review Metrics Using JIRA Integration in Crucible Reviews Summarising and Closing the Review Moving a Review to Another Project Deleting an Abandoned Review
Defining your Workflow
Using Favourites
Using Keyboard Shortcuts in Crucible
Using RSS Feeds in Crucible
Using Wiki Markup in Crucible
Using Gadgets in Crucible
Working with Builds
A Plan defines everything about your entire build process. Plans:
consist of one or more Jobs, which are organised into one or more Stages; contains a single 'Default Job' in a single Stage, after creating a new Plan; define default settings for what gets built by Jobs in the Plan (i.e. the 'default source repository'); define how the Plan's build is triggered; who will be notified of the Job's build result; define who has permission to view and perform various actions on the Plan and its Jobs.
Every plan belongs to a Project.
Projects and plans can only be configured by Bamboo administrators (see Creating a Plan).
A build is the execution of either a Plan or a Job. The execution of a Plan is referred to as a 'Plan build' and that of a Job is a 'Job build'.
Please note, the version of Bamboo running in JIRA Studio may differ from the latest released version of Bamboo. Please refer to JIRA Studio Application Versions for that latest version information.
On this page:
Working with Builds Bamboo User Documentation JIRA Studio-specific Documentation
Working with Builds
Builds application is disabled by default Please note, the Builds application is disabled by default. Your administrator needs to request for it to be enabled before it will become available for users.
To work with builds,
1. Click the 'Builds' tab in the header of JIRA Studio. Only 'Developer' accounts have access to this tab. 2. This takes you to Bamboo. For details about using Bamboo, please see the 'Bamboo User Documentation' section below.
Screenshot: 'JIRA Studio — Builds' (click to view larger image)
Bamboo User Documentation
The guide listed below contains information on how to use Bamboo. Please note, this guide does not contain documentation on JIRA Studio-specific functions (i.e. functions that cannot be found in standalone Bamboo). See the 'JIRA Studio-specific Documentation' section on this page for documentation on JIRA Studio-specific functions.
Bamboo User's Guide
JIRA Studio-specific Documentation
The following Bamboo functions are specific to JIRA Studio and cannot be found in standalone Bamboo:
Actioning Issues via Builds
Bamboo User's Guide
JIRA Studio May 2011 includes Bamboo 2.6.5 for its continuous integration build server. Use the search or click any of the links below to view the relevant page in the Bamboo User's Guide. You will need to use the 'Back' button on your browser to return to the JIRA Studio documentation.
Please note, some Bamboo functionality is restricted in JIRA Studio.
Search the Bamboo 2.6.5 documentation:
Getting Started
Using the Bamboo Dashboard Viewing Bamboo's Current Activity Viewing your Latest Build Results Working with Favourites Adding a Plan to your Favourites Removing a Plan from your Favourites Displaying a Build Monitor Viewing Bamboo's Agents
Working with Projects and Plans About Projects and Plans Viewing a Plan's Details Viewing a Plan's Activity Log Viewing the JIRA Issues linked to the Builds in a Build Plan Viewing a Plan's Maven 2 Dependencies Viewing the Clover Coverage Summary for a Build Plan
Working with Build Results
About Builds and Build Results Viewing a Build Result Viewing the Code Changes that triggered a Build Viewing a Build's Artifacts Viewing a Build Log Viewing the Metadata for a Build Result Viewing the Clover Code-Coverage for a Build Result Viewing the JIRA Issues for a Build Result Linking JIRA Issues to a Build
Working with Tests
Viewing Test Results for a Build Viewing a Test's History Viewing Test Statistics for a Plan
Reporting on Plan Trends
Viewing Build Statistics for a Plan Generating Reports across multiple Plans 'Build Activity' Report 'Build Duration' Report 'Build Queue Duration' Report 'Clover Code Coverage' Report 'Clover Lines of Code' Report 'Number of Build Failures' Report 'Number of Tests' Report 'Percentage of Successful Builds' Report 'Time to Fix' Report
Reporting on Author Trends
Viewing Build Statistics for all Authors Viewing Build Results for an Author Generating Reports on selected Authors 'Build Activity per Author' Report 'Number of Build Failures per Author' Report 'Number of Builds Broken per Author' Report 'Number of Builds Fixed per Author' Report 'Percentage of Successful Builds per Author' Report
Working with Comments
About Comments Commenting about a Build Result Viewing Comments about a Build Result Viewing Code Check-in Comments
Working with Labels
About Labels Labelling a Build Result Removing a Label from a Build Result Viewing Labelled Build Results Viewing Popular Labels
Subscribing to RSS Feeds
Subscribing to an RSS Feed for All Build Results for All Plans Subscribing to an RSS Feed for All Build Results for a Particular Plan Subscribing to an RSS Feed for Failed Builds for All Plans Subscribing to an RSS Feed for Failed Builds for a Particular Plan Subscribing to an RSS Feed for Labelled Build Results
Working with Instant Messenger (IM) Notifications
About Instant Messenger (IM) Notifications Labelling a Build Result via IM Commenting about a Build Result via IM
Managing your User Profile
Changing your Password Changing your Notification Preferences Associating your Author Name with your User Profile Changing your Personal Details Viewing your Notifications
Actioning Issues via Builds
If your administrator has integrated builds with issues in your JIRA Studio instance, you will be able to action issues via builds. If the default 'Builds Workflow' is being used with your project, the workflow will look like this:
Please check with your administrator to see whether the default 'Builds Workflow' has been modified.
Diagram: 'Builds Workflow' in JIRA Studio
# 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
Full Size
The 'Wait for Build', 'Build Passed' and 'Build Failed' transitions are Bamboo-specific transitions:
'Wait for Build' — This transition will be triggered when code is committed for this issue (and a build started) using the #build commit command. Note, you must manually enter the #build commit command in your commit message to trigger the transition, as described in Actioning Issues via Commit Messages. 'Build Passed' — This transition will be automatically triggered when a build for this issue passes. 'Build Failed' — This transition will be automatically triggered when a build for this issue fails.
If you want to resolve an issue via a particular (successful) build, you can add the #build commit command to your commit message. If the build is successful, the issue will automatically transition to 'Resolved'. If the build fails, it will automatically transition to 'Build Broken'.
You can still commit without the issue potentially transitioning to 'Resolved' simply by omitting the #build commit command from your commit message.
Working with Streams
The Activity Stream feature allows you to view the combined activity of your 'Issues', 'Wiki', 'Source', 'Reviews' and (if Bamboo is enabled) 'Builds'. You can view the activity for a single project or across all of your projects in JIRA Studio. This is presented in a project tab and can also be set up to display in a user-friendly dashboard gadget. The activity stream can also be viewed on your User Profile page and is provided as an RSS feed.
Screenshot: Activity Stream Related Topics
For information about where you can view an activity stream, read the Viewing the Activity Stream document. For information about configuring an activity stream, read the Configuring the Activity Stream document. For information about adding comments to an activity stream, read the Adding Comments via the Activity Stream document.
Viewing the Activity Stream
The activity stream is available in a number of places in JIRA Studio. Each view provides a different set of activities depending on whether you are in the context of a user, single project or multiple projects.
What will it show?
Issues: issues that are created, updated, and resolved, as well as comments and attachments Wiki: pages, comments, news items and attachments that are created or edited Source: committed changesets Reviews: reviews that are created, approved, commented, marked as complete or incomplete, closed, or otherwise updated Builds (if Bamboo enabled): build results (successful and unsuccessful)
See the 'Activity Stream Activities and Comments' table for a full list of activities displayed in an activity stream.
Activity Stream as a Dashboard Gadget Activity Stream as a Project Tab Activity Stream in your User Profile Activity Stream as an RSS Feed
Activity Stream as a Dashboard Gadget
Your Studio instance will be set up to display an activity stream gadget on your dashboard by default. This activity stream contains all of the recent activity (as described in the 'What will it show?' section above) for a configurable set of projects and users. By default, it will display the recent activity for all projects and all users in your Studio instance.
Screenshot: Activity Stream dashboard gadget (click to view full-size image)
If your dashboard does not display an activity stream gadget, you can add one by following the JIRA documentation on configuring your dashboard (see the 'Adding a Gadget' section). You will need to add the 'Activity Stream' gadget.
Activity Stream as a Project Tab
Every project in JIRA Studio has an 'Activity Stream' area on the project 'Summary' tab. This activity stream contains all of the recent activity (as described in the 'What will it show?' section above) by all users, for the project.
To view the activity stream for a project, 1. Select the required project from the 'Projects' dropdown list. The project page will display. 2. Click the 'Summary' tab. The project activity stream for all users displays at the right side of the page.
Screenshot: Activity Stream area of the Summary tab (click to view full-size image)
Activity Stream in your User Profile
Your user profile page is set up to display an activity stream by default. This activity stream contains all of the recent activity (as described in the 'What will it show?' section above) by you. In addition this activity stream will also show recent activity by other users on wiki pages you have authored or are watching.
To view the activity stream for your user profile,
1. Navigate to your user profile. Your user profile will show with the 'Summary' tab displayed. The right side of the page displays your recent activity. 2. You can select the 'Activity' tab to view your activity stream.
Screenshot: User Profile Activity Stream (click to view full-size image)
1. Personal Summary Tab 2. Personal Activity Stream Tab
Activity Stream as an RSS Feed
Any of the dashboard gadget, project tab, or user profile activity streams can also viewed as an RSS feed. This allows you to use an RSS reader to keep up to date with the latest changes in a particular project or set of projects.
The link for the RSS feed of an activity stream is available via the RSS symbol in the top right corner of each activity stream view.
Read more about working with RSS feeds in the Confluence documentation.
Screenshot: Activity Stream RSS View (click to view full-size image)
Configuring the Activity Stream
You can configure the activity stream that is displayed on the activity stream dashboard gadget to show a selected set of updates. Please note, the project tab activity stream (updates from all users for a single project) and the user profile activity stream (updates from all projects for a single user) are not configurable.
To configure an activity stream (dashboard gadget),
1. From the 'Dashboards' drop-down at the top left of your screen, select 'Manage Dashboards'. 2. In the 'Manage Dashboards' screen, click to select the required dashboard name. 3. In the 'Activity Stream' header, hold your mouse over the top right corner of the gadget until a down-arrow appears. 4. Click the down-arrow to display an options menu. 5. Click 'Edit' (see screenshot). Editing a Gadget (screenshot)
6. Update the configuration settings as desired. Configuring the Activity Stream (screenshot)
'Title' — specify the title that you wish to display on your dashboard gadget. The title will display in the title bar of your dashboard gadget after the 'Activity Stream:' text, e.g. 'Activity Stream: My Activity Stream'. 'Projects' — select the projects that you wish to include in the activity stream. You can select multiple projects. The default selection is all projects. 'Username' — enter the user id's of the users that you wish to include in the activity stream. You can specify multiple users. If you leave this field blank, all users will be selected. 'Number of entries' — enter the maximum number of updates that you want displayed in the activity stream. If you leave this field blank, it will default to 20. 'Refresh Interval' — from the drop-down list, select how often you would like the activity stream data display to refresh. 7. Click the 'Save' button. The activity stream will immediately update.
Adding Comments via the Activity Stream
Adding Comments via the Activity Stream
The activity stream in JIRA Studio is an interactive information source. If you see an activity in your activity stream that you wish to comment on, you can add your comment via the activity stream. Depending on what the activity is, your comment will be added directly to the appropriate issue or wiki page/blog in the relevant application.
To comment on an activity stream update, 1. Navigate to a page that displays an activity stream (e.g. the activity stream tab for a project). 2. Hover your mouse over the activity that you wish to comment on and click the add comment icon that displays. A text box will display in the activity stream (see screenshot).
3. Enter your comment and click the 'Save' button. Your comment will be displayed in the activity stream (see screenshot). Your comment will also be stored against the relevant issue, wiki page/blog or review, as described in the table below.
Table: Activity Stream Activities and Comments
Application Activity Can I comment on this Where will my comment be stored? activity?
Issues (JIRA) Issue Created Stored as a comment on the issue.
Issues (JIRA) Issue Edited Stored as a comment on the issue.
Issues (JIRA) Issue Resolved Stored as a comment on the issue.
Issues (JIRA) Comment Added to Issue Stored as a comment on the issue. Issues (JIRA) Attachment Added to Issue Stored as a comment on the issue.
Wiki Page Added Stored as a comment in a new thread on the (Confluence) page.
Wiki Page Edited Stored as a comment in a new thread on the (Confluence) page.
Wiki News Added Stored as a comment in a new thread on the (Confluence) news.
Wiki News Edited Stored as a comment in a new thread on the (Confluence) news.
Wiki Comment Added (to Page/News) Stored as a reply comment on the (Confluence) page/news.
Wiki Comment Edited (on Page/News) Stored as a reply comment on the (Confluence) page/news.
Wiki Attachment Added/Edited (for a N/A (Confluence) Page/News)
Source Changeset Committed N/A (FishEye)
Crucible Review Created N/A (Reviews)
Crucible Review Approved N/A (Reviews)
Crucible Review Completed N/A (Reviews)
Crucible Review Changed N/A (Reviews)
Crucible Review Closed N/A (Reviews)
Crucible Comment Added to Review N/A (Reviews)
Bamboo Build Result N/A (Builds)
Working with the Repository
Your Subversion repository in JIRA Studio contains your source code. To work with your repository, you can either access the files directly using the Subversion command-line client or use an IDE (integrated development environment) to interact with the repository.
On this page:
Using the Subversion Command-Line Client Checking out a Working Copy Updating your Working Copy Committing Changes to the Repository Other useful Subversion commands Using an IDE
Using the Subversion Command-Line Client
Subversion has a wide range of functions available via its command-line client. The following section describes how to use some of the more commonly used commands in Subversion.
Checking out a Working Copy
Checking out a project is typically the first step in working with your source repository. This will create a local working copy of the project on your machine. To check out your Subversion project, 1. Open a Subversion command-line client. 2. Enter the following command: svn checkout https://
Updating your Working Copy
Before you begin making changes to your working copy, it is highly recommended that you update your working copy with changes that other users (with access to the repository) may have committed. To update your working copy,
1. Open a Subversion command-line client. 2. Enter the following command: svn update 3. A confirmation message will be displayed at the end of a successful update, e.g. 'Updated to revision 2442.', as well as the list of files updated in your working copy.
Committing Changes to the Repository
Once you have finished making changes to your working copy, you can commit your changes to the repository by using the svn commit command. To commit changes to your Subversion project,
1. Open a Subversion command-line client. 2. Enter the following command: svn commit -m "
Other useful Subversion commands
The table below lists other useful Subversion commands that are commonly used 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 Description
svn add Add a new item (i.e. file or directory) to your repository.
svn copy Copy an item and add the new copied item to your repository.
svn Delete an item from both your working copy and repository. delete
svn move Copy an item and delete the original in your working copy and repository.
svn Determine what changes (at the file/directory level) have been made to your working copy. status
svn diff Display what has changed in each file that has been modified (i.e. the 'difference' between your modified file and the original).
svn Revert the working copy, removing all changes. revert
Using an IDE The steps required to configure an IDE with a source repository vary depending on which IDE you are using. You should be asked to provide the following repository details when configuring your IDE:
Location of your repository — that is, https://
Please refer to your IDE documentation for specific instructions on configuring your source repository and working with your source repository.
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.
Working with Google Apps Integration
This page links to documentation on using features of the Google Apps Marketplace integration for JIRA Studio. You can also find additional information in the Google Apps Integration FAQ.
For information on administering the features of the Google Apps Marketplace integration for JIRA Studio, see Administering Google Apps Integration.
Click the relevant document below to view it:
Logging In and Out With Google Apps Integration Using the Activity Bar
Logging In and Out With Google Apps Integration
This page contains instructions on how to log in and out of JIRA Studio with Google Apps Integration.
On this page:
Overview Logging In Logging in from Google Apps Logging in directly from JIRA Studio Logging in without a Google Apps account Setting your Subversion and RSS Log In Passwords Logging Out 1. Log Out of Google Apps 2. Log Out of JIRA Studio
Overview
When you use JIRA Studio with Google Apps Integration you need to manage your log in status in both of these systems. When you log in to Google Apps, you access your Google email, calendar, and documents. The Google Apps Marketplace offers products and services designed to integrate with your Google Apps. As a separately licensed product, JIRA Studio integrates with (i.e. The JIRA Studio Activity Bar ), but has a different login to your Google Apps.
Logging In
Logging in from Google Apps
Log into Google Apps with your account. You will then be redirected to JIRA Studio with Google Apps Integration.
Logging in directly from JIRA Studio
When you visit the JIRA Studio login page, you will be redirected to log into Google Apps (see 'JIRA Studio login prompt' screenshot below).
Logging in without a Google Apps account
If you do not have a Google Apps account, you can log in to JIRA Studio an an 'external user'. You will need to log in with the login details provided by your JIRA Studio Administrator.
Logging in without a Google Apps account, 1. From the 'Log In' drop-down, select the Log in directly option. (see 'Login options for external users' screenshot below) 2. The system will direct you to the JIRA Studio log in screen. 3. At the Log in using your JIRA Studio Account dialog, enter the Log In details provided by your JIRA Studio Administrator. 4. Click the Log In button to start using JIRA Studio.
Login options for external users (screenshot)
Setting your Subversion and RSS Log In Passwords
If you are using JIRA Studio with Google Apps integration, you can access Subversion with your Google Apps password. The first time you log in via Google Apps, you will be prompted to set your JIRA Studio Passwords for Subversion and RSS feeds.
These passwords cannot be set up automatically via the Google Apps single sign-on process. However, you can set these passwords to be the same as your Google Apps password.
Setting your Subversion and RSS logins,
1. Click the 'Source' tab in the JIRA Studio header. 2. At the Welcome to JIRA Studio login screen, set up your Subversion and RSS 'Username' and 'Password', then click 'Confirm'. 3. Log into Subversion and RSS using your Google Apps password, without the domain name. For example, if your username is: '[email protected]', you would log in as: 'alfred'.
Logging into the repository (screenshot)
Logging Out
You need to log out of Google Apps and JIRA Studio independently. This means that if you log out of JIRA Studio while you are still logged in to Google Apps, you can easily return to JIRA Studio. As a security measure, the system will prompt you to log out of Google Apps if you have exited JIRA Studio, but are still logged in to the Google domain.
1. Log Out of Google Apps
Simply click 'Log out' from the Google Apps interface.
2. Log Out of JIRA Studio
Click 'Log Out' from the JIRA Studio interface.
Logging out of JIRA Studio (screenshot) Using the Activity Bar
If you are using JIRA Studio with Google Apps integration, you have a menu bar at the bottom of the screen called the Activity Bar. This feature provides you with quick access to JIRA Studio and Google Apps functionality.
Activity Bar (JIRA Studio-only access): JIRA Studio users who do not have Google IDs (i.e. external users) will only see and be able to access JIRA Studio-specific features:
Recent Activity Recent Issues Favourite Pages Recent Builds Outstanding Reviews
Screenshot: External User Activity Bar
Activity Bar (Google Apps and JIRA Studio integration): JIRA Studio users who have Google IDs will be able to access both JIRA Studio and Google features:
Recent Activity Recent Issues Favourite Pages Recent Builds Outstanding Reviews Gmail Messages Google Calendar Events Google Docs Google Sites
Screenshot: The Activity Bar in JIRA Studio
Viewing Recent Activity with the Activity Bar
To view recent activity with the Activity Bar,
1. Click the Atlassian button on the Activity Bar. A short list of recent activity in JIRA Studio and Google Apps will be displayed. 2. Click a link in the activity stream to view the relevant information, e.g. issue, wiki page, etc.
Screenshot: Recent Activity in the Activity Bar See Working with Streams for more information about the activity stream in JIRA Studio.
Viewing Recent Issues with the Activity Bar
To view recent issues with the Activity Bar,
1. Click the issues button on the Activity Bar. A short list of recently changed JIRA issues will be displayed. 2. Click any link to open the issue.
Screenshot: Recent Issues in the Activity Bar
To add an issue via the Activity Bar,
1. Click the issues button on the Activity Bar.
2. Click the plus sign icon in the corner of the dialogue. A dialogue box will be displayed. 3. Select the project and the issue type in the dialogue box. 4. Click the 'Create' button. The 'Create Issue' screen will be displayed. 5. Enter the details for your issue and submit it.
Screenshot: Adding an Issue from the Activity Bar See Working with Issues for more information about using JIRA issues in JIRA Studio.
Viewing Favourite Pages with the Activity Bar
To view favourite pages with the Activity Bar,
1. Click the wiki favourite button on the Activity Bar. A short list of Confluence wiki pages that you have selected as favourites will be displayed. 2. Click a link to open the wiki page.
Screenshot: Favourite pages in the Activity Bar
See Working with the Wiki for more information about using Confluence wiki pages in JIRA Studio.
Viewing Recent Builds with the Activity Bar
To view recent builds with the Activity Bar,
1. Click builds button on the Activity Bar. A list of recent Bamboo builds that have completed will be displayed. Note, the builds button will only be visible to Developers on instances where Bamboo builds are enabled. 2. Click a link to open the build.
Screenshot: List of recent build activity on the Activity Bar
See Working with Builds for more information about using Bamboo builds in JIRA Studio.
Viewing Outstanding Reviews with the Activity Bar
To view outstanding reviews with the Activity Bar, 1. 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. Note, the reviews button will only be visible to Developers. 2. Click a link to open the review.
Screenshot: List of outstanding reviews on the Activity Bar
See Working with Reviews for more information about using Crucible reviews in JIRA Studio.
Viewing Gmail Messages with the Activity Bar
To view Gmail messages with the Activity Bar,
1. Click the Gmail button on the Activity Bar. A list of new email messages in your Gmail inbox will be displayed. A
red number on the chatbar icon shows how many unread messages are waiting in Gmail. 2. Click a link to open the email.
Screenshot: List of unread Gmail messages on the Activity Bar
Viewing Upcoming Google Calendar Events with the Activity Bar
To view upcoming Google Calendar events with the Activity Bar,
1. Click the Google Calendar button on the Activity Bar. A list of upcoming events will be displayed. 2. Click a link to open the event in Google Calendar.
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar See Using Google Calendar with Google Apps Integration for more detail on how Google Calendar integrates with JIRA Studio.
Viewing Google Docs with the Activity Bar
To view upcoming Google Calendar events with the Activity Bar,
1. Click the Google Docs button on the Activity Bar. A list of recently updated documents will be displayed. 2. Click a link to open the document.
Screenshot: List of recently updated Google Docs on the Activity Bar
See Using Google Docs with Google Apps Integration for more detail on how Google Docs integrates with JIRA Studio.
Launching Google Sites from the Activity Bar
To launch Google Sites from the Activity Bar,
1. Click the Google Sites button on the Activity Bar. Google Sites will be launched in a new web browser window. You will be automatically logged in with your Google ID.
Screenshot: Google Sites, launched by the Activity Bar Using Google Calendar with Google Apps Integration
This page explains the Google Calendar integration in JIRA Studio and how to use it.
On this page:
Viewing upcoming Google Calendar events from JIRA Studio Adding a Google Calendar event from JIRA Studio Removing an event from Google Calendar Related Topics:
Viewing upcoming Google Calendar events from JIRA Studio
Google Calendar is integrated into JIRA Studio, allowing you to view upcoming Google Calendar events with the Activity Bar.
Clicking the Google Calendar button on the Activity Bar will show a list of upcoming events. Click any link to open the event in Google Calendar.
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar
Adding a Google Calendar event from JIRA Studio
To add an event to the calendar, click the Google Calendar button on the Activity Bar, then click the plus sign icon in the corner of the dialog. A form field opens, where you can simply type the event details in then click 'Create', as in this example:
5pm requirements meeting
This example would add an event to the calendar called 'requirements meeting' at 5pm today. A small notification message will appear inline, confirming that the creation was successful. You can also set events for different days by typing in the day, as in the following example: 5pm tuesday requirements meeting
Screenshot: Upcoming Google Calendar events, shown on the Activity Bar
Screenshot: Adding a Google Calendar event from the Activity Bar
Screenshot: Notification on creating an event
Removing an event from Google Calendar
To remove an event from Google Calendar, launch Google Calendar by clicking the Google Calendar button on the Activity Bar, then clicking 'See More'. Google Calendar will launch in a new browser window — find your event and click to open it. A screen loads with the event details. Click the 'Delete' button to remove the event.
Screenshot: An event in Google Calendar
Screenshot: Deleting an event from Google Calendar Related Topics:
To learn more about Google Apps Integration in JIRA Studio, see Using the Activity Bar.
Using Google Docs with Google Apps Integration
This page contains instructions on how to use Google Docs integration in JIRA Studio.
On this page:
Viewing recently updated Google Docs from the Activity Bar Attaching Google Docs to issues Attaching Google Docs to wiki pages Attaching a list of Google Docs to a wiki page
Viewing recently updated Google Docs from the Activity Bar
Clicking the Google Docs button on the Activity Bar shows a list of recently updated documents. Click any link to open the document.
Attaching Google Docs to issues
Google Docs can be attached to JIRA issues. To do this:
1. Create or open the desired JIRA issue. 2. Click the 'Attach Google Docs' link. The 'Google Docs Picker' window appears. You can type text into the 'Title Contains' field to search for a document, also you can restrict the documents displayed by selecting an option from the 'Doc Type' drop-down menu. You can take a look at the contents of a document by clicking the 'preview' link next to each one. To select the document(s) you want to attach, check the box next to the document file name and click 'Attach Selected Documents '. 3. You will be returned to the view issue page. The attached documents will appear as a list in the 'Google Documents' section.
Note that attached Google Docs are not static, they will always be up to date with the most recent edits made in Google Apps. Users will only be able to view documents which they are allowed access to in Google Docs. You can only add one custom Google Docs field to a JIRA issue. Screenshot: Google Docs attached to a JIRA issue
Screenshot: Google Docs Picker
Screenshot: Previewing Google Docs in JIRA Attaching Google Docs to wiki pages
Google Docs can be attached to wiki pages. To attach Google Docs to a wiki page using the Rich Text Editor:
1. Edit the page. Place the text cursor where you would like to insert the Google Document.
2. Click the macro browser icon in the Rich Text Editor toolbar . Click the 'External Content' category in the left-hand navigation bar, or type 'Google' into the form field at the top right of the window. The Google Docs macros will appear in the list. You can choose from the following: Google Document, Google Presentation, Google Spreadsheet. Select one of the above by clicking. The Macro details screen appears. On this page, click 'Select Document' to select a document and choose attributes such as width and height, as well as view a preview of the document inline. When you're ready, click 'Insert'. 3. The Google Docs macro is added to the page with the selected document(s), which will appear inline when rendered. For now, the macro will appear in the editor window looking like the following:
{gdocument:docid=0AV1fqMj98CsNZGhodHN6NXhfNGR3bmZ4cGY1|height=100%}
4. Click 'Save' on the wiki page to keep your changes. 5. When the page loads, you will be able to read the document in the wiki page. An 'Edit' link will appear beneath the document, allowing you to instantly edit the document in Google Apps.
Screenshot: Browsing Google Docs macros 5.
Screenshot: Google Docs macro attributes in the Macro Browser
Screenshot: Google Docs macro in the Rich Text Editor 5.
Screenshot: Google Document embedded in a wiki page
Attaching a list of Google Docs to a wiki page
1. Edit the page. Place the text cursor where you would like to insert the list of Google Documents.
2. Click the macro browser icon in the Rich Text Editor toolbar . Click the 'External Content' category in the left-hand navigation bar, or type 'Google' into the form field at the top right of the window. Select the 'Google Documents List' macro from the results. The Macro details screen appears. You can also choose any or all of the following settings: 'Select Folder' filters the list of documents, to show only documents under the chosen folder. 'Sorting', specified as a comma-separated list of fields values (type, title, author, createdOn, updatedOn, folder) Append desc to any of the sort values to specify reverse sorting. 'Filter by Document Type' filters the list according to the specified document type(s). 'Filter by Title' filters the list according to the given document title. 'Filter by Author' filters the list according to the given author name. 'Filter by Date Since' filters the list of documents created since the specified date. Date format should be YYYY-MM-DD (e.g., 2009-11-20). 'Filter by Date Before' filters the list of documents created before the specified date. Date format should be YYYY-MM-DD (e.g., 2009-11-20). 'Display Documents in Folder View' can be switched on or off. 'Include Old Document Versions' can be switched on or off. When you're ready, click 'Insert'. 3. The Google Documents list macro is added to the page with the selected settings, which will appear inline when rendered. For now, the macro will appear in the editor window looking like the following:
{gdocumentlist}
4. Click 'Save' on the wiki page to keep your changes. 5. 5. When the page loads, you will be able to see the list of documents in the wiki page.
Screenshot: List of Google Docs in a Confluence wiki page
Creating Links
You can create links to your issues, wiki, source, reviews and builds. Once created, links enable you to quickly jump to related information.
To link to ... Type this Examples
an issue
a wiki page in the same project [
a wiki page in a different project [
a changeset revision:
a source file source:
a review
a build plan
a build result
For example, when developing a new feature, you may want to link in the new source file(s) to the original JIRA issue. Simply type the source file name in a text field of the issue (e.g. the 'Description' or 'Comment' field) prefixed with 'source:'. The link to the source file will automatically be created upon saving your change (see screenshot below).
Screenshot: 'Creating Links' Managing Your Profile
You can view user-specific information and personalise your user experience in JIRA Studio by managing your profile.
In your user profile page, you can access reports on your votes, watches and reviews, as well as perform user-related functions such as changing your password. Your user profile page also allows you to set your personal preferences for the following applications:
Issues Preferences Wiki Preferences Source Preferences Reviews Preferences
To view your user profile in JIRA Studio,
1. Click the menu labelled with your user name in the header of JIRA Studio. 2. Click 'Profile' in the dropdown menu that displays. 3. Your 'User Profile' will display (see screenshot below). 4. You can access functions for your user profile from the left hand menu.
Screenshot: 'User Profile'
Changing Your Password in JIRA Studio
This page provides information on how to change your password for JIRA Studio, both with and without Google Apps integration.
On this page:
Password Management in Standard JIRA Studio Changing your password as a JIRA Studio user Changing passwords as a JIRA Studio Administrator Password Management in JIRA Studio with Google Apps integration Changing your main password as a user of JIRA Studio with Google Apps integration Changing your main password as an administrator of JIRA Studio with Google Apps integration Changing your Subversion password in JIRA Studio with Google Apps integration
Password Management in Standard JIRA Studio When using standard JIRA Studio, all users have only one password that gives access to JIRA Studio, Subversion, RSS feeds and the Atlassian IDE Connectors.
Changing your password as a JIRA Studio user
As a user of JIRA Studio, you can change your password by visiting the change password screen under Issues. If you have forgotten your password, you can click the "forgot password" link on the JIRA Studio login screen to have a new password sent to you.
Changing passwords as a JIRA Studio Administrator
As an administrator of JIRA Studio, you access the User Browser menu, where you can change passwords for any user (including yourself). See the pages on changing user passwords in JIRA for details on this process.
Password Management in JIRA Studio with Google Apps integration
When using JIRA Studio with Google Apps integration, users have two passwords. One is their main password which is used to access JIRA Studio and Google Apps, but they also have a secondary password, which is used to access Subversion, RSS feeds and the Atlassian IDE Connectors. New users will be asked to set this secondary password in JIRA Studio when they first log in. However if you need to change your password, these discrete passwords must be changed separately, as detailed below.
Changing your main password as a user of JIRA Studio with Google Apps integration
As a user of JIRA Studio with Google Apps integration, you can change your general JIRA Studio password by selecting the "forgot password" link on the Google Apps login screen.
Changing your main password as an administrator of JIRA Studio with Google Apps integration
As an administrator of JIRA Studio with Google Apps integration, you access the Google Apps administration screens, where you can change general JIRA Studio passwords for any user (including yourself).
Subversion passwords must be changed separately, via the JIRA Studio User Browser.
Changing your Subversion password in JIRA Studio with Google Apps integration
Only administrators of JIRA Studio with Google Apps integration can change the Subversion password for a given user. To do this, the administrator accesses the JIRA Studio User Browser menu, where you can change Subversion passwords for any user (including yourself). Users will need to get in touch with their administrator to request a change to their Subversion password.
See the pages on changing user passwords in JIRA for details on this process.
JIRA Studio FAQ
On this page:
JIRA Studio FAQ JIRA Studio Evaluator's FAQ Need more help? JIRA Studio FAQ
Usage FAQ How are we notified in case of system maintenance or outage? 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 create issues or issue comments via email? How do I file bugs or log feature requests? How do I request support? How should Studio be configured for a shared code module? What is the activity stream in JIRA Studio? What is the URL for my installation of JIRA Studio? Why can't I find the documentation for a particular JIRA Studio function? Configuration and Administration FAQ How do I associate a JIRA Project with multiple FishEye Repositories? Can I import my existing JIRA data, Confluence data, Subversion data, etc? How do I enable issue and issue comment creation via email? How can I migrate my content to and from other Atlassian applications? Can I use a custom Elastic Bamboo image? When will my JIRA Studio applications be upgraded? Subversion is constantly asking users to re-authenticate and failing with the correct credentials Can I change the look and feel of JIRA Studio? Can I install my own plugins? Are alternative languages available for JIRA Studio? Do you support SSL? How do I request installation modifications? How do I enable Bamboo for JIRA Studio? Can I use JIRA Studio with Confluence Hosted? What remote APIs are supported in JIRA Studio? How do I update JIRA issues via subversion commit messages? How are commit messages defined (for actioning issues)? Can I import my existing data from an external system (Bugzilla, Trac)? Can I use EBS volumes with Elastic Bamboo? How do I create a backup copy of my Subversion repository? Can I change the global theme for the look and feel? How do I add Google Apps to JIRA Studio? Can I use Clover with JIRA Studio? How do I import Subversion data for a single JIRA Studio project? How do I migrate from Visual SourceSafe to JIRA Studio? Subscription and Account FAQ Can I disable a user without deleting them? Can I import external data into JIRA Studio? How do I add a technical contact to my account? How do I end my subscription or evaluation? 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 JIRA Studio licensed? How is the user count of my account calculated? How do I reduce my user count? How long will it take to receive my JIRA Studio installation after placing the order? I would like to try Studio out before buying. How do I do that? What are the storage and bandwidth limits? What database will the JIRA Studio instance use? What domain name will my JIRA Studio service be on? Can I use my own domain name? What happens to my JIRA Studio instance when my account is cancelled? What is the minimum number of users allowable in an upgrade? What is the minimum term of service? What level of customization and control will I have over my JIRA Studio instance? Google Apps Integration FAQ Deletion Policy for User Data JIRA Studio Application Versions JIRA Studio Licensing JIRA Studio Plugin Policy Third-Party Plugin Process Restricted Functions in JIRA Studio Support Policies Bug Fixing Policy How to Report a Security Issue New Features Policy Security Advisory Publishing Policy Security Update Policy Severity Levels for Security Issues Update Policy Supported Platforms End of Support Announcements for JIRA Studio JIRA Studio Evaluator's FAQ New users may wish to consult the JIRA Studio Evaluator's FAQ:
Page: Are alternative languages available for JIRA Studio?
Page: How is JIRA Studio licensed?
Page: What is the minimum term of service?
Page: What are the storage and bandwidth limits?
Page: Can I import external data into JIRA Studio?
Page: How do I update JIRA issues via subversion commit messages?
Page: What is the activity stream in JIRA Studio?
Page: Can I change the look and feel of JIRA Studio?
Page: Are alternative languages available for JIRA Studio?
Page: Can I change the look and feel of JIRA Studio?
Page: How do I update JIRA issues via subversion commit messages?
Page: Can I import external data into JIRA Studio?
Page: How is JIRA Studio licensed?
Page: What are the storage and bandwidth limits?
Page: What is the minimum term of service?
Page: What is the activity stream in JIRA Studio?
Need more help? Do you have a question, or need help with JIRA Studio? Please create a support request.
Usage FAQ
Find answers to common questions about using JIRA Studio here.
How are we notified in case of system maintenance or outage? 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 create issues or issue comments via email? How do I file bugs or log feature requests? How do I request support? How should Studio be configured for a shared code module? What is the activity stream in JIRA Studio? What is the URL for my installation of JIRA Studio? Why can't I find the documentation for a particular JIRA Studio function?
Have you read the other FAQs?
Don't know how to configure something in JIRA Studio? Try the Configuration and Administration FAQ. Have a question about your JIRA Studio account or ordering JIRA Studio? Try the Subscription and Account FAQ.
How are we notified in case of system maintenance or outage?
Atlassian will notify all hosted customers at least 48 hours prior to any planned maintenance, by sending an email message to all technical contacts listed under your account at my.atlassian.com. In the event of unplanned downtime, we will email all technical contacts within 24 hours after the downtime to explain why.
You can add a technical contact person to your account at my.atlassian.com, by entering the person's email address in your hosted account details on the 'Licenses' page. Full instructions follow.
To add a technical contact to your account:
1. Sign in at my.atlassian.com. 2. Go to your 'Licenses' page. 3. Click the plus '+' sign next to your hosted account to expand the options for the account. 4. Click the 'Add' option next to 'Main Technical Contact'. 5. Enter your contact's email address and click 'Add'. 6. If the person has not yet signed up to my.atlassian.com, you will be prompted for more information. Enter the information and click ' Save'. The person will receive an email informing them that they have been automatically signed up at my.atlassian.com. The email will contain their username and password.
You can assign an unlimited number of technical contacts to your account. However, if you have a large number of contacts, you may wish to create a mail alias at your organisation to manage the list. We currently can't add technical contacts to Evaluation licenses.
Adding a technical contact to my.atlassian.com does not automatically add the person as a user on your hosted system and does not affect the number of users in your account.
You may also wish to follow JIRA Studio on Twitter.
How can I edit or reassign closed issues?
JIRA's default workflow prevents closed issues from being edited or reassigned. If you wish to loosen this restriction, it can be done by editing the JIRA workflow and removing the jira.issue.editable flag from the Closed step:
1. If you are using the default jira workflow, copy the workflow and edit the copy. If you are already using a customised workflow, create a draft of it and edit the draft. 2. In the workflow, remove the jira.issue.editable flag as described in the JIRA workflow documentation. 3. Activate the workflow by creating a Workflow Scheme that uses your edited workflow, and associating the workflow scheme with the relevant projects.
You will now be able to edit or bulk edit the issues.
How can I prevent certain users seeing certain content?
Out the box, Studio assumes a single set of users that can see all projects. There are two ways that people often wish to restrict access:
1. Restrict issue visibility to just the reporter and some group. For instance you may wish to let end users raise issues, and not see issues raised by other users. This can be achieved by creating a security scheme and applying it to the project. 2. Divide users into groups, and restrict which projects a group can see. For instance one might have a Finance project that only finance people should be able to see. This can be achieved by defining new groups for each set of users and redefining the JIRA permission schemes, Confluence space permissions and Fisheye/Subversion permissions to be in terms of the new groups. For details, see the restricting project visibility section in the documentation.
How do I access my Subversion repository?
You may view your repository and code activity via the 'Source' tab of JIRA Studio.
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://
The free "Version Control with Subversion" (Pilato, Collins-Sussman, Fitzpatrick; 2004 O'Reilly) online Subversion reference contains detailed documentation on using the Subversion repository.
How do I create issues or issue comments via email?
You can create issues and issue comments in the 'Issues' application of your Studio instance via email, if your administrator has enabled this feature.
The email address that you use to create issues and issue comments is derived from the account name of your Studio instance, i.e. jira@ accountname.jira.com. You will also receive your email notifications from this email address.
For example, if you log into your Studio instance at https://myjirastudio.jira.com, the email address you use for issue and issue comment creation will be, [email protected]
Please refer to the JIRA documentation for further information on how your email is processed to create an issue or an issue comment.
How do I file bugs or log feature requests?
If you find a bug in JIRA Studio, or have a suggestion for improving it, please file a Bug or Feature Request at https://studio.atlassian.com under the JIRA Studio project (if you have not logged in to JIRA Studio before, you may need to create an account.
Please also see 'How we choose what to implement' for further details on how we handle feature requests and bugs.
How do I request support?
For assistance with administering JIRA Studio, please create a Support request at https://support.atlassian.com under the JIRA Studio project. You will need a support account to create a request. Sign up for a free support account here, if you do not have one.
You can also create a support request directly in JIRA Studio. Please see Creating a Support Request for further details.
How should Studio be configured for a shared code module?
Developers often factor out reusable code out of projects into separate modules, which are then moved to a Subversion directory separate from the main codebase. These modules are often not large enough to warrant their own JIRA project or Confluence space. In this case it is desirable to have just a Fisheye module (under the 'Source' tab) for viewing the source, with no other references to the module in the project list drop-down or elsewhere.
This can be achieved as follows:
1. Create a Studio project as usual (eg. COMMON). 2. In the new project's admin section: a. In the Project Roles: row, click View members and remove the groups from all roles. This effectively makes the JIRA project invisible everywhere except in the admin section. b. Click Space Admin, then Permissions, and revoke the 'View' permission from all groups. This makes the Confluence space invisible to everyone except the user who created the project. c. Click Manage Project Tabs and hide the Issues and Wiki tabs.
The project will now be invisible except for within the 'Source' tab.
Now for each project that uses the common module:
1. Go to that project's Studio administration page and on the 'Subversion Repository:' line and click Select 2. For 'FishEye repository key', enter the module name (eg. COMMON) and add it as a non-primary association.
Now any commits in the COMMON codebase that reference an issue key will appear on the referenced issue's 'Source' tab.
What is the activity stream in JIRA Studio?
The activity stream in JIRA Studio is an interactive information source. If you see an activity in your activity stream that you wish to comment on, you can add your comment via the activity stream. Depending on what the activity is, your comment will be added directly to the appropriate issue, wiki page/blog or review in the relevant application. A simple click on a feed item sends you directly to that activity contribution.
What is the URL for my installation of JIRA Studio?
By default, you are assigned a domain name of: https://accountname.jira.com where accountname is the account name you provided at sign-up.
Please note that installation may take up to 48 hours from when your order is placed, so your URL may not be immediately available after sign-up.
This URL can be changed to your own domain if required.
Why can't I find the documentation for a particular JIRA Studio function?
JIRA Studio is a product suite comprised of a number of different Atlassian applications, such as JIRA, Confluence, FishEye, Crucible, etc. The functional documentation in this space only covers the JIRA Studio-specific functions (for example, functions that are not found in the standalone applications), such as Configuring Commit Commands for Issues.
If you are looking for documentation on a function of a particular application, for example, creating a component in JIRA, you can find this in the documentation for the standalone product (for example, Confluence documentation). Each of the application hub pages in the JIRA Studio Administrator's Guide and JIRA Studio User's Guide contain links to the standalone product documentation as well as a search box for that documentation.
If you'd like to find documentation on how to create a wiki page (a Confluence function, not JIRA Studio-specific), you can find it by navigating to the Working with the Wiki page and using the search in the 'Confluence User Documentation' section.
Please note, the search in the left-hand navigation only covers the JIRA Studio documentation space. This means, you will only find documentation on JIRA Studio-specific functions in the search results.
Configuration and Administration FAQ
Find answers to common questions about configuring and administering JIRA Studio here.
How do I associate a JIRA Project with multiple FishEye Repositories? Can I import my existing JIRA data, Confluence data, Subversion data, etc? How do I enable issue and issue comment creation via email? How can I migrate my content to and from other Atlassian applications? Can I use a custom Elastic Bamboo image? When will my JIRA Studio applications be upgraded? Subversion is constantly asking users to re-authenticate and failing with the correct credentials Can I change the look and feel of JIRA Studio? Can I install my own plugins? Are alternative languages available for JIRA Studio? Do you support SSL? How do I request installation modifications? How do I enable Bamboo for JIRA Studio? Can I use JIRA Studio with Confluence Hosted? What remote APIs are supported in JIRA Studio? How do I update JIRA issues via subversion commit messages? How are commit messages defined (for actioning issues)? Can I import my existing data from an external system (Bugzilla, Trac)? Can I use EBS volumes with Elastic Bamboo? How do I create a backup copy of my Subversion repository? Can I change the global theme for the look and feel? How do I add Google Apps to JIRA Studio? Can I use Clover with JIRA Studio? How do I import Subversion data for a single JIRA Studio project? How do I migrate from Visual SourceSafe to JIRA Studio?
Have you read the other FAQs?
Don't know how to use something in JIRA Studio? Try the Usage FAQ. Have a question about your JIRA Studio account or ordering JIRA Studio? Try the Subscription and Account FAQ.
How do I associate a JIRA Project with multiple FishEye Repositories?
By default, a JIRA issue will display the changeset from Subversion in the Source tab if the commit message references the JIRA issue in question, and the source was committed within the same project:
If you have source commited in repositories outside that you'd also like referenced, you can configure this option like so:
1. Click Administration from the top-right corner. 2. Under Projects, click the project you wish to modify. 3. You should see FishEye Repository:
JIRA Studio has an Subversion importer that allows you to import versioned Subversion data. For more information on importing Subversion data, see the 'Source' section on the Importing Data page.
Other import functions, such as JIRA CSV imports, are currently disabled in JIRA Studio. However, you can request data to be imported into your instance of JIRA Studio by filing a ticket at https://support.atlassian.com in the 'JIRA Studio' project. Our support staff will schedule an appointment with you for an agreed upon time for your data to be imported. The data can be attached to the support case or (preferably) uploaded to the Studio WebDAV directory share.
Please note, we cannot import from a higher version of JIRA or Confluence than the version that is currently installed on JIRA Studio. Please see the JIRA Studio Application Versions page to view the current versions of JIRA and Confluence in Studio.
How do I enable issue and issue comment creation via email?
Studio is preconfigured to create comments on issues from email replies to issue notifications. Replies to the jira@youraccountname .jira.com address automatically become comments.
JIRA can further be configured to create issues from email, but requires some setup on your part and the final configuration done by Atlassian Support.
The typical arrangement is to have one email address/mailbox set up per project, eg. so any mail to [email protected] (for project X) becomes new issues or a comment on an existing issue. Studio does not provide custom mailboxes, so you would need to set these up yourself.
Once you have set up the mailbox(es) for incoming email, please file a ticket in our support system, and let us know:
The hostname of your mail server. The username and password of the account receiving emails to create issues from. The protocol (POP or IMAP) and whether to use SSL. The JIRA project to create issues in. The JIRA issue type that issues should be of. An email address we can forward unhandleable mail to. How to handle emails whose sender address is not known to Studio. The options are a) ignore the email, b) automatically create a Studio account for the sender, c) create the issue with a hardcoded reporter (see below).
Studio as a ticketing system
Companies sometimes wish to use Studio as a ticketing system, where external customers email the system, and those emails become issues which then get processed. This is a common way of using non-Studio JIRA, but usually does not work in Studio because of the per-user licensing.
For a ticketing system, typically one would configure JIRA to create a new user account for an email address it hasn't seen before. This new user account is used as the 'reporter' for the issue created from the associated email, and the notification scheme is configured such that the 'reporter' gets email notifications of subsequent comments and updates. In this way the email sender gets updates via email.
This doesn't work in Studio, because there is a fixed number of users licensed, and creating an unbounded number of users from email addresses would quickly exceed the license.
The best that can be done is for issues from unknown senders to be created with the 'reporter' set to a registered user, perhaps created for this purpose (eg. called supportuser). The original sender's email address will be recorded in the issue description. JIRA thus acts as a passive recorder of emails, and communication with the sender needs to be done outside of JIRA.
How can I migrate my content to and from other Atlassian applications?
If you wish to migrate data into JIRA Studio (from your other Atlassian applications or JIRA Studio trial) or from JIRA Studio (into your other Atlassian applications), you can find helpful information in the Guide To Migrating Content Between Editions support document.
Can I use a custom Elastic Bamboo image?
When you enable Bamboo for your JIRA Studio account, the Atlassian default image is used to create elastic agents to run your builds on. This means that all elastic agents will inherit capabilities from the default image.
If you want to use a custom Elastic Bamboo image, you can create one by following the instructions in the Bamboo documentation. However, please note that we do not support custom elastic images in JIRA Studio.
Maintaining your elastic image If you use a custom elastic image with your JIRA Studio instance, you will need to ensure that it is running the correct agent version. This means that you may need to periodically upgrade your image to match the Bamboo version in JIRA Studio, e.g. if JIRA Studio is running Bamboo 2.5.1, your agent version needs to be 2.5.1. You can view the Bamboo version running in JIRA Studio on the JIRA Studio Application Versions page. Using an EBS volume instead of a custom image For easier maintainability, you should use an EBS volume with the default Bamboo image rather than create your own custom image, as creating a custom image is not a trivial process. You do not need to update your image each time Studio's Bamboo version is upgraded if you use this method. You can read about EBS volumes and reasons for using them in the Bamboo documentation.
When will my JIRA Studio applications be upgraded?
We are committed to providing you with the latest versions of each of the JIRA Studio applications (i.e. JIRA, Confluence, FishEye, Crucible, Bamboo, Subversion). The upgrade process for each of the JIRA Studio applications will begin as soon as possible, after the equivalent version of the standalone application is released. However, it may take a few weeks for the application version to become available to you, as each application version must undergo rigorous testing first before we apply it to JIRA Studio.
We cannot delay the upgrade of any applications under any circumstances. Follow JIRA Studio on Twitter to keep up-to-date with system maintenance/upgrades. If you suspect that an application upgrade will create problems for you, please contact our support staff for assistance in mitigating any risks. You can contact our support staff by raising a ticket in our support system under the 'JIRA Studio Support' project.
Subversion is constantly asking users to re-authenticate and failing with the correct credentials
Certains user groups of Subversion may experience authentication issues such as this:
Authentication realm:
This may be due to a configuration issue on your Subversion permissions. Subversion clients require unnecessary read access on the root path.
To workaround this problem, ensure that a group which all Subversion users belong to (such as users) has read access to the root path. The permission from the root path will be inherited by your project folders. You can then revoke the read permission under each project. See also how to set default permissions for new projects.
The permission changes may require up to five minutes to take effect.
Can I change the look and feel of JIRA Studio?
JIRA Studio currently does not allow the modification or installation of themes. It is possible to modify the look and feel of some aspects of JIRA Studio, but changes may not apply to all applications, e.g. the colours of the links and headers in content can only be modified for JIRA in JIRA Studio. See Configuring the Appearance of JIRA Studio for further details.
Can I install my own plugins?
JIRA Studio comes with a set of pre-installed plugins, including third-party commercial plugins (e.g. Gliffy). Customers are not permitted to install new plugins or remove existing plugins. Pre-installed plugins that are not critical to JIRA Studio can be enabled and disabled by creating a support request, or by using the Universal Plugin Manager (Confluence plugins only).
Please read the JIRA Studio Plugin Policy for the list of installed plugins and instructions on how to request plugins.
Are alternative languages available for JIRA Studio?
JIRA Studio is currently only available in English.
Please check back for updates, as we expect future versions to be internationalised. For more detail, take a look at the feature request on our public issue tracking system.
Do you support SSL?
All JIRA Studio accounts are configured with SSL. You can choose whether you want to use the https (secure) or http (un-secure) URL for your installation. If you would like all logins to automatically redirect to SSL (https), you will need to create a new ticket at https://support.atlassian.com under the JIRA Studio project. As of JIRA Studio 2.4 all new instances enforce SSL by default
If you would like to use a custom domain name with SSL, please see this FAQ.
How do I request installation modifications?
The fastest way to request modifications is by creating a support request. If your request relates to installing/uninstalling or enabling/disabling plugins, please read this FAQ: Can I install my own plugins?
How do I enable Bamboo for JIRA Studio?
Bamboo is disabled by default in your JIRA Studio. If you want to use Bamboo in JIRA Studio, you must request for it to be enabled for your JIRA Studio account. You can do this via your administration console. Please see Getting Started with Bamboo in JIRA Studio for instructions.
Can I use JIRA Studio with Confluence Hosted?
If you are finding that JIRA Studio's tightly integrated development environment does not allow you enough freedom to theme and customise your wiki as you would like, you can consider using JIRA Studio together with Confluence Hosted as a web front-end. Confluence Hosted can be completely customised to the needs of the customer, including the use of custom themes, plugins and more.
The following section describes how Confluence Hosted can be implemented as a web front-end for your JIRA Studio instance. We recommend that you read this before requesting Confluence Hosted integration with your JIRA Studio instance.
In order to enable single sign-on between Confluence Hosted and Studio, Confluence Hosted uses Studio's Crowd for user and group management. Confluence Hosted and Studio must both be at the same domain name in order to achieve single sign-on; generally, a customer-provided domain name is preferred.
Note that there are some restrictions, mostly in regard to Studio's security requirements:
Two directories are created in Crowd, where Directory 1 is used by both services and Directory 2 is only used by Confluence Hosted. Studio: Dir1: read/write Confluence: Dir1: read-only Dir2: read/write Users that are to use both services should be created in Studio, whereas users that only need access to Confluence Hosted should be created in Confluence Hosted.
This configuration has the added benefit of allowing for a higher licensed user count in Confluence Hosted than in Studio, a factor that may be of value if you are planning to use Confluence Hosted as a public-facing website.
Requesting Confluence Hosted integration with your JIRA Studio instance To request Confluence Hosted integration with your Studio instance, please file a support request at http://support.atlassian.com. Please note that Crowd can only be configured by Atlassian support.
What remote APIs are supported in JIRA Studio?
JIRA Studio supports the remote APIs listed below. The JIRA Studio remote APIs are identical to the remote APIs shipped with the standalone version of these products.
JIRA — XML-RPC and SOAP APIs. Read more about the JIRA remote API. Confluence — XML-RPC and SOAP APIs. Read more about the Confluence remote API. FishEye — XML-RPC and REST APIs. Read more about the FishEye remote API
If you are having problems using these remote APIs, please raise a support request at https://support.atlassian.com under the JIRA Studio project.
How do I update JIRA issues via subversion commit messages?
If you are working with code, you can action issues in JIRA Studio via Subversion commit messages. By using particular keywords in your commit message, you can log work, add comments or change the status of an issue. This makes it easy for you to maintain any issues that are related to the code you are changing. Full details can be found here.
How are commit messages defined (for actioning issues)?
JIRA Studio allows you to action JIRA issues via commit messages. You can also customise the commit commands that can be used in commit messages (e.g. to action custom JIRA workflow events).
The formal syntax definition for commit messages is described below.
Formal Syntax Definition .------. v | >>----| svn-commit-message-line |-+--><
svn-commit-message-line: |---| non-issue-key-text |-+------+--newline--| | .------. | | v | | '----| trigger-message |-+--'
non-issue-key-text: Any text that doesn't contain an issue key.
trigger-message: .------. v | |-----
ignored-text: Any text that doesn't contain an issue key, or a # followed by a valid command name.
workflow-command: |--hash---
issue-comment: Any text that doesn't contain an issue key, or a # followed by a valid command name.
time-command: |--hash---time---| time-spec |---+------+--| '-| work-log-comment |-'
time-spec: A valid JIRA time specification, eg 2h, 1w.
work-log-comment: Any text that doesn't contain an issue key, or a # followed by a valid command name.
comment-command: |--hash---comment--| issue-comment |-----|
Can I import my existing data from an external system (Bugzilla, Trac)?
We are currently able to import data from existing JIRA installations and JIRA Hosted. However, data from third-party issue trackers (e.g. Bugzilla, Trac) need to be transformed into a CSV file that matches the format described here.
You can also request Confluence space imports from on-premises Confluence installations and Confluence Hosted as well as SVN dump imports.
For further information, please see Importing Data.
Can I use EBS volumes with Elastic Bamboo?
The Amazon Elastic Block Store (EBS) provides 'EBS volumes' which can attach to EC2 instances. EBS volumes (and the 'EBS snapshots' created from these volumes) provide persistent storage for your elastic instances.
If you have relatively static resources required for building your Bamboo Jobs (such as, source code checkouts and Maven repository artifacts), you can add these to an EBS volume. From this volume, you can create an EBS snapshot, which effectively records the 'state' of an EBS volume at a given point in time.
If you want to use an EBS volume, you can create one by following the instructions in the Bamboo documentation. You will also need to create a support ticket and attach your private key and certificate file. Our support team will copy these files to the EC2 directory of your JIRA Studio instance and configure Bamboo to use those files.
How do I create a backup copy of my Subversion repository? If you would like a local read-only mirror of the Studio-hosted Subversion repository, that can be done with the svnsync command. Eg.:
$ mkdir backupsvn $ svnadmin create backupsvn $ cat > backupsvn/hooks/pre-revprop-change << EOF #!/bin/sh EOF $ chmod +x backupsvn/hooks/pre-revprop-change $ svnsync init file://`pwd`/backupsvn https://
See this write-up for a full overview of the process.
If you find your sync is timing out after an hour or so, you may need to adjust the http-timeout setting in your SVN client as described here.
Can I change the global theme for the look and feel?
JIRA Studio currently does not allow modification or installation of themes.
It is possible to add a navigation sidebar to a set of wiki pages. It is also possible to modify the look and feel of some aspects of JIRA Studio, but changes may not apply to all applications, e.g. the colours of the links and headers in content can only be modified for JIRA in JIRA Studio. See Configuring the Appearance of JIRA Studio for further details.
How do I add Google Apps to JIRA Studio?
Thank you for your interest in Google Apps integration in JIRA Studio. This page contains up to date information on how to add Google Apps to your JIRA Studio experience.
On this page:
Does Google Apps integration cost extra? Which versions of Google Apps support JIRA Studio? Can I create user accounts in JIRA Studio 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 JIRA Studio customers How do you evaluate JIRA Studio with Google Apps integration? Can existing JIRA Studio 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 JIRA Studio just for some of them? (to limit cost of licenses) Can non-Google Apps users authenticate to JIRA Studio once I've migrated?
Does Google Apps integration cost extra?
No, it's available at no additional cost to every JIRA Studio customer (and evaluator).
Which versions of Google Apps support JIRA Studio?
JIRA Studio works with all versions of Google Apps.
Can I create user accounts in JIRA Studio for users who are not members of my Google Apps domain?
Yes. JIRA Studio enables you to provide access to clients, contacts, or remote workers who do not have access to your Google Apps domain, or who do not have a Google Apps account. See how to do this in: Managing Users with Google Apps Integration.
How do I get Google Apps pre-packaged?
New JIRA Studio customers can have Google Apps integration set up right from provisioning. Simply create a new JIRA Studio instance via the Google Apps Marketplace and enjoy Google Apps integration as soon as your JIRA Studio instance is live.
Upgrade process to Google Apps for existing JIRA Studio customers Note that this is not a trivial upgrade — you will need to merge the user accounts between systems. Your JIRA Studio service will depend on Google for user account management, chat, docs, etc. and will then appear in JIRA Studio. You can, of course, opt to not integrate Google Apps.
See Migrating to Google Apps for more information.
How do you evaluate JIRA Studio with Google Apps integration?
This can be done via the JIRA Studio listing on Google Apps Marketplace.
Can existing JIRA Studio evaluators enable Google Apps integration?
No. Existing evaluators can sign up for a new evaluation from Google Apps Marketplace if desired.
After migrating to Google Apps, can I change the history of my Subversion repository and issues?
(In other words, can we preserve the names of the owners of the tickets and revision authors after migration?)
Not at this stage. If a solution becomes available, we will update this page.
Is the number of users based on the number of Google Apps domain accounts, or can we enable JIRA Studio just for some of them? (to limit cost of licenses)
You don't need a JIRA Studio account for every Google Apps user, just your developers and collaborators. JIRA Studio Licensing provides further information.
Can non-Google Apps users authenticate to JIRA Studio once I've migrated?
Yes. JIRA Studio integration with Google Apps enables you to provide external users — remote workers, clients, contractors — log in ability to your Google Apps JIRA Studio instance. See how to do this in: Managing Users with Google Apps Integration. However, users who don't have a Google ID will not be able to access Google-specific features of the Google Apps Activity Bar. Google Apps features external users cannot access are: Chat and Google Docs.
Can I use Clover with JIRA Studio?
The Clover license is not included by JIRA Studio and the use of Clover with JIRA Studio is not supported.
How do I import Subversion data for a single JIRA Studio project?
The Subversion Importer in JIRA Studio overwrites any existing Subversion data for all projects, see Importing Versioned Data into Subversion. The Subversion importer cannot merge data into an existing repository.
If you want to import Subversion data for a single JIRA project, follow the instructions below.
1. Create the new project in JIRA Studio first. 2. Mirror your Studio Subversion repository locally. 3. Merge the new project data in, e.g.
$ cat newproj.svn.dump | svnadmin load --parent-dir NEWPROJ /path/to/my/studio/svn/
4. Create a new dump of this mirrored repository. 5. Use the Subversion Importer to upload it.
Alternatively, raise a support request and a Support Engineer will schedule a time to do it on your behalf.
How do I migrate from Visual SourceSafe to JIRA Studio?
To migrate from Visual SourceSafe to JIRA Studio, do the following:
1. Export your data from Visual SourceSafe, in the Subversion format. 2. Import the Subversion data to JIRA Studio.
How do I use Visual Studio to access code, and check in and check out source files?
You can use the Atlassian Connector for Visual Studio for this purpose.
Read the documentation and then download the Connector at the download page.
RELATED TOPICS How do I request support? How do I import Subversion data for a single JIRA Studio project?
Subscription and Account FAQ
Find answers to common questions about your JIRA Studio account and ordering JIRA Studio here.
Can I disable a user without deleting them? Can I import external data into JIRA Studio? How do I add a technical contact to my account? How do I end my subscription or evaluation? 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 JIRA Studio licensed? How is the user count of my account calculated? How do I reduce my user count? How long will it take to receive my JIRA Studio installation after placing the order? I would like to try Studio out before buying. How do I do that? What are the storage and bandwidth limits? What database will the JIRA Studio instance use? What domain name will my JIRA Studio service be on? Can I use my own domain name? What happens to my JIRA Studio instance when my account is cancelled? What is the minimum number of users allowable in an upgrade? What is the minimum term of service? What level of customization and control will I have over my JIRA Studio instance?
Have you read the other FAQs?
Don't know how to configure something in JIRA Studio? Try the Configuration and Administration FAQ. Don't know how to use something in JIRA Studio? Try the Usage FAQ.
Can I disable a user without deleting them?
You can disable a user by removing their ability to log into JIRA. In a default setup, you can do this by removing them from the 'users' and 'administrators' groups.
If you have a more complicated setup, you will need to determine what permissions to change by reading Managing Global Permissions in JIRA.
Disabled users do not count towards your licence, but will remain in the system.
RELATED TOPICS
Managing User Access Levels JIRA Studio Licensing
Can I import external data into JIRA Studio?
Yes, you can request data to be imported into your instance of JIRA Studio by filing a ticket in the 'JIRA Studio' project.
See the documentation on Importing Data for more information, including full instructions and a list of supported data formats.
How do I add a technical contact to my account?
You can add a technical contact person to your account at my.atlassian.com, by entering the person's email address in your hosted account details on the 'Licenses' page. Full instructions follow.
To add a technical contact to your account:
1. Sign in at my.atlassian.com. 2. Go to your 'Licenses' page. 3. Click the plus '+' sign next to your hosted account to expand the options for the account. 4. Click the 'Add' option next to 'Main Technical Contact'. 5. Enter your contact's email address and click 'Add'. 6. If the person has not yet signed up to my.atlassian.com, you will be prompted for more information. Enter the information and click ' Save'. The person will receive an email informing them that they have been automatically signed up at my.atlassian.com. The email will contain their username and password.
You can assign an unlimited number of technical contacts to your account. However, if you have a large number of contacts, you may wish to create a mail alias at your organisation to manage the list. We currently can't add technical contacts to Evaluation licenses. Adding a technical contact to my.atlassian.com does not automatically add the person as a user on your hosted system and does not affect the number of users in your account.
How do I end my subscription or evaluation?
To cancel your subscription to JIRA Studio (including evaluation accounts), please follow the instructions below:
1. Log in to your my.atlassian.com account. The 'My Account' page will display. JIRA Studio will be listed in the 'Hosted products' section. 2. Click the 'Manage' link for your JIRA Studio account. Your account management page will display. 3. Click the 'Cancel Subscription' link to request the cancellation of your account. Your account will be terminated at the end of the current billing cycle. Your credit card will not be charged again.
Re-activating your account Your JIRA Studio account data will be purged 30 days after you end your subscription. If you wish to reactivate your account after this date, the data will no longer be available to do so.
Screenshot: Cancel JIRA Studio Subscription
How do I get started with the Tempo Plugin?
The Tempo plugin requires time-tracking to be enabled in JIRA. Time-tracking is enabled by default, but if you have disabled it, you will need to re-enable it before using this plugin.
If you need help using the Tempo plugin, the Tempo website provides administration and user documentation:
Tempo Administration Documentation Tempo User Documentation
How do I upgrade my account, renew my license, change credit card details, etc?
JIRA Studio accounts are managed through your My Atlassian account. Go to http://my.atlassian.com to upgrade your account, renew your license, change your credit card details, update your personal information, etc.
More detailed instructions on upgrading your account are available below:
To upgrade your account,
1. Go to http://my.atlassian.com. 2. JIRA Studio will be listed in the Hosted Products section of the account information page that displays. Click the 'Manage' link. 3. Your account management page will display. Click the 'Upgrade' link, which will be displayed next to the 'Operations' link. 4. Select your preferred upgrade option from the desired dropdown list that displays, i.e. Developers or Collaborators (as per the screenshot below).
Screenshot: Studio Account Upgrade
How is JIRA Studio licensed?
JIRA Studio licensing is user-based. That is, the pricing for your JIRA Studio instance is determined by the number of users that you want to have access to it.
There are two different user access levels for licensing: Developer and Collaborator. Each user access level has a separate user count for your license and provides a different level of access to JIRA Studio. Full details can be found here.
How is the user count of my account calculated? How do I reduce my user count?
There are two user counts for your account, one for each of the user access levels: Developer and Collaborator.
You can view the user count on the JIRA Studio Administration Console. See the instructions on viewing your Account Information. This page will list the user counts of Developers and Collaborators for your account. The number of each user level of access purchased for your account is displayed, as well as the number currently being used.
You can assign Developer or Collaborator access to users with a direct JIRA Studio login, or to users who log in externally. This concept of external access applies to only customers who user JIRA Studio with Google Apps integration. An external user is a user — client, contact, remote worker — who does not have access to your company email domain, but who you allow to access your JIRA Studio integration with Google Apps.
External users assigned to Developer or Collaborator access level contribute toward your licensing user count.
How do I reduce the user count of my account?
If you have reached the user limit for one or both of the user account types for your account, you have a number of options available:
Change the user access level for some users — if you have only reached the user limit for one of your user access levels, you can change the user access level for those users. For example, if you have exceeded the number of developers allowable under your license, but have not exceeded your collaborator count, you could change some of your developers to collaborators. To make this change, read the instructions on changing a user's access level on the Managing User Access Levels page. De-activate some users — if you have reached the user limit for both of your user access levels, you can set the user access level as 'No Access'. This will remove the user from all user groups with login privileges. This also means that the user will no longer count against either your developer or your collaborator counts. To make this change, read the instructions on managing users and groups. Upgrade your account — if you do not wish to change user access levels for your users, or remove login privileges from any users, you may wish to consider upgrading your account to add more users. To make this change, read the instructions on upgrading your account
Please note that the 'contegix' and 'sysadmin' administrative accounts do not count towards your license total.
See the JIRA Studio Licensing page for further details.
How long will it take to receive my JIRA Studio installation after placing the order?
If you order using a credit card, your order will be processed immediately and provisioning will begin. Installation will be completed within 24 hours, after which, your installation details will be emailed to you.
If you select 'Pay Later' as your payment option, a quote/invoice will be mailed to you within 1-3 business days. After receipt of successful payment, we will prepare your server within 24 hours. Therefore, from the time you place your order to when you receive your credentials may take up to 4 business days (Australian time). With all orders, we'll send a quote/invoice via email. Once the instance has been setup, you will be sent an email with the installation information.
I would like to try Studio out before buying. How do I do that?
We currently offer free 30-day trials of JIRA Studio. If you choose to continue beyond your free trial, you can retain any data created during your trial period. Sign up for a free trial here.
What are the storage and bandwidth limits?
Available storage is calculated based on the number of users on your JIRA Studio account. Each user is allocated 15GB of storage which is shared between all users.
For example, if you have 10 users on your JIRA Studio account, you will have 150GB total storage which is shared between the 10 users.
Please note, there are no bandwidth limits.
What database will the JIRA Studio instance use?
All JIRA Studio instances run on the open source Postgres database.
What domain name will my JIRA Studio service be on? Can I use my own domain name?
Your JIRA Studio address will be at
If you wish to use your own domain name, you will need to create a new ticket at https://support.atlassian.com under the JIRA Studio project and supply your domain name. If you wish to use your domain name over https, you will also need to supply your SSL certificate in the support ticket.
Domain name changes are not available during the evaluation phase of JIRA Studio.
What happens to my JIRA Studio instance when my account is cancelled?
A note for customers re-directed to this page If you were trying to navigate to your JIRA Studio instance and were re-directed to this page instead, it is because your JIRA Studio service has been cancelled. Please refer to the information below for further instructions.
If your JIRA Studio service has been cancelled, either voluntarily by you or by the JIRA Studio team (e.g. for non-payment of account), your site will be removed. If you wish to re-enable your JIRA Studio service, please log into your account at http://my.atlassian.com and renew your license.
Your JIRA Studio account data will be deleted 30 days after you end your subscription. If you wish to reactivate your account after this date, the data will no longer be available to do so. If you have questions about the cancellation of your account, please contact us by email at [email protected].
What is the minimum number of users allowable in an upgrade?
JIRA Studio starts with a minimum purchase of five Developer users. You can then choose to add Collaborator users to your account and/or further Developer users. Please note that you must purchase the minimum five Developer users before you can add any Collaborator users to your account.
Further upgrades are available in pre-specified amounts, e.g. 5 users, 10 users, 15 users, etc. There is no maximum limit on the number of users you can upgrade to.
Please see the JIRA Studio pricing page for details on pricing. If you wish to purchase more developer and/or collaborator users for your account, please refer to the instructions in the account update FAQ
What is the minimum term of service?
The minimum term of service is one month. You can choose to renew on a month by month basis, or save money by purchasing a year in advance.
There is no maximum limit on the number of years in advance that you can purchase.
What level of customization and control will I have over my JIRA Studio instance?
JIRA Studio contains fully functional versions of JIRA, Confluence, FishEye, Crucible, and Subversion. However, in order to securely integrate these applications in a hosted environment, some of the functions that are available in the installable versions of the products are restricted in JIRA Studio. This means,
The function is pre-configured and cannot be altered by anyone, or, The function can only be configured by the Atlassian System Administrator - changes can be requested by filing a ticket at https://support.atlassian.com in the 'JIRA Studio' project.
See the full list of Restricted Functions in JIRA Studio.
Google Apps Integration FAQ
This page contains frequently asked questions and helpful information about using JIRA Studio with Google Apps Integration.
How do you evaluate or buy JIRA Studio with Google Apps integration?
This can be done via the JIRA Studio listing on Google Apps Marketplace.
Does Google Apps integration cost extra?
No, it's available at no additional cost to every JIRA Studio customer (and evaluator).
Which versions of Google Apps support JIRA Studio?
JIRA Studio works with all versions of Google Apps.
Can I create user accounts in JIRA Studio for users who are not members of my Google Apps domain?
Yes. JIRA Studio enables you to provide access to clients, contacts, or remote workers who do not have access to your Google Apps domain, or who do not have a Google Apps account. See how to do this in: Managing Users with Google Apps Integration.
How do I get Google Apps pre-packaged?
New JIRA Studio customers can have Google Apps integration set up right from provisioning. Simply create a new JIRA Studio instance via the Google Apps Marketplace and enjoy Google Apps integration as soon as your JIRA Studio instance is live.
Upgrade process to Google Apps for existing JIRA Studio customers
Note that this is not a trivial upgrade — you will need to merge the user accounts between systems. Your JIRA Studio service will depend on Google for user account management, chat, docs, etc. and will then appear in JIRA Studio. You can, of course, opt to not integrate Google Apps.
See Migrating to Google Apps for more information.
How do you evaluate JIRA Studio with Google Apps integration? This can be done via the JIRA Studio listing on Google Apps Marketplace.
Can existing JIRA Studio evaluators enable Google Apps integration?
No. Existing evaluators can sign up for a new evaluation from Google Apps Marketplace if desired.
After migrating to Google Apps, can I change the history of my Subversion repository and issues?
(In other words, can we preserve the names of the owners of the tickets and revision authors after migration?)
Not at this stage. If a solution becomes available, we will update this page.
Is the number of users based on the number of Google Apps domain accounts, or can we enable JIRA Studio just for some of them? (to limit cost of licenses)
You don't need a JIRA Studio account for every Google Apps user, just your developers and collaborators. JIRA Studio Licensing provides further information.
Can non-Google Apps users authenticate to JIRA Studio once I've migrated?
Yes. JIRA Studio integration with Google Apps enables you to provide external users — remote workers, clients, contractors — log in ability to your Google Apps JIRA Studio instance. See how to do this in: Managing Users with Google Apps Integration. However, users who don't have a Google ID will not be able to access Google-specific features of the Google Apps Activity Bar. Google Apps features external users cannot access are: Chat and Google Docs.
Deletion Policy for User Data
This page contains information on the deletion policy for JIRA Studio.
On this page:
What happens if I want to delete my JIRA Studio instance? Data retention Requesting a data export How to claim accounts How billing works
What happens if I want to delete my JIRA Studio instance?
If you cancel your JIRA Studio subscription, the system image and the data stored in it will eventually be deleted.
The events that occur during account cancellation are outlined below:
1. Cancel your subscription. Your JIRA Studio instance will remain active until the end of your final subscription period. 2. Once your subscription period is finished, your instance will be deactivated shortly afterward. 3. Once your instance is deactivated, Atlassian will retain your image and its data for 15 days. During this time, you can have your instance reactivated by renewing your subscription. 4. Once 15 days has elapsed after deactivation, Atlassian will delete the system image and all of its data. Once this is done, the data cannot be recovered.
Atlassian will not delete any of your data stored in Google Apps Marketplace, such as users or information in your Google Apps database, Google Docs, Gmail messages, Google Calendar entries, Google Chat, or Google Sites.
Data retention
Your data is retained for 15 days after deactivation. After that time, Atlassian will delete the system image and all of its data. Once this is done, the data cannot be recovered. See Data Backups for more information.
Requesting a data export
You can request an export of your data from the Atlassian support team. This can be done when your instance is active, or while it is deactivated. See Data Backups for more information.
Once your system image and its data have been deleted, that information cannot be retrieved.
How to claim accounts
Once your instance is deactivated, Atlassian will retain your image and its data for 15 days. During this time, you can have your instance reactivated by paying for a new subscription.
How billing works JIRA Studio fees are paid in advance, so when you deactivate your account, Atlassian will stop billing you immediately. Your JIRA Studio instance will remain active until the end of your final subscription period. Atlassian does not provide refunds for paid services.
JIRA Studio Application Versions
The following tables displays the current versions of the applications running in JIRA Studio. The tables also contain important information about the current version of the application running in JIRA Studio, i.e. which features of the standalone application version (listed in the release notes) are restricted or not available in JIRA Studio.
Please also see Restricted Functions in JIRA Studio for information on functions (all functions, not just the features listed in the current version's release notes) that are restricted in JIRA Studio.
When will my JIRA Studio applications be upgraded? We are committed to providing you with the latest versions of each of the JIRA Studio applications (i.e. JIRA, Confluence, FishEye, Crucible, Bamboo, Subversion). The upgrade process for each of the JIRA Studio applications will begin as soon as possible, after the equivalent version of the standalone application is released. However, it may take a few weeks for the application version to become available to you, as each application version must undergo rigorous testing first before we apply it to JIRA Studio.
We cannot delay the upgrade of any applications under any circumstances. Follow JIRA Studio on Twitter to keep up-to-date with system maintenance/upgrades. If you suspect that an application upgrade will create problems for you, please contact our support staff for assistance in mitigating any risks. You can contact our support staff by raising a ticket in our support system under the 'JIRA Studio Support' project.
On this page:
Issues (JIRA) GreenHopper Wiki (Confluence) Source (FishEye) Reviews (Crucible) Builds (Bamboo) Repository (Subversion) Single Sign-on (Crowd)
Issues (JIRA)
JIRA Studio Version: JIRA 4.3.1 (View JIRA 4.3 Release Notes)
Last Updated In? JIRA Studio May 2011 release
GreenHopper
JIRA Studio Version: GreenHopper 5.6.1 (View GreenHopper 5.6 Release Notes)
Last Updated In? JIRA Studio May 2011 release
Wiki (Confluence)
JIRA Studio Version: Confluence 3.5.3 (View Confluence 3.5 Release Notes)
Last Updated In? JIRA Studio May 2011 release
Source (FishEye)
JIRA Studio Version: FishEye 2.5.4 (View FishEye 2.5 Release Notes)
Last Updated In? JIRA Studio May 2011 release
Reviews (Crucible)
JIRA Studio Version: Crucible 2.5.4 (View Crucible 2.5 Release Notes)
Last Updated In? JIRA Studio May 2011 release
Builds (Bamboo) JIRA Studio Version: Bamboo 2.6.5 (View Bamboo 2.6.3 Release Notes — effectively the same as Bamboo 2.6.5)
Last Updated In? JIRA Studio April 2011 release
Notes: N/A
Repository (Subversion)
JIRA Studio Version: Subversion 1.6.6 (View Subversion Project Home)
Last Updated In? JIRA Studio 2.3.2
Notes: N/A
Single Sign-on (Crowd)
JIRA Studio Version: Crowd 2.2 (View Crowd 2.2.2 Release Notes — effectively the same as Crowd 2.2)
Last Updated In? JIRA Studio April 2011 release
JIRA Studio Licensing
JIRA Studio licensing is user-based. This means the pricing for your JIRA Studio instance is determined by the number of users that you want to have access to it.
There are two different user access levels for licensing: Developer and Collaborator. Each user account type has a separate user count for your license and provides a different level of access to JIRA Studio.
The sections below describe the differences between these two user account types and how to purchase and configure them.
On this page:
What can Developers and Collaborators access? What are the differences in pricing between Developer and Collaborator access levels? How do I change a user from a Developer to a Collaborator (and vice versa)? How do I calculate the user count for my account? How do I reduce the user count of my account?
What can Developers and Collaborators access?
Developers have complete access to JIRA Studio functionality.
Collaborators are not able to:
Create Projects in JIRA Studio. See the 'Source,' 'Review or 'Builds' application tabs in JIRA Studio. Access your Subversion repository, which means that they cannot commit code.
Users assigned a No Access level cannot access JIRA Studio.
Access JIRA Confluence FishEye Crucible Bamboo Subversion Level (Issues) (Wiki) (Source) (Reviews) (Builds) (Repository)
Developer
Collaborator
No Access
— has complete user access to the application. — has restricted access to the application. — cannot access the application.
What are the differences in pricing between Developer and Collaborator access levels?
Collaborator and Developer user access levels are priced separately, as they allow different levels of access to JIRA Studio.
JIRA Studio starts with a minimum purchase of five Developer users. You can then choose to add Collaborator users to your account and/or further Developer users. Please note that you must purchase the minimum five Developer users before you can add any Collaborator users to your account.
Further upgrades are available in pre-specified amounts, e.g. 5 users, 10 users, 15 users, etc. There is no maximum limit on the number of users you can upgrade to.
Please see the JIRA Studio pricing page for details on pricing. If you wish to purchase more developer and/or collaborator users for your account, please refer to the instructions in the account update FAQ
How do I change a user from a Developer to a Collaborator (and vice versa)?
You specify a user's access level when you create their account. You can also change their user access level. Please see the Managing User Access Levels page for instructions on how to change a user from a Developer to a Collaborator, and vice versa.
How do I calculate the user count for my account?
You can view the user count on the JIRA Studio Administration Console. See the instructions on viewing your Account Information. This page will list the user counts of Developers and Collaborators for your account. The number of each user level of access purchased for your account is displayed, as well as the number currently being used.
You can assign Developer or Collaborator access to users with a direct JIRA Studio login, or to users who log in externally. This concept of external access applies to only customers who user JIRA Studio with Google Apps integration. An external user is a user — client, contact, remote worker — who does not have access to your company email domain, but who you allow to access your JIRA Studio integration with Google Apps.
External users assigned to Developer or Collaborator access level contribute toward your licensing user count.
How do I reduce the user count of my account?
If you have reached the user limit for one or both of the user account types for your account, you have a number of options available:
Change the user access level for some users — if you have only reached the user limit for one of your user access levels, you can change the user access level for those users. For example, if you have exceeded the number of developers allowable under your license, but have not exceeded your collaborator count, you could change some of your developers to collaborators. To make this change, read the instructions on changing a user's access level on the Managing User Access Levels page. De-activate some users — if you have reached the user limit for both of your user access levels, you can set the user access level as 'No Access'. This will remove the user from all user groups with login privileges. This also means that the user will no longer count against either your developer or your collaborator counts. To make this change, read the instructions on managing users and groups. Upgrade your account — if you do not wish to change user access levels for your users, or remove login privileges from any users, you may wish to consider upgrading your account to add more users. To make this change, read the instructions on upgrading your account
Please note that the 'contegix' and 'sysadmin' administrative accounts do not count towards your license total.
JIRA Studio Plugin Policy
JIRA Studio comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existing plugins. However, JIRA Studio will consider bundling future plugins based on customer interest and JIRA Studio compatibility. JIRA Studio's Third-Party Plugin Process outlines to plugin developers the process of adding plugins to JIRA Studio. Customers can vote on plugins they would like bundled with JIRA Studio.
On this page:
Commercial Plugins Hosted Commercial Plugins Direct Purchase Commercial Plugins Bundled Plugins Issues (JIRA) Wiki (Confluence) Builds (Bamboo) Reviews (Crucible)
Commercial Plugins
The following third-party plugins are available in JIRA Studio under commercial licenses. This means that the plugins are installed in JIRA Studio, however, you need to purchase the relevant third-party license for each plugin to use it.
Hosted Commercial Plugins
The following plugins are available under Atlassian's Hosted Commercial Add-ons program. You may order licenses for these products by logging into your account at http://my.atlassian.com and selecting 'Configure' next to your Studio account. Please see this page for more ordering information.
Please note that for these plugins, the license term must match that of the Studio account (for example, monthly for monthly), and the number of licensed users must be equal to or greater than the number of licensed Studio users (Developers + Collaborators).
The Balsamiq Mockups for JIRA Studio, includes both JIRA and Confluence Plugins. A 30-day trial for Balsamiq (JIRA and Confluence) is enabled as part of the 30-day trial of JIRA Studio, after which you must purchase a license for it. Balsamiq Mockups for JIRA Balsamiq Mockups for Confluence The Gliffy Plugin for JIRA Studio, includes both JIRA and Confluence Plugins. A 45-day trial for Gliffy (JIRA and Confluence) is enabled as part of the 30-day trial of JIRA Studio, after which you must purchase a license for it. Gliffy Plugin for JIRA Gliffy Plugin for Confluence
Direct Purchase Commercial Plugins
Licenses for the following products must be purchased directly from the plugin vendor. See the individual products below for more information.
The Tempo Plugin for JIRA. This plugin enables you to track time using JIRA. A 30-day trial for Tempo is enabled as part of the 30-day trial of JIRA Studio, after which you must purchase a license for it. Further information on working with Tempo is available from this Tempo Plugin FAQ.
Bundled Plugins
Issues (JIRA)
The plugins listed below are installed on JIRA and enabled by default, unless specified below. You can enable/disable a plugin by raising a support request. If you want to request additional JIRA plugins, please see Third-Party Plugin Process.
FishEye for JIRA GreenHopper for JIRA Plugin JIRA Charting Plugin JIRA Labels Plugin JIRA Miscellaneous Workflow Extensions Plugin (disabled by default) JIRA Toolkit Plugin (disabled by default) JIRA Timesheet Plugin JIRA Wallboards Plugin Zendesk Notifier Plugin
Wiki (Confluence)
The plugins listed below are installed on Confluence and enabled by default, unless specified below. You can enable/disable a plugin by using the Universal Plugin Manager. If you want to request additional Confluence plugins, please see Third-Party Plugin Process.
Attachments Macro Blog Posts Macro Bookmarks Macro Calendar Plugin Change-History Macro Chart Macro Cheese Macro Children Display Macro Code Block Macro Color Text Macro Column Macro Content by Label Macro Content Formatting Plugin (disabled by default) Create Space Button Macro Excerpt Macro Excerpt Include Macro Favourite Pages Macro Gallery Macro Global Reports Macro IM Presence Macro Include Page Macro Info Macro JIRA Issues Macro JIRA Portlet Macro JUnit Report Macro
Livesearch Macro Loremipsum Macro Navmap Macro Noformat Macro Nolink and nl Macros Note Macro Office Connector Panel Macro Recently Updated Content Macro Recently Used Labels Macro Related Labels Macro Search Macro Section Macro Space Details Macro Spaces List Macro Table Plugin Tasklist Macro Tip Macro Userlister Macro Warning Macro Welcome Message Macro
Builds (Bamboo)
The [Auto-Favourite Plugin] is bundled with Bamboo and enabled by default.
If you want to request additional Bamboo plugins, please see Third-Party Plugin Process.
Reviews (Crucible)
While Crucible boasts a plugin API, we do not currently offer any plugins for Crucible.
Third-Party Plugin Process
JIRA Studio comes with a set of pre-defined plugins. Customers are not permitted to install new plugins or remove existing plugins.
Requests for additional plugins should be created as feature requests in the 'JIRA Studio' project on https://studio.atlassian.com. Plugins will be evaluated for compatibility with JIRA Studio and may be bundled in a future release.
For plugin vendors this means that any plugin you wish to be used with JIRA Studio needs to be tested against JIRA Studio, verified by the JIRA Studio team, and then added to a future release of JIRA Studio.
Getting commercial plugins verified for JIRA Studio
For vendors to verify a commercial plugin,
1. Create a feature request in the 'JIRA Studio' project on https://studio.atlassian.com, if one doesn't already exist. This will notify the team and product manager of the desire to bundle the plugin. 2. Create a support request in the 'JIRA Studio' project on http://support.atlassian.com to have the plugin installed on the Studio Plugin Testing instance, and have a user created with administrative access so you can test the plugin with JIRA Studio. 3. Once you verify that the plugin works with JIRA Studio, update the feature request on StAC to note that the plugin appears compatible. 4. The feature request will then be placed into the feature backlog for JIRA Studio development. We can not guarantee that any given plugin will be certified and bundled with a future release, but will prioritise bundling of future plugins based on customer interest. Plugin vendors who are seeing interest from customers should encourage these customers to vote on the feature request at StAC.
Unless otherwise stated, bundled third-party plugins are not considered "supported" by Atlassian, and support and future version compatibility is the responsibility of the vendor.
At this time, we have no plans to offer additional third-party commercial plugins for sale directly from the Atlassian website or order form.
Restricted Functions in JIRA Studio
JIRA Studio contains fully functional versions of JIRA, GreenHopper, Confluence, FishEye, Crucible, Bamboo and Subversion. However, in order to securely integrate these applications in a hosted environment, some of the functions that are available in the installable versions of the products are restricted in JIRA Studio. This means,
The function is pre-configured and cannot be altered by anyone, or, The function can only be configured by JIRA Studio Technical Support — changes can be requested by filing a ticket at https://support.atlassian.com under the 'JIRA Studio' project.
The functions that are restricted in JIRA Studio are listed below.
On this page:
JIRA Studio General JIRA GreenHopper Confluence FishEye and Crucible Bamboo Subversion
JIRA Studio General
Imports — Please read Importing Data for information on supported imports for JIRA Studio. Themes — Custom themes, look & feel, etc, are currently not supported. Plugins — JIRA Studio contains a number of popular plugins. Please read the JIRA Studio Plugin Policy for the list of supported plugins. Requests for additional plugins should be created as a feature request at https://studio.atlassian.com under the JIRA Studio project. Alternate Languages — Although we can install language packs for some of the apps, there's no full support for alternate languages except English(US) at the moment. Please follow JST-1434 for updates on this feature. Backups --- Refer our Data Backups policy.
JIRA
The following table lists all of the functions that are restricted in JIRA Studio, even to users with administrator permissions. The table also lists whether the function can be configured by JIRA Studio Technical Support on request (if not, then it is unavailable for configuration in JIRA Studio).
Restricted Configurable Notes Function on Request?
SMTP Mail NO JIRA Studio comes with an internal SMTP server configured to send notifications. server The [JIRA Studio] prefix is not configurable, as we need its presence to identify email replies to notifications (see JST-539).
POP/IMAP YES We can set up a JIRA service, on request, to use POP/IMAP mail servers to create issues and issue Mail servers comments in JIRA. Please read the documentation before filing a support ticket to request this feature.
Configure a NO Studio comes with Subversion hosting, and no external repositories are supported. CVS source code repository
Configure NO listeners
Configure NO services
Customising NO source files
Customising NO The procedure for customising email content sent in notification messages requires editing Velocity files email content within the JIRA webapp. This makes it a special case of "customising source files". See JST-1791 and JRA-7266 for feature requests to allow customisation of email contents through the web UI.
Change the NO index path
Run the NO integrity checker
Configure NO logging and profiling information
Access the NO scheduler
Export/backup YES Atlassian support will assist with generating a usable XML backups for standalone instances, only if you JIRA data to have a pending cancellation of a paid-subscription JIRA Studio account. Commercial customers can XML request an export by filing a ticket at https://support.atlassian.com.
Import/restore NO JIRA data from XML Import data NO from external systems (Bugzilla, Mantis, FogBugz)
Import data YES CSV imports can be requested by filing a ticket at https://support.atlassian.com. from external systems (CSV / Excel)
Import XML NO workflows into JIRA
Plugins NO Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins.
Plugin NO Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins. Repository
Disable NO Attachments enabled by default, maximum size set to 100MB. attachments, Set the attachment path or size limit
Enable NO trackbacks
Run Jelly NO Please see JST-1439 on the status. scripts
Configure NO LDAP integration
Configure NO trusted applications
Access NO license details
Modify NO SysAdmin users & attributes
Remote API YES This is already enabled by default. (XML-RPC, SOAP)
GreenHopper
All GreenHopper functions are available in JIRA Studio.
Confluence
The following table lists all of the functions that are restricted in JIRA Studio, even to users with administrator permissions. The table also lists whether the function can be configured by JIRA Studio Technical Support on request (if not, then it is unavailable for configuration in JIRA Studio).
Restricted Function Configurable on Notes Request?
General Configuration NO Public signup is managed via JIRA.
Server Base URL External user management Public Signup
Daily Backup Admin NO Backups are managed globally.
Plugins NO Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins. Plugin Repository NO Only default plugins are allowed. Please see JIRA Studio Plugin Policy for the list of supported plugins.
Mail Servers NO JIRA Studio comes with an internal SMTP server configured to send notifications.
User Macros NO
Attachment Storage NO Attachments enabled by default, maximum size set to 10MB.
Layouts NO As Studio's Confluence uses a custom theme, it is not possible to customise the layout.
Custom HTML NO
Backup & Restore Backup - YES Confluence exports can be requested by filing a ticket at Restore - NO https://support.atlassian.com.
SnipSnap Import NO
Logging and Profiling NO
Cluster Configuration NO
Remote API (XML-RPC, YES This is already enabled by default. SOAP)
FishEye and Crucible
A small set of administrative functions are available for FishEye and Crucible.
The administration consoles in the standalone versions of FishEye and Crucible are unavailable to JIRA Studio customers. We have configured the administration options for these applications to offer the greatest flexibility and security for our customers. To request changes to the default FishEye/Crucible configuration, please file a feature request at https://support.atlassian.com under the JIRA Studio project.
Please note, however, that the FishEye remote API (REST, XML-RPC) is available to JIRA Studio customers.
Bamboo
The following table lists all of the functions that are restricted in JIRA Studio, even to users with administrator permissions. The table also lists whether the function can be configured by JIRA Studio Technical Support on request (if not, then it is unavailable for configuration in JIRA Studio).
Restricted Configurable Notes Function on Request?
Configure NO Studio only runs builds using elastic agents. Hence, capabilities can only be configured by using a custom builders image.
Configure NO Studio only runs builds using elastic agents. Hence, capabilities can only be configured by using a custom JDKs image.
Configure NO Studio only runs builds using elastic agents. Hence, capabilities can only be configured by using a custom Server image. Capabilities
Support NO Due to its wide scope, support of customised elastic images is not provided. We recommend using the Custom default image with an EBS volume instead. You can customise the default image via scripts stored on your Elastic EBS snapshot during startup. Images
Plugin NO If you'd like to see a plugin supported, please submit a New Feature request here. Installation
Configure NO Bamboo users are managed via JIRA Studio's users and groups. Users
Configure NO Bamboo user groups are managed via JIRA Studio's users and groups. Groups
Configure NO Security Settings
Configure NO JIRA Studio comes with an internal SMTP server configured to send notifications. Mail Server
Database NO Configuration License NO Details
Indexing NO
Scheduled NO Backups
Export Data NO
Import Data NO
Subversion
While you can access many of the Subversion functions via the command line client, access to the administration console in Subversion is unavailable, meaning that functions like svnadmin dump and svnadmin load cannot be used.
Restricted Configurable Notes Function on Request?
Custom NO A pre-commit hook is available that requires a JIRA issue key. Custom hooks are not available at the Hooks moment due to reasons listed here. If you have suggestions on hooks you'd like to see in the future, please request the feature here.
Backups Full - Yes Subversion full exports can be requested by filing a ticket at https://support.atlassian.com. It's also possible to use svnsync to mirror the repository.
Support Policies
Welcome to the support policies index page. Here, you'll find information about how Atlassian Support can help you and how to get in touch with our helpful support engineers. Please choose the relevant page below to find out more.
Bug Fixing Policy How to Report a Security Issue New Features Policy Security Advisory Publishing Policy Security Update Policy Severity Levels for Security Issues Update Policy
To request support from Atlassian, please raise a support issue in our online support system. To do this, visit support.atlassian.com, log in (creating an account if need be) and create an issue under JIRA Studio. Our friendly support engineers will get right back to you with an answer.
Bug Fixing Policy
Summary
Atlassian Support will help with workarounds and bug reporting. Critical bugs will generally be fixed in the next maintenance release. Non critical bugs will be scheduled according to a variety of considerations.
Raising a Bug Report
Atlassian Support is eager and happy to help verify bugs — we take pride in it! Please open a support request in our support system providing as much information as possible about how to replicate the problem you are experiencing. We will replicate the bug to verify, then lodge the report for you. We'll also try to construct workarounds if they're possible.
Customers and plugin developers are also welcome to open bug reports on our issue tracking systems directly. Use http://jira.atlassian.com for the stand-alone products and http://studio.atlassian.com for JIRA Studio.
When raising a new bug, you should rate the priority of a bug according to our JIRA usage guidelines. Customers should watch a filed bug in order to receive e-mail notification when a "Fix Version" is scheduled for release.
How Atlassian Approaches Bug Fixing
Maintenance (bug fix) releases come out more frequently than major releases and attempt to target the most critical bugs affecting our customers. The notation for a maintenance release is the final number in the version (ie the 1 in 3.0.1). If a bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable to perform their normal functions) then it will be fixed in the next maintenance release provided that:
The fix is technically feasible (i.e. it doesn't require a major architectural change). It does not impact the quality or integrity of a product.
For non-critical bugs, the developer assigned to fixing bugs prioritises the non-critical bug according to these factors:
How many of our supported configurations are affected by the problem. Whether there is an effective workaround or patch. How difficult the issue is to fix. Whether many bugs in one area can be fixed at one time.
The developers responsible for bug fixing also monitor comments on existing bugs and new bugs submitted in JIRA, so you can provide feedback in this way. We give high priority consideration to security issues.
When considering the priority of a non-critical bug we try to determine a 'value' score for a bug which takes into account the severity of the bug from the customer's perspective, how prevalent the bug is and whether roadmap features may render the bug obsolete. We combine this with a complexity score (i.e. how difficult the bug is). These two dimensions are used when developers self serve from the bug pile.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
How to Report a Security Issue
Finding and Reporting a Security Vulnerability
If you find a security bug in the product, please open an issue on http://jira.atlassian.com in the relevant project.
Set the priority of the bug to 'Blocker'. Provide as much information on reproducing the bug as possible. Set the security level of the bug to 'Developer and Reporters only'.
All communication about the vulnerability should be performed through JIRA, so that Atlassian can keep track of the issue and get a patch out as soon as possible.
If you discover a security vulnerability, please attempt to create a test case that proves this vulnerability locally before opening either a bug or a support issue. When creating an issue, please include information on how the vulnerability can be reproduced; see http://confluence.atlassian.com/display/DOC/Bug+Fixing+Policy for general bug reporting guidelines. We will prioritise fixing the reported vulnerability if your report has information on how the vulnerability can be exploited.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
New Features Policy
Summary
We encourage and display customer comments and votes openly in our issue tracking systems, http://jira.atlassian.com and http://studio.atlassian.com. We do not publish roadmaps. Product Managers review our most popular voted issues on a regular basis. We schedule features based on a variety of factors. Our Atlassian Bug Fixing Policy is distinct from our Feature Request process. Atlassian provides consistent updates on the top 20 feature/improvement requests (in our issue tracker systems).
How to Track what Features are Being Implemented
When a new feature or improvement is scheduled, the 'fix-for' version will be indicated in the JIRA issue. This happens for the upcoming release only. We maintain roadmaps for more distant releases internally, but because these roadmaps are often pre-empted by changing customer demands, we do not publish them.
How Atlassian Chooses What to Implement
In every major release we aim to implement highly requested features, but it is not the only determining factor. Other factors include:
Direct feedback from face to face meetings with customers, and through our support and sales channels. Availability of staff to implement features. Impact of the proposed changes on the application and its underlying architecture. How well defined the requested feature is (some issues gain in popularity rapidly, allowing little time to plan their implementation). Our long-term strategic vision for the product.
How to Contribute to Feature Development
Influencing Atlassian's release cycle We encourage our customers to vote on feature requests in JIRA. The current tally of votes is available online in our issue tracking systems, http://jira.atlassian.com and http://studio.atlassian.com. Find out if your improvement request already exists. If it does, please vote for it. If you do not find it, create a new feature or improvement request online.
Extending Atlassian Products Atlassian products have powerful and flexible extension APIs. If you would like to see a particular feature implemented, it may be possible to develop the feature as a plugin. Documentation regarding the plugin APIs is available. Advice on extending either product may be available on the user mailing-lists, or at our community forums.
If you require significant customisations, you may wish to get in touch with our partners. They specialise in extending Atlassian products and can do this work for you. If you are interested, please contact us.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Security Advisory Publishing Policy
Publication of Security Advisories
When a security vulnerability in an Atlassian product is discovered and resolved, Atlassian will inform customers through the following mechanisms:
We will post a security advisory in the latest documentation of the affected product at the same time as releasing a fix for the vulnerability. This applies to all security advisories, including severity levels of critical, high, medium and low. We will send a copy of all security advisories to the 'Technical Alerts' mailing list for the product concerned. Note: To manage your email subscriptions and ensure you are on this list, please go to my.atlassian.com and click 'Email Prefs' near the top right of the page. If the person who reported the vulnerability wants to publish an advisory through some other agency, such as CERT, we will assist in the production of that advisory and link to it from our own.
Early warning of critical security vulnerabilities:
If the vulnerability is rated critical (see our criteria for setting severity levels) we will send an early warning to the 'Technical Alerts' mailing list approximately one week before releasing the fix. This early warning is in addition to the security advisory itself, described above. However, if the vulnerability is publicly known or being exploited, we will release the security advisory and patches as soon as possible, potentially without early warning.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Security Update Policy
When a security issue is discovered, Atlassian will endeavour to:
Add security fixes for the current release of a product (e.g. JIRA 4.0) to the next JIRA Studio update.
Visit our general JIRA Studio Update Policy as well.
As JIRA Studio is a hosted service, patches do not apply. Rather, the JIRA Studio system is upgraded regularly to incorporate recent updates to the component products that comprise the JIRA Studio suite, including patches for the individual Atlassian applications.
The development of JIRA Studio can be followed on our bug tracking system.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Severity Levels for Security Issues
Severity Levels
Atlassian security advisories include a severity level. This severity level is based on our self-calculated CVSS score for each specific vulnerability. CVSS is an industry standard vulnerability metric. You can learn more about CVSS at FIRST.org web site. CVSS scores are mapped into the following severity ratings:
Critical High Moderate Low
An approximate mapping guideline is as follows:
CVSS score range Severity in advisory
0 – 2.9 Low
3 – 5.9 Medium
6.0 – 7.9 High
8.0 – 10.0 Critical
Below is a summary of the factors which illustrate types of vulnerabilities usually resulting in a specific severity level. Please keep in mind that this rating does not take into account details of your installation.
Severity Level: Critical
Vulnerabilities that score in the Critical range usually include:
Exploitation of the vulnerability results in root-level compromise of servers or infrastructure devices. The information required in order to exploit the vulnerability, such as example code, is widely available to attackers. Exploitation is usually straightforward, in the sense that the attacker does not need any special authentication credentials or knowledge about individual victims, and does not need to persuade a target user, for example via social engineering, into performing any special functions.
For critical vulnerabilities, is advised that you patch or upgrade as soon as possible, unless you have other mitigating measures in place. For example, if your installation is not accessible from the Internet, this may be a mitigating factor.
Severity Level: High
Vulnerabilities that score in the High range usually have the following characteristics:
The vulnerability is difficult to exploit. Exploitation does not result in elevated privileges. Exploitation does not result in a significant data loss.
Severity Level: Moderate
Vulnerabilities that score in the Moderate range usually have the following characteristics:
Denial of service vulnerabilities that are difficult to set up. Exploits that require an attacker to reside on the same local network as the victim. Vulnerabilities that affect only nonstandard configurations or obscure applications. Vulnerabilities that require the attacker to manipulate individual victims via social engineering tactics. Vulnerabilities where exploitation provides only very limited access.
Severity Level: Low
Vulnerabilities in the Low range typically have very little impact on an organisation's business. Exploitation of such vulnerabilities usually requires local or physical system access.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Update Policy
If a problem has been fixed in an Atlassian application, provided that an update does not impact the quality or integrity of a product, Atlassian will ensure that patches for products are added to the next maintenance release.
As JIRA Studio is a hosted service, patches do not apply. Rather, the JIRA Studio system is upgraded regularly to incorporate recent updates to the component products that comprise the JIRA Studio suite, including patches for the individual Atlassian applications.
Updates for the component applications are issued under the following conditions:
The bug is critical (production application down or major malfunction causing business revenue loss or high numbers of staff unable to perform their normal functions). An update is technically feasible (i.e. it doesn't require a major architectural change). OR The issue is a security issue, and falls under our Security Policy. Atlassian does not provide updates for non-critical bugs.
The development of JIRA Studio can be followed on our bug tracking system.
Further reading
See How to Get Legendary Support from Atlassian for more support-related information.
Supported Platforms
This page describes the supported platforms for JIRA Studio.
Key: = Supported; = Not Supported; = Supported but not recommended or with restrictions;
Web Browsers Supported Versions
Microsoft Internet Explorer 8.0 7.0
Mozilla Firefox 3.6.x [1] 3.5.x 3.0.x
Safari 5.x [2] 4.x
Notes
1. If you use Firefox version 3.6, it is recommended that you use version 3.6.2 or above because of the data loss issue in Firefox 3.6.0. 2. Safari 5.x is not supported for Bamboo. As a result, you can use Safari 5.x if you do not use Bamboo. 3. Mobiles are still not supported.
End of Support Announcements for JIRA Studio
JIRA Studio is composed of individual applications that are integrated in a hosted environment. As such, the support for web browsers is subject to the end of support dates of the individual applications.
To find out the current application versions that are running in JIRA Studio, read the JIRA Studio Application Versions page.
The following section lists the End of Support pages for the individual applications.
Bamboo Crucible Confluence FishEye JIRA
JIRA Studio Resources
Resources for Evaluators
Free Trial Feature Tour
Resources for Administrators
JIRA Studio FAQ
Downloadable Documentation
JIRA Studio documentation in PDF, HTML or XML formats
Support Atlassian Support Support Policies
Training
Atlassian Training
News
JIRA Studio News JIRA Studio on Twitter
Forums
JIRA Studio Announcements JIRA Studio General Forum
Feature Requests
Issue Tracker and Feature Requests for JIRA Studio
JIRA Studio Release Notes
Latest Version Unable to render {include} Couldn't find a page to include called: _JIRA Studio New Release
Release Summary
For a summary of each major release of JIRA Studio, please see the JIRA Studio Release Summary. For full details on each of the JIRA Studio releases, please read the relevant release notes listed below.
Previous Releases
JIRA Studio Release Summary JIRA Studio May 2011 Release Notes JIRA Studio April 2011 Release Notes JIRA Studio 2.4 Release Notes JIRA Studio 2.3.1 Release Notes JIRA Studio 2.3 Release Notes JIRA Studio 2.2 Release Notes JIRA Studio 2.1 Release Notes JIRA Studio 2.0 Release Notes JIRA Studio 1.8 Release Notes JIRA Studio 1.7 Release Notes JIRA Studio 1.6 Release Notes JIRA Studio 1.5 Release Notes JIRA Studio 1.4 Release Notes JIRA Studio 1.3 Release Notes JIRA Studio 1.2 Release Notes JIRA Studio 1.1 Release Notes JIRA Studio 1.0 Release Notes
JIRA Studio Release Summary
This page lists release highlights of the major JIRA Studio releases since JIRA Studio 1.0.
Current Release
For information about the latest release, please visit the Release Notes.
JIRA Studio May 2011 — 6 May 2011
JIRA 4.3 GreenHopper 5.6 Confluence 3.5 FishEye/Crucible 2.5 Supported Platform Changes More details in the Release Notes
JIRA Studio April 2011 — 7 April 2011
Bamboo 2.6.5 Crowd 2.2
JIRA Studio 2.4 — 11 February 2011
JIRA 4.2 GreenHopper 5.4 Confluence 3.4 Subversion Importer More Bundled Plugins including the JIRA Wallboards Plugin Google Apps Change - Google Chat Removed More details in the Release Notes
JIRA Studio 2.3.1 — 31 October 2010
This release includes improvements and fixes, and component upgrades for:
GreenHopper upgraded to 5.2.4 Improvements to how JIRA Studio manages Google Apps external users More details in the Release Notes
JIRA Studio 2.3 — 27 September 2010
This release includes major component upgrades for:
GreenHopper upgraded to 5.2 Confluence upgraded to 3.3 Support for External Users in JIRA Studio with Google Apps Bamboo 2.6 supports up to 100 Remote Agents More details in the Release Notes
JIRA Studio 2.2 — 28 June 2010
This release includes major component upgrades for:
JIRA upgraded to 4.1.1 Crucible upgraded to 2.2.4 FishEye upgraded to 2.2.4 GreenHopper upgraded to 4.4.1 Confluence upgraded to 3.1.2 JIRA Quick-Add Feature for Google Apps Integration More details in the Release Notes
JIRA Studio 2.1 — 10 March 2010
Integration with Google Apps for Business. New collaboration platform Activity Bar interface Google Docs in Confluence wiki pages Google Docs in JIRA issues Advanced user management and single sign on Confluence upgraded to 3.1 JIRA upgraded to 4.0.1 Updates to review permission schemes JIRA comments from email functionality restored More details in the Release Notes
JIRA Studio 2.0 — 14 December 2009
JIRA upgraded to 4.0 GreenHopper upgraded to 4.2 Bamboo upgraded to 2.4 Repository Manager Improvements and Fixes Subversion upgraded to 1.6 More details in the Release Notes
JIRA Studio 1.8 — 13 July 2009
Confluence upgraded to 3.0 Commit Permissions for Subversion Directories Trac Imports Commercial Plugin Program - Balsamiq for JIRA More details in the Release Notes
JIRA Studio 1.7 — 20 April 2009
Global Administration Console Global and Default Tab Configuration Default Space Permissions Navigation Sidebar More details in the Release Notes
JIRA Studio 1.6 — 2 March 2009
Activity Stream Comments Activity Stream for Multiple Projects Activity Stream for Multiple Users FishEye and Crucible upgraded to 1.6. More details in the Release Notes
JIRA Studio 1.5 — 8 December 2008
Close Issues & Track Time via SVN Commit Messages QuickNav and Other Search Improvements Confluence upgraded to 2.10 Create Issues and Issue Comments via Email Commercial Plugin Program - Balsamiq for Confluence More details in the Release Notes
JIRA Studio 1.4 — 6 October 2008
Projects Toolbar Upgrade - Improved Layout and Global History Projects Toolbar Upgrade - Customisable Tabs JIRA upgraded to 3.13 Commercial Plugin Program - Greenhopper for JIRA Free WebDAV Directory More details in the Release Notes
JIRA Studio 1.3 — 8 September 2008
New licensing model Confluence upgraded to 2.9 Changes to Look and Feel customisation More details are in the Release Notes
JIRA Studio 1.2 — 6 July 2008
Confluence upgraded to version 2.8 JIRA Studio-wide search Performance improvements to Source (FishEye) and Review (Crucible) Commercial Plugin Program More details in the Release Notes
JIRA Studio 1.1 — 11 May 2008
Subversion Repository Manager More details in the Release Notes
JIRA Studio 1.0 — 18 March 2008
JIRA Studio launches Streams Projects Toolbar Linking More details the Release Notes
JIRA Studio May 2011 Release Notes
6 May 2011
The Atlassian JIRA Studio team is proud to announce that the May 2011 release of JIRA Studio will be available this weekend. The highlights of this release are the upgrades to JIRA 4.3, GreenHopper 5.6, Confluence 3.5, and FishEye/Crucible 2.5. These upgrades bring a host of new features to JIRA Studio including the Universal Plugin Manager in JIRA, improved quick filters for GreenHopper and the Share functionality in Confluence. Read below for details of these upgrades and enhancements.
Highlights of this release:
JIRA 4.3 GreenHopper 5.6 Confluence 3.5 FishEye/Crucible 2.5 Supported Platform Changes Updates and Fixes in this Release
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of JIRA Studio May 2011
JIRA 4.3
JIRA has been upgraded from 4.2 to 4.3. The highlight of this upgrade is the introduction of the Universal Plugin Manager (UPM) for JIRA. JIRA Studio administrators can enable and disable a range of pre-installed plugins, without having to request assistance from support. The JIRA 4.3 features available in JIRA Studio are:
Universal Plugin Manager (UPM) for JIRA. For information about how to use UPM in JIRA Studio, see Configuring JIRA Plugins in JIRA Studio. New Functions and Operators for JQL Security Enhancements, including password protection when users change emails and when administrators perform administration tasks. Note that the external URL 'Whitelist' feature does not apply to JIRA Studio. Dashboard Performance Improvements Revamped User Avatars Improvements to Issue Links Remembered Assignees REST API Improvements
Note, if a standalone JIRA 4.3 feature is not listed above, it is not part of JIRA 4.3 in JIRA Studio.
Click the 'Issues' tab in your JIRA Studio instance to start using JIRA. To learn more about the new features, read the JIRA 4.3 Release Notes. Screenshot above: JIRA UPM in JIRA Studio
GreenHopper 5.6
GreenHopper has been upgraded from 5.4.1 to 5.6. Versions 5.5 and 5.6 offer a number of features that can be used in JIRA Studio, e.g. a new wallboard for your task Board and improved inline field editing.
GreenHopper 5.5
GreenHopper 5.5 provides a new wallboard to display your task board in high-contrast on an information radiator. Other features include:
Improved Quick Filters Removal of the JIRA iframe to improve usability
GreenHopper 5.6
GreenHopper 5.6 provides improved inline editing of text fields for cards. Other features include:
The two-line 'List' view Ability to filter versions by 'Unscheduled' on the Task Board
Note, 'More Language Packs' does not apply to JIRA Studio.
Click the 'Issues' tab then the 'Agile' sub-tab in your JIRA Studio instance to start using GreenHopper. To learn more about this upgrade, read the GreenHopper 5.5 Release Notes and GreenHopper 5.6 Release Notes. Screenshot above: GreenHopper Task Board Wallboard
Confluence 3.5
Confluence has been upgraded from Confluence 3.4.2 to 3.5. With version 3.5, you can share pages and blog posts by using the Share button, and you can also make use of the notification improvements to manage the incoming information.
Other features and enhancements include:
New options in the Code macro New macro to include multimedia files in pages
Note, if a standalone Confluence 3.5 feature is not listed above, it is not part of Confluence 3.5 in JIRA Studio.
Click the 'Wiki' tab in your JIRA Studio instance to start using Confluence. To learn more about this upgrade, read the Confluence 3.5 Release Notes.
Screenshot above: Sharing a page in Confluence
FishEye/Crucible 2.5
FishEye/Crucible has been upgraded from 2.2.7 to 2.5. See the sections below for information on this upgrade:
FishEye/Crucible 2.3
FishEye/Crucible 2.3 introduces Crucible Snippet reviews allowing you to perform ultra-lightweight, ad-hoc code reviews with zero configuration. Other features are:
Crucible Changeset Discussions Crucible Review Coverage report FishEye 'Aggregate' functions in EyeQL query language
FishEye/Crucible 2.4
FishEye/Crucible 2.4 provides a FishEye branch and tag selector and simplifies the Crucible process for adding changesets to Reviews. Other features are:
Crucible User Interface Improvements Crucible Snippets Tweaks FishEye Redesigned File History FishEye User Interface Improvements FishEye Performance Improvements
FishEye/Crucible 2.5
FishEye/Crucible 2.5 introduces a revamped FishEye search. Other features are:
Crucible Comment Notification Batching FishEye RSS Improvements
Note, if a standalone FishEye/Crucible 2.3, 2.4 or 2.5 feature is not listed above, it is not part of FishEye/Crucible 2.5 in JIRA Studio.
Click the 'Reviews' tab in your JIRA Studio instance to start using Crucible. To learn more about this upgrade, read the release notes:
FishEye 2.3 Release Notes | FishEye 2.4 Release Notes | FishEye 2.5 Release Notes Crucible 2.3 Release Notes | Crucible 2.4 Release Notes | Crucible 2.5 Release Notes
Screenshot above: FishEye Search in JIRA Studio
Supported Platform Changes
Starting from this release, Safari 4.x and Firefox 3.0.x are no longer supported. For the latest list of supported Web browsers, refer to the Supported Platforms page.
Updates and Fixes in this Release
JIRA Studio 2.5 includes the following updates and bug fixes:
JIRA Issues (7 issues) Type Key Summary Priority Status Resolution
JST-4547 Upgrade wallboards to 1.5.2 Fixed Resolved
JST-4534 Upgrade to Confluence 3.5.x Fixed Resolved
JST-4533 Upgrade to FishEye 2.5.4 Fixed Resolved
JST-3980 Upgrade Studio to JIRA 4.3 Fixed Resolved
Fisheye repository permissions link from the project management project page goes JST-3605 Fixed to wrong url Resolved
JST-3075 Bundle the New Code Macro plugin for Confluence Fixed Resolved
JST-3054 Display last login time in user browser Fixed Resolved
JIRA Studio April 2011 Release Notes
JIRA Studio versions will be identified by the month of release rather than version number, from this release onwards.
7 April 2011
The Atlassian JIRA Studio team is pleased to announce that the April 2011 release of JIRA Studio is available to customers. We have upgraded Bamboo and Crowd in this release, and implemented a number of minor bug fixes. Please read below for further details.
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Bamboo 2.6.5 Upgrade
We have upgraded Bamboo from 2.6.2 to 2.6.5-studio-1. Please take note, if you are using a custom elastic image for Bamboo.
Crowd 2.2 Upgrade
We have upgraded Crowd from 2.0.7 to 2.2. This upgrade should not affect you.
JIRA Studio 2.4 Release Notes
11 February 2011
The Atlassian JIRA Studio team is proud to announce that JIRA Studio 2.4 has been released and is available to customers. The highlights of this release are the upgrades to JIRA 4.2, GreenHopper 5.4 and Confluence 3.4. These upgrades bring a host of new features to JIRA Studio including handy popup dialog boxes for JIRA, keyboard shortcuts for GreenHopper and a Confluence plugin manager. We've also bundled a number of new plugins with this release. Please read below for details of these upgrades and enhancements.
Highlights of this release:
JIRA 4.2 GreenHopper 5.4 Confluence 3.4 Subversion Importer More Bundled Plugins including the JIRA Wallboards Plugin Google Apps Change - Google Chat Removed Updates and Fixes in this Release
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of JIRA Studio 2.4
JIRA 4.2
JIRA has been upgraded from 4.1.2 to 4.2. This version of JIRA is all about speed and flexibility. Highlights of JIRA 4.2 include:
Issues can be triaged directly from the Issue Navigator without having to open each issue. For the mouse-averse, the new 'Operations Dialog' box provides access to all menu options via the keyboard. Common actions and workflow operations are now accessible from convenient dialog boxes. Time-tracking has become much more flexible. You can now edit the Original Estimate and set the Remaining Estimate to zero when resolving an issue. You can also log work via workflow 'transition' screens. The 'Labels' plugin is bundled with JIRA. The labels dialog has a great new user interface. Also, email notifications are now optional when updating labels for an issue.
Click the 'Issues' tab in your JIRA Studio instance to start using JIRA 4.2. To learn more about this upgrade, read the JIRA 4.2 Release Notes.
Screenshot: Dialogs for Common Actions and Workflow Operations GreenHopper 5.4
GreenHopper has been upgraded from 5.2.4 to 5.4.1. Highlights of GreenHopper 5.3 and 5.4 include:
GreenHopper 5.3
GreenHopper 5.3 includes an improved set of keyboard shortcuts to complement JIRA's keyboard shortcuts. Other features include,
One-Click Wallboards Customisable Printing of Cards Configurable Card Background Colour
GreenHopper 5.4
GreenHopper 5.4 provides time-tracking analysis for the Hour Burndown Chart. Other features include,
Releases from the Task Board now respect the selected Context Improvements to Cumulative Flow Diagram gadget
Click the 'Issues' tab then the 'Agile' sub-tab in your JIRA Studio instance to start using GreenHopper 5.4. To learn more about this upgrade, read the GreenHopper 5.3 Release Notes and GreenHopper 5.4 Release Notes.
Screenshot: Time-tracking data for an hour burndown chart
Confluence 3.4
Confluence has been upgraded from Confluence 3.3.2 to 3.4.2. The highlight of this upgrade is the introduction of the Universal Plugin Manager for Confluence. JIRA Studio administrators will be able to enable and disable a range of pre-installed plugins. Other highlights of Confluence 3.4 include:
New keyboard shortcuts, Mac-friendly too. A keyboard shortcut dialog. Improved performance
Click the 'Wiki' tab in your JIRA Studio instance to start using Confluence 3.4. To learn more about this upgrade, read the Confluence 3.4 Release Notes.
Subversion Importer Administrators can now import full Subversion (SVN) repositories into JIRA Studio from SVN dump files, using the new Subversion Importer. The Subversion Importer preserves all historical information in your dump file on import. Zipped dump files can also be imported, if file size is a problem for you.
For more information, read Importing Versioned Data into Subversion.
Screenshot: Subversion Importer
More Bundled Plugins including the JIRA Wallboards Plugin
We've bundled a number of new plugins with this release. The most noteworthy of these is the JIRA Wallboards plugin. The JIRA Wallboards plugin turns your JIRA dashboard into an information radiator for your team. You can set up an information radiator in your team's workspace to provide a highly visible display of the team's progress.
In addition to the JIRA Wallboards plugin, you'll also be able to use the Zendesk, Timesheet, Misc Workflow Extensions and Suite Utilities plugins for JIRA, as well as the Calendar, Content Formatting and Table plugins for Confluence. Please note that not all of these plugins are enabled by default.
For more information, read the JIRA Studio Plugin Policy.
Screenshot: JIRA Wallboard Example Google Apps Change - Google Chat Removed
If you are using Google Apps with your JIRA Studio instance, you will notice that the chat functionality (using Google Talk) has been removed from the activity bar. Google Talk required the chat bar to be loaded through HTTP, rather than HTTPS, which often caused intrusive warning messages. The chat functionality is not used by many people, however if you are concerned by this change, please contact our support staff.
Updates and Fixes in this Release
JIRA Studio 2.4 includes the following updates and bug fixes:
JIRA Issues (70 issues) Type Key Summary Priority Status Resolution
JST-3974 iFrame Plugin Fixed Resolved
JIRA Labels upgrade task fails on 2.4 upgrade for instances having no tabs for the JST-3836 Fixed default screen Closed
JST-3830 Distorted UI in Tempo "Log Work" dialog Fixed Resolved
JST-3829 Tempo plugin dialog does not pick up issue key Fixed Resolved
Upgrade task that creates balsamiq editors group fails if the instance uses external JST-3804 Fixed crowd, blocking other upgrade tasks from being executed Resolved
JST-3769 Spike UAL/Applinks Compatibility Fixed Resolved
JST-3767 Review JIRA integration points Fixed Resolved JST-3764 Prepare 2.5 Development Branch Fixed Resolved
JST-3756 Application Links are created with incorrect protocol scheme Fixed Resolved
JST-3742 Upgrade FeCru to 2.2.7 Fixed Resolved
JST-3732 Failed test: TestJiraApplicationLinks.testCreateFisheyeApplicationLinkWithInvalidUrl() Fixed Resolved
JST-3713 Gapps doesn't load properly due to UserService being unavailable Fixed Resolved
JST-3712 ActivityStreams doesn't show changes made under the Wiki tab Fixed Resolved
JST-3709 ActivityStreams displays an error ".../cache/indexes" does not exists Fixed Resolved
JST-3699 Menu items for Attachment based plugins not visible Fixed Resolved
JST-3690 Flaky test: TestStreams.testFeedAvailable() Fixed Resolved
JST-3689 Flaky test: TestRepositoryManager.testDeletePath() Fixed Resolved
JST-3688 Update Pre-Release Studio Instances Fixed Resolved
Make sure all bundled third-party plugins are configured as "User-installed Plugins" in JST-3682 Fixed Confluence Resolved
SVN-Importer: Do not require that top-level directories contain trunk, tags and JST-3680 Fixed branches sub-directories Resolved
Navbar loads too many project avatar URLs too many times leading to poor JST-3673 Fixed performance Resolved
JST-3624 Confluence not starting properly Fixed Resolved
JST-3623 Upgrade Confluence to the latest 3.4.x Fixed Resolved
JST-3604 Disable crucible user list Fixed Resolved
JST-3547 GApps user synchronisation can fail leaving some users unable to log in Fixed Resolved
JST-3522 Upgrade to JIRA 4.2.2 Fixed Resolved
JST-3512 Failed test TestJiraApplicationLinks Fixed Resolved
JST-3489 log4j-properties.patch needs updating due to failure Fixed Resolved
JST-3482 SVN Import Plugin tested by Support Fixed Resolved
JST-3446 Do not hide the Studio search box just because no projects have been created Fixed Closed
JST-3437 IE 7 not showing "Create Review" or Edit Detail page correctly Fixed Resolved
JST-3408 Upgrade to JIRA 4.2 Fixed Resolved
JST-3403 Investigate stable JST Build Fixed Resolved JST-3401 Move all builds off HBAC to BEAC Fixed Resolved
JST-3400 Fix FishEye status update in IE Fixed Resolved
JST-3398 Release 2.4 Milestone - M4 Fixed Resolved
JST-3326 Change studio-bamboo's seraph-config.xml into a patch Fixed Resolved
JST-3320 Remove AUI overrides Fixed Resolved
JST-3288 Spike integrating JIRA 4.2 into Studio Fixed Resolved
JST-3285 Upgrade Studio Confluence to 3.4.2 Fixed Resolved
JST-3283 All plugins in the bundled plugins zip appear as system plugins in the UPM Fixed Resolved
As a Studio supporter, I would like to be able to add additional plugins to the UPM JST-3282 Fixed whitelist/blacklist Resolved
Whitelist plugins restricted admin can enable/disable (unless they are also JST-3276 Fixed blacklisted) Resolved
com.atlassian.agmp.integration-common-plugin does not have the plugin key JST-3272 Fixed populated in atlassian-plugin.xml Resolved
JST-3268 Stop mojo fails if maven.test.skip is set to true Fixed Resolved
Re-enable Confluence mailpage plugin if it was enabled before upgrade task 24 JST-3244 Fixed disabled it Resolved
JST-3236 Upgrade Crowd to 2.0.7 for AGMP Fixed Resolved
JST-3235 Unable to redeploy App in dev mode Fixed Resolved
JST-3218 As a customer admin, I should be able to enable/disable bundled plugins Fixed Resolved
JST-3217 Upgrade Crowd Version to 2.0.7 Fixed Resolved
JST-3216 Investigate new features/improvements in Confluence 3.4 Fixed Resolved
JST-3215 Update Confluence version to 3.4 Fixed Resolved
JST-3199 Some requests to / return cache cleared Fixed Resolved
JST-3187 Streams performance issue Fixed Resolved
JST-3170 Upgrade JIRA Initial data Fixed Resolved
JST-3130 Flaky test: TestDeveloperLicenseUserManagement Fixed Resolved
JST-3113 UPM in Confluence Fixed Resolved
JST-3110 Upgrade to Confluence 3.4 Fixed Resolved
JST-3103 Remove jira labels plugin Fixed Resolved JST-3096 Check and fix admin path mappings Fixed Resolved
JST-3049 Support for ZenDesk Plugin Fixed Resolved
JST-3010 Allow the use of the Confluence Page Gadget Fixed Resolved
JST-2934 Remove override of addOrRemoveFromFavourites on Confluence 3.4 upgrade Fixed Resolved
JST-2920 Streamline patch generation Fixed Resolved
JST-2783 Remove unnecessary vm change when upgrading to JIRA 4.2 Fixed Resolved
JST-2737 Automate update of the footer version number Fixed Resolved
JST-2627 Flaky test: TestBambooJiraAndFisheyeIntegration.setUp Fixed Resolved
JST-2544 Bundle JIRA Wallboard plugin Fixed Resolved
JST-2496 Security issue with HTML macros Fixed Resolved
JST-1328 Bundle the JIRA Calendar Plugin Fixed Resolved
JIRA Studio 2.3.1 Release Notes
31 October 2010
The Atlassian JIRA Studio team is pleased to announce that JIRA Studio 2.3.1 has been released and is available to customers. This point release upgrades GreenHopper to 5.2.4, and includes a number of improvements and fixes. Please read below for further details.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
GreenHopper 5.2.4 Upgrade
The GreenHopper 5.2.4 upgrade resolves interaction interaction problems in Internet Explorer 8 and Chrome 6 on Windows relating to drag and drop and double-clicking to switch between the card and list views.
To learn more about this upgrade, read the GreenHopper 5.2.4 Release Notes.
Updates and Fixes in this Release
JIRA Studio 2.3.1 includes the following updates and bug fixes:
JIRA Issues (19 issues) Type Key Summary Priority Status Resolution
JST-3061 Error when trying to change the logo via the Administration > General > Account tab Fixed Resolved
Edit General Configuration admin screen for Issues incorrectly turns off "User JST-3045 Fixed Searching By Full Name", disabling auto completion for user picker fields Resolved
JST-3031 Upgrade GreenHopper to 5.2.4 Fixed Resolved
External user login is not enabled for Google users converted to external users during JST-3018 Fixed synchronisation Resolved JST-3012 Bamboo "UncategorizedSQLException" errors when saving build results Fixed Resolved
Workflow with AssignToRoleMemberFunction fails with "java.lang.LinkageError: JST-3002 Fixed javax/servlet/http/HttpServletRequest" Resolved
JST-2996 Bundle Tempo plugin Fixed Resolved
The "Linked Users" section cannot be collapsed in the User Import page displayed JST-2994 Fixed after enabling Google Apps integration Resolved
JST-2993 Change the "Modify" button to "Export these users to your Google Apps Domain" link Fixed Resolved
Invalid indexing language value can prevent issue searching from returning the JST-2970 Fixed correct results Resolved
JST-2969 Move the "Needs Activation" label in the user browser to the "User Type" column Fixed Resolved
JST-2955 Custom favicon is not used on login/logout pages Fixed Resolved
JST-2949 Unchecking the "Use Logo as Favicon" checkbox is not saved correctly Fixed Resolved
JST-2922 Sporadic "ConcurrentModificationException" errors Fixed Resolved
Warn Google Apps instances without external users that the login UI changes when JST-2921 Fixed public sign up is enabled Resolved
JST-2898 Remove the Google login countdown timer Fixed Resolved
JST-2870 External users added to JIRA Studio can conflict with existing Google users Fixed Resolved
The "Edit" link generated by Google Documents macro is not compatible with the JST-2655 Fixed latest version of the Google document editor Resolved
JST-2321 Cosmetic issues in the project menu when viewing the wiki Fixed Resolved
JIRA Studio 2.3 Release Notes
27 September 2010
The Atlassian JIRA Studio team is proud to announce that JIRA Studio 2.3 has been released and is available to customers. The highlight of this release is that Google Apps customers can now provide access to external clients, contacts, or remote users. We've also included significant new version upgrades of other Atlassian components. The focus is on smoother, faster, and more intuitive product components. Please read below for details of these upgrades and enhancements.
Highlights of this release:
GreenHopper 5.2 Confluence 3.3 Support for External Users in JIRA Studio with Google Apps Bamboo 2.6 Other JIRA Studio Features
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of JIRA Studio 2.3 GreenHopper 5.2
GreenHopper has been upgraded from 4.4 to 5.2, so there are lots of changes to help you streamline your workflow. The new user interface in GreenHopper 5.0 is a significant upgrade for JIRA Studio customers working with agile project management capabilities.
GreenHopper 5.0
Working with GreenHopper is now simpler and faster. A revised User Interface addresses the most common customer request, namely that GreenHopper look and behave more like JIRA. Smart drag-and-drop allows you to place cards at an exact position within the pagination of the Planning Board, and inline editing is available in all views ('Summaries', 'Cards' and 'List'). Further, common actions — comment, assign, log work — are available via a drop-down on every card. Features you'll want to use immediately include:
Inline editing Dialogs Quick Filters Drag and drop pagination
GreenHopper 5.1
Improvements to the Planning Board mean you can now categorise Assignees and Components by Version Improvements to the Task Board enable you to categorise Version by Assignee
GreenHopper 5.2
Key GreenHopper 5.2 features available with this release of JIRA Studio include:
Cumulative Flow Diagrams Version release from the Task Board 'Done' column Quick issue creation via the 'Issue Type' legend
From the 'Issues' tab, click the 'Agile' dropdown in your JIRA Studio instance to start using GreenHopper 5.2. To learn more about these upgrades, read the GreenHopper 5.0 Release Notes, GreenHopper 5.1 Release Notes and GreenHopper 5.2 Release Notes.
Screenshot: The Updated GreenHopper User Interface
Confluence 3.3
Confluence 3.2 and 3.3 updates include a Page Gadget which enables you to display Confluence content in other applications, and the ability to autocomplete for macros and for inserting links. Confluence also provides closer JIRA integration and an even faster and simpler editor:
Watch a short overview video. Significant Confluence features you'll find in JIRA Studio during this upgrade include:
Confluence 3.2
Autocomplete for Inserting Links Autocomplete for Embedding Images and Documents A Link Browser that's Smarter, Smoother, Faster
Confluence 3.3
Confluence Page Gadget Autocomplete for Inserting Macros Property Panels for Links Property Panels for Images Manage Watchers Email Notifications for Network Activity and Blogs Blog Improvements Context-Sensitive Help Links
Click the 'Wiki' tab in your JIRA Studio instance to start using Confluence 3.3. To learn more about these upgrades, read the Confluence 3.3 Release Notes and Confluence 3.2 Release Notes.
Screenshot: Using the Confluence Page Gadget
Support for External Users in JIRA Studio with Google Apps
JIRA Studio now works the way you do. You may have 'external' users – clients, contacts, or remote workers — who do not have a Google ID, or have a different company email domain on Google. JIRA Studio customers who use Google Apps can now provide access to external users for development or collaboration purposes.
Screenshot: Providing Google Apps access to External users See Managing External Users with Google Apps Integration for more information on this feature.
Bamboo 2.6
Bamboo 2.6 now provides support for up to 100 Remote Agents. The Bamboo 2.6 features added to JIRA Studio during this upgrade include the following:
Support for up to 100 Elastic Agents Revamped Dashboard Pages and Other Usability Enhancements Automatically Managed Elastic Instances Grails Integration with Optional Clover Code Coverage Need to update an elastic image to work with this Bamboo upgrade in JIRA Studio? Have a look at our flowchart to help you out.
Click the 'Builds' tab in your JIRA Studio instance to start using Bamboo 2.6. To learn more about this upgrade, read the Bamboo 2.6 Release Notes.
Screenshot: The Upgraded Bamboo User Interface
Other JIRA Studio Features
You can now use your logo as your favicon. The JIRA Studio Documentation Theme enables you to display a left navigation panel and customise it with your own header, footer, and links. We've improved the security around how your projects are managed. Projects can now only be created and deleted by those with Developer access privileges. Gliffy (45 day) and Balsamiq (30 day) trials for JIRA are now enabled by default as part of the free 30-day trial of JIRA Studio. At the end of the trial period, you can purchase these products from within your Studio account.
Screenshot: Applying a Theme to a Space
See Applying a Theme to a Space for more information on this feature.
JIRA Studio 2.2 Release Notes
28 June 2010
JIRA Studio 2.2 has been released and is available to customers.
With this release, JIRA Studio 2.2 adds some major component upgrades, including JIRA 4.1.1, Crucible 2.2.4 and FishEye 2.2.4.
JIRA 4.1.1 offers all-new functionality for JIRA Studio, most notably a completely new look and feel for the 'View Issue' page.
Crucible 2.2.4 has substantial UI updates, along with major new functionality, such as iterative reviews, pre-commit patch reviews, 'no moderator' reviews, wizard-like review creation and a new "edit mode" for reviews which allows instant changes to review titles, content and metadata.
FishEye 2.2.4 also has substantial UI updates, as well as bringing some exciting new features such as side-by-side diff viewing and wiki markup rendering in commit messages.
This release also includes new version upgrades of other Atlassian components: GreenHopper 4.4.1, Confluence 3.1.2, Crowd 2.0.5 and patches for Confluence. These include security patches and updates.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release: JIRA 4.1.1 Crucible 2.2.4 FishEye 2.2.4 JIRA Quick-Add Feature for Google Apps Integration GreenHopper 4.4.1 Confluence 3.1.2
Highlights of JIRA Studio 2.2
JIRA 4.1.1
With the release of JIRA Studio 2.2, the team has incorporated JIRA 4.1.1. JIRA 4.1.1 covers 16 updates and improvements, including significant security fixes and a general hardening of the product from a security perspective.
The JIRA features added to JIRA Studio during this upgrade include the following:
New-look 'View Issue' interface Streamlined Keyboard Shortcuts Image Gallery ZIP Download of Attachments Actions Dropdown in Gadgets Bulk Move Components and Versions New-Look User Profile Manage Dashboards Manage Filters Time Tracking now accepts Fractions
Screenshot: JIRA 4.1.1
Read the Release Notes for more details about this upgrade.
Crucible 2.2.4
Crucible 2.2.4 offers a raft of new features compared with those previously available in JIRA Studio. Jumping from Crucible version 1.6.6 to 2.2.4, this upgrade brings dramatic improvements in Crucible's feature set and user interface.
The Crucible features added to JIRA Studio during this upgrade include the following:
Smart Pre-Commit (Patch) Support 'No Moderator' Reviews Wizard-Like Review Creation Edit Mode for Reviews Wiki Markup Rendering Progress Tracking Review Time Tracking Review History Dialog "Blockers" Reports Threaded Comments Iterative reviews New User Interface
Screenshot: Crucible 2.2.4
Click the 'Reviews' tab in your JIRA Studio instance to start using Crucible 2.2.4. To learn more about this upgrade, see the Release Notes.
FishEye 2.2.4
FishEye 2.2.4 offers a raft of new features compared with those previously available in JIRA Studio. Jumping from FishEye version 1.6.6 to 2.2.4, this upgrade brings a dramatic increase in FishEye's capability, interface and look-and-feel.
The FishEye features added to JIRA Studio during this upgrade include the following:
Enhanced Side-by-Side Diff View Mode Annotation Context Menu Code Copying Wiki Markup in Commit Messages Activity streams People statistics Favourites, bookmarks & saved search New user interface
Screenshot: FishEye 2.2.4
Click the 'Source' tab in your JIRA Studio instance to start using FishEye 2.2.4. To learn more about this upgrade, see the Release Notes.
JIRA Quick-Add Feature for Google Apps Integration
You can now add new issues right from the Actvity Bar in JIRA Studio, when using Google Apps integration. Simply click on the 'Issues Button', then click the plus sign. You'll be able to select a project and an issue type for rapid issue creation.
Screenshot: Click the 'Plus Sign' to Quick-Add Issues on the Activity Bar
Screenshot: Quick Add for Issues
See the documentation for more information on this feature.
GreenHopper 4.4.1
GreenHopper has been updated, adding a number of major new features such as 'jump from JIRA issue to the planning board', 'days remaining' gadget and marker handling enhancements. It also includes a round-up of security hardening features.
Screenshot: Jumping to the Planning Board from a JIRA Issue
To learn more about this upgrade, see the documentation.
Confluence 3.1.2
This release is a bug-fix roundup which solves a number of issues. This upgrade adds to the general stability and smooth functioning of your wiki instance. It also includes various security hardening features.
See the documentation to learn more.
Upgrade Notes: Please be aware that a number of JIRA upgrade tasks will have been run automatically for your JIRA Studio instance. These include:
Confluence Mailpage Plugin will be disabled The Confluence Mailpage Plugin will be disabled for anyone that previously had it enabled due to a security issue that has been discovered. A future version of JIRA Studio will contain a patched version of the plugin, and at that time customers will be able to submit a request to have it enabled.
JIRA Studio 2.1 Release Notes
10 March 2010
JIRA Studio 2.1 with Google Apps Integration has been released and is available to customers. We are proud to announce that we now support full integration with Google Apps for Business.
Google Apps is now integrated with Atlassian's application suite in exciting ways. You can attach Google Docs to issues and attach Google Docs to wiki pages. You can use Gmail, Google Calendar, Google Talk and Google Sites to collaborate seamlessly, with all the power and features of JIRA Studio at your fingertips.
JIRA Studio is the software-as-a-service solution from Atlassian, offering issues powered by the issue tracker JIRA, wiki pages powered by Confluence, source code reviews powered by Crucible and builds powered by Bamboo, along with industry standard version control with Subversion.
JIRA Studio 2.1 also includes the most recent release of the Atlassian enterprise wiki, Confluence 3.1. Confluence 3.1 has some dramatic new additions including gadget support, Office 2007 support, drag-and-drop for page attachments and improvements to the editing experience. Check out the wiki application in your JIRA Studio instance to start using the new features.
How do I get Google Apps integration on my JIRA Studio? Existing customers and evaluators, please see the FAQ page on how to migrate to the new features.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
New collaboration platform Activity Bar interface Google Docs in Confluence wiki pages Google Docs in JIRA issues Advanced user management and single sign on Confluence 3.1 JIRA 4.0.1 Updates to review permission schemes JIRA comments from email functionality restored
Highlights of JIRA Studio with Google Apps Integration
New collaboration platform
Google Apps and JIRA Studio are now tightly integrated. This effectively creates a brand new platform for development team workflow collaboration. JIRA Studio with Google Apps integration offers email, calendar, issue tracking, wiki, code reviews, continuous integration and source control, all rolled into a cohesive package. The following features are now available with a single click:
Chat with multiple users from inside Studio, See all recent activities from JIRA Studio, See all recent issues from JIRA Studio, See favourite pages from JIRA Studio, See outstanding reviews from JIRA Studio, See recent build activities from JIRA Studio, See unread Google Gmail messages, See upcoming events from Google Calendar, See recently edited Google Docs files, Access Google Sites with one click.
Activity Bar interface
The new Activity Bar forms a single persistent control panel for effortlessly loading information from the integrated applications and launching them inline. It also provides integrated chat via Google Talk.
Screenshot: The JIRA Studio Activity Bar for Google integration
To learn more about the Activity Bar, see the documentation.
Google Docs in Confluence wiki pages
With the new ability to attach Google Docs to wiki pages in JIRA Studio, the following exciting features become available:
Attach any Google document, presentation, or spreadsheet to a wiki page, Set document size and other constraints from macro parameters, Launch Google doc editor with one click, List Google Docs in a Wiki page, Macro will display all Google docs or filter by a doc type, folder, or label, View doc title, creator, created date, and last modified date, Edit or preview a document with one click.
Screenshot: Google Docs in a Confluence wiki page To learn more about Google Docs in JIRA Studio, see the documentation.
Google Docs in JIRA issues
With the ability to attach Google Docs to issues in JIRA Studio, these exciting features become available:
Browse Google Docs, preview and attach them, Only view those docs to which you have access, Attached docs are always up to date with most recent edits.
Screenshot: Google Docs attached to a JIRA issue
To learn more about Google Docs in JIRA Studio, see the documentation.
Advanced user management and single sign on
Easily import your user base from Google Apps, then manage them in bulk with new JIRA Studio administrator functions. When users sign into JIRA Studio, they are signed on to all the Atlassian applications and the Google Apps suite in one action.
Confluence 3.1
Confluence 3.1 is a significant upgrade and it's now available to you in JIRA Studio. With the Confluence 3.1 wiki, you can embed OpenSocial gadgets into pages, use drag-&-drop to quickly add attachments to a wiki page and enjoy full Office 2007 support. There are also a raft of small improvements to the user experience including smart fields in the Macro Browser and Rich Text Editor performance enhancements.
Read the Confluence 3.1 Release Notes for more details. Please also read the upgrade notes at the bottom of these release notes for important information about the upgrade tasks for your JIRA Studio instance.
JIRA 4.0.1 With the release of JIRA Studio 2.1, the team has incorporated JIRA 4.0.1. A point release of the award-winning issue tracker, JIRA 4.0.1 adds over 60 updates and improvements. These include performance and memory fixes. JIRA 4.0.1 is a generally faster and more resilient version of the product, which now powers JIRA Studio 2.1.
Read the JIRA 4.0.1 Release Notes for more details.
Updates to review permission schemes
With the release of JIRA Studio 2.1, administrators have more control over code review access. This is controlled via repository permissions:
If a user has read access to the repository, then they will have permissions to view code reviews in the respective Crucible project. If they have write access to the repository, then they have 'create review' permissions in Crucible. If anonymous read access is set in the repository, then all users will be able to view Crucible reviews.
The default repository permissions affect the default Crucible permissions.
Read the JIRA Issue for more information.
JIRA comments from email functionality restored
A bug that had inconvenienced a number of users has been solved with the release of JIRA Studio 2.1. The comments via email function, which had been unavailable, has now been fully restored.
Upgrade Notes:
1. Please be aware that a number of JIRA upgrade tasks will have been run automatically for your JIRA Studio instance. These include: Your repository permission settings will now affect your review permissions, affecting who can view and start reviews. See Point 2 on this page for more details. The default role permissions are the only allowed ones in Crucible. Please check your permissions after the upgrade. An upgrade task will create a new permission scheme for existing projects, applying the new permission schemes. JIRA Studio does not use path-based permissions.
JIRA Studio 2.0 Release Notes
14 December 2009
JIRA Studio 2.0 has been released and is available to customers.
We are proud to announce that JIRA Studio now includes Atlassian's biggest product release to date, JIRA 4.0. JIRA 4.0 has a host of improvements, including a revamped user interface. Check out the Issues application in your JIRA Studio instance to start using the new features.
We've also taken the opportunity to upgrade the GreenHopper plugin in JIRA Studio to version 4.2. You will now have even more tools at your disposal to manage your agile projects, including epics, Kanban support, multiple filters in contexts and more.
Finally, the application suite in JIRA Studio has also been expanded in this release to include Atlassian's popular continuous integration build tool, Bamboo. JIRA Studio's Bamboo lets you run your builds in the Amazon Elastic Compute Cloud (EC2) so you can scale your builds on demand to support your development team's needs.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
JIRA 4.0 GreenHopper 4.2 Bamboo 2.4 Repository Manager Improvements and Fixes Subversion 1.6
Highlights of JIRA Studio 2.0
JIRA 4.0
JIRA 4.0 is the biggest Atlassian product release to date and it's now available to you in JIRA Studio. Try searching for issues using JIRA query language (JQL), add some gadgets to your dashboard, check out the brand new user interface and more.
Read the JIRA 4.0 Release Notes for more details. Please also read the upgrade notes at the bottom of these release notes for important information about the upgrade tasks for your JIRA Studio instance. Please note that some features listed in the JIRA 4.0 Release Notes do not apply to JIRA Studio 2.0. Please see JIRA Studio Application Versions for further details. GreenHopper 4.2
We've also upgraded the GreenHopper plugin for JIRA in this release from GreenHopper 3.7 to 4.2. GreenHopper has been dramatically overhauled since GreenHopper 3.7. You can now use create epics, set up your Task Board for a Kanban project and use multiple saved filters in contexts to name a few of the improvements.
Read more the GreenHopper Release Notes for more details. Bamboo 2.4
Run your builds in JIRA Studio! JIRA Studio 2.0 now includes the Bamboo build tool. The JIRA Studio version of Bamboo allows you to run your builds in the Amazon Elastic Compute Cloud (EC2) giving you the flexibility to scale your builds in line with the demands of your development team.
Read more about Getting Started with Bamboo in JIRA Studio.
Repository Manager Improvements and Fixes
We've improved the user interface for the JIRA Studio repository manager in this release as well as fix a number of significant bugs (e.g. https://studio.atlassian.com/browse/JST-1959). Configuring path-level permissions should now be much more intuitive.
Read more about Configuring Repository Permissions for a Project. Subversion 1.6
Subversion has been upgraded to version 1.6 in this release.
Read more in the Subversion 1.6 release notes.
Upgrade Notes:
1. Please be aware that a number of JIRA upgrade tasks will have been run automatically for your JIRA Studio instance. These include: Calculating a resolution date for all resolved issues in your system — this is a new field that captures the date when an issue last entered into a 'Resolved' workflow state. Re-indexing your issues Converting saved filters to use JQL Converting existing portlets to gadgets 2. JIRA 4.0 introduces several changes that may break existing plugins. If you have custom plugin installed on your JIRA Studio instance, please ensure that it works correctly. If you are experiencing issues, raise a support ticket and our support team will assist. 3. Prior to JIRA 4.0, it was possible to create two statuses whose names differed only in case (e.g. 'Resolved' and 'RESOLVED'). If you upgrade to JIRA 4.0, this will lead to ambiguities. Consider this scenario: 1. You have defined two issue statuses in a project with names that differ only in case, ('In Progress (Services)' and 'IN PROGRESS (SERVICES)'), to use in different workflows. 2. At a point in time, 100 issues are assigned the first status of 'In Progress (Services)' and 50 issues are assigned the second status of 'IN PROGRESS (SERVICES)'. 3. You browse the project's issues. The 'Status Summary' will incorrectly show only one 'In Progress (Services)' status with either 100 or 50 issues (picked randomly). The issue totals in the other summaries (By Priority, etc) will also be incorrect, due to JIRA not recognising the statuses as distinct. Additionally, you will receive ambiguous results if you attempt to perform a search by name on the status in the Advanced Search (e.g. "Status = In Progress (Services)"). To resolve this issue, we recommend that you ensure that each issue status is distinct by renaming the duplicate statuses appropriately. You may also need to update any issue filters that you have set up.
JIRA Studio 1.8 Release Notes
13 July 2009
JIRA Studio 1.8 has been released and is available to customers.
The wiki application in JIRA Studio has been upgraded to Confluence 3.0 in this release. Confluence 3.0 is a major Confluence release that incorporates a number of new features and improvements, such as the new macro browser, the new user network and improvements to the rich text editor.
JIRA Studio 1.8 also includes path-level commit permissions for your Subversion repository. This powerful feature lets you override inherited permissions for a Subversion directory to grant or remove commit privileges from user groups.
We are happy to announce that we now support Trac imports on request. Just raise a ticket with our support team and we'll get your Trac projects up and running in JIRA Studio.
Finally, we have expanded our commercial plugin program in this release to include the popular Balsamiq for JIRA plugin for graphical mockups.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Confluence 3.0 Commit Permissions for Subversion Directories Trac Imports Commercial Plugin Program - Balsamiq for JIRA
Highlights of JIRA Studio 1.8
Confluence 3.0
Confluence 3.0 is one of the biggest releases that Atlassian has produced and it's now available in JIRA Studio. You will be able to take advantage of a host of new features in your JIRA Studio wiki, such as the new macro browser, the new user network and improvements to the rich text editor.
Read the Confluence 3.0 Release Notes for more details. Please note that some features listed in the Confluence 3.0 Release Notes do not apply to JIRA Studio 1.8. Please see JIRA Studio Application Versions for further details.
Commit Permissions for Subversion Directories
We have refined the repository permissions configuration in JIRA Studio 1.8. You can now set commit permissions for specific directories on your Subversion repository. These directory level commit permissions will override any commit permissions inherited from higher levels of the Subversion repository hierarchy.
Read more about Configuring Repository Permissions for a Project.
Trac Imports
You can now get your Trac issues, wiki and source data imported into your JIRA Studio instance by submitting a request to our support team.
Read more about importing data into JIRA Studio.
Commercial Plugin Program - Balsamiq for JIRA
The Balsamiq plugin for JIRA is now available in JIRA Studio under our commercial plugin program. You can request for this plugin to be enabled in your JIRA Studio instance, if you have the appropriate license.
Read more about the commercial plugin program in the JIRA Studio Plugin Policy page.
JIRA Studio 1.7 Release Notes
20 April 2009
JIRA Studio 1.7 has been released and is available to customers.
JIRA Studio contains a completely revamped administration console. Administrators should find it easier to manage each of the applications as well as the global settings in JIRA Studio. The administration changes also include a number of new administration functions, such as global and default configuration for tabs and default wiki space permissions.
Finally, the popular navigation sidebar from Atlassian's Confluence is now available as a wiki theme in JIRA Studio. This popular layout allows you to browse through a wiki space via an easy-to-use navigation tree.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Global Administration Console Global and Default Tab Configuration Default Space Permissions Navigation Sidebar
Highlights of JIRA Studio 1.7
Global Administration Console
We've completely overhauled the Administration interface in JIRA Studio 1.7. The new tab-based UI provides you with easy access to the JIRA Studio applications as well as global settings. The console also contains a number of new functions, such as global and default configuration for tabs (described below), default wiki space permissions (described below), review defaults, defect classifications and web statistics.
Read the JIRA Studio Administrator's Guide for more details.
Global and Default Tab Configuration
JIRA Studio already allows you to customise your application tabs for your projects. In this release, you can configure global tabs and default tabs as well. Global tabs are the application tabs that are displayed when no project is selected. Default tabs are the application tabs that are displayed for a project when it does not have a customised tab configuration.
Read more about configuring global and default application tabs.
Default Space Permissions
You can now set default space permissions for your wiki in JIRA Studio 1.7. These permissions are assigned to all newly created spaces. You can also administer the existing permissions for each of your spaces, via the same screen used to set the default space permissions.
Read more about configuring the default space permissions. Navigation Sidebar
The popular navigation sidebar from Atlassian's Confluence is now available in JIRA Studio. Choosing the new 'JIRA Studio Sidebar Theme' for your space will display a handy navigation tree on the left side of all pages in that space.
Read more about [adding a navigation sidebar].
JIRA Studio 1.6 Release Notes
2 March 2009
JIRA Studio 1.6 has been released and is available to customers.
It's all about the activity stream in this major release. You should notice a raft of new features, including the ability to make comments against updates in the activity stream. The activity stream can now also be configured to display updates from multiple projects and/or selected users.
We've spent time reworking the plumbing of the activity stream. You should notice a faster and more stable activity stream, whether you use it as a dashboard portlet or view it on your project or user profile pages.
Finally, we've upgraded a few of the Studio applications. The Source (FishEye) and Reviews (Crucible) applications in JIRA Studio have been upgraded to version 1.6. New features include search enhancements for Source, wiki page reviews and enhanced pre-commit reviews.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Activity Stream Comments Activity Stream for Multiple Projects Activity Stream for Multiple Users FishEye and Crucible Upgraded to 1.6
Highlights of JIRA Studio 1.6 Activity Stream Comments
The activity stream is a great informative tool, but now it is also a collaborative tool with the introduction of activity stream comments. If a user sees an update in the activity stream that they want to respond to, they can add a comment on the spot. Almost any update in the activity stream can be commented on, and the comment will be stored against the appropriate issue, wiki or review.
Read more about adding comments via the activity stream.
Activity Stream for Multiple Projects
If you need to keep up to date with multiple projects in JIRA Studio, the activity stream can now help you do so. The activity stream now allows the aggregation of updates across multiple projects via a simple configuration option.
Read more about configuring the activity stream.
Activity Stream for Multiple Users
Managing information is about filtering information as much as aggregating it. You can also configure the activity stream to restrict the updates to a specific set of users. For example, you may want to only see updates from the lead developer on a project in your activity stream.
Read more about configuring the activity stream.
FishEye and Crucible Upgraded to 1.6
The Source (FishEye) and Reviews (Crucible) applications in JIRA Studio have been upgraded to version 1.6, opening up a number of new features for you to use. These include search enhancements for source searching, wiki page reviews and enhanced pre-commit reviews.
Read more about the new features in the FishEye 1.6 Release Notes and Crucible 1.6 Release Notes. Please note that some features listed in the FishEye 1.6 Release Notes and Crucible 1.6 Release Notes do not apply to JIRA Studio 1.6, including Multiple Admin Users, Remote API Improvements and Perforce Performance Tweaks for FishEye 1.6, and Support for Non-FishEye Repositories, Shared File System Repositories, Multiple Admin Users and Expanded API for Crucible 1.6. JIRA Studio 1.5 Release Notes
8 December 2008
JIRA Studio 1.5 has been released and is available to customers.
We have made it easier for you to manage issues in this release, by integrating JIRA workflow with Subversion. Your developers will be able to resolve issues, comment on issues, and track time via SVN commit messages, without leaving their development environment. We've also provided more tools for your users to collaborate with, by adding issue and issue comment creation from email.
Searching in Studio has been greatly improved in JIRA Studio 1.5 as well. The new Search Quick Navigation (or QuickNav) suggests possible matches to you as you enter search criteria, making it even faster to find what you are looking for. Other changes include a simpler user interface for the search and speedier responses when searching your Source (FishEye).
JIRA Studio 1.5 includes the latest Confluence version — Confluence 2.10. You will have access to a number of new features and improvements for your wiki, including an improved rich text editor, enhanced macros, the popular Office connector, and a new widget connector that allows you to display videos, slide shows, twitter chats and more, on your wiki pages.
Finally, we've included a new plugin under our commercial plugin program in this release, the powerful Balsamiq for Confluence plugin for graphical mockups.
Free JIRA Studio trials If you have always wanted to try JIRA Studio, now is the time! We are offering free 30-day trials of JIRA Studio for a limited time. Experience the benefits of our development collaboration platform immediately, without paying a cent. Try it now!
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Close Issues & Track Time via SVN Commit Messages QuickNav and Other Search Improvements Confluence Upgraded to Version 2.10 Create Issues and Issue Comments via Email Commercial Plugin Program - Balsamiq for Confluence
Highlights of JIRA Studio 1.5
Close Issues & Track Time via SVN Commit Messages We've made it even easier for your developers to manage their issues and time tracking in this release, with the introduction of issue actions via SVN commit messages. The simple but powerful syntax allows you to log work against an issue, change the issue status and add comments.
Read more about actioning issues via commit messages. Please note, if you are using a custom JIRA workflow, you will need to configure the commit message syntax to allow workflow transitions via commit messages. Read the documentation on configuring commit commands for further details.
QuickNav and Other Search Improvements
The JIRA Studio Search is a frequently used tool and we've spent some time improving it in this release. The most noticeable change is the addition of a QuickNav feature. Search results will be automatically suggested to you, as you enter your search criteria, and any of these suggestions can be clicked to navigate directly to the result.
The application selector has been removed from the JIRA Studio Search, but please don't be alarmed! The search results page will now display up to five results for all applications, instead of for just your chosen application. You can still drill down for further matches for an application.
We've also gotten into the nuts and bolts of the Source (FishEye) search to improve the performance. It's now faster than ever to find the source code that you are looking for.
Read more about searching in JIRA Studio.
Confluence Upgraded to Version 2.10
The wiki application has been upgraded to Confluence version 2.10 in this release. Confluence 2.10 is a major release that includes a number of major improvements and new features. Office documents can now be viewed, imported into and embedded in Confluence with the Office Connector. Page editing has also been made easier with major improvements to the rich text editor.
The new widgets macro allows you to embed a range of popular audiovisual and collaborative tools into Confluence pages. The JIRA issues macro has had a facelift as well. You should notice a much more flexible and user friendly interface. Read more about Confluence 2.10. Please note that some of the points listed in the Confluence 2.10 release notes do not apply to this Studio upgrade, including 'New Quick Navigation Feature' (different from Studio QuickNav), '"Did You Mean" and Other Search Improvements', 'Stylesheets for Confluence Spaces', 'User and Group Management Enhanced', 'Cropping of Profile Pictures', 'Universal Wiki Converter now with SharePoint Import and More', 'Plugin Framework 2' and 'Engine Room and Developers' Community'.
Create Issues and Issue Comments via Email
We've added issue and issue comment creation via email in JIRA Studio. If you enable this feature, your users will be able to create issues and issue comments simply by sending an email to the email address for your Studio instance.
Read more about creating issues and issue comments via email.
Commercial Plugin Program — Balsamiq for Confluence
The Balsamiq plugin for Confluence is now available in JIRA Studio under our commercial licenses program. This means that you can request for this plugin to be enabled in your JIRA Studio instance, if you have the appropriate license.
Read more about the commercial plugin program in the JIRA Studio Plugin Policy page.
JIRA Studio 1.4 Release Notes
6 October 2008
JIRA Studio 1.4 has been released and is available to customers.
The projects toolbar in Studio has been overhauled in JIRA Studio 1.4. The new toolbar not only looks better, but it also incorporates some neat new features, such as global history and customisable tabs.
We've also upgraded the JIRA application to version 3.13 in this release. This major upgrade brings a host of new features and improvements to your issues application.
By popular request, we have included the Greenhopper for JIRA plugin under our commercial plugin program in this release. You can add a range of agile project management features to your issues application, if you have the appropriate Greenhopper license.
We have also made it easier for you to provide us with large files, like SVN dumps, by including a free WebDAV directory with your Studio account in this release.
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Projects Toolbar Upgrade - Improved Layout and Global History Projects Toolbar Upgrade - Customisable Tabs JIRA Upgraded to Version 3.13 Commercial Plugin Program - Greenhopper for JIRA Free WebDAV Directory
Highlights of JIRA Studio 1.4
Projects Toolbar Upgrade — Improved Layout and Global History
The projects toolbar has been given a facelift in Studio 1.4. We've made a number of changes to the layout, including changing the width of the toolbar, realigning the tabs, and moving controls into dropdowns, but you should just notice a cleaner interface with functions that are easier to find. You can now also access your global navigation history in Studio via the projects toolbar. You will be able to view the last twenty pages you have visited in any of the default Studio applications.
Read more about the using the projects toolbar.
Projects Toolbar Upgrade — Customisable Tabs
You can now customise the tabs for each of your projects to provide a more streamlined user experience. The default application tabs can be hidden or shown, and new custom tabs can be added to any project.
Read more about customising application tabs for your project.
JIRA Upgraded to Version 3.13
We've upgraded the JIRA application to version 3.13 in this release. This is a major JIRA upgrade, which includes popular features such as sharable dashboards and filters, favourite dashboards and filters, and editable active workflows.
Read more about JIRA 3.13. Please note that some of the points listed in the JIRA 3.13 release notes do not apply to this Studio upgrade, including 'Restoring projects', 'Personal licenses', 'Plugins' and 'Application improvements'.
Commercial Plugin Program — Greenhopper for JIRA
The Greenhopper plugin for JIRA is now available in JIRA Studio under our commercial licenses program. This means that you can request for this plugin to be enabled in your JIRA Studio instance, if you have the appropriate Greenhopper license.
Read more about the commercial plugin program in the JIRA Studio Plugin Policy page.
Free WebDAV Directory
Your JIRA Studio account now includes a free WebDAV directory. This allows administrators to easily provide us with big files, in relation to a support request or initial account setup. For example, a large database or SVN dump. Please note, this directory is not intended for general file storage.
Read more about uploading data via WebDAV. JIRA Studio 1.3 Release Notes
8 September 2008
JIRA Studio 1.3 has been released and is available to customers.
We have revised the licensing for JIRA Studio in this release. You should be able to cost your service more accurately with the new user-based model. Please refer to the documentation referenced below to ensure that you understand the changes.
In addition, we have recently upgraded the Confluence application to version 2.9. You should notice a number of significant improvements to your wiki. We also recently introduced colour scheme customisation to Studio, making it easier than ever to change the look and feel of your Studio instance.
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
New Licensing Model Confluence 2.9 Changes to Look and Feel Customisation
Highlights of JIRA Studio 1.3
New Licensing Model
JIRA Studio's user-based licensing now can allows you to select from two different user account types for licensing, Developer and Collaborator. Each user account type has a separate user count for your license. Developer user account types provide the same level of Studio access, as your current users. Collaborator account types provide a more restricted level of access to your Studio instance, but at a reduced price.
Read more about JIRA Studio Licensing. Confluence 2.9
The wiki (Confluence) application in JIRA Studio has been upgraded to Confluence version 2.9. This upgrade brings you an even richer set of functionality for your wiki, including improved menus and page ordering, and enhanced editing.
Read the release notes for the Confluence 2.9 standalone application for more details on the new features. Please note that the New Tutorial mentioned in the release notes is not included in this JIRA Studio upgrade. You can also read the updated wiki documentation in the JIRA Studio User's Guide.
Changes to Look and Feel Customisation
You can now change the colour scheme for a number of different features in your Studio instance. Configure the look and feel of your Studio-wide navbar, as well as customise the colours for content in your Issues application.
Read more about editing the colour scheme. JIRA Studio 1.2 Release Notes
6 July 2008
JIRA Studio 1.2 has been released and is available to customers.
We've upgraded the Confluence application to version 2.8 in this release bringing a range of user interface improvements and new features to your wiki.
Studio-wide Search has been introduced in JIRA Studio 1.2. Search all of your issues, wiki, source and reviews from one search page. There have also been significant performance improvements made to JIRA Studio, particularly in the Source and Reviews applications (i.e. FishEye and Crucible).
By popular request, we are also introducing a commercial plugin program in this release. Gliffy and Editgrid are the first third-party plugins now available in JIRA Studio for customers with licenses for these plugins, with more to come.
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
Highlights of this release:
Confluence upgraded to version 2.8 Studio-wide Search Performance Improvements Commercial Plugin Program
Highlights of JIRA Studio 1.2
Confluence upgraded to version 2.8
We've upgraded the Confluence application to version 2.8 in this release. You will notice a simplified and more user-friendly user interface, which places the functions you need at your fingertips. Other new features include page ordering, collapsible comments and multi-label filters.
Read more about Confluence 2.8. Studio-wide Search
The new Studio-wide search provides you with a birds-eye view of related information, by aggregating search results across applications and projects into a set of summary results. Find the information you need on a single page or drill down for more results from a specific application. Like the Streams and application links features, this can be a powerful tool for keeping on top of the information produced by your development team.
Read more about Searching in Studio.
Performance Improvements
We have made significant performance improvements to JIRA Studio in this release. In particular, you should notice big improvements to your Source and Review applications (i.e. FishEye and Crucible).
Commercial Plugin Program
A number of third-party plugins are now available in JIRA Studio under commercial licenses, including the popular Gliffy and EditGrid plugins. This means that you can request for these plugins to be enabled in your JIRA Studio instance, if you have a valid license for the relevant plugin.
Read more about the commercial plugin program in the JIRA Studio Plugin Policy page.
JIRA Studio 1.1 Release Notes
11 May 2008
JIRA Studio 1.1 has been released and is available to customers. This release introduces the much anticipated Subversion Repository Manager.
Please help us improve JIRA Studio by reporting any bugs and issues you find, in the JIRA Studio project at studio.atlassian.com.
What's New in JIRA Studio 1.1?
Subversion Repository Manager — The page Administering Permissions for the Repository does not exist. Read more about the Subversion Repository Manager.
Screenshot: 'Subversion Repository Manager'
JIRA Studio 1.0 Release Notes
18 March 2008 JIRA Studio has been launched into production!
JIRA Studio is a development collaboration platform designed to support software development teams of any size. Based on JIRA, the popular issue tracker and workflow management tool, JIRA Studio adds industry standard revision control, repository viewer, wiki, and code review, all in one seamless hosted experience.
Important Information
JIRA Studio Security Statement JIRA Studio Terms of Use JIRA Studio Privacy Policy
Highlights of JIRA Studio:
Streams Projects Toolbar Linking And much more!
Highlights of JIRA Studio
Streams
Streams keeps you in touch with your team, showing you who's up to what, and when. Streams brings together updates from the Wiki, Issues, source commits and code reviews, and displays them in a single time line. Read more about streams.
Projects Toolbar
JIRA Studio acts and feels like a single, integrated system, capable of managing multiple projects. The Projects Toolbar, available on every JIRA Studio page, lets you switch between your projects with only a couple of clicks.
Read more about using the Projects Toolbar. Linking
JIRA Studio allows you to link between your source, issues, wiki and reviews, so that you can quickly jump between applications for related information. Creating links is as simple as inserting the appropriately formatted text into your application. For example, you can link a source file to the JIRA issue by typing the filename into your JIRA issue, in the appropriate format.
Read more about creating links.
And much more!
To learn more about the features of JIRA Studio, take the tour or try it yourself by signing up for a free trial. Looking to get an account? Purchase one here.
Contributing to the JIRA Studio Documentation
Would you like to share your JIRA Studio hints, tips and techniques with us and with other JIRA Studio users? We welcome your contributions.
On this page:
Contributing Documentation in Other Languages Updating the Documentation Itself Getting Permission to Update the Documentation Following our Style Guide How We Manage Community Updates
Contributing Documentation in Other Languages
Have you written a guide to JIRA Studio in a language other than English, or translated one of our guides? Let us know, and we will link to your guide from our documentation. More....
Updating the Documentation Itself
Have you found a mistake in the documentation, or do you have a small addition that would be so easy to add yourself rather than asking us to do it? You can update the documentation page directly.
Getting Permission to Update the Documentation
Our documentation wiki contains developer-focused documentation (such as API guides, plugin and gadget development guides and guides to other frameworks) as well as product documentation (user's guides, administrator's guides and installation guides). The wiki permissions are different for each type of documentation.
If you want to update the Developer Network or other developer-focused wiki spaces, just sign up for a wiki username then log in and make the change. If you want to update the JIRA Studio product documentation, we ask you to sign the Atlassian Contributor License Agreement (ACLA) before we grant you wiki permissions to update the documentation space. Please read the ACLA to see the terms of the agreement and the documentation it covers. Then sign and submit the agreement as described on the form attached to that page.
Following our Style Guide
Please read our short guidelines for authors.
How We Manage Community Updates
Here is a quick guide to how we manage community contributions to our documentation and the copyright that applies to the documentation:
Monitoring by technical writers. The Atlassian technical writers monitor the updates to the documentation spaces, using RSS feeds and watching the spaces. If someone makes an update that needs some attention from us, will make the necessary changes. Wiki permissions. We use wiki permissions to determine who can edit the various types of documentation spaces. Developer documentation (API guides, plugin development and gadget development): Anyone can edit these spaces, provided they have signed up for a wiki username and logged in to the wiki. Product documentation (user's guides, administrator's guides, installation guides): We ask people to sign the Atlassian Contributor License Agreement (ACLA) and submit it to us. That allows us to verify that the applicant is a real person. Then we give them permission to update the documentation. Copyright. The Atlassian documentation is published under a Creative Commons 'cc-by' license. Specifically, we use a Creative Commons Attribution 2.5 Australia License. This means that anyone can copy, distribute and adapt our documentation provided they acknowledge the source of the documentation. The cc-by license is shown in the footer of every page, so that anyone who contributes to our documentation knows that their contribution falls under the same copyright.
Related Topics:
Contributing to the JIRA Documentation Contributing to the Confluence Documentation Contributing to the FishEye Documentation Contributing to the Crucible Documentation Contributing to the Bamboo Documentation Author Guidelines Atlassian Contributor License Agreement
JIRA Studio Documentation in Other Languages
Below are some links to JIRA Studio documentation written in other languages. In some cases, the documentation may be a translation of the English documentation. In other cases, the documentation is an alternative guide written from scratch in another language. This page presents an opportunity for customers and community authors to share documentation that they have written in other languages.
Please be aware that these are external guides. Most of the links point to external sites, and some of the information is relevant to a specific release of JIRA Studio. Atlassian provides these links because the information is useful and relevant at the time it was written. Please check carefully whether the information is still relevant when you read it. The information in the linked guides has not been tested or reviewed by Atlassian.
On this page:
No guides yet
None
No guides yet
We do not yet have any guides to link here. Be the first to suggest one!
Adding Your Own Guide to this Page
Have you written a guide for JIRA Studio in another language? Add a comment to this page, linking to your guide. We will include it if the content fits the requirements of this page.
Giving Feedback about One of the Guides
If you have feedback on one of the guides listed above, please give the feedback to the author of the linked guide.
If you want to let us know how useful (or otherwise) one of these guides is, please add a comment to this page.
Other Sources of Information JIRA Studio documentation Atlassian website Atlassian blog