--- title: "Integration with Tempo" canonical: "https://support.appfire.com/space/RFTT/803013104/Integration%20with%20Tempo" format: markdown --- > Macro (aura-html) [Timesheets by Tempo - Jira Time Tracking](https://marketplace.atlassian.com/apps/6572/timesheets-by-tempo-jira-time-tracking?hosting=datacenter&tab=overview), also known as *Tempo Timesheets* or simply *Tempo*, is a robust and widely used time-tracking Jira app. Among other features, Tempo offers Jira administrators the ability to create additional custom work attributes, which users can fill out when logging time on Jira issues. These attributes act like custom fields for work logs, enabling users to provide additional information about the time logged on an issue. Custom work attributes can indicate work types, like design or development, track costs, or record other specific data. To learn more about configuring these work attributes, please refer to the '[Configuring Work Attributes](https://tempo-io.atlassian.net/wiki/spaces/TEMPO/pages/365199745/Configuring+work+attributes)' section in Tempo's documentation. *Rich Filters::Time Tracking Dashboards* offers comprehensive support for Tempo's custom work attributes. More precisely, different Tempo work attributes can be used as statistic types or values in rich filter statistics and chart gadgets. Moreover, Tempo's work attributes are also supported in the [Worklog Query Language (WQL)](https://appfire.atlassian.net/wiki/spaces/RFTT/pages/803012930). This documentation section describes the way *Rich Filters::Time Tracking Dashboards* integrates with Tempo. More precisely: 1. [Support for Tempo's work attributes in rich filter configuration and gadgets](/wiki/pages/resumedraft.action?draftId=803013104#IntegrationwithTempo-section1) 2. [Support for Tempo's work attributes in the Worklog Query Language (WQL)](/wiki/pages/resumedraft.action?draftId=803013104#IntegrationwithTempo-section2) 3. [Worklog visibility permissions](/wiki/pages/resumedraft.action?draftId=803013104#IntegrationwithTempo-section3) 4. [Worklog timestamp](/wiki/pages/resumedraft.action?draftId=803013104#IntegrationwithTempo-section4) ## > Macro (anchor) Support for Tempo's work attributes in rich filter configuration and gadgets Tempo provides several types of work attributes. Below, we list Tempo's work attributes currently supported in rich filter configurations and gadgets. | **Work attribute type** | **Use in rich filter configuration and gadgets** | | --- | --- | | Account | Account work attributes can be used in:
- Rich filter configuration: - Dynamic Filters - Rich filter gadget configuration - can be used as statistic type in: - Rich Filter Statistics - Rich Filter Two-Dimensional Statistics - Rich Filter Pie Chart | | Numeric Input Field | Numeric Input Field work attributes can be used in:
- Rich filter configuration: - Dynamic Filters - Base values in Custom Values - Values in Time Series - Rich filter gadget configuration - can be used as a value in: - Rich Filter Simple Counter - Rich Filter Smart Counters - Rich Filter Simple Gauge - Rich Filter Smart Gauges - Rich Filter Statistics - Rich Filter Two-Dimensional Statistics - Rich Filter Pie Chart - Rich Filter Date Bar Chart - Rich Filter Time Series Chart (via Time Series based on Numeric Input Field work attributes) | | Static list | Static list work attributes can be used in:
- Rich filter configuration: - Dynamic Filters - Rich filter gadget configuration - can be used as statistic type in: - Rich Filter Statistics - Rich Filter Two-Dimensional Statistics - Rich Filter Pie Chart | | Billable | The Billable work attribute can be used in:
- Rich filter configuration: - Base values in Custom Values - Values in Time Series - Rich filter gadget configuration - can be used as a value in: - Rich Filter Simple Counter - Rich Filter Smart Counters - Rich Filter Simple Gauge - Rich Filter Smart Gauges - Rich Filter Statistics - Rich Filter Two-Dimensional Statistics - Rich Filter Pie Chart - Rich Filter Date Bar Chart - Rich Filter Time Series Chart (via Time Series based on the Billable work attribute) | > ⚠️ *Input Field* and *Dynamic Dropdown* work attributes are currently not supported in rich filter gadgets. ## > Macro (anchor) Support for Tempo's work attributes in the Worklog Query Language (WQL) Below, we list Tempo's work attributes currently supported in the [Worklog Query Language (WQL)](https://appfire.atlassian.net/wiki/spaces/RFTT/pages/803012930). | **Attribute Type** | **Supported Operators** | **Values** | **Examples** | | --- | --- | --- | --- | | Account | - `=` - `!=` - `IN` - `NOT IN` - `IS` - `IS NOT` | - the account keys or names | - `Account = ACC1` - `Account in ('Bluecorp', 'Red star')` - `Account is empty` | | Numeric Input Field | - `=` - `!=` - `>` - `>=` - `<` - `<=` - `IN` - `NOT IN` | - numeric value/s | If `Budget` is a Numeric Input Field work attribute:
- `Budget = 300` - `Budget >= 100 AND Budget <= 300` - `Budget in (1, 2, 3)` - `Budget is empty` | | Static List | - `=` - `!=` - `IN` - `NOT IN` - `IS` - `IS NOT` | - static list option name/s | If `Work Type` is a Static List work attribute:
- `'Work Type' = Development` - `'Work Type' in (Development, Testing)` - `'Work Type' is empty` | | Checkbox | - `=` - `!=` - `IS` - `IS NOT` | - `YES`, `NO` - `0`,` 1` - `TRUE`, `FALSE` - `SET`, `UNSET`
`TRUE`,` FALSE` and` SET` are [reserved JQL words](https://confluence.atlassian.com/jirasoftwarecloud/advanced-searching-764478330.html#Advancedsearching-restrictionsRestrictedwordsandcharacters). When used in queries, you need to surround them by quote-marks (single or double). See the **Quote-marks in WQL** note below. | If `Overtime` is a checkbox work attribute, here is how we retrieve the work logs that have this checkbox checked:
- `Overtime = yes` | | Billable | - `=` - `!=` - `>` - `>=` - `<` - `<=` - `IN` - `NOT IN` | - duration values | - work logs where the billable time spent is more than 2 hours: `Billable > 2h` | > ℹ️ *Input Field* and *Dynamic Dropdown* work attributes are currently not supported in WQL. > 📝 ### Quote-marks in WQL > 📝 > 📝 Text search queries, date-time and duration values containing spaces (such as `'2018/10/25 13:20'` or` '4w 2d'`), and reserved JQL words need to be surrounded by quote-marks (single or double). > 📝 > 📝 Because WQL is always used inside JQL queries, the entire WQL query will already be surrounded by one type of quote-marks. If you used one type of quote-mark (single or double) for the entire query, you should use the other type inside the WQL query. For example: > 📝 > 📝 `rfWorklogs ~ "wasUpdated = 'TRUE'"` > 📝 > 📝 You can also use the same type of quote-mark inside the WQL if you escape them using the character `'\'`. For example: > 📝 > 📝 `rfWorklogs ~ 'wasUpdated = \'TRUE\''` ## > Macro (anchor) Worklog visibility permissions Jira and Tempo use different approaches to restrict worklog visibility at worklog level: - **in Jira natively:** it is possible to configure the instance so that for each work log, the user can add visibility restrictions based on project roles and/or groups. To learn more about visibility restrictions at worklog level in Jira, please refer to the [Atlassian's documentation](https://confluence.atlassian.com/jirakb/add-restricted-comments-on-jira-962353957.html) (Atlassian's KB article mentions only the comments but exactly the same setting applies to work logs too). - **once Tempo is installed on a Jira instance:** Jira's native visibility restrictions on work logs are removed/ignored and Tempo provides a different worklog permissions mechanism. To manage worklog visibility rights, Tempo relies on a new project permission called *View All Worklogs*. Without this permission, users can see only their own work logs. To lean more about visibility restrictions at worklog level, please refer to the [View All Worklogs Permissions for a Project in Tempo Timesheets for Server](https://tempo.scrollhelp.site/timesheets-dc/latest/view-all-worklogs-permissions-for-a-project-in-tem) section in Tempo's documentation. Depending on whether or not Tempo is installed on a Jira instance, *Rich Filters::Time Tracking Dashboards* respects the worklog visibility restrictions that apply: if Tempo is not installed, then the worklog visibility rules provided by Jira natively are applied; if Tempo is installed, then the worklog visibility restrictions provided by Tempo through the *View All Worklogs *project permission apply. This applies in all rich filter gadgets and in the [Worklog Query Language (WQL)](https://appfire.atlassian.net/wiki/spaces/RFTT/pages/803012930). > ⚠️ Currently, when Tempo is installed, *Rich Filters::Time Tracking Dashboards* supports visibility permissions granted through the *View All Worklogs *project permission only. Visibility permissions provided through Tempo Team permissions are not currently supported. ## > Macro (anchor) Worklog timestamp Tempo and Jira have different approaches to timestamps in work logs. To learn more about these differences, please refer to the [Why is there a time difference between my Jira worklog and my Tempo worklog?](https://tempo-io.atlassian.net/wiki/spaces/KB/pages/232816644/Why+is+there+a+time+difference+between+my+Jira+worklog+and+my+Tempo+worklog) documentation section provided by Tempo. As a summary: - **in Jira natively:** the timestamp for time logged through Jira natively is the precise timestamp selected by the user in their own time zone. - **once Tempo is installed on a Jira instance: **the default timestamp for time logged through Tempo is midnight on the date according to the user’s time zone. Depending on whether or not Tempo is installed on a Jira instance, *Rich Filters::Time Tracking Dashboards* complies with the timestamp conventions that apply: if Tempo is not installed, then the worklog timestamp is the one provided by Jira, or if Tempo is installed, then the worklog timestamp is the one provided by Tempo.