Version on timeline with epics committed

Hi. I am trying to make a report similar to this but with more information.
Version timeline

  1. I’d like to show the issues resolved (with options to choose by issuetype, so maybe this will be a dropdown on the column) for that specific version at the release date
  2. I’d like to show open issues that has the specific version at the start date or release (again option to choose by issuetype)
  3. I’d like to show the issues that were added on the version after the release start date
  4. I’d like to show the issues that were removed on the version after the release end date
  5. Instead of having time on the row, I’d like the version be on the row as my versions are in mid-month. So if it’s by month on the time row, it shows open issues for the upcoming version, not on the current version.

Will appreciate the help! Thanks!

Hi @jest

“Fix version” is a multi-value field in Jira, and eazyBI won’t import changes for multi-value fields.
That means you can not analyze release history in eazyBI reports.
You can create reports based on the current release of an issue.

For the first requirement, you can add the “Issue type” dimension as a page filter and calculate results for certain issue types.

For the 5th requirment you could create a calculated measure to count open issues for each release.
This will count issues based on their current release, but you can calculate them also at certain point in the release (for example at version release date) if you want.

This formula (when used in calculated measure) would return the open issue value at the release date of the Fix version.

(
  [Time].[Day].DateMember(
    [Fix Version].CurrentMember.get('Release date')
  ),
  [Measures].[Open issues]
)

It will work if “Fix version” dimension is used in rows and selected at the “Version” level.

Martins / eazyBI support

Hi @martins.vanags

Thanks for the feedback. I think I found another way to do this through jql in jira. Would you be able to help me translate this to a calculated measure?

Fixversion changed from ‘x’ during (start date, end date) and statuscategory !=done, issuetype=initiative, status not in (a,b,c) an fixversion =! x

This checks if fixversion was changed from x on specific duration, also checks that the current fixversion also not x (fixversion could have changed from x to y but changed back to x)

@jest

Unfortunately, eazyBI won’t import changes for multi-value fields such as fix version.
We do have a feature request for such improvement but I can’t promise any release dates yet.

Martins / eazyBI