Group reordering causes incorrect expansion state of adjacent groups when pausing/resuming #4626

New issue

Open

opened 2026-02-28 04:09:40 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 04:09:40 -05:00

Owner

Originally created by @MrNerubian on GitHub (Jan 21, 2026).

Description:

When pausing or resuming a group, the group is automatically moved to the top or bottom of the sorted list.
If the group was expanded before the operation, this reordering causes unexpected changes to the expansion state of adjacent groups.

Observed behavior:

When pausing a group:
- The group below the paused group becomes expanded automatically
When resuming a group:
- The group above the resumed group becomes expanded automatically

This happens even though those adjacent groups were not interacted with.

Expected behavior:

Pausing or resuming a group should not affect the expanded/collapsed state of other groups
Group expansion state should remain consistent regardless of automatic reordering

Notes:

The issue only occurs when the group was expanded before pausing or resuming
The behavior is likely related to list reordering and state reuse

🛡️ Security Policy

I have read and agree to Uptime Kuma's Security Policy.

📝 Description

When a group is paused or resumed, it is automatically moved to the top or bottom of the sorted group list.
If the group was expanded before the operation, this reordering causes the expanded/collapsed state of adjacent groups to change unexpectedly.

The issue results in unrelated groups being expanded without user interaction.

👟 Reproduction steps

Create multiple groups.
Expand one group (Group A).
Ensure there is another group directly above or below Group A.
Pause Group A.
Observe the expansion state of the group that is now adjacent to Group A.
Resume Group A.
Observe the expansion state of the group adjacent to Group A again.

👀 Expected behavior

Pausing or resuming a group should not affect the expanded/collapsed state of other groups.
Group expansion states should remain consistent regardless of automatic reordering.

😓 Actual Behavior

When pausing a group, the group that was originally below it becomes expanded automatically.
When resuming a group, the group that was originally above it becomes expanded automatically.
This occurs without any direct user interaction with those groups.

🐻 Uptime-Kuma Version

2.0.2

💻 Operating System and Arch

Red Hat Enterprise Linux 8.7 64bit

🌐 Browser

Google Chrome 143.0.7499.193

🖥️ Deployment Environment

📝 Relevant log output

Originally created by @MrNerubian on GitHub (Jan 21, 2026). ### 📑 I have found these related issues/pull requests **Description:** When pausing or resuming a group, the group is automatically moved to the top or bottom of the sorted list. If the group was **expanded** before the operation, this reordering causes **unexpected changes to the expansion state of adjacent groups**. **Observed behavior:** * When **pausing** a group: * The group below the paused group becomes **expanded automatically** * When **resuming** a group: * The group above the resumed group becomes **expanded automatically** This happens even though those adjacent groups were not interacted with. **Expected behavior:** * Pausing or resuming a group should **not affect the expanded/collapsed state of other groups** * Group expansion state should remain consistent regardless of automatic reordering **Notes:** * The issue only occurs when the group was expanded before pausing or resuming * The behavior is likely related to list reordering and state reuse ### 🛡️ Security Policy - [x] I have read and agree to Uptime Kuma's [Security Policy](https://github.com/louislam/uptime-kuma/security/policy). ### 📝 Description When a group is paused or resumed, it is automatically moved to the top or bottom of the sorted group list. If the group was expanded before the operation, this reordering causes the expanded/collapsed state of adjacent groups to change unexpectedly. The issue results in unrelated groups being expanded without user interaction. ### 👟 Reproduction steps 1. Create multiple groups. 2. Expand one group (Group A). 3. Ensure there is another group directly above or below Group A. 4. Pause Group A. 5. Observe the expansion state of the group that is now adjacent to Group A. 6. Resume Group A. 7. Observe the expansion state of the group adjacent to Group A again. ### 👀 Expected behavior * Pausing or resuming a group should not affect the expanded/collapsed state of other groups. * Group expansion states should remain consistent regardless of automatic reordering. ### 😓 Actual Behavior * When pausing a group, the group that was originally **below** it becomes expanded automatically. * When resuming a group, the group that was originally **above** it becomes expanded automatically. * This occurs without any direct user interaction with those groups. ### 🐻 Uptime-Kuma Version 2.0.2 ### 💻 Operating System and Arch Red Hat Enterprise Linux 8.7 64bit ### 🌐 Browser Google Chrome 143.0.7499.193 ### 🖥️ Deployment Environment - ### 📝 Relevant log output ```bash session ```

deekerman added the

bug

label

2026-02-28 04:09:40 -05:00

deekerman commented

2026-02-28 04:09:45 -05:00

Author

Owner

@bittoby commented on GitHub (Jan 23, 2026):

@CommanderStorm I'd like to fix this issue.
Before that, I want to know the expected behavior in issue is correct or not.

@bittoby commented on GitHub (Jan 23, 2026): @CommanderStorm I'd like to fix this issue. Before that, I want to know the expected behavior in issue is correct or not.