|
As some customers would like to edit the original estimate after some work has been logged against an issue, should this ability be protected by a separate permission so that regular users cannot "fudge" estimation accuracy by editing the "original estimate" after they have finished working on the issue?
A typical use case where we would need to be able to change the original estimate after some work has been logged is for instance when the analysis of an issue takes weeks because it is very hard to reproduce. So in order not to loose track of the time already spent analysing the request, we log the work done against the issue as we progress in its analysis. However, it's only at the end of it that we are able to put an original estimate. As a consequence, deleting the worklogged and start all over again is not an option since it could mean too much effort re-entering every steps and may be loosing some of them.
As for protecting the edition of the original estimate by some specific permission, it seems a good idea to me. Another use case is when you did a mistake when you entered your original estimate. Of course you could remove and re-enter the issue but this allways takes time.
It would be very nice if at least one person (or group) would be able to change this value. So a permission for this field would be very nice. I forgot to mention that it's also impossible to set an original estimate when a time was alredy logged. So if someone forgot to set an original estimation you have no more chance to get a correct report. But maybe our processes are just not good enough yet.
I agree with the cases Alexander brought up. Both of them are exactly the cases we have hit. An improvement in this area would be great.
+1
Because of this flaw we are unable to use original estimate field properly and reports become useless as soon as scope of issue changes or work is logged before any estimate is given. One use-case is that customer reports issue that later turns out to be bigger and it does not make sense to create a new issue just because the scope changed. Creating a new/alternative issue after some work is already reported is not solving this because customer is interested in tracking one single issue progress as a whole. Are there plans to make original estimation editable after work is logged? I have the same issue as described by Ahti above.
The end result being that it makes the time statistics unusable for a project. I could live with the workaround to delete the work log items, but I don't see a function for that either.
Our use case is:
Actually, on further playing with this, we are allowed to edit the original estimate up to the time the first work is logged. This is goodness. From that point on, perhaps more an administrative authority to fix any mistakes that are made after work is logged. Hi everyone,
This issue has my vote. I'm not familiar with making my own plugin, but I think it's possible, right? Altought, and I think more urgent, is to alter the possibility to put a new Original Estimate after being added any worklog. Thanks, Hi Atlassian.
I just had a project manager asking me for this functionality. He just entered 300-400 issues that need an Original estimate set. It will be time consuming to make this settings another way. Is there any workaround? Thanks Olle I have this problem. I would rather not edit the database by hand, but I will if it comes down to it.
Bob Swift above asked if it was safe to directly modify the original estimate value in the database but his question wasn't answered. So I'll ask it again. Also I think it would be great to make a Permission for modifying the Original Estimate value. Thanks, |
||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Improvement
Open
Major
Can't edit original estimate
You can edit the Time Remaining for an Issue or delete the worklogged and then start over.
Does this makes sense?
Is there a use case for being able to edit the original estimate?