**Acceptance criteria**

- Have a project independent route in the API v3 for creating work packages via `POST /api/v3/work_packages`
- The behaviour is similiar to the project specific route `/api/v3/projects/:project_id/work_packages`
- The `project` attribute/link on the resource:
- is set to the first of the current users project if no project is provided
- can be set like other fields (e.g. status, type) via e.g.

<!-- end list -->

{
"_links:"
{
"project":
{
"href": "/api/v3/projects/openproject"
}
}
}

- The `form` describing the desired payload is to be available via `POST /api/v3/work_packages/form`
- The `project` attribute needs to become `writable` in the schema
- The schema’s href linked in the `form` is unchanged `/api/v3/projects/:project_id/work_packages/schema/:project_id-:type_id`

Begin of the insertion**Out of scope**End of the insertion Begin of the deletion **Open**End of the deletion

- Begin of the insertionRemove project specific routes. Technically, they won’t be needed onceEnd of the insertion Begin of the deletion DoEnd of the deletion we Begin of the insertionfully switchEnd of the insertion Begin of the deletion needEnd of the deletion to Begin of the deletion keepEnd of the deletion the Begin of the insertionglobal create.End of the insertion Begin of the deletion project specific routes?End of the deletion
- Begin of the insertionWeEnd of the insertion Begin of the deletion I guess weEnd of the deletion should keep Begin of the insertionthemEnd of the insertion Begin of the deletion it for nowEnd of the deletion as removing it would violate API versioning.