Common Timesheet Reporting Use Cases

On this page, we have collected some of our customers' common reporting use cases, and we also show how they can be achieved with the new Timesheet reporting.

Time on Parents and Issues by Users in a project

• Hierarchy and grouping:

  • User

    • Parent Issue

      • Issue

• Goal: how much time each user spends on each task and on Epic in total

My team’s work based on task types

• Hierarchy and grouping:

  • Issue type

    • User

      • Issue

• Goal: how much time the TEAM spent on each issue type, e.g. with bugfixes and individual issues

Time per Customer (custom field)

• Hierarchy and grouping:

  • Customer (CF)

    • Issues

• Goal: how much time we work for each customer

Work type distribution based on Issue tpyes

• Hierarchy and grouping:

  • Project

    • Issue type

• Goal: How much time spent on bugs, stories, etc.… how the project is performing

Simple Project work report

• Hierarchy and grouping:

  • Project

    • Users

      • Worklog

• Goal: Check our team’s work regularly

Billable hours for customers

• Hierarchy and grouping:

  • Customer (custom field)

    • Invoice number (custom field)

      • Billable

• Goal: to create report that tell us how many hours can be invoiced for each customer

Work distribution by tags on projects

• Hierarchy and grouping:

  • Project

    • Tags

      • User

• Goal: to see how many hours our team spent on each work category

Multi level hierarchy report (Advanced Roadmap)

• Hierarchy and grouping:

  • Level 3

    • Level 2

      • Level 1 (Epic)

        • Level 0 (Standard types)

          • Sub-tasks

• Goal: Track hours spent on each advanced level

Sprint report with time tracking

• Hierarchy and grouping:

  • Project

    • Sprint

      • User

        • Issue

• Columns: Estimated, Remaining

• Goal: Check how many hours are spent in each sprint, and what were the estimations