July 2012

Changes in this month:

30 July 2012

JIRA OnDemand upgrade

JIRA OnDemand has been upgraded, as part of our ongoing commitment to regularly deliver new functionality to JIRA OnDemand.

We're excited to announce that we've improved our upgrade process, so that you'll be receiving JIRA OnDemand updates much more frequently. Every two to four weeks we'll be updating JIRA OnDemand with new features and improvements. Many of these features and improvements will be available in JIRA OnDemand before they become available in a downloadable JIRA release.

This upgrade introduces the workflow scheme viewer. This feature gives administrators a simple view of the workflows associated with the workflow scheme for a project. We also have a number of other workflow administration improvements planned for future upgrades.

For administrators

Workflow administration improvements — Workflow scheme viewer

Following on from the improvements to workflow administration in JIRA 4.4 and project administration in JIRA 5.1, we're continuing to make editing workflows easier within your project. You'll still have the power and flexibility of JIRA workflows at your fingertips, but configuration will be much more intuitive.

This JIRA OnDemand upgrade provides you with the perfect complement to the existing workflow 'Diagram edit mode'  — the workflow scheme viewer. The workflow scheme viewer replaces the existing workflow scheme page for a project. It provides you with a visual representation of the scheme by showing the diagrams for each workflow in a table, as well as the associated issue types. Each workflow can be edited from the workflow schemes page. You can still see the old text-based view of each workflow too, if you prefer.

Refer to the documentation for more information.

Screenshot: The project's 'Workflows' page (annotated, click to view larger image)

Bitbucket and GitHub Connector (JIRA DVCS Connector) upgrade

This upgrade ships a redesigned DVCS connector, which manages linked repositories (repos) based on account instead of project. After you link JIRA OnDemand with a Bitbucket or GitHub account, all repos on which the account has admin permission will appear automatically. There is no need to specify repo-project mapping any more because the connector now looks for referenced issue keys in commits and shows them automatically for the relevant project. 

New features:
  • Autolink new repositories: This is a configurable setting. When it is enabled, the connector automatically looks for new repos for the linked account and displays them in JIRA OnDemand.
  • Change the credentials for a linked Bitbucket account once and all the linked repos will remain valid.

For the documentation on the connector, see the Administering Bitbucket and GitHub with JIRA page.

For existing linked repositories:

The repos you have linked with JIRA OnDemand will appear under the user account. The 'Autolink new repositories' setting is disabled for these existing linked accounts. This means that no other repos will appear except than the previous linked ones.

Known issues

There is a known issue when you set up accounts using email addresses. The workaround is to use your Bitbucket account name instead of email addresses. For details, see Known Issues and Workarounds.

Screenshot: Linked accounts and repos

Screenshot: Linking a Bitbucket account with JIRA OnDemand

Bonfire upgrade

Bonfire has been upgraded from 2.2.3 to 2..3. For features and fixes, check out the release notes: Bonfire 2.3.1 Release Notes.

23 July 2012

New maintenance window for APAC customers

To minimize the downtime during business hours for APAC customers, we have adjusted the maintenance window from Monday 20:00 - 22:00 Sydney time to Monday 23:00 - Tuesday 01:00 Sydney time.

For the maintenance windows for other regions, see Atlassian OnDemand maintenance windows.

A new user interface for login

We are shipping the new login user interface to customers in groups starting from 23 July and you will start seeing the interface in the following weeks. This interface will be shipped to JIRA-only and multi-app sites.

The screenshots show the current interface and we will continue improving it in the next few weeks.

Please note the the following with regards to settings on the General Configuration page for JIRA:

  • The maximum authentication attempts allowed is now 5 times, and after the 5th time, users will see the CAPTCHA field. Your corresponding settings in JIRA are ignored.
  • The Contact Administrators Form setting does not take effect and the contact administrator link is not shown on the login page even if the option is set to ON.
  • The Logout confirmation setting does not take effect and it now always requires users to confirm to log out.

Also, on the administration page for users, the failed login count is not accurate and the Reset Failed Login option is missing. 

Screenshot: Logging in to a standard OnDemand site

Screenshot: Logging in to an OnDemand site with Google Apps

16 July 2012

Bamboo upgrade

Bamboo OnDemand has been upgraded from Bamboo 3.0 to Bamboo 4.1. The relevant features introduced in the versions from 3.0 to 4.1 have been summarized below.

Build management

This Bamboo OnDemand upgrade includes a range of features that help you manage builds better. Jobs can now be configured with tasks, which allow you to build your application, execute a script, upload files to another server, create your documentation and much more. Stages can now be configured as manual stages that allow the execution of a plan to be paused until manually triggered. You will also be able to rerun failed stages, without having to rerun the entire plan. Finally, better JIRA-Bamboo integration improves the release management process — release activities, like releasing a JIRA version, can now be synchronized between the two applications.


Diagram: R
elationship between plans, stages, jobs and tasks

Screenshot: Manual stages

Screenshot: Releasing a version in JIRA (release management)


Bamboo OnDemand allows you to connect to external repositories in this upgrade. You can continue to use the integrated Subversion repository, if you choose, or connect to one of your own. Bamboo OnDemand supports a number of different repository types, including Git and Mercurial.

Support for multiple source repositories has been added in this upgrade — you can now monitor and check out code from multiple repositories for a plan, and specify which of the repositories will trigger the build. Multiple source repository user aliases can also be mapped to the same user in Bamboo. The shared repositories feature allows repositories to be defined globally and shared between plans.

Screenshot: Multiple source repositories

DVCS support

Bamboo OnDemand now features automated build branches (plan branches) and branch merging for customers who want to use Git or Mercurial. You can have Bamboo watch Git and Mercurial repositories and create plan branches automatically when a developer creates a branch. With automatic merging, Bamboo allows you to automatically test and merge your code on every change using the Gatekeeper or Branch Updater model.

In addition, Bamboo OnDemand's support for Git and Mercurial repositories also extends to bitbucket and GitHub.

Agents and Images

A number of improvements have been made to agents and images in this upgrade. The most significant change is that your agents will now be upgraded automatically with every Bamboo OnDemand upgrade. Other improvements include a new Windows stock image and support for Amazon EC2 spot instances.

Actions for administrators

If you use custom images, you will need to update the images to be compatible with Bamboo 4.1. For instructions, see Updating elastic images for Bamboo upgrades.

This is the last time that a Bamboo OnDemand upgrade will break custom images. Bamboo will automatically upgrade images at runtime for future upgrades.

The overall user experience has been improved in this Bamboo OnDemand upgrade. You'll notice redesigned user interfaces for plan pages, new email templates, a commit-centric "My Bamboo" page, Gravatar support and more.

(info) Note, Gravatars are currently supported in JIRA OnDemand. If you are have JIRA OnDemand as well as Bamboo OnDemand, the same Gravatar will be used in both applications.

Fixes this week

Issue Summary

Task board drag & drop broken in JIRA 5.1      

JIM-778 Importing CSV files fails

GreenHopper Upgrade

GreenHopper has been upgraded from 5.10.4 to 5.10.5.

Version 5.10.5 is a bugfix release. For details, see GreenHopper OnDemand Release Summary.

9 July 2012

Confluence upgrade

Confluence has been upgraded to 4.2.8. Version 4.2.8 is a bugfix release:

GreenHopper Upgrade

GreenHopper has been upgraded from 5.10.3 to 5.10.4. For details, see GreenHopper OnDemand Release Summary.

JIRA OnDemand – new features

Atlassian OnDemand has been shipping new features of version 5.1 incrementally in previous weeks. Refer to the following page for an overview of all the JIRA 5.1 features that are new to OnDemand customers in this week's upgrade. 

JIRA 5.1

Known issues

There is a known issue with the CSV import functionality in this week's upgrade. For more information, please refer to Known Issues and Workarounds.

2 July 2012

Getting copies of your JIRA OnDemand data

The Backup Manager is now available in JIRA OnDemand. This is useful if you want to import OnDemand data into local JIRA installations or into a new Atlassian OnDemand site.

You can also use this approach as a way of taking occasional offline backups. Please note that since the OnDemand service takes backups for your instance every 24 hours, there is no need to regularly back your data up with the Backup Manager.

For instructions on how to use the backup manager, see Exporting issues.

Known issues

On a subset of instances that have JIRA

Unable to render {include} The included page could not be found.
only, the JIRA Backup Manager menu cannot be found on the user interface.

(info) Workaround: Access the two menus with one of the following URLs. 

Unable to render {include} The included page could not be found.


Screenshot: Backup Manager in JIRA OnDemand


Field markup changes in JIRA OnDemand

If you are configuring a custom field's Description or the Introduction message (to display on the dashboard), please note that we changed the formatting functionality of these fields from HTML to wiki markup. Help on wiki markup syntax is provided by clicking the question mark icon under the respective Description and Introduction fields.

Please also note that multi checkbox option fields now only accept plain text (and no longer render HTML markup).

Bitbucket and GitHub Connector (JIRA DVCS Connector) upgrade

This upgrade fixes the issue that causes problems in connecting to GitHub repositories. The issue is tracked at https://studio.atlassian.com/browse/BBC-210.

GreenHopper upgrade

GreenHopper has been upgraded from 5.10.1 to 5.10.3. For details, see GreenHopper OnDemand Release Summary.

Bonfire upgrade

Bonfire has been upgraded from 2.1.2 to to 2.2.3. For features and fixes, check out the release notes:

Tempo upgrade

Tempo has been upgraded from 7.1 to 7.2. Check out the new features here: http://wiki.tempoplugin.com/display/TEMPO/Tempo+7.2+Release+Notes.

Confluence upgrade

Confluence has been upgraded to 4.2.7. 4.2.7 is a bugfix release.

Gliffy in Confluence

Gliffy has been upgraded from 4.0 to 4.2.5 in Confluence OnDemand. This upgrade resolves the issue that causes the the following error where Gliffy diagrams are referenced. The issue is tracked at https://studio.atlassian.com/browse/JST-5891.

"Gliffy Macro Error. An error occurred while rendering this diagram. Please contact your administrator."

FishEye/Crucible upgrade

FishEye and Crucible have been upgraded from from to This upgrade includes a number of performance improvements and resolves a number of bugs.

July: multiple product upgrades

A few product upgrades have been planned for July. We'd like to give you a rundown of the major new features and changes for each upgrade beforehand, so that you can prepare for them. Please note, the exact dates of the upgrades and whether they will roll out as planned have not been finalized yet. As we move closer to the actual upgrades, we will publish more comprehensive release summaries.

JIRA 5.1

Atlassian OnDemand has been shipping new features of version 5.1 incrementally in previous weeks, so although this will be a big version jump, the 5.1 upgrade is actually a much smaller upgrade than it sounds.

One of the highlights is the new issue collector. The issue collector allows you to easily embed a JIRA feedback form into a different web site, which when used by people visiting that site, creates issues in JIRA.

Bamboo 4.1 (upgraded from 3.0.4)

Bamboo 4.1 is coming!

  • Support for building external Git, Mercurial and Subversion repositories:
    • GitHub & Bitbucket are included
    • DVCS features, such as plan branches and auto-merging are also included
  • Improvements to elastic agent handling:
    • Elastic Bamboo support for Windows & .NET builds
    • Automatic agent upgrades
  • A large number of general build improvements: Tasks, Quarantined Tests, Responsibilities
  • Better JIRA integration for release management
Actions for administrators

If you use custom images, you will need to update the images to be compatible with Bamboo 4.1 after the upgrade. For instructions, see Updating elastic images for Bamboo upgrades.

This is the last time that a Bamboo OnDemand upgrade will break custom images. Bamboo will automatically upgrade images at runtime for future upgrades.

Was this helpful?

Thanks for your feedback!

Why was this unhelpful?

Have a question about this article?

See questions about this article

Powered by Confluence and Scroll Viewport