issue raise automatically reflect in backlog instead of backlog status

[Dort Teo]

each time issue is raised it automatically show in board/backlog. i have to manually shift up to the board.

in the workflow had already indicate to reflect in backlog status.

are these 2 backlog not related/link?

how to have the issues automatically to be on the board/board instead of board/backlog?

[Fazila Ashraf · Accepted solution]

Hi @Dort Teo 

Welcome to community!

You are right. These 2 backlogs are 2 different things.

The backlog section you see in the board is where the product backlog gets listed and can be groomed from there to plan your sprints (in scrum) or 'Selected for development' (in kanban). Read more in https://support.atlassian.com/jira-software-cloud/docs/use-your-kanban-backlog/

The other backlog you see on the ticket itself is only a status that you have named as Backlog. If it confuses your team, you could think about renaming that status as 'New' or 'To do' to avoid confusion.

[Dort Teo]

Thank you Fazila for your time and response.

well, each time the issue is raised it was automatic go into the board backlog, when the team looking at the kanban board, the backlogs are not shown, only to realise they are at the board backlog instead of backlog status. then need to manually shift up. need additional actions.. 

refering to the documentation you shared, thinking of disabling this kanban backlog, hoping it will be at backlog status, as the workflow indicated any new creation is to be at backlog status.

however as it navigate to the board settings, there is no option to "disable". is this because i'm using new_gen project?

[Fazila Ashraf]

@Dort Teo  , you should be able to disable it back from the 'Project settings'-> features section.

The enable instructions in https://support.atlassian.com/jira-software-cloud/docs/enable-the-backlog/ can help you find the disable button as well.

[Dort Teo]

got it! thank you so much! :)

[Fazila Ashraf]

If my answer helped, you can choose to 'accept' the answer :)  Future searches on this topic could easily land on this page