Remaining time is rewritten when issue status is changed

[t0mk]

1. I open an issue with remaining time 6.0 hours and state "new"
2. I update remaining time to 3 hours.
3. I change issue status to "in progress".

-> remaining hours are changed back to 6.0.

I find that quite annoying because I have to change the remaining time twice. I am sure people have encountered this before, but I wasn't able to find it in the issue tracker here on github. I also understand this is not a bug per se, and it in the end depends on the devs whether they fix it upstream or not.

What can I do to prevent the remaining time to be re-set when status is changed? I looked through the settings and briefly checked the code.

Redmine 2.2.4
Backlogs 1.0.5

[pakivika]

+1

[dtwaling]

We had some (what seemed to be) strange behavior with issue status and time remaining as well. It was a while ago so I don't remember the details, but it also affected the story statuses, and it seems that the config option "Loosely follow Tasks average done ratio" under the setting "Story follows Task status" was causing this part so we disabled that setting manage that part manually.

After some playing around with it I think we got a feel of how to dial it in a bit. We were very specific and purposeful in setting up your statuses and %Done for issue types and workflows; this helped a little but we still had some issues. I like the automation in here, we can definitely see the functionality is there, but setting it up to work properly is not exactly intuitive (maybe even taken for granted as common knowledge for some who already familiar). I just think it needs a little more focus:

1. Based on what is being reported it probably could use a bit of tweaking. Perhaps even add some control over the related functions directly within the plugin config as it relates to the added function of Redmine Backlogs.

2. Maybe some documentation explaining the functionality and some tips on "recommended" status settings. I see there is a "To Do" page (http://www.redminebacklogs.net/topics/story_follows_task.html) for the Story Follows Tasks function, but it seems that drilling down the the task level as well to address the topic here would be very helpful (especially for those who may be new to Agile PM).