How to move a ticket from the backlog to the board? Edited

[Matthias Posch]

Am I stupid or blind? I can't seem to find a way to move a ticket onto the board, without locating it on the "Backlog" page and moving it.

Setup:

• Jira next-gen
• Kanban

Flow that works:

• Go to "Backlog"
• Locate a ticket
• Drag&Drop to "Board" section or click "Move to Board" in the "..." menu at the right

Flow that does not work:

• Go to "Issues"
• Search for a particular ticket and open it
• Change status from whatever to "In Progress"
• !!! Now the status does change, but the ticket is still in the backlog and not visible on the board. There is no way to get this ticket on the board on the ticket detail screen

[Daniel Ebers · Accepted solution]

Hi @Matthias Posch ,

am I getting you right you want to select a bunch of issues and put them to a sprint? After that you want to transition them one by one or in bulk?

I tested it and it works the following way on my test instance in Cloud for a Next-Gen project:

1. I created a sprint
2. I created some test issues and updated the Sprint field using bulk operation (works fine for Jira Next-Gen)
   ==> Doing so a time-consuming locate of them in backlog view is not needed.
3. Start the sprint.
4. From there on you can draw the card later from column to column or (if this works better for your team) update it using another Bulk Change from TO DO into IN PROGRESS (or whatever status is needed that time).
   
   ==> Does this make sense? Is it what you are looking for?

Regards,
Daniel

[Matthias Posch]

Hey @Daniel Ebers

thanks for your response!

We work with Kanban, not Scrum Sprints, added that info to my post. So even if I would bulk change them, they would have the correct status but be stuck in the backlog, not on the board. So I just need to add a ticket to the board, without dragging&dropping it from the backlog. Makes sense?

[Daniel Ebers]

Hey @Matthias Posch

got you. The missing piece in the puzzle was the info about Kanban board.
Yes, you are right. This is not possible currently like you described.

Please watch and vote the corresponding Suggestion in order to show this is relevant to your team:
https://jira.atlassian.com/browse/JSWCLOUD-17471

At least there seem to be several parties interested in this - so I have hope :)

[Matthias Posch]

Awesome @Daniel Ebers thanks! :)

[Monika Rani]

Hi, @Matthias Posch You need to simply drag the issue from the backlog and drop it into the active sprint. You will be able to see that issue on to the board.

Please watch this video where I am telling about starting the

sprint: https://www.youtube.com/watch?v=k6rdai2eQLU

If you can not do drag and drop it means you do not have correct permissions. You should check your permission.

I hope it will help you.

[Matthias Posch]

thanks @Monika Rani for your response, but that doesn't solve my issue, if I have hundreds of tickets in the backlog it's cumbersome to locate them in the backlog view. I search for them in the issues advanced search or am in the epic view and getting to a specific issue that way. So there seems to be a "move to board" button missing on the ticket detail view.

[Sudarshan TS]

Hello @Matthias Posch  

What do you mean by "dedicated backlog"?

No option called move to board.!
But there is move to Sprint (if future sprints are created in your backlog)

I understand the below:
1. I assume you should be having specific boards with filters to view your issues. (example - support board to view issues received from support desk, innovations board etc....)
2. so, one of the ways would be to gather all the related issues in your backlog (bulk select) and group them to a specific filter criterion, then I think you may achieve your need easily.

Hope it helps.

[Matthias Posch]

Hey @Sudarshan TS , thanks for your response.

Sorry, let me clarify, by "dedicated backlog page" I mean THE backlog page :)

Also there are not multiple boards per project and also no bulk select in next gen.

[Sudarshan TS]

ok Great so its next gen, I am sorry.
let us wait for the experts to answer.!

but try this.
check in your board configuration --> columns --> if the mapping of status to column gives you any clue.!