Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-8906

In Cockpit, User Operation Log is not deterministic

    • Icon: Bug Report Bug Report
    • Resolution: Fixed
    • Icon: L3 - Default L3 - Default
    • 7.9.0, 7.9.0-alpha4
    • 7.9.0-alpha3
    • cockpit
    • None

      Steps to reproduce:
      1) deploy a process with two user tasks
      2) start an instance of that process
      3) go to cockpit
      4) select the started process instance
      5) assign the pending user task to "demo"
      6) modify the process instance (move to token to second user task)
      7) open user operation tab in historic process definition view

      Observed Behavior:

      Expected Behavior:

      • The user operation log shows always the same.

      Hint:

      • The implementation [1] does not respect that multiple user operation can have the same operation id but different operation types.

      [1]: https://github.com/camunda/camunda-bpm-platform-ee/blob/f1683c519fbf7ebecddb16d0512713790761b0af/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/components/userOperationsTable.js#L49-L65

        This is the controller panel for Smart Panels app

            [CAM-8906] In Cockpit, User Operation Log is not deterministic

            Roman Smirnov created issue -
            Roman Smirnov made changes -
            Description Original: *Steps to reproduce:*
            1) deploy a process with two user tasks
            2) start an instance of that process
            3) go to cockpit
            4) select the started process instance
            5) assign the pending user task to "demo"
            6) modify the process instance (move to token to second user task)
            7) open user operation tab in historic process definition view

            *Observed Behavior:*
            - The user operation log contains two rows, see [^cockpit-user-operation-1.png]:
            -# Operation Assign
            -# Operation ModifyProcessInstance
            - But sometimes it also shows, see [^cockpit-user-operation-2.png]:
            -# Operation Assign
            -# Operation Delete

            *Expected Behavior:*
            - The user operation log shows always the same.

            *Hint:*
            - The implementation [1] does not respect that multiple user operation can have the same operation id but different operation types.

            [1]: https://github.com/camunda/camunda-bpm-platform-ee/blob/f1683c519fbf7ebecddb16d0512713790761b0af/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/components/userOperationsTable.js#L49-L65
            New: *Steps to reproduce:*
            1) deploy a process with two user tasks
            2) start an instance of that process
            3) go to cockpit
            4) select the started process instance
            5) assign the pending user task to "demo"
            6) modify the process instance (move to token to second user task)
            7) open user operation tab in historic process definition view

            *Observed Behavior:*
            - The user operation log contains two rows, see [^cockpit-user-operation-log-1.png]:
            -# Operation Assign
            -# Operation ModifyProcessInstance
            - But sometimes it also shows, see [^cockpit-user-operation-log-2.png]:
            -# Operation Assign
            -# Operation Delete

            *Expected Behavior:*
            - The user operation log shows always the same.

            *Hint:*
            - The implementation [1] does not respect that multiple user operation can have the same operation id but different operation types.

            [1]: https://github.com/camunda/camunda-bpm-platform-ee/blob/f1683c519fbf7ebecddb16d0512713790761b0af/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/components/userOperationsTable.js#L49-L65
            Roman Smirnov made changes -
            Description Original: *Steps to reproduce:*
            1) deploy a process with two user tasks
            2) start an instance of that process
            3) go to cockpit
            4) select the started process instance
            5) assign the pending user task to "demo"
            6) modify the process instance (move to token to second user task)
            7) open user operation tab in historic process definition view

            *Observed Behavior:*
            - The user operation log contains two rows, see [^cockpit-user-operation-log-1.png]:
            -# Operation Assign
            -# Operation ModifyProcessInstance
            - But sometimes it also shows, see [^cockpit-user-operation-log-2.png]:
            -# Operation Assign
            -# Operation Delete

            *Expected Behavior:*
            - The user operation log shows always the same.

            *Hint:*
            - The implementation [1] does not respect that multiple user operation can have the same operation id but different operation types.

            [1]: https://github.com/camunda/camunda-bpm-platform-ee/blob/f1683c519fbf7ebecddb16d0512713790761b0af/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/components/userOperationsTable.js#L49-L65
            New: *Steps to reproduce:*
            1) deploy a process with two user tasks
            2) start an instance of that process
            3) go to cockpit
            4) select the started process instance
            5) assign the pending user task to "demo"
            6) modify the process instance (move to token to second user task)
            7) open user operation tab in historic process definition view

            *Observed Behavior:*
            - The user operation log contains two rows, see [^cockpit-user-operation-log-1.PNG]:
            -# Operation Assign
            -# Operation ModifyProcessInstance
            - But sometimes it also shows, see [^cockpit-user-operation-log-2.PNG]:
            -# Operation Assign
            -# Operation Delete

            *Expected Behavior:*
            - The user operation log shows always the same.

            *Hint:*
            - The implementation [1] does not respect that multiple user operation can have the same operation id but different operation types.

            [1]: https://github.com/camunda/camunda-bpm-platform-ee/blob/f1683c519fbf7ebecddb16d0512713790761b0af/webapps/camunda-webapp/plugins/src/main/resources-plugin/cockpit/history/app/components/userOperationsTable.js#L49-L65
            Roman Smirnov made changes -
            Rank New: Ranked higher
            Roman Smirnov made changes -
            Rank New: Ranked lower
            Roman Smirnov made changes -
            Rank New: Ranked lower
            Seif made changes -
            Status Original: Open [ 1 ] New: In Progress [ 3 ]
            Seif made changes -
            Assignee Original: Seif [ seif.ghezala ] New: Fabian [ fabian.hinsenkamp ]
            Resolution New: Fixed [ 1 ]
            Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
            Remaining Estimate New: 0 minutes [ 0 ]
            Original Estimate New: 0 minutes [ 0 ]
            Fabian made changes -
            Status Original: Resolved [ 5 ] New: In Test [ 10004 ]
            Fabian made changes -
            Assignee Original: Fabian [ fabian.hinsenkamp ] New: Michael Schoettes [ michael.schoettes ]
            Yana Vasileva made changes -
            Affects Version/s New: 7.9.0-alpha3 [ 15301 ]

              michael.schoettes Michael Schoettes
              roman.smirnov Roman Smirnov
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: