nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Moving issue from DONE / DEPLOYED to backlog then it dissapears

Bart Spangenberg

Dear reader,

When I try to move an issue from the kanban board to the backlog it dissappears. See the screenshot for the button that was pressed.

In the backlog overview the issue isn't added. "I thought that it might take some time, however I did it for a few issues over a few days, and they are all gone. Did it go somewhere else or is this a bug?

Thanks for the help.

Kind regards,

Bart

Accepted answers

Trudy P Claspill

Hello @Bart Spangenberg @Alex Koxaras -Relational-

The "Move to Backlog" option is available when you are

- working with a Team Managed project

- using a Kanban board

- have enabled the Backlog feature.

When you select the "Move to Backlog" option, then the issue should stop being displayed in your Board view. It will start being displayed in the Backlog View only if it is not in a "done" status. An issue in a "done" status has been completed, and the Backlog displays only incomplete work, so there is no reason to show a "done" issue in the Backlog view.

The issue still exists, and you can see it using an issue search or by selecting the Issues option from the navigation pane on the left.

All comments

Alex Koxaras -Relational-

Hi @Bart Spangenberg and welcome to the community

Go to your

project > project settings
Board > Columns and Statuses
Check if there is any unassigned status and assign it to a column

Let me know if that resolved your problem.

Bart Spangenberg

HI @Alex Koxaras -Relational-

Thanks for your message.

Unfortunately the Unassigned statuses are empty.

Could it be something else?

Alex Koxaras -Relational-

@Bart Spangenberg do you have any app installed on your instance? For the love of me, I can't find the "move to backlog" action on my instance. So one of the three cases stand: