💔 This Split isn’t a breakup story.



Instead of sappy break-up or a romantic comedy that ends with broken hearts (insert The Break-Up or My Best Friend’s Wedding) we’ve brought in the infamous Moira Rose to tell you a little more about the Split and Jira integration. That’s right….we’re sharing all the juicy details about the successful Jira and Split integration relationship.


For a relationship that started in the middle of 2021, it’s already off to a great start!



Why are Split and Atlassian the perfect pair? 



  • Atlassian and Split combine best-in-class issue and project tracking, feature flagging, and experimentation to enable software teams to build impactful products with unparalleled speed and safety.
  • Connect issues and flags so teams can seamlessly coordinate and stay up-to-date on projects and releases.

  • Enable continuous delivery – allow engineers to merge code early and often without disrupting the user experience.

  • Coordinate across teams – allow engineers and project managers to easily view and share release and project statuses.

  • Mitigate technical debt – quickly determine if a feature is fully released and ready for code cleanup.


Tell us the secrets to a successful relationship, Moira:

1. That special connection - Connect feature flags to Jira issues.


  • Add a feature flag (split) to an issue by connecting to an existing flag or creating a new flag from the Jira issue screen.

  • Easily ensure all features are gated behind a flag and track flag and rollout status directly in the issue details.


2. Communication is key - View outstanding Jira issues in Split.




  • See the issue name, assignee, and status for all Jira issues linked to a feature flag in Split.

  • Add Jira issues directly within Split by issue number.

  • Check for outstanding Jira issues in Split to ensure all related work is complete before rolling out a feature to users.


3. Always be on the same page - Coordinate controlled rollouts across teams.




  • Once a feature flag has been configured with targeting rules in Split, the Jira issue will reflect the current feature flag configuration (on or off) and rollout status (percentage rollout or a number of targeting rules applied).

  • Having flag and issue details in both platforms helps reduce context switching between windows and creates better visibility across teams.


4. Relationships take work!


Continuous delivery is a huge benefit of the integration. Advocate, Dave Karow, from Split walks through the benefits in this episode of Team Talks. Check it out so your team can start to reap the integration benefits: 


Just some of the benefits and more!

  • Decouple code deploy from release, so engineers can merge code early and often.

  • Control how many people see a new version at any given time.

  • Quickly determine if a feature is fully released and ready for code cleanup.

Get the free app now!


Jimmy Seddon
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
February 15, 2022

Great post @Kalee Williams!  I'm interested to see how this works.

Like Kalee Williams likes this
Yi Meng April 16, 2024

Great post! 

I'm interested to know if it's possible to use Jira automation to create rules to manage feature flag in split. Thanks. 


Log in or Sign up to comment
AUG Leaders

Atlassian Community Events