VM

Thread sort order not kept current

Bug #538729 reported by Uday Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
VM
Triaged
Low
Uday Reddy

Bug Description

When a message is edited or expunged, the thread that it belongs to needs to get updated, and its position in the sorted order should change if necessary.

At the moment, this is not happening. It looks like the function vm-unthread-message doesn't do a full job of updating the properties, especially the youngest-date and oldest-date properties.

Tags: threads
Uday Reddy (reddyuday)
Changed in vm:
status: New → Confirmed
importance: Undecided → Low
status: Confirmed → Triaged
assignee: nobody → Uday Reddy (reddyuday)
tags: added: threads
Uday Reddy (reddyuday)
description: updated
description: updated
Uday Reddy (reddyuday)
Changed in vm:
milestone: none → 8.1.2
Uday Reddy (reddyuday)
Changed in vm:
milestone: 8.1.2 → 8.2.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.