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.

Use of Start and End date in Tempo teams when running Logged Time Report

When running logged time report using Tempo teams is it not taking into account the joining and leaving dates aligned to the resources. This has becoming very problematic ensuring all of the required time is being logged for projects/portfolios. Below is an example:

Enjamuri, Vinay joined the HRSD team on 12/6. When I run the logged time report with the HRSD team, which Vinay is part of (see attached screen shots), and has a joining date of 12/6 it does not take the date into consideration. This is indicating he has not logged all of his required time which is not accurate. If you look at the logged time report on the right is has 168 hrs required through 12/26 for Vinay. It should be 144 hrs. The same scenario occurs if you a percentage on the resource. It does not take that into consideration as well.

Link to Tempo Team https://jira.service.tools-pi.com/secure/Tempo.jspa#/teams/team/1547/


  • Donna Seymour
  • Jan 5 2022
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Janice Borel commented
    27 Jan 04:20pm

    When associates transfer divisions within the company it is extremely difficult to reconcile the data. This would help significantly with the administrative burden of reconciliation.

  • Eileen Banasiak commented
    27 Jan 04:05pm

    We are a large company and resources often move from team to team. We constantly use the joining and leaving dates for team members. If this is not fixed, the logged time reports will continue to provide inaccurate reports.

  • Eileen McEneaney commented
    20 Jan 03:37pm

    Must have for Sever also

  • Thomas Petite commented
    5 Jan 06:56pm

    This is so important and a must-have. The description and why it is needed is well articulated and I have the same issue trying to ensure the accurate number of hours are logged each month.

  • Donna Seymour commented
    5 Jan 05:56pm

    This is critical functionality to ensure the accurate number of hours are logged each month. We can't relay on the required hours since it is not accurate if the resource was not part of the team for the full month.