Jira transition missing? Find the workflow condition that hides it

A Jira transition vanished from the status menu with no message? See which workflow condition hides it, checked with your own permissions, in one click.

4 min read

You open a work item to move it to the next status, and the transition is not in the menu. Jira gives no message. A workflow condition is not met, but Jira does not say which one, or whether it is a condition at all and not a missing permission. So the person asks a Jira admin, and the admin opens the workflow editor and works through each condition by hand.

Simple Workflow Automation answers that question on the work item itself. Its panel, Why can't I move this?, lists the transitions Jira hides from you and says for each one whether a Simple Workflow Automation condition is the cause. Simple Workflow Automation is coming to the Atlassian Marketplace.

Why Jira hides a transition without a message#

A workflow condition decides whether a transition is offered at all. When it is not met, Jira leaves the transition out of the status menu. A validator, by contrast, runs after you pick the transition and shows its error message. That is why a missing transition is the harder one to explain: there is no message to read.

The Troubleshooting page lists "A transition is missing" for this reason, and points to the panel.

How the panel finds the cause, step by step#

  1. Open the work item and click Why can't I move this? in the row of panel buttons. Jira shows the button to people who can edit the work item, and nothing runs until someone clicks it.
  2. The app asks Jira for every transition from the current status, including the ones that fail a condition. It asks as you, with your own permissions, so it never shows anything Jira would not show you.
  3. For each hidden transition, the app runs the Simple Workflow Automation conditions on it as Jira expressions, again as you.
  4. The panel opens with one line: how many transitions Jira offers you, and how many more it hides.
  5. Each hidden transition gets a row with one of three labels:
    • Blocked by a rule: a Simple Workflow Automation condition is not met for you. The row names the rule type, for example Allowed statuses, Allowed people, Related work items, Only at certain times or Expression gate.
    • Not by our rules: none of our conditions hides it. The cause is a Jira condition, a permission or another app.
    • Cannot tell: our condition sits beside conditions the app cannot read, or the app has nothing to judge by. The panel says so instead of guessing.
  6. Fix what the rule checks, such as the status, a field or a linked work item, then click Check again. The panel runs the check once more.

What a Jira admin sees#

A Jira admin gets more detail from the same panel. The app reads the workflow as it is now, as the admin, so the answer matches the current workflow. Each blocking rule also shows its own sentence, which says what the rule checks.

Anyone else gets the answer from the last scan of the workflows. A Jira admin runs that scan on the Rules tab of the admin page. When an answer rests on a scan, the panel shows the scan time in UTC and says the answer may be out of date if a rule changed since.

When the panel says it cannot tell#

The panel names the reason when it has no answer:

  • No admin has scanned the workflows yet, so the app does not know which rules are on this workflow.
  • The last scan saw no Simple Workflow Automation condition, but the workflow may have changed since, and only a Jira admin can read it as it is now.
  • The work item is in a team-managed project, whose workflow the app cannot match to its rules from the panel.
  • Jira lists no transitions for you at all. That happens when the status has no way out or when you lack the Transition Issues permission, and Jira does not say which.

Why it reads Jira as you#

Every read about the work item, its transitions and the expressions runs as the person who opened the panel, so Jira's own permissions decide what you see. The app reads the workflow scheme as itself, as every rule does, and takes only the workflow's name from it. The Trust pages list the panel among the app's work item panels.

The panel runs at most 20 expressions per check. When a transition would need more, its row says Cannot tell.

Share this post

Related help pages

Back to Blog