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.

Make historical data on workload accessible

For reporting reasons it would be great to get access to the historical data on workload assignments (secure/Tempo.jspa#/settings/workloads). At the moment only the currently assigned workload-scheme is visible, we'd like know when an employee changed from 80% to 100% to 30%, i.e. during partial paternal leaves or the like. Are there any plans to extend this similar to team-assignments (i.e. date-based)?

  • Guest
  • Apr 21 2020
  • Likely to implement
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Taras Tsiutsyk commented
    9 Jan 03:17pm

    We need this as well!

  • Pavel Parma commented
    7 Dec, 2023 12:30pm

    We are In need for this too as we are trying to measure real and planned utilisation of our resources and the accurate available capacity over time is crucial for such reporting and monitoring.

  • Simon Sahli commented
    7 Nov, 2023 08:52am

    We have based our Flex time (over- under time) based on the Tempo data and changes in workload can mess this up. So if we could just have a date when a user changes from one workload scheme to another then this would help us a lot.
    Thanks!

  • Marcel Bernhardt commented
    10 Aug, 2023 06:17am

    This has been a big problem for us for years.

    Parental leave, adjustment of the weekly working time by changing the working time model, as well as the holidays would have to be fixed for the past.


    It regularly shatters our data and overtime, which is very much against Tempo and has often caused resentment.

    We need really this function.

  • Michael Mohr commented
    27 Jul, 2023 10:19am

    Unbelievable that historic workload reports will be wrong. This is a big problem for us, as currently many workload scheme changes was necessary.

  • Volker Heim commented
    19 Jul, 2023 09:53am

    We urgently need this functionality. Hope this will be implemented soon

  • Alexandre Allart commented
    21 Jun, 2023 03:19pm

    Hello,

    Do you have any news about this feature?

    Best regards,

  • Dan Lemon commented
    11 Jan, 2023 04:08pm

    Is this something that can be built for the Cloud version?


  • Volker Heim commented
    16 Dec, 2022 02:12pm

    For us this is really an important functionality for the Review Reporting (e.g. look back and find out about how many projects whre overbooked based on the settings at that time.

  • Guest commented
    18 Oct, 2022 08:32am

    What happened to the implementation of the idea?

    Currently there is no start-/end date for workload configurations.

    Best regards,.

    Benny Nestler

  • Teresa Hornung commented
    6 Dec, 2021 08:30pm

    its exactly the same. We are working with working students and freelancers and the capacity differs from time to time (e.g. working students normally work 20h / weeek, during semester break they can work up to 40h/ week or with freelancer they sometimes work 16h/ week and in project peaks they support us up to 40h/ week). It would be great to get that update !

  • Daniel Lowe commented
    17 Sep, 2021 12:14am

    To be honest I'm not sure this idea will help in my situation for Planner, I'm wanting to report at a team level going forward but adding a leaving date to an employee only removes them if the reporting period doesn't include any dates they're available.

    Seems like quite a flaw in reporting for Planner

  • Daniel Lowe commented
    16 Sep, 2021 11:57pm

    This impacts Planner reporting also per
    https://tempo-io.atlassian.net/servicedesk/customer/portal/6/TCS-31146

    it makes the planner reporting looking forward at capacity almost useless from x date forward without being able to end date a workload for a specific team member as the Required hours and Planned % data is incorrect where someone is not available from x date.

  • Tilman Muerle commented
    25 Mar, 2021 07:45am

    Is there any update on this?

  • Guest commented
    9 Nov, 2020 03:57pm

    Would really be great to also have a column with the sum of all the overtime accumulated through the different months, without having to do it manually after the export.

  • Jeff Schumacher commented
    11 May, 2020 06:20pm

    This comment applies more to the 3 "merged" ideas attached to this idea. When we moved from monthly to weekly time reporting, tempo "reopened" all the previously submitted/approved timesheets. This caused a HUGE amount of confusion and I had to write code to resubmit/approve all time sheets back to the beginning of the year.

  • Hlynur Johnsen commented
    22 Apr, 2020 06:06pm

    Thanks for the feedback!

    We are currently looking into adding support for start and end dates of workload and holiday schemes which would allow for accurate historical reporting on worklog data. At the moment I do not have an ETA, but I'm updating the status of this idea to "likely to implement".

    Cheers,

    Hlynur Johnsen

    Group Product Manager - Tempo for Jira