Degraded performance Customers may experience intermittent errors using Community search. Our platform vendor is investigating.
I would like to be able to edit a Jira issue and adjust the Remaining Estimate whilst leaving the Original Estimate blank. This is so that I can accurately see which date the release is tracking to without adding in an original estimate for an issue that has come into queue mid-release. If I try to do this Jira copies the value for the Remaining Estimate to the Original Estimate when I save. If I put 0 hours in for the original estimate, that messes with my time tracking report as it thinks all these issues were wildly under-estimated, when in fact I just want them excluded.
I'm not using Legacy Mode for time tracking.
I think I have a similar problem, we would like all our remaning estimates to be 0 when an issue is being closed. However, when I add a post funtion that set remaining time to 0 when issue is beeing closed, the orignal estimate also gets set to zero as well which messes up our follow-ups through the hour burndown charts.
Would also be very intressted to hear if anyone have solved this.
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