How to define that task go to the board and not to backlog in kanban board

Yehuda Yaakov August 4, 2022

Hi

all my task in kanban board going to the backlog. how I can define that task go to the board and not to backlog in kanban board?

4 answers

2 votes
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 4, 2022

Hi @Yehuda Yaakov welcome to the community.  By default new issues go into the backlog due to Status of the ticket.  If you had not enabled the backlog in the kanban board then the first column in that board would have been considered the backlog.  The only way to have them show on the board on create would be either put in an automation that would bring them in re: change the status or to create a new board without the backlog enabled and have your first column in that new board as your backlog.

Yehuda Yaakov August 9, 2022

Thanks Craig,
Can you tell me how to put in automation that would bring them in the board to specific column?

Like # people like this
Yehuda Yaakov August 9, 2022
Like Jess Jones likes this
Craig Nodwell
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
August 9, 2022

Columns are mapped to statuses, your automation would have to review the issue type on create and then apply the status you want for the column you want.

Jacob Rose April 20, 2023

I have this same problem. We're losing visibility of our work because things drop into the backlog and engineers may not remember to go to the backlog view, click the kebab menu, and add their tickets to the board when they start work.

It's very weird to me that this manual step is required when other actions imply that a ticket is no longer backlogged, but actively being pursued.

While I'm quite comfortable writing filters and automations, I don't understand what field(s) to update to move something out of the backlog. I would have thought that a status change from "TODO" to "IN PROGRESS" would have automatically moved something to the board, but no.

Like # people like this
Jess Jones May 17, 2023

We've been having this problem too. We want to have a backlog, but we want newly-created tickets (which are already assigned "To-Do" status!) to be on the board, in the—you guessed it—"To-Do" column. Having to go into the backlog every single time we create a ticket, to manually drag it to the board is a HUGE inefficiency/waste of time.

Why is it that when a ticket is created with the "To-Do" status, it winds up in the backlog, when there's a column on the board for that status?

Like # people like this
Jacob Rose July 9, 2023

That's a great point, Jess. Even a ticket in "TODO" might be something you want on the board, depending on your workflow.

I can't understand why default backlog status is not something we can choose for ourselves.

Max October 10, 2023

I am having this exact same issues. No news on this since July?

Brandon Checketts October 31, 2023

Same issue. This is a time waste and things get lost and then duplicated because the ONLY way to move something from the backlog to the Board is to drag it on the   Backlog page.

1 vote
Welske, Melanie February 28, 2024

I have the opposite problem. I enabled a backlog and want all my created issues to go directly into the separate backlog but somehow they always go into the first column of the board...and I actually have no idea why

0 votes
Max November 6, 2023

There has been some movement in the feature request for this:
https://jira.atlassian.com/browse/AUTO-605

It should be implemented soon.

0 votes
Bharathi
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.
August 4, 2022

As @Craig Nodwell rightly pointed out, if the backlog is not part of the kanban board's columns and is enabled as a separate section, all the newly created issues will go to backlog by default. If the backlog is not enabled on the kanban board, it'll be a column on the kanban board and in turn, even though the issues are in backlog status, they'll be displayed on the kanban board.

Hope this helps.

Thanks!

Jacob Rose April 20, 2023

Is there any field we can update to move something from the backlog to the board, though?

Updating the status from "TO DO" to "IN PROGRESS" doesn't make any difference, which is so strange to me.

The only way I know to do so is to use the UI to view the backlog, then manually choose "Move to Board" from the kebab menu. After that, the status of the ticket starts to matter. But before then, no matter what we do, it doesn't work.

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS
AUG Leaders

Atlassian Community Events