52 karma · joined April 5, 2011
Our aim was to provide an at the glance view of the development status (# of commits, branches, pull requests and their status, builds and deployments) with the option to see more detailed information right within JIRA. And of course you can create a new branch right from your JIRA issue.
Lastly, ensuring that the data is 100% reliable and up to date was an important consideration which most of the basic webhook integrations simply ignore.
Take a look at the documentation, which provides a great overview of the integration: https://confluence.atlassian.com/jira/viewing-the-code-devel...
Do we want people to use JIRA? If they require more than simple issue tracking, absolutely. But that doesn't mean that we aren't improving the base tools.
For example, Bitbucket already provides the ability to vote for issues and recently added rendering of the CONTRIBUTING.md file for pull requests (http://blog.bitbucket.org/2016/01/26/pull-request-guidelines...).
The core of Stash is actually written in JAVA, with only few plugins being implemented in Scala. But that number will likely grow going forward.
You are probably right that some of us are slightly opinionated. But as was pointed out before, I believe product managers should be opinionated as long as the opinions are formed by knowing your customers and market extremely well.
Internally we use Stash of course ;)