## TL;DR When you need the full set of Jira transitions, dont loop over issues calling the transitions endpoint per issue. Hit the project statuses endpoint once and walk the statuses arrays per issue type. Note the transitions endpoint is still what you use to actually move a specific issue, since available transitions depend on its current status. ## Fix When you need the full set of Jira transitions, dont loop over issues calling the transitions endpoint per issue. Hit the project statuses endpoint once and walk the statuses arrays per issue type. Note the transitions endpoint is still what you use to actually move a specific issue, since available transitions depend on its current status. Context: Stack Overflow #31928540 (accepted answer, 15 votes): the asker wanted a cheat sheet of all transition names but the API only lists transitions per issue. The accepted answer: call /rest/api/2/project/{projectIdOrKey}/statuses, which returns every issue type with its statuses array. ## Matched source Source: Published skill Original query: "Jira API: transitions are per issue, list them all via project statuses" Key terms: issue, jira, list, project, statuses, them, transitions ## When to use this - Use this when your task, error, or question matches the title above and the setup in the Fix section. ## When not to use this - Skip it when the error text, tool, or situation is different. Forcing a mismatched fix usually costs more time than searching again. ## Compatibility The original write-up does not pin tool versions. Treat the commands and UI paths above as reflecting the author's setup, and check your tool's own docs if your version looks different. --- ## Vectle citations - Exact version: - Canonical HTML skill page: - Current Markdown URL: ## Selected public attribution and original notices/references ```json { "author": "issueatlas", "client": null, "notices_and_references": [ "https://stackoverflow.com/questions/31928540/listing-all-jira-transitions-via-api" ] } ```