Charting Story Points for Cross-functional Teams

[daina.tupule]

eazyBI included the option to build custom hierarchies based on additionally imported properties for sprint dimension with version 6.1.
Here are two community posts with examples on how to use this option to build hierarchies by sprint start date (weekly) or by sprint naming pattern:

Sprint date (weekly):

Aggregate Sprint By Name

Here is an example of REST API that would import Week cycle as Sprint property. This Sprint property will pick the Sprint start date and show it to the Monday of that week, and import the property with this pattern: %yW%U, %b %d %Y, for example, 20W39, Sep 28 2020 - year, week number, and week start date) To use this code: In Source Data (where you already have Jira as a data source), select “Add new source application”. Chose the option to “import definition” and paste in the code below…

Sprint naming pattern:

Combining different teams sprints into one

With version 6.1 we added a new to create custom hierarchies in some dimensions, including Sprints. You would like to import custom properties for sprints to represent a potential grouping mechanism. For example, you can import a property cycle for Sprints with additional data import. Then you can use this custom property Cycle to build a new custom hierarchy in Sprint dimension and group sprints by cycles dynamically. Import additional property to Sprint based on Sprint naming pattern XX Spr…

With version 6.4 we added a default Sprint hierarchy by Sprint status. It allows using this dimension to work with the currently active Sprint or use more efficient filtering for issues closed in any sprint.

Daina / support@eazybi.com