Tempo Ideas

Tempo Timesheets should be able to display and filter on Jira custom fields that are protected by the Add-on Protected Fields plugin, by providing a supported integration/whitelist mechanism or API permission flow so protected fields can be made available safely to Tempo.

Current behavior: We have a custom field called “Projects” (used to record project/customer on Jira issues). That custom field is protected by the Add-on Protected Fields add-on, so it does not appear as an available filter or column in Tempo Timesheets reports and timesheet filters. Tempo currently reads field data directly from Jira; however, third-party protection prevents Tempo from accessing the field.

The field is not visible in Tempo Timesheets due to protection by the Add-on Protected Fields add-on.

Requested behavior: Provide a supported way for Tempo Timesheets to access protected custom fields (read-only for reporting) when a Jira admin explicitly grants Tempo permission. This could be implemented as a whitelist/consent mechanism in the Add-on Protected Fields add-on, an API scope that allows selected apps to read protected fields, or a Tempo setting to request/obtain access. The goal is to allow teams to report on and filter time by these protected custom fields while preserving the protection model and security controls enforced by the protected-fields add-on.

Use case: Our team needs to run reports and timesheet filters by our “Projects” custom field (customer/project). Because it is protected, it does not appear in Timesheets’ filter list, preventing accurate reporting by customer/project.

Business value: Enables accurate time reporting and billing by customer/project for companies that use the Protected Fields add-on for security/compliance. Reduces manual workarounds (export/import or manual tagging), prevents reporting gaps, and improves adoption of Tempo Timesheets among organizations that use field protection.

I’d appreciate if this could be considered in the near future, as it’s essential for our daily work and would make us much more efficient with Tempo Timesheets. Best regards, Ahmad