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

Handle conflicting variable names across definitions when providing labels

    • Not defined

      After introducing variable labelling, there has been some confusing behaviour in regards to applying dashboard variable filters. More specifically, if there are two variables across two definitions having the same name and type, then the given dashboard filter will be applied to both variables, even if their labels differ.

      As part of this ticket, we need to document this behaviour and link it to our UI.

        This is the controller panel for Smart Panels app

            [OPT-5965] Handle conflicting variable names across definitions when providing labels

            Andromachi Rozaki created issue -
            Andromachi Rozaki made changes -
            Status Original: Open [ 1 ] New: In Development [ 10312 ]
            Andromachi Rozaki made changes -
            Status Original: In Development [ 10312 ] New: In Development [ 10312 ]
            Andromachi Rozaki made changes -
            Status Original: In Development [ 10312 ] New: In Development [ 10312 ]
            Andromachi Rozaki made changes -
            Status Original: In Development [ 10312 ] New: Open [ 1 ]
            Sebastian Bathke made changes -
            Component/s New: documentation [ 13751 ]
            Sebastian Bathke made changes -
            Labels Original: current_release New: next_release
            Sebastian Bathke made changes -
            Assignee New: Andromachi Rozaki [ andromachi.rozaki ]
            Sebastian Bathke made changes -
            Labels Original: next_release New: current_release next_release
            Sebastian Bathke made changes -
            Labels Original: current_release next_release New: current_release

              Unassigned Unassigned
              andromachi.rozaki Andromachi Rozaki
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: