We couldn't load the project sidebar. Refresh the page to try again.
If the problem persists, contact your Jira admin.
Uploaded image for project: 'camunda BPM'
  1. camunda BPM
  2. CAM-12270

I want to add an annotation to incidents

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

      User story

      When working on incidents, I want to add an annotation to them so that the next person trying to resolve an open incident is up to date.

      Background

      Some teams have concierge roles to check for incidents in Camunda and resolve them.

      As some incidents cannot be resolved during the day, there is a need to perform Incident status coordination - doing that outside Camunda is not efficient.

      Therefore, the request is to have a comment facility in Cockpit were a small annotation can be left.

      Acceptance criteria

      • I can add/edit/delete an annotation at runtime process instance incidents that inform the next operator
      • The general scope is the same as CAM-9556, i.e. I can add an annotation to an incident and edit/delete it at any time; a comment thread or something similar is not in the scope of this ticket
      • The annotation is immediately propagated to the historic incident as well
      • The annotation is read-only in the historic incidents
      • The user needs to have the same authorizations needed to resolve an incident - any of UPDATE on PROCESS_INSTANCE and UPDATE_INSTANCE on PROCESS_DEFINITION

        This is the controller panel for Smart Panels app

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

            I want to add an annotation to incidents

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

                User story

                When working on incidents, I want to add an annotation to them so that the next person trying to resolve an open incident is up to date.

                Background

                Some teams have concierge roles to check for incidents in Camunda and resolve them.

                As some incidents cannot be resolved during the day, there is a need to perform Incident status coordination - doing that outside Camunda is not efficient.

                Therefore, the request is to have a comment facility in Cockpit were a small annotation can be left.

                Acceptance criteria

                • I can add/edit/delete an annotation at runtime process instance incidents that inform the next operator
                • The general scope is the same as CAM-9556, i.e. I can add an annotation to an incident and edit/delete it at any time; a comment thread or something similar is not in the scope of this ticket
                • The annotation is immediately propagated to the historic incident as well
                • The annotation is read-only in the historic incidents
                • The user needs to have the same authorizations needed to resolve an incident - any of UPDATE on PROCESS_INSTANCE and UPDATE_INSTANCE on PROCESS_DEFINITION

                  This is the controller panel for Smart Panels app

                        martin.stamm Martin Stamm
                        andre.bappert Andre
                        Votes:
                        0 Vote for this issue
                        Watchers:
                        3 Start watching this issue

                          Created:
                          Updated:
                          Resolved:

                              martin.stamm Martin Stamm
                              andre.bappert Andre
                              Votes:
                              0 Vote for this issue
                              Watchers:
                              3 Start watching this issue

                                Created:
                                Updated:
                                Resolved: