Moving issue from one to another project puts project in not desired status

Ben Garcia

Hello!

I've been trying to find a solution for this quirk. When an issue is moved from one project to another the status is moved to a state that has resulted in people missing the ticket. 

Example, on the original issue the status is set to 'TO DO', when the user moves the ticket to another project the status for the new project defaults to 'In Progress' (not good since the assignee is still empty).

I tried shifting the status order (Settings -> Issues -> Statues (under 'issue attributes)) and also seeing if opsbar does anything, but that didn't produce anything.

 

The categories for both 'To Do' and 'In Progress' are correct To Do/In Progress respectively. Ideally I would want it to be 'Backlog' instead of 'In Progress' by default.

 

And yes, the option to pick the 'Backlog' is there in the drop menu, but the user moving this has missed/ignored it more than once. If anyone has some suggestions it would be greatly appreciated!

 

Thanks! 

Derrick Nguyen

Hi Ben - just to confirm, does the "TO DO" status exist in the "FA Standard Kanban Workflow -Ops"?  This is the most likely reason why Jira is prompting you to select a status when moving an issue.

 

Regarding the ordering of the list of statuses - a quick test has shown that the ordering of each status is defined by the order in which particular statuses were added to the workflow, i.e. "Investigate/Design" is likely to be the newest status in the "FA Standard Kanban Workflow - Ops" workflow.  Unfortunately, it seems that this list isn't configurable, but you might be able to reorder this list by recreating the workflow, and adding each status in the order in which you'd like to see them listed in the list shown in your screenshot.

 

Hope this helps!