Here I would like to be able to group by teams and see the account details grouped under there.
For Example:
Program contains - Team 1, Team 2 and Team 3
Accounts contains CapEx and INTERNAL
Team 1
CapEx Hours Hours % CapEx Program Hours %
INTERNAL Hours Hours % Internal Program Hours %
Total Team 1 Hours
Team 2
CapEx Hours Hours % CapEx Program Hours %
INTERNAL Hours Hours % Internal Program Hours %
Total Team 2 Hours
Team 3
CapEx Hours Hours % CapEx Program Hours %
INTERNAL Hours Hours % Internal Program Hours %
Total Team 3 Hours
Program (Total)
Program Capex Hours Program Capex Hours %
Program Internal Hours Program Internal Hours%
Tempo Products | Tempo Timesheets, Tempo Reports |
Tempo Platform | On-Premise |
Fully agree with Mykenna Cepek.
Group by Tempo Team would be amazing helpful for internal accounting between Teams.
I need a report that groups by customer. The idea to do that was merged here but this looks like a different idea. Will this idea give me group by customer?
I'm very concerned that T-I-283 "Group by Customer or Category..." is getting lost by being merged with this one.
Adding just "Customer" to the list of Group-by options in a report seems very straightforward and extremely helpful. My leadership is awfully confused why their seemingly basic request for such reports isn't possible with Tempo.
Adding "Category" is quite similar. From a leadership and finance perspective, grouping by CapEx, OpEx, Billable, etc is a no-brainer.
This request (T-I-191) doesn't even mention Customer, and it intermixes grouping by Category with additional and orthogonal needs (grouping by Team and Account).
Note that Group-by Account is already supported.
I feel that Tempo user needs would be better served by having this request (T-I-191) focus on simply "Add Group-By Team" as one feature. I'd further suggest that T-I-283 be split into two separate requests: "Add Group-By Customer" and "Add Group-By Category".
That way, progress on any one of those three more specific requests would be solve current user-base problems. Let's not hold up forward motion by keeping these requests overly complicated.