Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Why do some tickets, moved to another project, not default to the first status in the Workflow?

Christian Calkins March 21, 2023

I have noticed that when I move tickets from a Service Desk project to Company Managed Kanban projects, some projects have the status default to "Open" which matches the Workflow that the create transition goes to.

Some projects default to "In Progress" even though the Workflow has "Open" as the first status.

Is there a way tell why?

Does it have anything to do with the "Step Name (id)" order in the text view of the Workflow? If so, can that order be changed?

Thank you for any help or advice.

1 comment


Log in or Sign up to comment
Johnny FromCanada March 21, 2023

Workflow states are shared across projects in the Jira instance.  If you change from one workflow to another, where the latter has the same state as the former, it will leave the issue in that state by default.  If not, the move request should challenge you to select the destination state you want.

Note:  Workflow states are different from columns (which map to states).

Like Taranjeet Singh likes this
Christian Calkins March 21, 2023

Thank you Johnny.

I understand your point.

I really want to understand why sometimes destination status is default to "Open" and sometimes default to "In Progress" in the list of choices in the move steps.

I would like to be able to adjust the order of those destination status options.

Like Johnny FromCanada likes this
Johnny FromCanada March 21, 2023

K, makes sense.

Perhaps default status for moving is also affected by StatusCategory (To Do, In Progress, Done).  It might try “best effort” to match the category if it cannot match status exactly.

Like # people like this
AUG Leaders

Atlassian Community Events