Create an issue (key is assigned by the server).

The key (e.g. KJ-102) is assigned by the server. priority is highest, high, medium, low or lowest (default medium) — set it when the user or the issue makes it clear. status defaults to the first status of the project (Backlog on kanban and pipeline boards). sprint has no default (scrum only — kanban and pipeline issues have none): omit it (or null) for the backlog, or pass a sprint id. Several sprints can be active at once when the project has parallel sprints on — if the user says "the current sprint" and list_sprints (state=active) shows more than one, ask which. Custom fields (spec D129): pass values in fields keyed by the field id from get_project fields — text / select / customer / url / person = string (select: one of the field's options; person: a user id from list_people), number / money = number (money is kept with 2 decimals in template_settings.currency), date = YYYY-MM-DD. Only fields whose types include the issue's type are accepted and required ones must be present (else 400 invalid_field_value, details.expected = required); an id the project does not define → 400 unknown_field; a formula field is never written (400 formula_readonly — read it in computed). Sales & Billing (D130): a deal is a task (customer, amount, quote_no, payment_terms, sent_at, signed_at, valid_until, owner); an installment is a subtask with parent = the deal key and fields amount, bill_on, due_on (invoiced_at, invoice_no, paid_at, paid_amount come later) — its state Not yet → Invoiced → Paid is derived from invoiced_at / paid_at, not from status, so leave status out. Service desk: a request is a task — set fields.requester to the person you take it for (ask who when unclear); sla_due defaults from urgency and the project's sla_days. Budget planning: a budget line is a task with planned (and actual); remaining is a formula. Roadmap & Goals (D131): a goal is a task with start and end (required, YYYY-MM-DD), quarter, owner, reach / impact / confidence / effort; score, progress and linked are computed (formula / rollup → 400 formula_readonly if sent). A key result is a subtask of the goal. links may point at issues of other projects of the company (you must open both — 403 link_target_forbidden) and, with type delivers, at a release KEY/R-n. Body: Optional colour (D137, use sparingly; markdown stays the main format): <mark>text</mark> highlights (yellow; or <mark data-color="green">), <span data-color="red">text</span> colours text; colours yellow, green, red, blue, purple (e.g. green = passed / expected, red = bug / actual, purple = question); any other HTML is shown as plain text; keep the open and close tag in the same paragraph.

You act with exactly the rights of the user who owns this token; a project you cannot see returns not_found.