Group multiple tickets across multiple projects

[Vaishnavi Manda]

This sprint onwards, we are going to start doing "Fix Version" tagging. 

• What this means is, every JIRA tied to a fix version has to be launched in M2 together. If a particular JIRA in a particular Fix version is not done completely, then it has to be fixed first on priority before going to M2. 
• In M2 testing, focus will be on testing fix version items, and only when all are clear, launch to P1. 
• In M1, deployment can happen independently. But in M2, the whole fix version has to be deployed together. Similarly in P1 and P3

We want fix version tagging across multiple project s happening through multiple tickets.

[Hannes Obweger - JXL for Jira]

Hi @Vaishnavi Manda

versions generally exist per project, so cross-project versioning isn't particularly well supported in Jira. 

Couple of ways forward:

• You can create your own custom field (which can be cross-project), and use this custom field instead of the built-in fix version field. Note that there are some versioning-related views and features in Jira; these would then no longer work.
• IIRC, Jira's Advanced Planning supports cross-project versions (see here). You'll need to upgrade to Jira Premium, though.
• If you are open to solutions from the Atlassian Marketplace, you'll find options there. I myself work on an app in which cross-project grouping by versions is easily available. I'll add more information below.

Hope this helps,

Best,

Hannes

[Hannes Obweger - JXL for Jira]

Just to expand on the last point: If you're open to solutions from the Atlassian Marketplace, this would be easy to do with the app that my team is working on, JXL for Jira.

JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of advanced features, including support for cross-project issue grouping by any issue field(s), like so: 

In the above example, there's a version "v1" in project WORK and another version "v1" in project OKR, and because they have the exact same name, the respective issues are grouped together. Issue grouping can also be combined with JXL's other advanced features, including support for configurable issue hierarchies, sum-ups, or or conditional formatting.

Any questions just let me know!

[Vaishnavi Manda]

This is good idea Hannes but we are want something that isn’t chargeable and available for free.