[#JRA-11336] Allow the Update Issue Field Function to setting Remaining Estimate to 0 even when no work has been logged

JIRA

Allow the Update Issue Field Function to setting Remaining Estimate to 0 even when no work has been logged

Created: 19/Oct/06 02:45 PM Updated: 24/Mar/08 09:26 PM

Component/s:

Workflow, Time Tracking, Issue Fields

Affects Version/s:

3.6.5

Fix Version/s:

None

Time Tracking:

Not Specified

Issue Links:

Reference

This issue relates to:

JRA-868 Resolve & Time spent

This issue is related to:

JRA-13512 Setting remaining time to 0 in a post function of the workflow causes the original estimate to be set to 0 as well (only when no time was logged by the assignee)

JRA-1744 "Log work done" as a MANDATORY field when resolving issues

Participants:	Anton Mazkovoi [Atlassian], Lorien Gremore and Wim Deblauwe
Since last comment:	66 weeks, 1 day ago
Labels:

Description

« Hide

I've created a workflow post function in my installation that does: "The Remaining Estimate of the issue will be set to 0h."

When resolving an issue, I find that it actually sets both the Remaining and Original Estimates to 0m, instead of preserving the Orignal Estimate as intended.

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Anton Mazkovoi [Atlassian] - 21/Jan/07 06:43 PM

I believe in JIRA there is no way to change the Remaining Estimate if no work has been logged against an issue. If no work has been logged then the Original Estimate will be updates, and if some work has been logged the Remaining Estimate will be updated. This is the intended behaviour.

However, I can see your problem: as far as I can tell all you would like to do is ensure that the Remaining Estimate is 0 when an issue is e.g. Resolved. The only way to do this know is to either ensure that each issue has at least on work log entry logged against it, or code up a custom workflow post-function.

Therefore I will change this issue to be an Improvement.

[ Permlink | « Hide ]

Wim Deblauwe - 09/Feb/07 07:57 AM

Thank you Lorien for putting this bug here. I was about to implement this change in workflow myself, but with this bug, I will not do it. Especially since JIRA has no validator to check the value of a field. I can't believe you let your customers code this as a plugin, it seems so simple and such a common need.