I am setting up a JIRA / Confluence / Git environment and I would like to know what are the benefits of using Stash?
Our developers already use GitHub and they would like to continue using GitHub Enterprise as they find it very useful for documenting code changes.
If the company is already using GitHub, then does Stash provide any major benefits over GitHub?
I would be very interested to know what enhancements are planned for JIRA/Stash in 2013?
We will be using GitHub for code documentation so I guess my question is, should we be looking to set up Stash alongside GitHub to complement Git/JIRA integration - or should we use GitHub for now and consider replacing it when Stash is a more mature product?
It doesn't make sense to run Stash and Github in parallel. I would suggest to work out what features you require and pick the solution that best suits your needs. A few things to consider:
I'm sure you will have a few more factors to consider when deciding which tool is right for you, but the above might be a good start.
Hi Simania - Thanks for reaching out to us!
Stash provides a ton of benefits when it comes to managing your Git repository in-house. It was designed with Enterprise Security in mind, allowing you to connect to LDAP for user management and provides 3 levels of permissions to make sure your repository is locked down tight. You can even go as far as giving a certain group of users the ability to commit to specific branches within your repository - all through the Stash UI.
Another huge win here is the seamless integration with other Atlassian products. It's super easy to connect to JIRA out of the box giving you insight into which Stash commits fixed certain issues. You can also connect to our continuous integration server, Bamboo, to give greater context to your builds.
Stash also provides a number of plugin points, giving you the ability to extend its built-in feature set to include a number of cool items. I definitely recommend looking through our Atlassian Marketplace to get an idea of what's available to you.
If you'd like to learn more, see our Stash QuickStart Guide.
I hope this helps clarify! Let us know if you have any other questions.
Stash is mainly for a Git repo that has to be within an organization's firewall - it has to be private and protected. It also needs to be controlled and self maintained. It's also tied to Atlassian's user management system, such as Crowd.
As it's "self" hosted it can be customized and there is a lot more freedom.
Thanks for posting answers - interesting comments and made me think about the options that I need to consider (e.g. we dont have LDAP server, should we use Crowd?)
The Git repository is within our company firewall and we looked at using Bamboo but have decided to stick with Jenkins for the time being simply because it is less effort to migrate at this point in time (this decision will be reviewed in migration phase 2).
One of my main objectives is to ensure good integration between Git <-> JIRA - does Stash provide better integration with JIRA or can the same integration be achieved between GitHub and JIRA using plugins? (i.e. is it easy to navigate from a JIRA issue to associated code commit in Git?
Stash offers a number of features that are not available via Github and the DVCS Connector. Most notably the integration of JIRA within Stash.
Take a look at this page which outlines an important part of the integration:
Hope this helps,
The JIRA to Stash integration has come a long way over the last 6 months. We've added the ability to create branches in Stash with a single click from JIRA and will shortly release new features that provide more insight into your development porgress via the issue view.
Something else to note is the integration from Stash to JIRA. In Stash, you can see issues associated with commits and pull requests and view details of the issues. Furthermore, the integration allows you to transition issues right within Stash, which is really usefull when you create a pull request and you want to move the issue into the "review" state for example.
The page describes some of the features and shows how we are thinking holistically about the integration between JIRA and Stash to create a streamlined development workflow.
Hope this helps.
I am very currently struggling with having Stash commits displayed in a project's Agile board. I can see the commit link (using the automatic link with the commit comment containing the issue link) in the Source tab of the Jira issue, but not in the Commits tab and neither in the Details view in the Agile board. The closest I've to a solution is this: https://jira.atlassian.com/browse/GHS-9364, but it does not seem to solve it for me. I've got the DVCS connection plugin enabled and there are no actions required to upgrade it, so my guess is that it is at the latest version.
Where do you think I should go from here in order to get my Stash commits to be displayed both in the Jira issue Commits tab and in Jira Agile's Detail view commits section?
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs