Tempo Ideas

Welcome to Tempo’s Idea Portal! Your suggestions are valuable to us and help us make our products even better.
Below is a list of ideas for Tempo, so please search, review and vote for those that would help you the most. We encourage you to add an idea if you don’t see it listed. You can stay updated on the work we are doing here at Tempo by contributing to this page.
To learn more and see our Frequently Asked Questions, click here.

Group by issue type in Tempo report

I would like to be able to group by issue type in Tempo reports, so that I have concise report on how much my teams invest on epics, bugs and other todos

  • Guest
  • Mar 15 2021
  • Future consideration
Tempo Products Tempo Timesheets, Tempo Reports
Tempo Platform On-Premise
  • Attach files
  • dave gelinas commented
    17 Mar 08:56pm

    Just started using this today and still trying to wrap my head around why this ability is not already there.


  • Cristian Iorio commented
    26 Jan 02:07pm

    Our customers would enjoy this feature too. They need to group worklogs by custom issue type, also to differentiate various project types.

  • Ye Fung Tchen commented
    14 Jul, 2021 03:27pm

    We have issuetypes which basically are above epic level and it would be great if we could group them together in the reports.. it is really annoying to aggregate all the hours of epics together to see all the worklogs of the above-epic-issuetype

  • Marton Lipcsik commented
    17 May, 2021 07:20pm

    I just wanted to create an idea, when I found this one.
    Group by issue type would rise the business value of Tempo reporting.

    Issue type cannot be just the Atlassian default (task, subtask, bug, epic, story, etc..), but JIRA user can define his own issue type to represent his business entity.
    "Custom order" or "presales" or "deliverable" can be issue types as well.

    With grouping by issue type, Tempo customer could group worklogs by "presales" type issues, "deliverable" type issues, etc...just how his business is represented in JIRA.

    Now group by "EPIC" is the only issue type usable in grouping, but EPIC cannot represent "everything".