1. Yes it is only happened when transition to Resolved.
2. Yes performing regular work logging does not set the original estimate to 0
3. We have a custom workflow like
Open > Active > Resolved.
There is a Post function on Resolve transition which says :
The Remaining Estimate of the issue will be set to 0.
But it sets the original estimate to 0 . on resolution transition if a worklog is also entered on the resolution screen.
Hmm, that is indeed true. The post function The Remaining Estimate of the issue will be set to 0. is something that caters for the remaining estimates only. Do you have other plugins that are installed in your instance that adds functionalities to the workflow? Also, can you check whether the Active status and the transition from Active > Resolve has any other post functions?
There were some instances where the Script Runner plugin caused a possible issue with the workflow transitions.
I am experiencing the same issue with post function The Remaining Estimate of the issue will be set to 0. This is the only post function we have on the transition. There are no Conditions or Validator on the transition either.
Here is what the history captures:
|Status||In Progress [ 3 ]||Resolved [ 5 ]|
|Original Estimate||6 hours [ 21600 ]||0 minutes [ 0 ]|
|Remaining Estimate||6 hours [ 21600 ]||0 minutes [ 0 ]|
Fixed/Completed [ 1 ]
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs