Tempo Ideas

The Problem:

Currently, it is too easy for users to log time and submit timesheets without an associated Tempo Account. This creates a massive manual "cleanup" task for administrators at the end of every month.

Furthermore, because Tempo registers worklogs in Jira under the system user "Tempo Timesheets" rather than the individual user, standard Jira JQL filter subscriptions (e.g., worklogAuthor = currentUser()) do not work. This prevents us from automating personal reminders to users to fix their own missing accounts.

The Proposed Solution:

We are looking for two specific improvements:

1. Native Submission Validation: Add a global setting that prevents a user from clicking "Submit for Approval" if any worklog in the period has an empty "Account" field.

2. True Worklog Attribution: Ensure that when Tempo syncs worklogs back to the Jira issue, the Jira worklog entity reflects the actual user as the worklogAuthor. This would allow native Jira automation and JQL subscriptions to function correctly.

Business Impact:

• Data Integrity: 100% of hours will be correctly billed/allocated to Accounts.

• Reduced Overhead: Eliminates hours of manual reporting and "chasing" users for corrections.

• User Accountability: Allows for automated, personalized nudges rather than manual, organization-wide pestering.