makeplane / makeplane/plane

[feature]: Group work issue updates to reduce clutter in the work issue activity stream

Open
#8,967 1 comment 0 reactions 2 assignees View on GitHub

@vihar is already working on this.

Since Apr 28, 2026.

✨feature plane
Dominant language
TypeScript
Stars
59.6k
Forks
5.8k
Avg merge
1d 22h
Merged PRs (30d)
49

Description

Is there an existing issue for this?
  • I have searched the existing issues
Summary

User Story: As a general user, I'd like to choose any of the provided filters for activity - All, Activity, and History to group those items and reducing spacing in the UI so that I can scan through activity more easily and find comments and updates more easily.

Suggested AC:

  • The first change in a string of changes, should still list a contributor's name next to the update
  • Following changes should be listed underneath with an indent to show their correlation to that user
  • The following updates should each have unique time stamps, still.
  • If another user makes an update in between, then the names should display again for following "first updates" when not consecutive
Why should this be worked on?

Currently you see items listed with the user, then the activity done/action taken. For someone who updates the description a couple times, this looks like several updates and begins to flood the UI a bit. It would be nice to condense some of the actions in Activity, History (and on the All view as well for those elements) to just state the user once if they made consecutive updates without others interrupting.

Optional:

  • Perhaps only group items done within a 6-hr, or 24-hr period to not make things look to consecutive historically when the context might have changed from day to day.
  • Group icons on the left bar/timeline if multiple types of changes were made.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.