-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
6.0.6
-
6
-
12
-
Severity 2 - Major
-
4
-
NOTE: This bug report is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding bug report.
Steps to replicate:
- The issue's Original Estimate is set to 8h
- The user logs in a 4h work and closes the issue
- The Remaining Estimate will be reduced to 4h
- Post-function from the workflow sets the Remaining Estimate to 0h
- Greenhopper does not understand that the Remaining Estimate had been decreased first by 4h and then by 4h again.
If the post-function of Update Issue Field is not used, the issue does not occur. Considering the post-function ships with the out-of-the-box, JIRA, it should take into consideration of setting the Remaining Estimate to 0.
- duplicates
-
JSWSERVER-9079 Remaining time estimates not updating on Burndown chart
- Closed
- is related to
-
JRASERVER-31929 Update Issue Field Post-Function using Time Spent does not work
- Gathering Impact
-
JSWSERVER-8340 Burndown report includes time remaining from Resolved and Closed issues.
- Closed
- relates to
-
JSWSERVER-8191 Total time remaining is incorrect if user edits the work log and sets Remaining Estimate manually
- Closed
-
JRACLOUD-65078 Update issue field post function gets saved twice in issue history if it is placed first in the list of post functions
- Closed
-
JSWCLOUD-6788 The Burndown Chart does not consider JIRA post function when calculating Remaining Estimate
- Closed
-
JRACLOUD-66261 Ofbiz and business layer piercing: manipulating directly the ofbiz GenericValue on time-tracking.
- Closed
-
JSWSERVER-9316 Rapid Boards do not report burndown as expected with edits to work log
- Closed
- mentioned in
-
Page Loading...