What term combines the entities ticket, request, task, order, project?

Question

User interface

There is a main essence around which everything is built. Let's call it ticket for now .
It is assumed that it can be used as a normal appeal and as a task.
Comments, invoices and additional materials (files, links) are already attached to it.

Which term would be the most appropriate so that the user is not misled?

ps Or maybe add a feature? Something like the Type field .

Answer 1

Initially, for the user, any request to the service is always a "call" until it is accepted for execution.
Then, the operator / system puts a "flag" of the type of this appeal and turns it into one of the listed terms, in parallel notifying the user who created this appeal.