Bundles shouldn't have any filters by default

Open
#271 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
python
Domain
web-dev

Research direction

Trace how bundle pages apply their default filters and identify the entry point responsible for the initial bundle view. Reproduce the issue with a bundle containing multiple patches, then verify that all patches appear without filters by default while explicit filter parameters still work.

Written by the indexing model from the issue text.

Description

enhancement

By default, bundles look like this:

default view

The bundle actually contains 7 patches, though - they just don't show by default because of the "action required" filter. It takes two clicks and page loads for the user to get what they want (with the filter ?state=%2A&archive=both:

all patches

So bundles should have no filters by default, because if you put something in a bundle, chances are you want to see it.

reported by @oohal

Dominant language
Python
Stars
317
Forks
91
No merged PRs in 30d

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.

More from getpatchwork/patchwork

All issues in getpatchwork/patchwork

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.