Filing Jira Tickets

Tickets get read outside the context that produced them, so each one has to stand alone.

Live tickets are awkward to unwind, so create_issue and link_issues both default to a dry run that returns the exact payload without sending it. Preview before every live write. A live write takes an explicit dryRun: false.

Nothing gets created without approval unless you are explicitly told to skip it. See Step 3.

Step 1: Read the target project's create screen

Bitwarden files into many projects and they do not share a shape. PM and SM expose an Acceptance criteria field; QA, VULN, and PLT do not. VULN has no Story type. PLT's only creatable type is Platform Initiative. Never assume a field id, a required field, or that an issue type exists.

Call get_create_fields with the project key, and again with the intended issue type. It returns the project's creatable types, then every field on that type's create screen with its id, whether it is required, and its allowed values.

• The type is not in the list: pick from what the project offers, or ask the user which one they want.
• The tool reports it cannot read the create screen (a 404): this means the project key does not exist, or the user lacks create permission there — the tool cannot tell which. Re-check the project key for a typo before concluding the latter; if it's correct, tell the user they likely lack create permission and stop. Do not guess at a different project.

Completion criterion: for the target project and issue type, a list of the required fields and the ids of any optional fields this work should populate.