Stash Latest (2.8) : Stash 2.7 release notes

20 August 2013

Introducing Stash 2.7

Today we're pleased to announce Stash 2.7, which introduces a range of JIRA integration improvements, to help optimise your development workflows. We've also included a brand new Stash backup and restore solution.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

Please also check the End of support announcements for Stash.

The Stash 2.7 changelog is at the bottom of this page.

JIRA issue transitions

Now you can easily transition a JIRA issue from within Stash. For example, when creating a pull request you may want to transition the issue into review. Click on a linked JIRA issue anywhere in Stash to see a dialog with the available workflow steps:

 

Your Admin needs to have set up linking with JIRA before you'll see this. Read more about JIRA integration in Stash.

Autolink JIRA issues in markdown

When you mention JIRA a issue key in Stash, for example in a pull request description or comment, the key gets automatically linked:


You can click on the linked key to see details for the issue. 
Note that issue keys in a URL will link directly to the JIRA instance, as you'd expect. Read more about JIRA integration in Stash.

Support for multiple JIRA instances

Stash can now link to more than one JIRA server at a time, so different teams can work with their own projects in different JIRA instances, or a single team can link to issues across multiple JIRA servers.

Read more about JIRA integration in Stash.

Backup and restore beta  

With the Stash 2.7 release we have made available a beta release of a backup and restore client for Stash. The Stash backup client locks access to Stash, checks that all Git and database operations have completed, and then performs a concurrent backup of the Stash database, repositories and data. You can download the Stash backup and restore client from the Atlassian Marketplace. 

Although we are confident about the performance of this tool, we are interested in hearing how well it meets your requirements in actual use – this is why we are releasing the client as a beta. We look forward to your feedback! 

Read more about backing up and restoring your Stash data. 

Small improvements

Improved LDAP synchronisation performance

We have greatly improved the performance for LDAP synchronisation. For example, on a test LDAP server with 10,000 users and 10,000 groups, the time for a full synchronisation improved from 64 minutes to 4 minutes.

The Repository System Information plugin is now deprecated

The functionality of the  repository system information plugin  has now been moved into core Stash. The plugin will still work for Stash 2.x versions but is redundant as of Stash 2.7.

Syntax highlighters are now configurable

You can now update the extensions associated with different syntax highlighters using the stash-config.properties file in the Stash home directory. For more details see  Configuring syntax highlighting for file extensions.

MySQL default isolation level

Stash 2.7.x uses READ_COMMITTED instead of the MySQL default isolation level (REPEATABLE_READ). This can result in exceptions when installing/upgrading to 2.7.x, if binary logging is enabled in your MySQL server. More details and a fix can be found in this KB article.

Change log

This section will contain information about the Stash 2.7 minor releases as they become available. These releases will be free to all customers with active Stash software maintenance.

If you are upgrading from an earlier version of Stash, please read the Stash upgrade guide.

The issues listed below are just the highlights of all those that have been resolved for the Stash 2.7 release.

19 September 2013 - Stash 2.7.2

Type Key Summary
Bug STASH-3843 LazyReference$InitializationException: java.lang.IllegalArgumentException: duplicate key: {username}
Bug STASH-3838 Public repositories not showing project after first 25
Authenticate to retrieve your issues

29 August 2013 - Stash 2.7.1

Type Key Summary
Bug STASH-3807 Show the first few lines of an exception on the console
Bug STASH-3805 Backup client fails if backup directory starts with same string as Stash home
Bug STASH-3804 Admin > Users returns empty user list for Oracle database
Bug STASH-3798 nav-links and ref-syncing are not in the list of bundled plugins
Bug STASH-3793 git rev-list fails on startup
Bug STASH-3788 Pull request events are not audited
Bug STASH-3786 StringIndexOutOfBoundsException: String index out of range: -1
Authenticate to retrieve your issues

20 August 2013 - Stash 2.7.0

Type Key Summary
Sub-task STASH-3634 De-Activated Users In Crowd Still Count Against the User License
Story STASH-3720 Document .mailmap feature
Story STASH-3698 Create an "End of Support Announcements for Stash" page
New Feature STASH-3733 Bundle Repository System Info Plugin with Stash
New Feature STASH-3594 Syntax Highlighting For Erlang Code
New Feature STASH-2471 Support integration with multiple JIRA servers
Improvement STASH-3632 Deactivated users synchronized when using JIRA for authentication
Improvement STASH-2552 Provide a way to locate the repository directory on disk
Bug STASH-3651 JIRA issue link not obeying Display URL value in Application Links (JIRA Issues pop-up only)
Bug STASH-3588 Synchronising a directory fails on MySQL
Bug STASH-3577 Mouseover tooltip on "Approve" button always tells user to "Approve this pull request"
Bug STASH-3471 HistoryService lacks documentation
Bug STASH-3415 Hide upload public SSH key option, when SSH access is disabled
Bug STASH-3301 About page doesn't respect that I'm logged in
Authenticate to retrieve your issues

Attachments: