Allow querying for standalone tasks

[ThorbenLindhauer]

This issue was imported from JIRA:

Field	Value
JIRA Link	CAM-14392
Reporter	4qVE0py What is this name? This pseudonym name was generated based on the user name in JIRA to protect the personal data of our JIRA users. You can use this identifier to search for issues by the same reporter.
Has restricted visibility comments	true

---

Background:

There is the possibility to create so called "standalone tasks" by either using  the Camunda Tasklist function "Create Task" or calling the REST-API ("POST /task/create").

Standalone tasks differ from regular process tasks e.g. by not belonging to a definition/not having an execution.

User Story (Required on creation):

As a developer, I want to be able to build a filter query that returns all existing standalone tasks using the task REST-API (e.g. Get List (POST))

Functional Requirements (Required before implementation):

• Query for standalone tasks via REST API
• Query for standalone tasks in filters
• Support querying within OR queries

Technical Requirements (Required before implementation):

• Add a new query option to the Task Query API like "isStandaloneTask"
• Consider the option in the task entity mappings
• Supported the option in task filters
• Make the option available in the REST APIs for querying (historic) tasks

Limitations of Scope (Optional):

Hints (optional):

Querying for the absence of a definition or execution by posting something like this to the REST-API:

POST /task

{
 "processDefinitionId": null,
 "executionId": null
}

does not seem to do the job. As a result, the query filter seems to be ignored and always all tasks are returned including the regular process tasks.

Links:

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @koevskinikola

---

Hi 4qVE0py,

Thank you for raising this topic. I will forward it for a decision.

Best, Nikola

[ThorbenLindhauer]

This comment was imported from JIRA and written by user @tmetzke

---

Hi 4qVE0py,

thanks for opening this request. I agree with Nikola here that this generally makes sense in the scope of the product.

We will add this to our backlog for prioritization in the next release planning sessions. This does not mean we will build this in the near future, however. If you are interested in contributing this as a pull request, we are happy to provide pointers on how to start with it.

Let us know if you have any further questions.

Best, Tobias