Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
If we have a certain budget/amount of hours we can spend on a project, and we don't know how many issues will there be in said project, can we somehow limit how many working hours can be logged for the entire project, so that the users can't log hours exceeding the limit? We are also using Tempo plugin.
I believe the admin will need to make time tracking mandatory as well as specify an Original Estimate for a given issue.
Prior to logging work on an issue, you may want to specify an Original Estimate for an issue (i.e. the total amount of time you think it will take to resolve the issue).
When work is first logged against the issue, the Time Spent is subtracted from the Original Estimate and the resulting value is automatically presented in the Remaining Estimate. When subsequent work is logged, any Time Spent is subtracted away from the Remaining Estimate.
See Specifying time estimates here for more details:
You might also be interested in the User Reports that compliment Time Tracking:
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
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