"Start" command changes task estimate

[Two9A]

When using ralio start to mark a task as In-Progress, the estimate and todo fields on the task are changed to "1.0". This is probably incorrect behaviour.

[igorescobar]

Hello! ;)

Actually, that is an expected behaviour. People usually don't estimate tasks, only user stories and living the to do and estimate empty. That causes an bad collateral effect making the burn down inefficient. That's way ralio behaviour like this. Just to make sure that the burn down is working as expected.

[igorescobar]

Hello! ;)

Actually, that is an expected behaviour. People usually don't estimate tasks, only user stories and living the to do and estimate empty. That causes an bad collateral effect making the burn down inefficient. That's way ralio behaviour like this. Just to make sure that the burn down is working as expected.

[igorescobar]

Hello! ;)

Actually, that is an expected behaviour. People usually don't estimate tasks, only user stories and living the to do and estimate empty. That causes an bad collateral effect making the burn down inefficient. That's way ralio behaviour like this. Just to make sure that the burn down is working as expected.

[Two9A]

Interesting. Don't suppose we can add an option to have it not change the estimate? (--keep-time or something...) I ask because we generally put task estimates on story contents, so obviously the burndown's affected by changes to those.

[igorescobar]

A good "work around" to this problem is verify is this is already set and only set those fields if those are empty.