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

Processes appear multiple times in search dropdown

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 2.5.0-alpha1, 2.5.0
    • None
    • frontend
    • None

      • given:
        • I have some processes deployed to the engine and I run Optimize
        • I go to the report builder and want to select a Process
      • when:
        • I open the process/decision definition selection and start typing to look for a process
      • then:
        • multiple times the same process appears in the list and it also does not go away if I search for something else
      • Expected:
        • The list should be filtered correctly and items should not be duplicated

        This is the controller panel for Smart Panels app

            [OPT-2181] Processes appear multiple times in search dropdown

            Johannes added a comment -

            felix.mueller: I think this is actually due to the data that is deployed on the engine. We have the same process deployed several times, which also has the same name. So it's not a bug but rather a problem that the staging data is in the need of improvement.

            Johannes added a comment - felix.mueller : I think this is actually due to the data that is deployed on the engine. We have the same process deployed several times, which also has the same name. So it's not a bug but rather a problem that the staging data is in the need of improvement.

            Johannes added a comment -

            That's true. I could actually reproduce that. Thanks for reporting it

            Johannes added a comment - That's true. I could actually reproduce that. Thanks for reporting it

            It only happens when the user uses the typeahead to search for a process. Since we have multiple processes with the same name I can imagine that React get confused with the map key to tell the options apart. We should investigate and make sure to use unique map keys for every item (that cannot be the name nor the index, maybe the process-definition-key?)

            Sebastian Stamm added a comment - It only happens when the user uses the typeahead to search for a process. Since we have multiple processes with the same name I can imagine that React get confused with the map key to tell the options apart. We should investigate and make sure to use unique map keys for every item (that cannot be the name nor the index, maybe the process-definition-key?)

              Unassigned Unassigned
              felix.mueller Felix Mueller
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: