nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow Post Function - setting Remaining Estimate to 0 also sets Original Estimate to 0

Joe F. Lee

Hi,

in one of our workflows we have implemented a Post Function "The Remaining Estimate of the issue will be set to 0. The expected behavior is that only this single field is being updated (set to 0) but unfortunately it also changes the Original Estimate value to 0 thus making the use of any burndown graphs (e.g. in Greenhopper) useless.

It does not matter if we do enter any time on this issue or not - the outcome is always the same.

Any ideas on how to resolve this issue?

Thanks,

Joe

Accepted answers

Joe F. Lee

Ok... looking throug the Support cases I found out that this was caused by the fact that the Legacy Mode was activated in our time tracking. Turned it off and issue was resolved.

Thanks,

Joe

All comments

Joe F. Lee

Forgot to add that we are using JIRA v4.4.3#663-r165197

Joe F. Lee

Ok... looking throug the Support cases I found out that this was caused by the fact that the Legacy Mode was activated in our time tracking. Turned it off and issue was resolved.

Thanks,

Joe

Jeanne Nicole1

We had the same results with setting the Remaining Estimate to 0d and with Legacy mode enabled. However, for us turning off legacy mode is not an option, as we do not want users to edit Original Estimate after work is logged. We consider this as a bug to be fixed.

Others who are in the same spot can watch, vote for, or comment on the JIRA support ticket, https://jira.atlassian.com/browse/JRA-25031