We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'Camunda Optimize'
  1. Camunda Optimize
  2. OPT-5358

Refactor external task locking and incident creation to be businessKey specific

    • Icon: Task Task
    • Resolution: Done
    • Icon: L3 - Default L3 - Default
    • 3.5.0
    • None
    • backend
    • Not defined

      Context:

      The fetchAndLock helper takes a processInstanceId which suggests that we only lock those tasks associated with that specific instance, when in fact we lock everything but only return the tasks of that instance. This unexpected side effect makes it hard to eg create incidents for multiple different process instances and is generally a bit confusing. 

      We can refactor this helper as well as the related incident helpers to take a businessKey instead and then only lock those tasks related to the given business key - the methods for this already exist, we just need to refactor the usages.

      See also: https://github.com/camunda/camunda-optimize/pull/3639 

       

      AT:

      • Refactor fetchAndLock and incident helpers to always take a businesskey

        This is the controller panel for Smart Panels app

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

            Refactor external task locking and incident creation to be businessKey specific

              • Icon: Task Task
              • Resolution: Done
              • Icon: L3 - Default L3 - Default
              • 3.5.0
              • None
              • backend
              • Not defined

                Context:

                The fetchAndLock helper takes a processInstanceId which suggests that we only lock those tasks associated with that specific instance, when in fact we lock everything but only return the tasks of that instance. This unexpected side effect makes it hard to eg create incidents for multiple different process instances and is generally a bit confusing. 

                We can refactor this helper as well as the related incident helpers to take a businessKey instead and then only lock those tasks related to the given business key - the methods for this already exist, we just need to refactor the usages.

                See also: https://github.com/camunda/camunda-optimize/pull/3639 

                 

                AT:

                • Refactor fetchAndLock and incident helpers to always take a businesskey

                  This is the controller panel for Smart Panels app

                        Unassigned Unassigned
                        helene.waechtler Helene Waechtler
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        1 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              Unassigned Unassigned
                              helene.waechtler Helene Waechtler
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              1 Start watching this issue

                                Created:
                                Updated:
                                Resolved: