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.

Multi-level approvals: Require more than one approver on a Timesheet

Administrator should be able to define how many approvers are needed in order to have a Timesheet/Account fully approved.

  • Guðrún Fema Ólafsdóttir
  • Mar 25 2020
  • Future consideration
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Admin
    Kathryn Vargas commented
    5 Mar 03:47pm

    Thanks to everyone who has booked a call with us so far. We understand most of you might not have the time, so we've prepared this short survey. If you have two minutes to spare, we'd appreciate your feedback at this stage to help us shape and prioritize the right improvements.

    Best regards,
    Kathryn Vargas
    Tempo Product Management

  • Admin
    Kathryn Vargas commented
    28 Feb 09:46pm

    Hello all – thank you for your patience and feedback. An update: we're now actively working on building this feature in Timesheets for Jira Cloud and would love to learn more about your use cases. If you have time for a quick call, we hope you find a slot here.

    Looking forward to speaking with a few of you, and we'll keep you all posted on our development.

    Thank you,
    Kathryn Vargas
    Tempo Product Management

  • Mykhailo Bentsa commented
    14 Dec, 2023 11:01am

    I wish this to be implemented on Cloud platform also

  • Cláudia Ferro commented
    14 Dec, 2023 10:35am

    Great feature, it would be very appreciated

  • Guest commented
    25 Jul, 2023 04:13pm


    This would be a benefit for the approval system where team members are working across 2 or more projects and need different people to sign off areas of work

  • Sami Awad commented
    11 May, 2023 02:09pm

    I support this idea. My customer wants to have weekly approval by team lead and monthly approval by project lead.

  • Ivar Brundtland commented
    13 Dec, 2022 09:56pm

    ����

    Sendt fra Outlook for iOS
    ________________________________
    Fra: Tempo (Christopher Castine)
    Sendt: Tuesday, December 13, 2022 5:49:58 PM
    Til: Ivar Brundtland
    Emne: Multi-level approvals: Require more than one approver on a Timesheet status has changed to Future consideration

  • Guest commented
    16 Sep, 2022 08:04am

    Can this be implemented on Cloud as well?

  • Martin Altenberger commented
    9 Mar, 2022 01:31pm

    Multi-level approvals for logged hours and for billable hours would be awesome

  • Florian Royer commented
    13 Dec, 2021 02:13am

    Is it planned also for the Cloud version please ?

  • Gerhard Mesch commented
    30 Aug, 2021 09:06am

    Yes would be a good feature and I would like if the approval chain is derived from the teams.

  • Tania Rey Labandeira commented
    21 Apr, 2021 02:31pm

    Required function for people working on multiple teams

  • Michael Mohr commented
    25 Feb, 2021 07:58am

    We have a slightly other use case.

    We need different timesheets for a user for a period that he can submit to different time leads. These different timesheets should include his worklogs for different projects that must be charged to different customers. And so these project(s) specific timesheets needs to be approved by the specific project(s) managers. And in addition to that the user also needs to worklog non chargeable work and the timesheet for these hours need to be approved by his disciplinary manager.


    So summarized a possibility is needed to somehow define which worklogs of a user get part of which of his different timesheets in one period.

  • Kosh Sarkar commented
    12 Nov, 2020 04:33pm

    Having this feature would really help our Organization. The lack of it is making us consider other solutions. We would like to be able to specify multiple approvers, where the approver does not need to be part of the team and could be anyone in the instance.

  • +11