It describes two problems with the current handling of the 'updated' item state:
- Changes are not persistent. There is a bug preventing correct saving of the state change into the DB.
- Many users confuse this state with the item read state and wonder why "Mark All Read" cannot be used to reset the 'updated' state.
If you got ever confused by this feature starting with 1.4.19 this will be fixed.