You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug] Custom Inbox groups jump when a thread is added or removed #1015
In the Threads inbox with Custom sort and Group by project, a group without a saved position is placed where its first visible thread falls in the global order. Removing or wrapping that thread can make another group jump ahead, even though both groups still have threads. The same problem can happen when changing the first row in a group.
How to reproduce
Choose Custom sort with grouping off.
Start with two projects A and B. Arrange the flat thread order so the first A thread is above the first B thread and another A thread is below it.
Turn on Group by project and archive or wrap the top A thread.
A and B can switch places. The same applies to grouping by computer. This follows up on #767.
Expected
A and B stay in the same order. If a group holds 3, 2, 1, a new unpinned thread 4 appends as 3, 2, 1, 4. Removing 1 leaves 3, 2, 4. A newly shown group goes after the known groups. Existing lead and pin rules still apply.
Version and fix
Reproduced from the source logic at 07d1ed0 on Linux. The patch records group positions separately from thread positions and persists newly seen keys. A regression test interleaves rows from two groups, removes the row that used to determine the first group's position, and checks the surviving group and thread order.
Thanks @live2ride, for the clear repro and for the patch. Fixed in #1028. In Custom sort, a group now keeps its place when its top thread is wrapped, archived or pinned, and a new group goes after the ones you already have.
We used the group part of your patch with one change. The remembered places live in their own setting, so the other sorts still move groups with their latest activity. We left out saving new threads into the custom order, since new threads already go to the bottom without it.
It'll be in the next nightly build and the next release. If a group still jumps after you update, reply here and we'll reopen.
Activity
badcuban commentedon Nov 21, 2026
Thanks @live2ride, for the clear repro and for the patch. Fixed in #1028. In Custom sort, a group now keeps its place when its top thread is wrapped, archived or pinned, and a new group goes after the ones you already have.
We used the group part of your patch with one change. The remembered places live in their own setting, so the other sorts still move groups with their latest activity. We left out saving new threads into the custom order, since new threads already go to the bottom without it.
It'll be in the next nightly build and the next release. If a group still jumps after you update, reply here and we'll reopen.