Description:
We’re looking for the ability to enforce a time-based restriction on worklog entries in Tempo, tied to Jira workflow status transitions.
Use case:
When an issue transitions into a specific status (e.g., “Done”), we want to allow time logging for a limited period (e.g., 7 days). After that defined duration, logging time against the issue should be restricted.
Current limitation:
Jira’s workflow property jira.permission.work.denied applies immediately upon transition and does not support delayed enforcement. Tempo also does not currently provide a native way to enforce time-based constraints relative to status duration.
Why this matters:
Ensures timely and accurate time logging
Prevents retroactive logging long after work is completed
Supports compliance and reporting integrity
Requested capability:
Configure a delay (e.g., X days) after entering a status before worklog restrictions apply
Apply this rule per workflow status or project
Optional: admin override or exception handling
Additional notes:
This capability would ideally integrate with Jira workflow states while being enforced at the Tempo level.
Thanks for considering this enhancement.
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |