We are looking to implement strict work-logging compliance by preventing users from logging time against specific issue statuses. While we are aware this can currently be achieved using Jira status properties (e.g., jira.permission.work.denied), we have hit a critical limitation regarding retroactive logging.
Status properties only check the current status of the issue when a user attempts to log time. They do not validate the status the issue was in on the actual date the work is being logged for.
Example Scenario:
Our process blocks work logging in the To Do status, but allows it in In Progress.
Days 1–2: The issue is in To Do. (Work logging is correctly blocked if attempted on these days).
Day 3: The issue is moved to In Progress.
The Loophole: On Day 3, a user can log work and manually set the "Date Started" to Day 1 or Day 2. Jira allows this because the issue's current status is "In Progress", bypassing our compliance rules for the "To Do" phase.
Guest
| Tempo Products | Tempo Timesheets |
| Tempo Platform | Cloud |
