Only allow time tracking if original estimate is not reached

[Kevin Ulrich Moschallski]

Hi,

we try to prevent "overtracking" of issues. So if an issues had an original estimate of 4h and there's 2h remaining estimate we don't want to allow the user to track more than this 2h rest.

Is there a way to prevent this with tempo or maybe with a custom condition?

Does anybody has this or something like in his / her workflow?

[Albert Hauksson [Tempo]]

Hi Kevin,

The short answer is no, that is not possible.

The reason is that most want people to be able to log more work that the original estimate to know if the issue "goes over budget".

Best regards,
Albert Hauksson
Tempo Team 

[Kevin Ulrich Moschallski]

Thanks for your replies. I guess we then need something else to watch the budget.

[Albert Hauksson [Tempo]]

One way to manage budget with Tempo Timesheets is to set a budget for your Accounts and use a Account Budget-Burnup Chart Gadget to monitor the budget status. Here's how to setup your accounts: https://tempoplugin.jira.com/wiki/display/TEMPO/Link+to+Tempo+Accounts and here's how to create the account bugdeg burn-up gadget: https://tempoplugin.jira.com/wiki/display/TEMPO/Account+Custom+Budget+Burn-up+Chart Hope this helps! Regards, Albert Hauksson

[Deleted user]

I agree with Albert. It is called an "estimated" time because it's really an estimate after all. It's not called "Hours to burn" field. If you ask your developers to work on "ghost mode" not charging hours to the ticket, that's a lost opportunity to improve your estimating skills.