Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-3017

Revise sharing functionality

    XMLWordPrintable

    Details

    • Type: Task
    • Status: Open
    • Priority: L3 - Default
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: backend, frontend
    • Labels:
    • Effort:
      Not defined

      Description

      Context:
      The sharing functionality has been added in the beginning of Optimize. Since then, a lot of things have changed so that the sharing is in a weird state. For instance, the dashboard sharing model in the front-end does a get request to /share/dashboard/{dashboardId} to check if a dashboard has been shared (response has content 200 or no content 204). However, it never uses the content of the get request.

      AT:

      • the sharing functionality is revised so it is adjusted to the current functionality
      • the dashboard share get request is change to a request that returns a boolean, if the dashboard is being shared
      • same behavior as described in the previous point should be applied to the report sharing
      • the dashboard/report evaluation endpoints return "not found" if the respective entity was not found instead of null
      • the dashboard share index does not store the report ids, because it's not needed, since the actual dashboard is fetched anyway.
      • In case we don't store the reports in the dashboard share any longer, check if we can remove the DashboardRelationService
      • find out why we store the x and y coordinate in the report share
      • the upgrade script is adjusted accordingly

        Attachments

          Activity

            People

            Assignee:
            Unassigned Unassigned
            Reporter:
            johannes.heinemann Johannes Heinemann
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Dates

              Created:
              Updated: