intersystems-community / intersystems-community/DeepSeeWeb
Filters set to individual widgets still interact across widgets
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 19
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
On a single dashboard page, we have several widgets displayed. For each widget, individual filters are configured, and those filters are set to affect only that specific widget.
Expected behavior:
Filters applied to one widget should not affect or interact with filters in any other widget. Each widget should behave independently with its assigned filters.
Actual behavior:
Despite the filters being limited to individual widgets, we observe that selecting a filter in one widget can impact the filters of other widgets on the page.
Screenshot 1 - a value is selected in the Year filter of widgets, the filter in another widget shows “Invalid filter” and doesn’t display the dropdown list.
Screenshot 2 - after clearing the Year filter in all widgets, the Age Group filter in another widget loads the values correctly as expected.
Please note: for the Text Meter widget (second widget), and table widget (last on the screenshots) the Year filter must be present in order to calculate the rate correctly.
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.
Research direction
Reproduce the issue on a dashboard with several widgets, including the Text Meter and table widgets, each configured with individual filters. Start by tracing how widget filter selections are shared across the dashboard. Done means selecting one widget’s filter no longer invalidates or changes another widget’s filter, while required Year filters still calculate the affected widgets correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- angularjs, typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100