The MDX you have written is correct to get count of issues with Hours spent. It is true that such a calculation could take some time in case of many issues and it would be more efficient to pre-calculate this.
Nevertheless in this case the pre-calculation would not provide such a dynamic result. For example it would be possible to pre-calculate that a user updated an issue on a certain date and no longer count if the same user updates issue in the same month (to get the distinct count). Now if this user again logs hours next month, then again the issue would be counted - on monthly hierarchy this would give correct result, but on Yearly level the count would not be distinct as issue would be counted every month it was updated.
Let me know though if you would like this report on some specific Time level and it would not matter for other levels and you would need assistance with the JIRA Misc field to pre-calculate this.
Lauma / firstname.lastname@example.org
This is an advanced solution and some more details could be needed to get it working correctly for your case.
Could you send a request to email@example.com for this? Please add an additional information about you report. Could you mention any other dimensions, measures you would like to use in the same report? What would you want to use in Rows, Columns, and Pages?
More information would help us better assist you.
Daina / firstname.lastname@example.org
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot