nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Next gen projects points not reflected in dashboard (EazyBI)

Erna_uildwe

Hi,

We're using EazyBI for our reporting and dashboard displaying project, team, personnel performance including points.

However, I notice that for next gen projects, the points is not displayed in the reports. Seems like EazyBI (or maybe other reporting add-ins) failed to import the data from next-gen projects and display it in the report. Classic projects has no issues with this so far.

Anyone facing the same issue and has the solutions? or can JIRA team help check this for me please.

Accepted answers

All comments

Jack Brickey

I would suggest reaching out to EazyBI support. I have added the product tag here in case they are monitoring the community for product questions.

Erna_uildwe

Thank you. Yep they already responded to me and there's some differences with the "label" between classic projects and Next Gen.

Still not 100% resolved but we're gonna try to find out how to solve the different labeling.

Zane eazyBI Support

Hi,

We at eazyBI are investigating the Jira Next-Gen project import. While basic next-gen project field import is working, not all project customizations are possible to import in eazyBI for now. We already know that there are some obstacles for Jira Software specific field import into eazyBI.

Best,

Zane / support@eazyBI.com

Erna_uildwe

noted. Hope you guys managed to solve it soon.

Tony Padovano

Any update on this? Not having points available in the data pretty much makes eazyBI not usable for next-gen projects

Alec Jasanovsky

When you say "Label" are you using quotes because you're referring to "Labels" of field names - and not referencing the actual field "Labels"?

Zane eazyBI Support

Hi,

Nex-gen projects do not share the same fields for Story Points as traditional projects (next-gen projects have field "Story Points estimate" and traditional projects have "Story Points"). Therefore Software specific measures are not working as expected for nex-gen projects in eazyBI (https://docs.eazybi.com/eazybijira/data-import/data-from-jira-and-apps/jira-software-custom-fields).

However, you may import "Story Points estimate" as any other numeric custom field in e eazyBI and analyze next-gen Projects and Sprints.

1) In eazyBI import options, tab Custom fields, select "Story Points estimate" for data import as a measure and property, and to import value changes.

2) After data import, eazyBI has generated a set of new measures - Story point estimate created, Story point estimate due, Story point estimate resolved, Story point estimate closed, Story point estimate with due date, Story point estimate change, Story point estimate history.

3) You may build Sprint specific measures (sprint commitment, sprint changes, sprint completion, etc.) by defining new calculated measures. Use similar calculations as eazyBI has created for traditional projects.
For example, to get "Sprint Story Points estimate committed."

3.1) Find predefined measure "Sprint Story Points committed" and copy its formula:

( [Measures].[Story Points added],
  [Transition Field].[Sprint status],
  [Sprint Status].[Active],
  -- An issue was in a sprint at a sprint start time
  [Issue Sprint Status Change].[Future => Active],
  [Time].CurrentHierarchy.Levels('Day').DateMember(
    [Sprint].CurrentMember.get('Start date')
  )
)

3.2) Define a new calculated measure for "Sprint Story Points estimate committed" and paste in the copied formula. In the formula, replace [Story Points added] with [Story point estimate added] so it would look like this:

( [Measures].[Story point estimate added],
  [Transition Field].[Sprint status],
  [Sprint Status].[Active],
  -- An issue was in a sprint at a sprint start time
  [Issue Sprint Status Change].[Future => Active],
  [Time].CurrentHierarchy.Levels('Day').DateMember(
    [Sprint].CurrentMember.get('Start date')
  )
)

I hope this approach at least give you some options to analyze Story Points of next-gen projects.

Best,

Zane / support@eazyBI.com

Daina Tupule eazyBI

eazyBI has released default support for NextGen projects including support for Story Points estimates custom field import and default set of sprint scope measures based on Story Points estimates custom field.

Daina / support@eazybi.com

Angel Hernandez_qbb6f6

Hi!

I'm struggling using next gen projects and metrics in Eazy Bi. Does this update allow to combine this story points and issues created, etc?

Do you have a list of measurements and dimensions that are available in next gen?

Daina Tupule eazyBI

Hi,
all who follow this conversation,eazyBI has enhanced support for next-gen projects that allows analyzing Story point estimate and issue type and statuses across projects. For more details, please check out the documentation:

A set of metrics for Story point estimate and Sprint scope analytics. See more about Jira Software.

Changes in predefined dimensions Issue Type and Status; statuses and issue types with the same name are grouped as one, thus allowing to analyze issues by issue types, statuses, transition statuses, or transitions across all next-gen and standard projects. See more about core dimensions.

Changes in predefined dimensions for change history Transition Status and Transition; statuses with the same name are grouped as one, thus allowing to analyze issues by issue types, statuses, transition statuses, or transitions across all next-gen and standard projects. See more about about issue history import.

We also support other next-gen project options, for example, you should find your next-gen custom fields in custom field selection list. They will be marked with project code as well.

Daina / support@eazybi.com

Jack Brickey

Hi Daina, that is certainly great news for EasyBI users! Thanks for sharing here. One thing I encourage you to do is update your member name in the Community according to the Partner Guidelines.

pertinent excerpt ...

Identify yourself as a partner: Make sure the user is aware you are affiliated with a partner company; for example, by placing the name of your company in your user name in {curly brackets} or -dashes- (note that regular brackets no longer work and have been automatically converted to dashes). If you are mentioning your own products or services, make sure you include wording to make it clear that you are affiliated with the company providing those products or services.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-software

addon-com.eazybi.jira.plugins.eazybi-jira