-
Feature Request
-
Resolution: Won't Do
-
L3 - Default
-
None
-
4
-
Not defined
AT:
- There is a new endpoint PUT /api/dashboard/:id/filter
- The payload of this new endpoint is identical to the one sent for report evaluation by id with filters applied
- The GET /api/dashboard/:id endpoint returns a new field called "filter" containing the array saved
- When a user is removed from the collection, their filter configurations for any dashboards within the collection are removed first
- After syncing identities with the engine, we should clear up any filter configurations for revoked users
- The filter array is bound to both the dashboard and the user. The same dashboard can have different filter settings for each user. The same user can have different filter settings for each dashboard
PUT /api/dashboard/:id/filter
request payload:
[
{...} // same structure as filters defined in the report
]
GET /api/dashboard/:id
response payload:
{
..., // rest of the dashboard info
filter: [
{...} // same structure as filters defined in the report
]
}
This is the controller panel for Smart Panels app
[OPT-3586] Dashboard Filter settings are persisted per user
| Description |
Original:
AT:
* There is a new endpoint PUT /api/dashboard/:id/filter * The payload of this new endpoint is identical to the one sent for report evaluation by id with filters applied * The GET /api/dashboard/:id endpoint returns a new field called "filter" containing the array saved * The filter array is bound to both the dashboard and the user. The same dashboard can have different filter settings for each user. The same user can have different filter settings for each dashboard {code:java} PUT /api/dashboard/:id/filter request payload: [ {...} // same structure as filters defined in the report ] GET /api/dashboard/:id response payload: { ..., // rest of the dashboard info filter: [ {...} // same structure as filters defined in the report ] }{code} |
New:
AT:
* There is a new endpoint PUT /api/dashboard/:id/filter * The payload of this new endpoint is identical to the one sent for report evaluation by id with filters applied * The GET /api/dashboard/:id endpoint returns a new field called "filter" containing the array saved * When a user is removed from the collection, their filter configurations for any dashboards within the collection are removed first * After syncing identities with the engine, we should clear up any filter configurations for revoked users * The filter array is bound to both the dashboard and the user. The same dashboard can have different filter settings for each user. The same user can have different filter settings for each dashboard {code:java} PUT /api/dashboard/:id/filter request payload: [ {...} // same structure as filters defined in the report ] GET /api/dashboard/:id response payload: { ..., // rest of the dashboard info filter: [ {...} // same structure as filters defined in the report ] }{code} |
| Mentioned Roles |
| Mentioned Groups |
| Labels | Original: dashboard next_release | New: current_release dashboard next_release |
| Labels | Original: current_release dashboard next_release | New: current_release dashboard |
| Labels | Original: current_release dashboard | New: dashboard |
| Effort | New: Not defined [ 11259 ] |
| Issue Type | Original: Feature Part [ 10202 ] | New: Feature Request [ 2 ] |
| Parent |
Original:
|
| Epic Link | New: OPT-3699 [ 52239 ] |