Stash 3.11 release notes

14 July 2015

If you are upgrading from an earlier version of Stash, check the Stash upgrade guide. See also the End of support announcements for Stash and the changes listed in the API changelog.

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

Controlling HTTP(S) access to Git repositories

Supporting Git operations like push and pull over HTTP(S) comes with additional maintenance and configuration burdens, like managing SSL certificates or opening additional firewall ports for instance. To provide more control over the security of your instance you can now disable HTTP(S) completely within Stash so access relies on using SSH key pairs exclusively. Learn more about disabling HTTP(S) access to Git repositories in Stash.

Change log

This section will contain information about the Stash 3.11 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, check the Stash upgrade guide.

The issues listed below are the highlights of all those that have been resolved for the Stash 3.11.x releases, and are ordered by votes received.

18 September 2015 - Stash 3.11.3

14 August 2015 - Stash 3.11.2

20 July 2015 - Stash 3.11.1

14 July 2015 - Stash 3.11.0

Loading
T Key Summary
Bug BSERV-5490 Language sometimes not consistent
Bug BSERV-7094 Cannot ctrl+F on Markdown rendered files
Bug BSERV-4662 Handle unreachable Application Links gracefully when their unreachability is non-critical
Bug BSERV-7052 "User not permitted message" when viewing a pull request
Bug BSERV-7177 README.md files are rendered differently from other *.md files
Bug BSERV-4302 False-positive issue key recognition in whole word
Bug BSERV-5292 Anchor links in markdown include a slash that causes them to work inconsistently
Bug BSERV-7037 JIRA transition Resolution field in Stash does not work for other languages
Bug BSERV-7398 Performance regression for instances with a large disparity of licensed to unlicensed users
Bug BSERV-7566 Branch permissions AccessGrants and PermittedEntities return incorrect restrictionId
Bug BSERV-7176 Tag display on commits list
Bug BSERV-7344 Workflow actions "More" drop-down in Jira Pop-Up is hidden by the pop up
Bug BSERV-6958 Hovering over task checkbox in diff comment with IE11 uses wrong mouse cursor
Bug BSERV-7083 Adding JIRA User Directory With URL Context Path Containing "services" Fails
Bug BSERV-7457 Cross-repository pull request merges sometimes fail to fetch objects after upgrading to Stash 3.9
Bug BSERV-7510 The permitted endpoint in the Rest API is returning 0 results when it should return a list of users/groups who have been given permission to the repository
Bug BSERV-6877 Syntax highlighter breaks with Scala's triple quotes / String interpolator
Bug BSERV-4805 Cannot follow link to JIRA issue if user does not have access to all linked JIRA instances
Suggestion BSERV-7345 Add target branch/repository and source branch to JS State API
Bug BSERV-7260 Anchor links in markdown broken when not on the default branch
Showing 20 out of 54 issues Refresh

Redirection notice

This page will redirect to /display/BitbucketServer/Stash+3.11+release+notes .

14 July 2015

If you are upgrading from an earlier version of Stash, check the Stash upgrade guide. See also the End of support announcements for Stash and the changes listed in the API changelog.

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

Controlling HTTP(S) access to Git repositories

Supporting Git operations like push and pull over HTTP(S) comes with additional maintenance and configuration burdens, like managing SSL certificates or opening additional firewall ports for instance. To provide more control over the security of your instance you can now disable HTTP(S) completely within Stash so access relies on using SSH key pairs exclusively. Learn more about disabling HTTP(S) access to Git repositories in Stash.

Change log

This section will contain information about the Stash 3.11 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, check the Stash upgrade guide.

The issues listed below are the highlights of all those that have been resolved for the Stash 3.11.x releases, and are ordered by votes received.

18 September 2015 - Stash 3.11.3

14 August 2015 - Stash 3.11.2

20 July 2015 - Stash 3.11.1

14 July 2015 - Stash 3.11.0

Loading
T Key Summary
Bug BSERV-5490 Language sometimes not consistent
Bug BSERV-7094 Cannot ctrl+F on Markdown rendered files
Bug BSERV-4662 Handle unreachable Application Links gracefully when their unreachability is non-critical
Bug BSERV-7052 "User not permitted message" when viewing a pull request
Bug BSERV-7177 README.md files are rendered differently from other *.md files
Bug BSERV-4302 False-positive issue key recognition in whole word
Bug BSERV-5292 Anchor links in markdown include a slash that causes them to work inconsistently
Bug BSERV-7037 JIRA transition Resolution field in Stash does not work for other languages
Bug BSERV-7398 Performance regression for instances with a large disparity of licensed to unlicensed users
Bug BSERV-7566 Branch permissions AccessGrants and PermittedEntities return incorrect restrictionId
Bug BSERV-7176 Tag display on commits list
Bug BSERV-7344 Workflow actions "More" drop-down in Jira Pop-Up is hidden by the pop up
Bug BSERV-6958 Hovering over task checkbox in diff comment with IE11 uses wrong mouse cursor
Bug BSERV-7083 Adding JIRA User Directory With URL Context Path Containing "services" Fails
Bug BSERV-7457 Cross-repository pull request merges sometimes fail to fetch objects after upgrading to Stash 3.9
Bug BSERV-7510 The permitted endpoint in the Rest API is returning 0 results when it should return a list of users/groups who have been given permission to the repository
Bug BSERV-6877 Syntax highlighter breaks with Scala's triple quotes / String interpolator
Bug BSERV-4805 Cannot follow link to JIRA issue if user does not have access to all linked JIRA instances
Suggestion BSERV-7345 Add target branch/repository and source branch to JS State API
Bug BSERV-7260 Anchor links in markdown broken when not on the default branch
Showing 20 out of 54 issues Refresh

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