Skip to content

Collapse large sequences of label, milestone, etc changes #615

Closed

Description

@aaronbushnell

Issuehunt badges

I apologize if this has already been mentioned, but I did not see an issue for it.

Sometimes issues get very noisy when labels and milestones are added/removed. They push comments down and make it difficult to see updates to the item that aren't related to the project management side.

It would be nice if these large sequences (excluding comments) could "collapse". Here's an example of what I'm describing.

screenflow


IssueHunt Summary

fregante fregante has been rewarded.

Backers (Total: $50.00)

Submitted pull Requests


Tips

Activity

  1. fregante commented on Jul 13, 2017

    @fregante
    Member

    The title changes are definitely annoying so I'd put a vote to hide those, but references from other issues are useful.

  2. jgierer12 commented on Jul 13, 2017

    @jgierer12
    Contributor

    I also think references and commits should stay expanded. But hiding title changes, deploys and label changes would be great. Some things like assignments don't occur very often per issue, so I think they should stay expanded too.


    Hidden events should be as unobstrusive as possible IMO, perhaps something like this would work:
    Hidden events mockup
    Clicking the "+" would expand the hidden events

  3. hkdobrev commented on Jul 13, 2017

    @hkdobrev
    Contributor

    I'd prefer collapsing title changes with title changes, label changes with label changes, milestone changes with milestone changes, project changes with project changes, reviewers changes with reviewers changes and assignees changes with assignees changes.

    P.S. The label changes are particularly bad as they're easy to misclick!

  4. jgierer12 commented on Jul 13, 2017

    @jgierer12
    Contributor

    Another idea, perhaps we could hide or group events that are reverted in a short period of time, such as closing and re-opening an issue within a few minutes as that's almost always an accident

  5. hkdobrev commented on Jul 13, 2017

    @hkdobrev
    Contributor

    Another idea, perhaps we could hide or group events that are reverted in a short period of time, such as closing and re-opening an issue within a few minutes as that's almost always an accident

    I consider closing/re-opening or restoring and re-deleting a branch to be significant events.

  6. fregante commented on Jul 14, 2017

    @fregante
    Member

    Closing/reopening within minutes is probably because of a mistake and IMHO it should be hidden.

    Restoring/deleting branches... not sure of when they are ever useful (other than "let's display every event")

  7. sindresorhus commented on Oct 18, 2017

    @sindresorhus
    Member

    Pull request welcome if anyone wants to see this feature :)

  8. yakov116 commented on Feb 7, 2018

    @yakov116
    Member

    Going to give this a bump, could have used this today

  9. added a commit that references this issue on Aug 22, 2018
  10. fregante commented on Dec 9, 2018

    @fregante
    Member

    This could be made part of hide-useless-comments and the feature can become hide-noise

    The logic should already be there. If anyone is interested you probably just need to tweak the selector and update the name/docs.

  11. added
    smallIssues that new contributors can pick up
    on Dec 9, 2018
  12. 6 remaining items

  13. self-assigned this
    on Jul 2, 2019
  14. added and removed
    smallIssues that new contributors can pick up
    on Jul 2, 2019
  15. removed their assignment
    on Jul 2, 2019
  16. fregante commented on Jul 2, 2019

    @fregante
    Member

    I made some noise in #2201

    Can all those events be hidden? Or just nearby events that cancel each other out?

    What do you think about:

    • Labels: hide all
    • Title changes: hide all but the first one (to show its original title)
    • Branch deletion: only when they cancel each other out
    • Assignments: only when they cancel each other out
    • Open/close: only when they cancel each other out
    • Milestones: only when they cancel each other out
    • Projects: only when they cancel each other out

    And then:

    • Lock/unlock: leave unchanged
    • Project events: 🤷‍♂️ I don't use projects
  17. sindresorhus commented on Jul 25, 2019

    @sindresorhus
    Member

    What you suggested above sounds good to me.

  18. AnthonyLenglet commented on Aug 27, 2019

    @AnthonyLenglet
    Contributor

    to combined #2384 here, this issue is an exemple of issue noise caused by bots that upgrade dependencies when an issue is mentioned in the release note

    FortAwesome/Font-Awesome#15396

    stuff like this makes it simply impossible to read anything easily :/

    I really like the idea @fregante proposed here, for the projects I would suggest only when they cancel each other out just like most of those (moving a card back and forward between columns)

  19. fregante commented on Oct 29, 2019

    @fregante
    Member

    @AnthonyLenglet Bots may be best handled by #1745

  20. Tiramisu77 commented on Nov 10, 2019

    @Tiramisu77
    Contributor

    I'm working on this feature (as per @fregante 's comment), and it's not clear to me what exactly should count as a sequence of actions. So far I have the following ideas:

    1. Don't use sequences at all and handle actions on the whole page
    2. Group actions by date
    3. Select all actions between comments
  21. pradyunsg commented on May 25, 2020

    @pradyunsg

    Flagging that #1745 was closed since straight-up hiding bot comments isn't a good idea (and I agree!).

    Coming from pypa/pip#5182 (comment), I think it'd be great to have some way to collapse commit/PR references as well.

  22. issuehunt-oss commented on Mar 5, 2021

    @issuehunt-oss

    @sindresorhus has rewarded $45.00 to @fregante. See it on IssueHunt

    • 💰 Total deposit: $50.00
    • 🎉 Repository reward(0%): $0.00
    • 🔧 Service fee(10%): $5.00
  23. locked as resolved and limited conversation to collaborators on Aug 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions