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

User Task: processInstanceId is not propagated when comment is added

    XMLWordPrintable

Details

    Description

      Environment (Required on creation):

      • Any setup with Tasklist

      Description (Required on creation; please attach any relevant screenshots, stacktraces, log files, etc. to the ticket):

      • When adding a task comment via the UI, the Java API for retrieving all comments of the corresponding process instance does not return the task comments

      Steps to reproduce (Required on creation):

      • Create a task comment in tasklist
      • Call TaskService#getProcessInstanceComments with the process instance id

      Observed Behavior (Required on creation):

      • The result is empty

      Expected behavior (Required on creation):

      • The task should be included

      Root Cause (Required on prioritization):

      • The underlying REST and Java API for creating comments does not set the process instance id
      • This is expected behavior on the API level, however on tasklist level it should be possible to set the process instance id

      Solution Ideas (Optional):

      • REST API: expose a process instance id parameter when creating a task comment so that the process instance id can be set along with it
      • Tasklist: Create a tasklist configuration setting that toggles if task comments are also assigned the process instance id (let's not change the default behavior since using task comments without the process instance id is a valid use case as well)

      Hints (Optional):

      mgm-controller-panel

        This is the controller panel for Smart Panels app

        Attachments

          Activity

            People

              michael.schoettes Michael Schoettes
              michal.dytko MichaƂ Dytko
              Tassilo Weidner Tassilo Weidner
              Michael Schoettes Michael Schoettes
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Salesforce