Transitioning state does not move out of backlog

Reinhard Hofmann October 11, 2024

Hi,

I have a Kanban Board with Backlog enabled, see below.
But when I change the state of a Backlog issue, it is not moved to the Board.
It seems that the Backlog/Board-state is treated in addition to the Workflow-state.
How can Backlog be treated like all other states, so I can change it to ToDo - having it moved to the Board automatically?
I expected this to be the default in my standard Kanban board...

BTW: it would also be interesting, why some of the states in the board an backlog are written in bold, while others are not.

Screenshot 2024-10-11 084040.png

Screenshot 2024-10-11 084316.pngScreenshot 2024-10-11 084149.pngScreenshot 2024-10-11 084020.png

1 answer

0 votes
Tobias H
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.
October 11, 2024

Hi @Reinhard Hofmann and welcome to the community!

The answer is that the status do not represent whether the issue lies in the backlog or board.

However, it's very easy to set up an automation that moves them over automatically for you:

When Issue transtion From / To STATUS
THEN Move issue to board:
* Select which board
* Select what it should move to (in this case board)

Screenshot 2024-10-11 at 11.24.11.png

This should fix the issue you are describing, and if it doesn't let me know! :D

Reinhard Hofmann October 11, 2024

Hi @Tobias H - and thanks for the amazingly quick response!

I saw another project, that also uses the Backlog (interestingly there this Feature cannot be disable) - but the the Backlog is somehow configured directly as state - which sounds more reasonable to me (does not need an additional automation to synchronize the Backlog-vs-Board-state with the Workflow-state). But how could I configure my board to work like that as well?

Screenshot 2024-10-11 121453.png

Screenshot 2024-10-11 121427.pngScreenshot 2024-10-11 121730.png

Tobias H
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.
October 11, 2024

Hmm, to me that looks and sounds like a company managed project. Both the workflow and the lack of ability to disable backlog.

I think the Selected for Development in the picture is a sprint, as it has a darker box around it.

They would then either manually move issues into the "Selected for Development", or have an automation that would move them once the transition is done.

They would then use the "Start Sprint" button to move all the issues into the current sprint.

But then again, I am just making some guesses based on the limited info I have of the workflow arrows and backlog layout 😅

Reinhard Hofmann October 11, 2024

Ok, thanks - I will try to gather some more details.

Offtopic: do you have an idea regarding the "BTW" part of my original question
(why some states in the Backlog/Board view are bold)?

Tobias H
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.
October 11, 2024

No clue, I have never seen/noticed that before. I just went and checked in my own teams backlog and the status appear not bolded first as well, if I however over them for a second or so they become bold.

I know Atlassian are pushing out their new Jira layouts around now, so that might be related?

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
FREE
TAGS
AUG Leaders

Atlassian Community Events