Are you in the loop? Keep up with the latest by making sure you're subscribed to Community Announcements. Just click Watch and select Articles.

Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


I would like to know if there's a way to block log time when exceeded the estimate

I use tempo timesheets but i cant block the log time when exceeded the estimate plan, i was looking for a way to block this so i create an automation to compare the time spent field with the estimate field, and i would like to know if there's anyway to pop up a screen with a message or delete the worklog if time spent>Estimate, or another way or add-on where is possible to do that.

1 answer

2 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 13, 2022

Hello @Guilherme de Oliveira Viol 

Why specifically do you want to prevent logging time? What are you trying to achieve with that? 

Logging time usually occurs after the time has already been worked. If you prevent users from logging time or delete time logged then you are losing data about actual time spent working on the issue.

for example, i have an issue on a project with one hour estimate, if the user register two hours something went wrong and the extra hour will be taken from the project manager account, because its a project with a closed scope.

Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Dec 13, 2022

It seems to me that you need to address this with your users rather than trying to address it with customizations to the product. Educate your users to look at the estimate on the task and stop work when they have spent that much time on the task. If the task requires more time to complete have a process for the user to alert the project manager that more time is needed. If the users are still logging more time than they should, you can use a Filter Subscription or an Automation Rule to receive alerts about it and address it interactively.

However, if you are committed to your current course of action, this is my feedback.

I'm not aware of a native method to selectively disable logging of time in that manner.

I am also not aware of a predefined action in Automation Rules that would allow you to selectively delete an entire work log record. There is a Send Web Request action that would allow you to interact with the Jira REST API, which would allow you to delete a worklog. You would first have to identify the specific worklog you need to delete.

Alternately you could modify the time spent on the last work log entry made when that entry causes the total time to exceed the Estimate. You can operate on the specific Work Log Entry by having a rule that uses the Work Logged trigger.

Screen Shot 2022-12-13 at 10.15.21 AM.png

I have not tested those options on a system that includes Tempo Timesheets.

Like Deleted user likes this


I think the issue is not to prevent a time log, but to alert the user that he logs more time than was specified in Remaining Estimate, especially if time is entered via Timesheet.
If Remaining Estimate was 2h, and the user logs 5h, then the remaining estimate will be 0. This is logically equivalent to increasing the Remaining Estimate by 3h.
If logging the time was an error, and the user then deletes the log, then then the issue will have a Remaining Estimate of 5h. This can happen very easily without the user noticing it.

If a PM requires to be notified whenever the Remaining Estimate is changed other than by subtracting logged time, in that case this will not happen.

A solution could be:
* preventing logging more than Remaining Estimate in "auto adjust" mode - you have to change Remaining Estimate manually before logging, or use one of the other modes.

* Sending a notification E-Mail to someone whenever more time is logged than Remaining Estimate (in auto adjust mode).


You can do this easily if you are using WorklogPRO as timesheet app. You can enter the following expression as worklog verification script:

issue.fields.timetracking.remainingEstimateSeconds >= worklog. timeSpentSeconds 

 You can also do a lot more complex verifications using WorklogPRO's script feature

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events