Overall Satisfaction with Bitbucket
The software engineering [department] uses BitBucket as its choice of version control for all repositories (over 30). It allows us to manage our advanced development and deployment workflows and integrates well with JIRA and Confluence.
- Very intuitive and user-friendly user interface.
- Lot of options for integrations, such as with JIRA, and with Slack.
- Very reliable. Never an issue with being buggy or not working.
- It would be cool to have better options to search for individual User contributions.
- You can set up a list of users who are required to approve certain pull requests (which is VERY useful). It would be nice to set up a group of users, then assign a group as being required for approval, so that if that group changes, you can update it in one place and not across every code repository.
- There are storage limits to how much you can store, and anything above it costs money. This generally isn't an issue, but can be in certain scenarios.
- Better quality development using base capabilities provided (branching strategies), linking Bitbucket branches to JIRA tickets.
- Increased visibility into issues with integrations with Slack (notifications sent on important actions, ie: alerts)
- Greater ability to investigate issues with views of history and ability to "roll back" commits to previous instances of the code.