Tempo Ideas

I did not want to believe this feature is missing in "the time tracking tool" referenced all the time. Advanced Roadmaps an its parent issues like initiatives is a jira core feature and cannot be handled with timesheets in DataCenter while cloud can deal with it :-(

Essential for visibility of the financial manager module, so you don't have to take out Excel and make Tempo useful

This is really strange for an established tool like Tempo not to allow grouping by initiatives and only by Epics and Issues. How are people meant to generate reports and track time spent on projects at a higher levels such as Initiative level?

https://ideas.tempo.io/ideas/T-I-295 has just been released to TempoLabs for Cloud, so you obviously agree to the need for this type of grouping.

Can you please confirm when the development of the on-premise equivalent will begin?

CCM

Checking in to see if this idea / request is going to get implemented. I'm fully with @Marton Lipcsik on this one, Epic's can not represent everything. We work with a completely different hierarchy Vision -> Strategic themes -> Objectives -> Initiatives -> Epics and we want to be able to report based on objectives / initiatives for example.

Yea, I also want to have grouping by issue type. In my case I plan to group issues by bugs, tickets, stories. Another option to add filter by issue type

Hi,

We have a number of teams who are looking to group by Story on their Tempo reports. Epic is too high level, Issue is too low level.

I agree with Marton, that being able to group by the generic "Issue Type" would provide more flexibility instead of supporting Story, but then someone may want Bugs V FR's etc.

CCM

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

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

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

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".