Post-lock warnings

Saguaro Hours for Jira cannot stop someone from editing a worklog inside Jira after the period is locked. Jira writes that edit without asking the app. So the app watches for it and flags it.

What is watched

Jira tells the app when a worklog is created, updated or deleted. If the day of the change falls in a submitted or approved period of the author, the app:

• adds an audit entry,
• records a warning on the timesheet with the number of changes and the hours before and after,
• leaves the status and the submitted hours unchanged,
• does not revert the change.

Where you see it

• The grid shows a chip such as "Changed after lock: +0.25h (3.5h at lock, 3.75h now), 1 change".
• The Approvals tab shows the same chip for each member, and the audit trail has a line such as "post-lock change: worklog edited by Sam".
• If the change is undone, the warning stays and reads "2 changes, no net difference".

Clearing a warning

There is no acknowledge button. The warning clears on the next status change of the sheet: a rejection, or approval of a submitted sheet. Approve all clears it on the submitted sheets it approves. The audit trail keeps the entries.

Limits

• The check runs when Jira reports the change, usually within a few seconds.
• A change to a worklog that has no stored record, moved out of a locked period, is not detected, because Jira does not send the old date. Worklogs made in the panel, and grid worklogs when the billable default is on, have records.
• Deleting a whole issue sends no worklog events. Stored tags for its worklogs stay in the app's storage.
• If the live total cannot be read, the entry is still written and the difference reads as unknown. Periods with more than 300 issues also show unknown.
• A viewer who cannot browse every issue, or an approver in another time zone, can see a false difference.
• Two events within milliseconds can lose one audit entry. The total stays right.
• There is no retry for a failed event.