Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Jira issues go directly to the status to-do instead of going to backlog in jira server

priyanka
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
September 2, 2020

Jira issues go directly to the status to-do instead of going to backlog in jira server. What can the reason possibly be? 
there was unmapped status in the kanban backlog called- on hold having 29 issues which i moved to the column in progress still when i create an issue it goes to to do and not backlog. Can anyone please help?

 

2 answers

2 accepted

0 votes
Answer accepted
Trudy Claspill
Community Champion
September 2, 2020

Hello @priyanka 

Welcome to the community.

Is Backlog a status in your workflow?

Are you talking about what you see in a Kanban board, where the Backlog screen has been enabled?

The workflow for the issue type in the destination project will indicate the initial status an issue will get when it is created. Only one status can be specified in the workflow as the one to set when a new ticket is created.

If you are talking about the Backlog screen on a Kanban board, then in your board configuration you have to map a status to the Backlog. Issues in that status would appear only in the Backlog screen, not in the columns of your Kanban board. If the initial status of your new issues is To Do, and you want them to appear in the Backlog screen, then you would have to move the To Do status from the board column to the Backlog section.

Screen Shot 2020-09-02 at 1.48.49 PM.png

0 votes
Answer accepted
Sudarshan
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
September 2, 2020

Hello,

I think In your workflow, the default status is To-do when you create your issues.

Hence all issues get the To-do status, and they will be default be in backlog.

The backlog is simply a list of issues which are outstanding in your project, your team can create sprints and add them to it, as needed.

Maybe you can check your board configuration and workflow settings once again.!

Marcus Choi January 20, 2022

Hello,

 

So I am having an issue similar to this. When I bulk import a csv file as tickets and map the status to the jira fields, all the tickets get stored in the backlog and not the kanban board. Could anyone assist with this issue? I would like the import issues to go directly to the board based on the status that was mapped.

Trudy Claspill
Community Champion
January 20, 2022

 

<deleted>

 

Suggest an answer

Log in or Sign up to answer