We’d like to raise a feature request and seek clarification regarding time tracking behavior in Tempo Timesheets, specifically around the lack of a start/stop time logging feature and discrepancies in activity-based time suggestions.
Our team is exploring ways to improve time tracking accuracy in Jira. One of our colleagues, Muthuselvam Ragu, highlighted the need for a start/stop timer similar to what’s available in EIP (Enterprise Issue Portal), which allows users to log time more precisely when switching between multiple tasks.
Currently:
Tempo does not offer a native start/stop timer.
Time suggestions in the calendar view are limited to certain Jira activities.
Overlapping activities prioritize calendar events over Jira activity logs.
Manual timesheet updates are error-prone and time-consuming, especially when users forget to log time while multitasking.
We’d like to request the following enhancements:
Start/Stop Timer Functionality:
Allow users to start and stop a timer directly from the issue view or Tempo panel.
Automatically log time entries based on active work sessions.
Improved Activity Tracking:
Expand the scope of Jira activities that generate time suggestions.
Provide clearer logic or customization options for how overlapping activities are handled.
Optional Prompt for Time Logging:
Prompt users to log time when switching issues or closing an issue tab, to reduce missed entries.
Accurate time tracking is essential for project reporting, billing, and productivity analysis. These enhancements would significantly reduce manual effort and improve data reliability across our teams.
Please let us know if these features are on your roadmap or if there are any existing workarounds we can explore.
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |