Issue status remains unchanged after transition

Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.

Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.

*Except Fisheye and Crucible

Summary

Problem

When transitioning an issue from status A to status B, the screen loads but the status does not change. The issue doesn't transition to status B.

When dragging and dropping the issue across columns in an Agile board, status B shows as a possible destination status but the issue goes back to status A.

No errors are shown in the screen. No error are logged in the server logs nor in the console.

Diagnosis

Environment

  • The issue may occur in any environment type/config.

Diagnostic steps

  • Find out how if the workflow was created manually in Jira or imported as XML

  • Review the workflow transition's post function.

Cause

The issue occurs because the workflow transition's post function from status A to status B do not include:

Set issue status to the linked status of the destination workflow step.

This is a default post function that can't be removed from the UI. It is possible that the workflow was imported via an XML file that had the function removed.

Solution

Resolution

Add the post function to the workflow transition and publish the workflow.

Updated on April 2, 2025

Still need help?

The Atlassian Community is here for you.