Our company has multiple development teams working independently with their own priorities and schedules. However, all teams contribute to the same codebase and we deploy everything together in unified releases.
I’m looking for the best approach to handle this situation in Jira. Here are some options I’ve been considering:
Shared release versions - If Jira supported release versions that span multiple projects, this would solve our synchronization issues perfectly.
Label-based approach - We could implement a tagging system and modify our existing filters to properly organize and display relevant items for each team.
Manual synchronization - Keep release versions aligned manually across projects (not ideal but possible).
API automation - Build a custom solution using Jira’s API to automatically synchronize release versions between projects.
Alternative methods - Open to completely different approaches.
What strategies have worked well for similar multi-team, single-codebase scenarios? Any recommendations would be appreciated.
Component-based versioning proved to be far more efficient for us than attempting to synchronize across various projects. With four teams contributing to our releases, we required distinct tracking methods. We established components within a single master project that corresponded to each team’s focus areas. Each component maintains its own version tracking, while still enabling coordinated releases from one central location. We set permissions so that teams could only access their components by default, granting release managers visibility into all components. Automation rules were added to update component versions based on specific triggers. While the migration and training process lasted two weeks, we’ve eliminated synchronization issues. Release planning has become significantly more streamlined, with everything organized in one place and a proper hierarchy.
been using api automation for like 6 months now, and it’s been working great! took some time to set up at first, but now we don’t have to manually update versions every time. def beats doing it manually!
We hit the same coordination mess and went hybrid. Set up one release management project next to our existing team projects. The release project has all unified versions and epics that link back to team tickets. Teams keep their own setup but create linked issues in the release project for shared releases. We get central visibility without killing existing workflows. Release manager tracks everything from one dashboard, teams stay autonomous day-to-day. Took a month for everyone to adjust, but it fixed our version sync issues without custom dev or big process overhauls. Teams actually like it now - they focus on their work while still hitting the bigger goals.
API automation’s your best bet, but building from scratch sucks. Been there with multiple teams sharing one codebase.
I skipped the custom scripts and used Latenode instead. It hooks into Jira’s API and auto-creates matching release versions across all projects when you add a new one. 15 minutes setup vs weeks of dev work.
Best part? It handles the actual release workflow too. One team marks their version released, everything else updates automatically. No more forgotten manual updates or mismatched versions.
Threw in Slack notifications so everyone knows when versions change. Runs in the background, just works.
we also tried a shared board for tracking instead of a master project. it really helped teams get on the same page. but make sure to have a point person to coordinate—it’s super essential!