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?
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.
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
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
A picture tells a thousand words. And agility boards have just released their latest feature: cover images on issues – so now your board can tell a story at first glance. Upload attachmen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs