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.

Linking Team role to worklog rather than JIRA issue

A JIRA issue moves through a workflow that one or may people may work on and log time against at any point, they may not be the same role . Therefore having a role assigned to an issue assignee means all your exported worklogs will have a team role or it may be incorrect as they are not the assignee anymore.
This leads to poor & inconsistent reporting.

  • Guest
  • Mar 12 2020
  • Future consideration
Tempo Products Tempo Timesheets
Tempo Platform On-Premise
  • Attach files
  • Simon Cunningham commented
    4 Aug, 2020 08:24pm

    I second this request. We have yet to figure how we can actually make use of Teams/Roles. For a given project a Team is assigned, but when someone logs time against an issue in that project there is no way to indicate the role in the work log. Assigning role to the issue makes no sense. It may be that the user is filling multiple roles, so we must be able to identify the role when the time is logged. If Teams were handled like Accounts, that would be great. A default team could be set (per project / user, perhaps), and a default role (per project / user). This could be overridden in the work log as necessary. It may be helpful to make the Team / Role hierarchical such that Role is filtered by Team i.e. select the Team then pick from a list of Roles in the team which are assigned to you.

    Not supporting multiple teams/roles per project is certainly workable in most cases (for us), except for Service Desk projects that can have issues across many customers/accounts.

    I looked at the REST API to see if I could use it to present a list of values to be consumed by a dynamic work attribute list. The Tempo REST API documentation really needs to be updated as there are holes. For example, there is a Teams API, but that isn't documented. At a glance it doesn't appear that there is a way to determine the role of team members via the Teams API, or even return a list of roles, which kills this idea...I guess we have no choice at the moment but to create a static list.

    At the end of the day, we will be exporting worklog reports and importing them into QuickBooks Online as timesheet entries so invoices can be generated for clients, and we need to be able to determine rates based on the role. I understand that Tempo has Price Tables, which are associated with the roles, but there doesn't appear to be a way to export costs in the timesheet reports, so we can't use them.

  • Hlynur Johnsen commented
    3 Apr, 2020 09:23am

    Thanks for the feedback. This is a subject we've been considering in the recent months. In our cloud products, we added a Group by Role to the logged time and planned time reports. The caveat there is that we can only report on 1 role per employee - and the way we select the role is by taking the most recent one.

    So I'd be interested to hear whether you generally have a 1-1 mapping between individual employees or whether the same employees are sometimes members in different teams with different roles?


    Hlynur Johnsen

    Group Product Manager - Tempo for Jira