1. Tempo Avatar Tempo
  2. Prime
  3. servertimesheet
  4. Issues

Enhance Project Pivot Report

Issue #326 resolved
Former user created an issue

In our instance of JIRA, we have components like Artist and Engineer. This helps us differentiate tasks by disciplines. It's possible on our projects to have several artists or engineers. As such, we are often interested in the summation by component instead of by user.

Can the Project Pivot Report be enhanced such that you can choose what value is being summed over a particular time interval? Examples:

  • Sum by component (as described above)
  • Sum by label
  • Sum by some custom value

Comments (20)

  1. Andriy Zhdanov

    This is possible with Timesheet Report to group by any issue field. Could you please try if it suites your needs, and let me know if you still need the same or similar functionality for Pivot Report?

  2. Former user Account Deleted

    I'm playing around with the Timesheet Report, and it's not offering me the info I'm after. (Or at least it's not with my current config and in a way I can digest.)

    I'll attach a few files to demonstrate in just a moment.

  5. Former user Account Deleted

    What I want it to look like (except imagine it says "Project Management", "Artist", etc) instead of users up top.

  6. Andriy Zhdanov

    May be I don't get it, but I think problem is that Components is not single value field. So it's not grouped properly and can't be used for Pivot Report in future. In the example you have one issue with three components, so it's impossible to separate worked hours by component.

    Please let me know your thoughts.

  7. Former user Account Deleted

    ahh ... yeah. i can see the confusion. for our organization, component is a single value field since our tasks have exactly one component. but i do see your dilemma for generalizing the plugin across all JIRA instances.

  8. Andriy Zhdanov

    But even in your example it looks like one issue has all three components assigned. If you would have three issues, and each different component you would get what you'd like with timesheet. Then similar would be possible with Pivot in future.

  9. Former user Account Deleted

    what you see above includes our two issue types: ticket and task (child of a ticket). a few things to note:

    • tickets are a container of like tasks. no time is logged to the ticket.
    • tasks have exactly one component.
    • components of tickets are the union of its tasks' component.

    speaking outside our situation and when it comes to how core JIRA currently handles summing hours across multi-components issues, it counts the hours against both components. for example:

    • issue have components CompA, CompB.
    • user1 logs 5 hours to issue
    • user2 logs 2 hours to issue

    JIRA then sums it so 7 hours is logged against CompA and also 7 hours is logged against CompB. I'd be satisfied with the plugin behaving in the same manner as the core JIRA product in such circumstances.

  11. Former user Account Deleted

    I'll assume you mean for me to uncheck it for Time Sheet Report. I'll attach what I see. The problem here is it's only showing me on the report instead of the entire team. I see I can also configure it to select a user (but only one), a group (but only one), a role (but only one).

    It's that "but only one" that keeps getting in the way of giving me what I want in one single view. :)

  13. Andriy Zhdanov

    Right, Timesheet report is for user or group, though you may specify 'jira-users' for all users

  14. Former user Account Deleted

    Yep. Sure enough ... jira-users will do the trick. I'm not quite fond of how horizontal it becomes, especially over large date ranges, but it does give all the data I'm looking for.

  15. Former user Account Deleted

    Thanks for the support and patience. I'm an idiot for not seeing jira-users in the drop down. ;)

  16. Andriy Zhdanov

    No problem, glad it suites your needs now, and I'll keep this request open for Pivot enhancement as you described. I think of it for long time already, to make it more flexible, your example is great!

  21. Log in to comment
Assignee
Type
proposal
Priority
minor
Status
resolved
Component
–
Version
2.8
Votes
0
Watchers
1