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.

Please bring back the 'custom' date range of 'Last 14 days'

Our organization is required to complete Tempo timesheet every day and that timesheet needs to match our organization online timesheet. In the older version of timesheet there was an option custom - last 14 days. When you chose that option it stayed the default. Now with the newest version of timesheet every time we access the timesheet we first have to set the date range. Very annoying.

  • Guest
  • Jul 20 2020
  • Already exists
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Hlynur Johnsen commented
    August 25, 2020 09:15

    Thanks for the feedback!

    If I understand your use case correctly, this should still be supported in the user timesheet, along with remembering other config options you choose in the timesheet. That said, there was a bug in a few recent versions that caused this to not function correctly. This bug was introduced in version 10.13, and fixed in version 10.16.

    To use this, go to your timesheet, select the date picker and find the words "Last", "Current", "Next" on the right hand side. When you click "Last", the option to specify # of days becomes available. type 14, and Apply, and your setting should be remembered between sessions.

    https://tempo-io.atlassian.net/wiki/spaces/THC/pages/290128330/Selecting+View+Options+in+the+Timesheet+View+-+Tempo+Server

    Please note there is still a minor bug in the # of days input box in that it only has room to display1 digit. We'll fix that soon.

    I'm updating the status of this to "Already exists", but please let me know if I misunderstand your use case, and the problem persists.

    Cheers,

    Hlynur Johnsen

    Group Product Manager - Tempo for Jira