Releases are at the core of every project. They help teams organize the delivery of work and act as a historic reference for future needs.

Jira releases are good for managing your releases at project level.

Now imagine that you run a bigger project that you decided to split into many smaller projects in Jira, e.g. based on the structure of your teams or clients.

Each team can manage their own tasks, can have different workflows, reports, etc. But when it comes to releases you still need to release only one version that delivers tasks from several of these projects. How would this work in Jira?

You could try to create a version with the same name in each of the projects and then once release is done manually update each of these releases. It might work fine for 2 to 3 projects for a while. But can you imagine doing this every time and for more projects 🤯?

Cross-project or portfolio releases aren't the core functionality of Jira. But, they can be added by using an external app like Swanly - Release Management Timeline.

Here is how it works

In Swanly you can create a release with multiple projects assigned. Then Jira versions are created in each selected project. Any change done to any of these versions are automatically synchronised. Magic 🎩🐇...

Now you can go ahead and assign the issues to these versions as usual and carry on.

Share Jira Versions Across Projects in Swanly
Assign multiple projects to the release

As a bonus, Swanly shows your releases on a timeline and a list view and provides advanced release details with:

  • Aggregated Story points and Time tracking
  • List of the issues linked to the version and List of issues that affect the version
  • Release History

So you find everything you need in one place.

Tracking Progress of Jira Version across Multiple Projects
Track progress of cross-project releases in one place