Difference between Tempo Planner and Timesheet

Giovanni Pagliani July 30, 2015
Hello , I have installed Tempo Timesheet for a few days and I'm considering buying Tempo Planner . I 've seen some tutorials and I've read the documentation of Planner, Planner and Timesheet are very similars . What is the difference , the additional features and benefits that Time Planner has more than Timesheet ? I can program the work of teams and users also in Timesheet . 

1 answer

1 accepted

2 votes
Answer accepted
Albert Hauksson July 30, 2015

Hi Giovanni,

That's a good question. Tempo Timesheets and Planner are quite different although they have some similar features. Tempo Timesheets is mainly for logging work in JIRA, generating reports on that work, it allows you to manage teams centrally as well as customers and their accounts. It will cover any of your time / work logging needs. It will also allow you to plan on issues to a certain extent. Individuals can make plans for themselves and Team Leaders are also able to plan/allocate (not to be confused with Assignee) for their team members. The planning features of Timesheets are quite limited but will be enough for some use cases.

Tempo Planner on the other hand is a much more comprehensive planning tool. It will allow teams to plan their work in a great planning interface, they can do long term planning on projects and short term planning for individual issue. Sprint planning is a big part of Tempo Planner allowing you to manage sprints (and create sprints without JIRA Agile) and assign issues within sprints to team members based on their actual availability (lots of things can affect a persons availability).

Tempo Planner will also enable you to get a higher level view of your plans, where you can group your teams together into so called Programs. In the program view you can lay out roadmaps for your teams and projects, get an overview plan health and progress as well as insights into the capacity of your teams and when they will be able to take on the next project.

I hope this answer will clarify the difference between the two add-ons.

Best regards,

Albert Hauksson
Tempo Team 

Dnyaneshwar Ramesh Borase March 15, 2019

Hello Albert,

Thanks for the detail explanation.

Currently,we are using Tempo Timesheet and Tempo Planner on same JIRA instance. 

We are mostly using Tempo Timesheet on daily basis for the time tracking and infrequently using Tempo Planner (only limited users are using).

We would like to know can we use independently? or Is there any dependency of each other?   

If we use only tempo timesheet then will it working fine or it requires to install Tempo Planner?

Thanks for the advance.

Regards,

Dnyaneshwar Borase

Deniz Oğuz
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
March 15, 2019

Tempo Timesheet is a standalone product. You don't need Tempo Planner for timesheet to work.

QA Team May 15, 2019

before we upgrade to tempo 10.2 we use tempo timesheets to log time, plan time (apply leave, off etc) for approval. After we upgrade to tempo 10.2 we realise that plan time can no longer use in timesheets but move to tempo planner. May i confirm whether can we use tempo planner for both log time & plan time for approval and unsubscribe from tempo timesheets

Susanne Götz _Tempo_
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
May 16, 2019

Hi @QA Team ,

Tempo Planner and Tempo Timesheets are two plugins that can be used individually or together. 

Tempo Timesheets focuses on worklogs and reporting on hours logged. Users can plan time for themselves ( in My Work, Calendar view) but other users have no access to their plans. Worked hours can be approved on a weekly / monthly basis.

Tempo Planner is focuses on plans. Users can plan for themselves and team leads ( or other users with the required permissions) can create plans for their team members. Planned time can be approved by team leads. It is not possible to create worklogs or report on worked hours in Tempo Planner. 
When using both plugins, they are sharing information (f.x. plans created in Timesheets will be displayed in Planner).
In case you are only using Tempo Planner, you can use the native JIRA Log work option.

Regards,
Susanne Götz
Tempo team

QA Team May 16, 2019

Based on your reply we will still need both planner & timesheets in which we will have to buy tempo planner. we only need to have a mean to apply plan time (leave) in timesheet but will have to buy tempo planner because of 1 function. anyway to waive the tempo planner license for us as tempo timesheet active users.

Like Federico Scheu likes this
Josie Hoffman September 11, 2019

Hi @QA Team , if your question is you want to have a means of planning or logging planned time (ie leave) for team members, then you don't need Tempo Planner for that. You can do that in Tempo Timesheet. According to this page, https://tempoplugin.jira.com/wiki/spaces/TEMPO/pages/172785882/Configuring+internal+issues+and+activities, it's called creating Internal Issues.

Internal Issues are used to log work on common issues like vacations, sickness and staff meetings. Remaining estimate is not required for issues that are configured as Internal Issues. You would need to be a Tempo Administrator in order to add this issue type to Tempo.

But once you have Tempo Admin rights, here are the steps to adding plan time as an issue type for team members to log time against : https://tempo-io.atlassian.net/wiki/spaces/THC/pages/332267654/Configuring+Internal+Issues+-+Tempo+Server

 

They recommend that you first create a new project for issues you wish to use for internal time, then create issues in that project.  This simplifies viewing and editing permissions, and helps maintain privacy. You can limit View All Worklogs permission to Team Leads, HR Managers and the like.  Creating a dedicated project also ensures all internal issues use the same prefix, such as "INT", and are easy to identify.

I didn't do that. Instead I created my internal issues in the same Jira project as the rest of my epics and just used the prefix: 'INT' before the issue name ex: INT-Vaction; INT-Bench; INT-Administrative Tasks.

Hope this helps!

QA Team September 11, 2019

Thanks Josie on yr reply. We already have the internal issue to track the leave. just that we need approval workflow which can only be found in tempo planner. 

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events