Creating new task for the process instance is not listed in process instance tasks

[dbenesj]

Environment

Tomcat ZIP 7.21

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

Trying to create new task that should be part of the running process instance.
In the REST API documentation of the Create Task it is stated it can be done by providing parameter processInstanceId.
When this endpoint is called, HTTP 204 is returned, but when later performing Get Task List specifying processInstanceId, the new task is not returned.

Steps to reproduce

1. create new process instance
2. create new tasks specifying previously created process instance ID
3. list tasks for the process instance

Observed Behavior

Newly created tasks is not added to the tasks of the process instance.

Expected behavior

Newly created task should be visible when retriving tasks for the process instance ID.

[danielkelemen]

Hi @dbenesj,

Thank you for opening a bug ticket.
I'll test it myself soon and identify what the root cause is. After that we can think about a fix. This might take some time as we are currently in our release cycle. Thank you for your patience.

-Daniel

[joaquinfelici]

Hello @dbenesj,

I confirm the bug is present, not only for processInstanceId, but also for a few other fields. I created a failing test #4873 that shows which are the missing fields.

I found out that the root cause if that, when creating the Task object from the TaskDto, we're not setting every field present in the dto. This is done in the updateTask method. This way, the processInstanceId never reaches the java api so it makes sense that when you retrieve the list of tasks this one is not listed.

Would you be interested in working on this? The fix should be pretty simple, we also might want to add a couple of tests to check this behavior.

[dbenesj]

Hello @joaquinfelici,

Thank you for confirmation and nice description.

I took a look on necessary changes and found out that Task interface does not even include methods to set the those missing properties.
Adding them is simple, but made me think whether it is intentional. Found out that all those properties were added in the REST API in version 7.19 when documentation format has been changed. In version 7.18 none of those properties were mentioned.

So the question: isn't it actually intentional and just documentation was mistakenly adding those properties?