How to enable fix version across all projects as Jira Admin

[gunasekar_rajendran]

I am looking to offer few more Fix version data to my team for various projects how do I enable them

Guna

[Walter Buggenhout]

Hi @gunasekar_rajendran and welcome to the Community!

Could you be more specific as to what you are trying to achieve?

Fix Versions (releases) are specific to Jira Software projects. That means you'll have to create them in each project separately for them to become available. You cannot use a version from one project in another project.

If you are using them in company managed projects, a project administrator can add new versions from the Releases tab in the project navigation by clicking Create Version.

In team managed projects, you'll need to enable the Releases Feature from Project Settings > Features in order to make them available.

Hope this helps!

[Walter Buggenhout]

Thanks for your swift response. I am Jira Admin managing projects across the Portfolio and all of my projects are following the same release schedule. So instead of me creating release schedules for each and every project, I would like to create one across board so every team can use that value for their Fix version assignment to their stories. Hope this clarifies and will try what you had recommended as Team Managed projects as well.

Yes, @gunasekar_rajendran. Thanks for the additional context. You can create a board that brings together work from different Jira projects through a JQL filter. But boards and projects are different things.

As mentioned in my first response - and also by @Calvin - versions are defined inside Jira projects (not boards). That means you'll still have to define your releases inside each separate Jira project if you'll be able to link them to the work items from that project.

If you were on a premium plan, you could create a cross-project release in a Plan - which connects to the separate project releases and allows you to group those different releases into a single item you can use to collectively manage your cadence. But even with that in place, you will still need to create your versions in each individual Jira project.

[gunasekar_rajendran]

Hello Walter,

Thanks for your swift response. I am Jira Admin managing projects across the Portfolio and all of my projects are following the same release schedule. So instead of me creating release schedules for each and every project, I would like to create one across board so every team can use that value for their Fix version assignment to their stories. Hope this clarifies and will try what you had recommended as Team Managed projects as well.

Guna

[John Funk]

Hi Guna - Please reply inline with the thread you are answering so readers can properly follow the conversation. 

[gunasekar_rajendran]

Thanks John. I am now trying to group by my release number any JQL help someone can offer please.

Scenario is like this: 4 Different Teams all aligning to the same release number R1, R2 ETC.

The ask is to show a filter with data for each release count across different projects. 

Guna

[gunasekar_rajendran]

Thanks Walter and what you mentioned at the end is the solution. We need to use Plan, but can you guide me where can I use the trial version of the software before we can make the decision.

Please see a screen shot 

As you can see the ones which are in red are our data so had to retract it, but they are all individual projects as you can see on the table, I am getting different rows for the same release count why?

Guna

[gunasekar_rajendran]

Calvin,

Thanks for the note and I believe the problem statement is not understood. You can have multiple teams with different projects but they all would converge to a single release schedule. So in the sense the enablement to a single project is fine but what if you are running a portfolio with multiple projects aligning to a single release window that time it becomes painful to create these individual releases for each project. For ex: Let's say you want to release a Product to the market with Sales team, Operations Team, Product team all of them are working on their own backlog but they need to converge to a single release point. It's something for the Jira Product team to look into it and we can close the thread here please.

Appreciate all the responses and help offered.

[Calvin]

As the other user noted above, Fixed Versions are a "per project" sort of thing for Company Managed project as far as I'm aware. So a Project or Product Admin has to create them each time.

We've tried dealing with this in two different ways:

1. Every time we create a project we have an automation that creates the Fix Version for the next couple years. Usually this is long enough for the project to start/end.
2. We no longer do this now and now use a custom field dropdown to set a specific "Release Version", that way all teams can customize their own "Fixed Version" if they want but in Plans and reporting we use the custom field that is shared with all the projects.