3 minute read
Every engineering team today is striving to move faster with less risk. The challenge is, moving fast is inherently risky, and mitigating risk is often slow.
One of our primary goals is ensuring that you never have to make the tradeoff between speed and safety. As announced in Trevor’s product roadmap today, our upcoming Jira integration is our newest investment in reducing engineering cycle times and mitigating release risk.
Split’s Jira Integration
Atlassian’s Jira offers flexible issue and project tracking with best-in-class agile tooling for software teams. We are super excited to partner with Atlassian to enable teams to safely charge at full speed from develop and deploy to target and release, using tools they’re already accustomed to.
Once configured, you’ll be able to associate Split feature flags with Jira issues and view corresponding information in both platforms. If you’re in Jira, you can connect an issue with an existing Split feature flag or create a new one. Alternatively, you can also connect Jira issues to a feature flag in Split.
Support Continuous Delivery
By making feature flags part of the issue creation process, engineers are encouraged to deploy code to production early and often by gating unfinished work behind feature flags. When ready for release, the Jira issue will automatically update to the current rollout status. For a percentage rollout, the Jira issue will display the percent of your user base exposed to the flag treatment along with the treatment name. If any other targeting rules are being applied, the Jira issue will display the total number of allowlists, traffic allocations, and targeting rules in effect.
Coordinate Across Teams
Having issue and feature flag information available in both platforms makes it easy for teams to collaborate and keep each other informed throughout the entire feature delivery lifecycle. If your teammate is about to ramp a feature flag to more users in Split, they can quickly check for any unresolved Jira issues before making the change and save time from having to confirm with you or manually search in Jira.
Manage Technical Debt
You can also quickly determine what feature flags are ready for code cleanup, preventing more technical debt from accumulating over time. On Split’s Environments page, you can see which feature flags have not been evaluated in the last week and may be ready for retirement. Clicking into each feature flag, you’ll be able to check the rollout status and if it has any unfinished Jira issues. If the feature is 100% released and all Jira issues are marked done, it’s safe to conclude you can remove the code.
Get Early Access
Today, our existing Jira integration allows you to keep your team up-to-date as new feature flags are enabled, and rollouts are modified. This integration is now available in our Free Edition, so be sure to check it out.
For our new Jira integration as described above, you can join our Early Access Program to share your input with our Product team and be the first to try once it’s entered beta.
Learn More About How We Support Continuous Delivery at Split
Check out the links below for tips and tutorials on how feature flags and continuous delivery come together. If you like what you’re reading, follow us on Twitter and subscribe to our YouTube channel!