December 2012

Changes in this month:

17 December 2012

JIRA OnDemand upgrade

Global autowatch configuration

We've implemented a new JIRA option that allows administrators to disable the autowatch feature for all users. To configure autowatch for all users, navigate to JIRA Admin > User Settings > User Preferences and update Default autowatch.

Users can choose to inherit the global autowatch setting or override it via their user Profile > Preferences > Autowatch setting.

All users who have not explicitly set their Autowatch setting will have it set to 'Inherit from global settings' in this upgrade.

Maximum project name size and maximum project key size configuration

JIRA administrators will be able to set the maximum size for both the project name and project key in this upgrade. Navigate to JIRA Admin > General Configuration and update Maximum project name size or Maximum project key size as desired.

The Maximum project name size or Maximum project key size are defaulted to 80 and 10 respectively. This will not affect the names or keys for your existing projects.

Confluence OnDemand upgrade

Confluence has been upgraded to OD-25. This is a bug-fix upgrade only.

10 December 2012

Confluence OnDemand upgrade

Confluence has been upgraded to OD-20. This upgrade does not include any changes that will affect customers.

GreenHopper upgrade

GreenHopper has been upgraded from 6.0.8 to 6.1-RC1. This upgrade includes a number of new features enhancements, including several additional features for epics. 

For details, check out GreenHopper OnDemand 2012-12-10

Fixes this week

Issue
Summary
AOD-6245

Team shortcuts are not working in Bamboo for remote applications

3 December 2012

GreenHopper upgrade

GreenHopper has been upgraded from 6.0.7 to 6.0.8. 

For details, check out GreenHopper OnDemand 2012-12-03.

Tempo upgrade

Tempo has been upgraded from 7.3.3 to 7.4.1. This upgrade includes a number of new features. Check out the following release notes: 

JIRA OnDemand upgrade

Team shortcuts

In a previous release, we removed project custom tabs to improve the interaction and visual design of OnDemand. In this release, we've restored the ability for you to set up links that are project-specific, such as links to a JIRA filter, a GreenHopper board, or a project planning page on your Intranet. These links are called "team shortcuts" and appear in a pop-up window when you click the project avatar. Team shortcuts are the first iteration of the design to make it easier for you to set up links for your users.

Click the project avatar to open the team shortcuts window

Team shortcuts

Links that previously appeared in your project custom tabs will be added to this window for you automatically. Admins can also add new team shortcuts and change the order of links using the Team Shorcuts section of the project admin area.

Known issues

There is a known issue in Bamboo that causes the team shortcuts to not appear in the pop-up window. We are working on fixing this problem, and you can track the progress at https://jira.atlassian.com/browse/AOD-6245.

Project creation based on application access

Previously, JIRA admins had to have access to all applications in their OnDemand instance to create projects. Now, users can create projects in JIRA as long as they have access to JIRA. When JIRA admins create projects, corresponding objects in other applications (such as a Confluence space, a Subversion repository, a FishEye repository, and a Bamboo project) will be created automatically in the applications the user has access to. If the user doesn't have access to those applications (even if they exist in that instance), the objects won't be created. We recommend giving admins access to all applications so they have the same level of access across your whole instance. For information on how to set application access, see Managing application access.

Also, with this release, when an admin deletes a JIRA project, only that project is removed. Any related objects in other applications remain and admins must delete them from that application.

JIRA issues no longer have a Google Documents section. Instead, you link documents to issues using the same process as for other types of links (see Linking Issues).

If you previously attached Google Docs to an issue, the documents will now appear under the Issue Links section in the issue. If you used the default Google Docs field to attach the documents, their link names will be the same as the Google Doc names. However, if you attached Google Docs using a custom field based on the Google Docs field, any documents attached in the custom field will appear as "field_name - DOC_Name".

Reports have moved

We have moved reports from the dropdown menu on the Browse Project > Summary tab to a panel on the same tab, so that they are more accessible.

Confluence OnDemand upgrade

Confluence has been upgraded to OD-19. This includes an upgrade to the Widget Connector, some fixes to table handling in the editor, and a fix to the display of breadcrumbs during preview.

Issue
Summary
CONF-27304  Update widget connector to 2.0.3. to fix problems with YouTube and Twitter integrations
CONF-27363

Cannot change a table row from header to normal

CONF-27364

Highlight row/column doesn't work if whole row/column is selected

CONF-27365 Add a new icon for disabling cell highlight - not white
CONF-27367 Editing table with cells with non-white background looses any previous background color set
CONF-27366

Breadcrumbs do not expand properly when doing a preview during page creation

Space 'Advanced' option renamed to 'Space Operations'

To access space options, like watching a space and exporting content to PDF, HTML or XML, you should now choose BrowseSpace Operations. Previously, you would choose Browse > Advanced. This change is part of our drive to make the Confluence user interface simpler and easier to understand. The change is just the name of the menu option and tab. The functionality and options remain the same.

The 'Space Operations' option in the 'Browse' menu and 'Browse Space' view:

OnDemand themes migrated to Atlassian themes

There used to be five Confluence themes from which you can choose for a space. We've simplified the selection by removing the Atlassian OnDemand theme and the Atlassian OnDemand Documentation theme. 

Spaces that use the Atlassian OnDemand Documentation theme are migrated to use the Documentation theme. If you have configured the Atlassian OnDemand Documentation theme, the customizations are copied over to the Documentation theme. 

Before:

A space that uses the Atlassian OnDemand Documentation theme

 

After:

The theme is changed to Documentation theme

Bamboo upgrade

Bamboo OnDemand has been upgraded from 4.2 to 4.3. Improvements include:

  • Build from any revision: Build, release and deploy off of an exact revision in your Git, Mercurial, Subversion or Perforce repository.
  • Multiple build triggers per plan: Configure your build to run every time a developer commits and once a day using multiple triggers.
  • Runtime variables for manual stages: Change host names, deployment targets, passwords and other variables on the fly when running manual stages.
  • Upload files to remote servers using SCP: Upload and deploy static HTML, JavaScript and PHP & Ruby web applications to remote servers.
  • Execute remote commands using SSH: Call database migration scripts, start and stop services, or anything else you can run on the command line on a remote machine.
  • Rebuild with one click: Quickly rollback a deployment or shake out any intermittent failing tests.
  • Automatic plan dependencies for Maven 3: Automatically set up child and parent build dependencies between your plans based on the dependencies in your Maven 3 project.
  • Wallboard for plan branches: Displays the status of all the branches and the plan that the branches belong to.
  • Amazon Virtual Private Cloud for Elastic Bamboo: Launch Elastic Bamboo agents in your own Virtual Private Cloud for extra security and peace of mind.

See the Bamboo 4.3 Release Notes for more information.

Maximum project name size and maximum project key size configuration

JIRA administrators will be able to set the maximum size for both the project name and project key in this upgrade. Navigate to JIRA Admin > General Configuration and update Maximum project name size or Maximum project key size as desired.

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