DQD status filter not applied when filtering by status "0"
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 76/100
- Issue type
- Bug
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in the Data Quality Dashboard checks view and reproduce the issue with a dataset containing both status 0 and status 1 checks. Apply the status "0" filter, then change sort order to verify the results. Done means only status 0 checks remain and the funnel icon indicates the filter is active, while status "1" filtering continues to work.
Written by the indexing model from the issue text.
Description
Preconditions:
Data Quality Dashboard open for a dataset with a mix of status 0 and status 1 checks
Steps to reproduce:
Open the DQD checks view.
Apply the status filter with value "0".
Review the resulting list and the filter (funnel) icon on the column
Manipulate with the order: ascending/descending to verify results quickly
Expected result:
- Only checks with status 0 are shown.
- The funnel icon appears, indicating the filter is active.
Actual result:
- Checks with status 1 still appear in the list.
- The funnel icon does not show up, which suggests the filter is not fully applied.
https://github.com/user-attachments/assets/692df57b-b374-4fb8-9762-5eadcb132c8f
Additional notes:
Filtering by status "1" works as expected and does not reproduce the issue.
Reproduced across datasets and environments (project PROD, DEV synthetic), so it is not tied to a specific dataset.
- Dominant language
- TypeScript
- Stars
- 43
- Forks
- 12
- Avg merge
- 4d 6h
- Merged PRs (30d)
- 93
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from OHDSI/Data2Evidence
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
OHDSI/Data2Evidence#3363 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 82/100
OHDSI/Data2Evidence#3293 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
OHDSI/Data2Evidence#3245 ·
-
QA
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OHDSI/Data2Evidence#2907 ·
-
Add dataset type bug Open
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
OHDSI/Data2Evidence#2671 ·
All issues in OHDSI/Data2Evidence
Similar issues
-
calcite-components needs triage refactor
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Esri/calcite-design-system#15203 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 91/100
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 95/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Automattic/studio#4908 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100