|
History
| Log In
|
|
|
|
Don't understand why this has been resolved as "won't fix".
Allowing people to resolve issues where there is still some estimated time left seems inconsistent to me. Scheduling for consideration in 2.7
Just noticed the versions in this issue seem to be wrong
The fix version is currently 2.5 (but that has already been released!) Maybe the values are interchanged? From Tim Dawson via e-mail:
The log work screen currently allows logging work and adjusting the time Sounds like the way to go. There may be situations where automatically setting the time remainging to 0 is not the best policy. This depends of course on the issue workflow and whether an organisation wants to raise multiple related issues to represent the different aspects of a task (ie. coding, testing and UAT).
Often after a developer has implemented their code, it requires independent verification (either internal or external). An organisation might like to capture this time as well. The problem then becomes whether to: 1) raise a separate but related issue (perhaps a sub-task) or I don't think Jira can tally linked issues and I'm not sure if it can tally the estimates and actuals of all sub-tasks belonging to an issue. If it could, it makes more sense to raise separate issues, alternatively one probably has to use a single issue (with extended statuses) to avoid having to programmatically extend Jira or engage in tedious, error prone manual calcualtion. Just my two cents Nyree,
Thanks for the feedback. In this situation I believe the best way is to create a workflow that better represents your business process. So the issue gets resolved only when the code has been verified. When we implement this, we will make the bahaviour optional. Thanks, Would a post-function work for this? The longer-term solution is to be able to log work on the resolve page, but for the moment, would this be a valid work-around?
Can't seem to get pop-ups to allow control on Windows version XP
Lauren,
Please only add test issus, comments and atttachments to the Test Project. Cheers, In my team people also want JIRA to automatically set remaining time to 0 when certain transition occurs (typically going to Close or Resolved status - as this often means that nobody is going to work on given issue anymore. Also only with remaining time set to 0, many reports (e.g. time tracking) begin to give better picture of the project status.
I wanted to use post-functions of workflows. I am setting remaining time to 0 there. Unfortunately I have the following problem: if nobody has logged any work till the moment when the issue is closed (or resolved) then this post-function in fact resets original estimation to 0 (instead of resetting remaining time). Our people often close issues and then report time spent. It means disaster for us - original estimations are erased. What Atlassian is going to do on that? Maybe some quick recommendation? Thanks in advance, Wojtek I'm having this problem as well. I want to set remaining estimate to zero when resolving but I can't find a way:
1) Post-function to set remaining to zero is buggy and sets Original Estimate to zero, ruining my burndown charts. |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
 |
|
Bug
Reopened
Major
Resolving an issue should automatically put the estimated time remaining to 0
We'll have a look at this later.
Cheers,
Dave