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?
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.
Thanks Craig,
Can you tell me how to put in automation that would bring them in the board to specific column?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I am having this exact same issues. No news on this since July?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have managed to solve this in the Project by:
- Opening the relevant Kanban Project/Board
- Go to Project Settings
- Go to Automation
- It loads an initial list of suggested Rules and Automations - don't bother trying to find it there. Use the AI tool - I entered 'Move New Issue to Board instead of Backlog'
- The AI had a think and then returned a new Rule 'Move Issue to Board on Creation'.
I then tested it by creating a new ticket and it seems to work fine.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Você é o pica, funcionou aqui
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There has been some movement in the feature request for this:
https://jira.atlassian.com/browse/AUTO-605
It should be implemented soon.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It is now Aug 2024 and still no obvious way to set up a board to have new issues in the board rather than the backlog. Automation is clunkier than a simple option in a menu.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.