I use this code to get the original estimated workload in which time has been logged.
Then I get the sum of all on weekly basis. The problem I have is there are issues that are counted several times between 2 different weekdays. I guess it's because time has been logged into 1 issue several times in different weekdays.
I want to exclude them and I don't know how.
Calculated member 1 /*Return the original estimated based on the list of issues filtered */ Sum( Filter( /*All issues of the CurrentMember (e.g. Building) that started*/ Descendants([Issue].CurrentMember, [Issue].[Issue]), [Measures].[Hours spent] > 0), /*We retrieve the workload planned for issues we started to work on*/ ([Measures].[Original estimated hours], [Time].CurrentHierarchy.DefaultMember) )
Calculated member 2 Sum( PreviousPeriods([Time].CurrentHierarchy.DefaultMember), ([Measures].[member 1],[Issue Type].CurrentHierarchy.DefaultMember))
Your assumption is correct - Filter with Hours spent will retrieve you an issue for each time period when any hours spent are logged.
If you would like to filter all issues with any hours spent then you could use Hours spent in a tuple with Time current hierarchy default member. In addition, you need to define in which Time period you would like your issues to appear to and any property could do a job.
For example, you could use Issue property ‘Issues created’ to retrieve issues on Time period when they were created and then apply an additional filter with hours spent and default time member to limit to only those issues with logged hours.
Please try this code:
Sum( Filter( /*All issues of the CurrentMember (e.g. Building) that started*/ Descendants([Issue].CurrentMember, [Issue].[Issue]), DateInPeriod([Issue].CurrentMember.Get('Created at'),-- all issues at time when they were created [Time].CurrentHierarchyMember) AND ([Measures].[Hours spent], [Time].CurrentHierarchy.DefaultMember) > 0), -- additional filter limits to only thoses issues with hours spent /*We retrieve the workload planned for issues we started to work on*/ ([Measures].[Original estimated hours], [Time].CurrentHierarchy.DefaultMember) )
Daina / email@example.com
Welcome to your weekly Jira Ops Early access program update, where we’re sharing news and updates on Jira Ops' progress as we work toward our 1.0 release. If you ever want to drop us feedback or idea...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs