Best practices for setting up Tempo Timesheets

Abstract

How to get started with Tempo Timesheets and what are the best practices

Setting up Tempo Timesheets can be fairly straightforward, but there are things that you can do to improve the experience for both the administration and usage of Tempo Timesheets.

Here are some ideas:

  • Give access to Tempo Timesheets to a small number of stakeholders at first for evaluation. Then when you’re ready to implement Timesheets, roll it out to all employees who need to use it. You can easily control access with a Jira group that you set up for all Tempo users - see Create and update groups (Atlassian documentation) and Giving Access to Tempo Apps

  • Create different Jira groups for your Tempo needs according to your company. Then it's easy to add or remove users from these group as situations change: no need to grant permissions on an individual basis. Here are some suggestions:

    • All Tempo users - if only certain Jira users in your company need to use Tempo, create a group with only them in it. Then you can give access to Tempo Timesheets using this group. 

    • Tempo administrators - high-level admins who have permissions to manage Tempo in your company.

    • Tempo Account administrators - admins and financial managers who will be creating and using accounts for billing and/or tracking Capex and Opex.

    • Tempo Team administrators - team leads and managers who will be creating and possibly managing teams in your company.

    • Tempo teams - create one Jira group for each team you plan on creating, or one group for each department. Then you can add all members to a team in one click using the Bulk Add Members button - see Creating Tempo Teams

  • Create an “Internal” Jira project and issues so that employees can log their time to non-work company issues, such as sickness, vacation, meetings, travel, or company events - see Configuring Internal Issues and Create a new project (Atlassian documentation).

  • Create a separate Permission Scheme for this Internal Jira project and assign your Jira group that includes all Tempo users. This way, the permission scheme will not be used for work-related Jira projects - see Managing project permissions (Atlassian documentation).