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

Adjust columns configuration for raw data report

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 3.11.0-alpha4
    • None
    • None

      User Problem:

      Context:

      • The raw data report allows the configuration of columns included in the report.
      • For the Machine Learning User Case, we added additional columns (e.g. Count)

      Problem:

      • The UX to disable NOT needed fields, e.g. if you are NOT doing Machine Learning, is time-consuming.

      User Story:

      • As a user of Optimize, I would like to have an improved way to exclude a certain columns from the raw data report. This allows me to build a report more quickly.

      Solution Ideas

      • Group all "count columns" in a group called "Counts" similar to the grouping of variables
      • Set the default status for all columns included in collapsed groups to "disabled" (this is not done, see the comment below). This results in the default report only containing the main process columns that are not grouped by "Counts" / "Variables" / "Flow Node Duration"

      Testing Notes:

      the columns Incidents Count, Open Incidents Count and Executed User Tasks Count are now grouped together into counts group and column names are now called: Count: incidents, Count: openIncidents and Count: userTasks.

      In the report configuration popover (when you click on the cog button in top right) there is new collapsible section called Counts which groups the incidents, openIncidents and userTasks together

      All the functionalities like column rearrangement and disabling columns should work as before

       

        This is the controller panel for Smart Panels app

          1. image-2023-07-12-09-54-58-165.png
            71 kB
            Tobias Conz

            [OPT-7104] Adjust columns configuration for raw data report

            Tobias Conz added a comment -

            michal.konopski can we do a subtask on this FR?!

            Tobias Conz added a comment - michal.konopski can we do a subtask on this FR?!

            Tobias Conz added a comment -

            joshua.windels the solution does not solve the described problem, so I would suggest keeping this open. I would suggest to add this as an Epic to our product board. How much (backend) effort is this?

            Tobias Conz added a comment - joshua.windels the solution does not solve the described problem, so I would suggest keeping this open. I would suggest to add this as an Epic to our product board. How much (backend) effort is this?

            Tobias Conz added a comment -

            > This is now achieved, as they just need to disable it once right?

            joshua.windels  How is the functionality implemented? I tested it on stage - the attributes are now grouped, but it is still challenging to disable all of them. 

            Tobias Conz added a comment - > This is now achieved, as they just need to disable it once right? joshua.windels   How is the functionality implemented? I tested it on stage - the attributes are now grouped, but it is still challenging to disable all of them. 

            Omran Abazeed added a comment -

            This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10046. Please use this link for any future references and continue any discussion there.

            Omran Abazeed added a comment - This ticket was migrated to github: https://github.com/camunda/camunda-optimize/issues/10046 . Please use this link for any future references and continue any discussion there.

              Unassigned Unassigned
              tobias.conz Tobias Conz
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: