Logged by time and Remaining estimated hours

Questions & Answers
1

Hi,

I was wondering why the Remaining estimated hours_ is the same for the different teams. If should be different. The teams are basically a group of users logging time. I’m using the Logged by field to group users.

image
image831×278 5.65 KB

This is my formula for Remaining estimated hours_

CASE WHEN
[Measures].[Hours spent] > 0
THEN
(
  [Measures].[Original estimated hours],
  [Logged by].CurrentHierarchy.DefaultMember
) * 1
END

What am I doing wrong ?

2

Hi @Karim_Momo,

Measure “Hours spent” is taken from work logs, and you can combine it with the “Logged by” dimension to group logged work by users and user groups or teams. On the other hand, measures “Remaining estimated hours” and “Original estimated hours” are from issue fields, not work logs. Those measures don’t work with the “Logged by” dimension. You can combine “Remaining estimated hours” and “Original estimated hours” with the “Assignee” dimension.

To compare the logged hours with the original and remaining estimate for the Logged by users, you can build a report as follows.

  1. Choose one dimension representing Jira users who worked on issues and are assigned to issues. In your case, set the “Logged by” dimension on report rows.

  2. Select measure “Hours spent” to see logged work by each use. The standard behavior of measure.

  3. Create a calcauted measure to show the original estimated hours of issues assigned to the user. For the calcaution, use function GetMemberByKey to look up the user in the Assignee dimension matching the “Logged by” user name:

    (
  [Measures].[Original estimated hours],
  [Assignee].[User].GetMemberByKey(
    [Logged by].CurrentMember.Key),
  [Logged by].CurrentHierarchy.DefaultMember,
  [Logged by Team].CurrentHierarchy.DefaultMember
)

    Note the calculation example above works when individual “Logged by” users are on report rows.

  4. You can modify this calculation further so it would also work for calcauted members grouping “Logged by” users into teams and for the “Logged by Team” dimension.

    Sum(
  --set of logged by users in selected team
  DescendantsSet([Logged by].CurrentMember,[Logged by].[User]),
  --for each user in the team look up the original estimated hours
  CASE WHEN
    ([Measures].[Hours spent],
    [Logged by].CurrentHierarchyMember,
    [Logged by Team].CurrentHierarchyMember) > 0
  THEN
  (
    [Measures].[Original estimated hours],
    [Assignee].[User].GetMemberByKey(
      [Logged by].CurrentMember.Key),
    [Logged by].CurrentHierarchy.DefaultMember,
    [Logged by Team].CurrentHierarchy.DefaultMember
  )*1
  END
)

Check out the Demo account to see a few more examples of how you can analyze logged hours by “Assignee” and “Logged by” users and what the difference is: Logged hours by user on assigned and unassigned issues - Issues - Jira Demo - eazyBI

And here is a training video explaining the concept of looking up the members in one dimension to show the values for a similar dimension: Advanced MDX: Recipe to Change Report Context.

This Community post also uses a similar concept using GetmemberByKey(): Original estimated hours & Hours spent by "Logged-by" and "Assignee"" - #2 by nauris.malitis.

Best,
Zane / support@eazyBI.com