I just got a new client. They are a software development firm and they make the most amazing product! I’m impressed with what they’ve shown me and they seem to have a robust SDLC process. But then we start taking about Jira administration and that’s where the conversation takes a different direction. All those great practices they have in place for their own software do not extend to Jira. They frequently make Jira configuration changes in production, the multiple admins don’t communicate their changes to each other, and no one bothers to keep any form of documentation. Yuck. Luckily, I convince them to treat their internal applications just like they treat the software that they develop. It’s time to connect Jira to a source code repository to better manage change.
Benefits
Here are some benefits of connecting Jira to Bitbucket (an Atlassian product), GitHub, GitLab, or Azure DevOps.
- Collaborate with multiple admins making changes in multiple places
- Automatically address dependencies
- Reduce conflicting configuration changes
- Automate change documentation
- See branches, pull requests, and commits right in Jira issues
- Manage configuration changes in the same place you manage code changes
- Create a legal and historical record of who changed what
- And more
In my latest series, we’ll explore ways to evolve by introducing DevOps principles into Jira administration. This week’s article shows you how to connect Jira, Bitbucket, and Salto to effortlessly manage the entire process.
Check out my new series on Salto’s website. In the second article, we’ll tackle how to connect to a git-based repo like Bitbucket.
Read: DevOps for Jira #2: Connecting to a code repository
From creating a test environment to automatically creating pull requests – this series has you covered.
2 comments