Dashboard Filter settings are persisted per user

XMLWordPrintable

    • Type: Feature Request
    • Resolution: Won't Do
    • Priority: L3 - Default
    • 3.6.0-alpha2, 3.6.0
    • Affects Version/s: None
    • Component/s: backend
    • 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
        ]
      }

            Assignee:
            Unassigned
            Reporter:
            Sebastian Stamm
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: