The report does not import directly because my data cube uses Feature link, not Epic link. I tried building the measures that the report uses individually. When building the ‘Epic end date’ measure, my account does not produce (have as an option) ‘CurrentHierarchyMember.Key’. The .Key is not an available option after CurrentHierarchyMember.
In this string I am replacing Epic Link with Feature Link: Descendants([Issue.Epic].[Epic].GetMemberByKey([Epic Link].CurrentHierarchyMember.Key
You can successfully convert the Epic burn-down report to the Feature burn-down report. This requires replacing “Epic Link” dimension with the “Feature Link” dimension in the report and updating calculated measures to take attributes of Feature instead of Epic.
Measures that need updating or better equivalents for Feature:
“Epic Start date” and “Epic End date”–The report uses calculations to assess those dates based on issue changes. If you have start and end dates assigned to Feature issues, that woudl be the better option. Those two dates are the most essential building blocks for the report as they affect all other calculations and the report timeline.
For example, maybe Feature has assigned Target start and Target end dates, which you can import as properties and use instead for the report.
“Time in Epic”—Make an equivalent “Time in Feature” based on the Feature Start and Feature End dates from the previous point. Then, filter rows by the new measure “Time in Feature” and remove the filter “Time in Epic.” (Create reports).
For “Burn-down issues” and “Burn-up issues,” update “Epic End Date” with the respective Feature End date.