Workflow Transition Order Standards & Project Transition API

Jira Development
, , , , ,
1

:loudspeaker: Request: Workflow Transition Order Standards & Project Transition API

Hi team,

In our Jira, we’re seeing that transitions like Backlog→ any status or In Progress → any status are allowed in some workflows. This creates inconsistency and makes it hard to define a standard transition order.

:red_question_mark: What We Need Help With

  1. Is there an Atlassian-defined standard workflow transition order?
    For example:
Backlog → Selected for Development → In Progress → Done
  1. Is there any REST API to fetch all transition names (including custom ones) for a project?
    We know about:
GET /rest/api/3/issue/{issueKey}/transitions

But this only returns transitions from the current status — not the full transition map for the project.

:chart_increasing: Goal

We want to:

  • Understand standard transition paths
  • Audit or visualize all transitions (custom or standard) per project

:framed_picture: Desired Flow (Standard)

Backlog → Selected for Development → In Progress → Done

But currently, transitions like Backlog → Done or In Progress → Backlog are allowed, which breaks that structure.

Any official guidance or API suggestions would be appreciated!

Thanks,
Sarvesh

2

Hello @SarveshLowanshi

This is a forum for programmers and developers to discuss problems that are specifically about developing applications for Atlassian’s products. Your question seems to be more about requesting someone to provide advice or training on how Jira’s Issue Transitions and Workflows fundamentally work, and you are asking to be given specific answers to what are essentially very broad, non-specific questions.

If you have such very broad questions about how to use Jira’s features or what can or can’t be done with its REST API, the best place to ask those questions really is the Jira section of the public Community forum.

Good luck!