Is there a way to see the number of tickets that span releases?

We use fix versions to tag epics (and others) to a quarterly release plan. At times we miss delivery and we add another fix version to show it is now a part of a new quarter plan.

UNI-1 is slated for Release 2020.1. It was not finished in 2020.1 and will be finished in 2020.2.

UNI-1 has Fix Version = 2020.1.

PO adds Fix Version 2020.2 to UNI-1, so now 2020.1 and 2020.2 are in the Fix Version field for the ticket.

I’d like to be able to report on the number of tickets that span multiple releases; what is the easiest way to do this?

Thank you!

Hi @leigh.crawford,

I understand that you would like to identify and count issues that have more than one Fix version.

One option is to create new calculated measures that go through all fix versions and count how many are related to each individual issue. This method works if you have individual issues on rows. Check out this community post for where is a solution how to Generate() the list of fix version, but you may use a similar calculation to Count() fix versions for each issue:

A more convenient approach is to group issues by how many fix versions they have using JavaScript calculated custom field . Then you may import version count into eazyBI as dimension or interval dimension and use it to group and filter issues by fix version count.

There is an example of advanced settings with JavaScipt that counts how many fix versions each issue has and defined intervals 0, 1, 2 and more.

# count of fix versions
name = "Fix version count"
data_type = "integer"
dimension = true
intervals = "1,2"
javascript_code = '''
if (issue.fields.fixVersions) {
  issue.fields.customfield_versioncount = issue.fields.fixVersions.length;

More details on how to build, test, and import JavaScript calculated custom field is here:

After data import, you can use the new dimension “Fix version count” to show how many issues get in each category, 0 versions, 1 version, or 2 and more versions. If you like, you may edit the intervals for version counts (

Zane /

You may also check out topic on how to build histogram where is used similar approach: