How can I move an issue to the board outside of the "Backlog" page?

Ezra March 8, 2021

I should be able to see and choose where the issue is displayed from any screen that makes its contents editable. 

I feel like JIRA classic had a feature like this. 

But it seems the only way to add an issue to a Board is to find it in the Backlog list and drag or move to board. 

 

A simple workflow explaining this could be from any screen:

  1. I need to create a new issue for whatever the context is right now
  2. Click the create button from the top panel (visible on every page)
  3. Fill out the issue details
  4. Move the issue to the board/sprint. 

 

But I cant do step 4 from the issue, I have to specifically go to the backlog page, find the issue and move it to the board from the list. Then return to my previous location to continue. 

1 answer

0 votes
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 8, 2021

Hi Ezra, welcome to the Community. So the Backlog is generally the starting point for all newly created issues. Moreover. The Backlog is defined by the initial status when an issue is created. The board represents the workflow and the transitions therein. So if the backlog is defined as the initial status it stands to reason that the issue begins there and is transitions from there to the board. If I am missing your point or this doesn’t make sense please let me know.

Ezra March 8, 2021

My point is that moving issues directly from the backlog is often cumbersome as it assumes a particular way of working with issues.

When discussing/scoping/refining issues for work our team would like to move them directly to the board once we finish editing them, but in the screen to edit the issue can cannot do that, we have to navigate to the backlog, find the issue and move it, then resume our previous workflow. 

It might seem trivial, but as JIRA (continues) to run quite slowly, making those navigations during a fairly fast paced meeting takes far too much time and we frequently have to stop and wait for JIRA to catch up. 

Simply being able to see if the issue is in the backlog or on the board or in a sprint from the issue's page and being able to edit it there quickly and easily would be most ideal.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 8, 2021

If you are in the detailed issue view you can change the status directly which will result in the issue moving to the board. You don’t need to go the the Backlog view.

Ezra March 8, 2021

How do you do that?

  1. I selected a story in the backlog,
  2. navigated to its detail page,
  3. changed its workflow status from "To Do" to "In Progress",
  4. went back to the backlog page and refreshed it.
  5. the story is *still* in the backlog and has not transitions to the Board. 
Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
March 8, 2021

Are you using scrum or Kanban board. If Kanban In Progress items will show in both places until it is on done. While it is on the backlog page it isn’t in the backlog section. Yes that can be confusing. So my question is, when you move an issue to In Progress is is showing in both places?

Ezra March 9, 2021

We are using a Kanban board. 

If I take an issue that is on the Backlog page in the backlog section and change it's workflow from "To Do" to "In Progress",

The issue will remain in the backlog section of the backlog page and *not* move to the "Board" section on the backlog page and will *not* move to the board on the board page. 

Issues in the backlog section of the backlog page with the workflow status "To Do" *do not* display in the "To Do" column of the Kanban board. 

Beñat Gurmendi
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
July 15, 2021

We have the same issue. And is very frustrating.

Like # people like this
Wouter van Lelyveld
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
November 29, 2023

2.5 years later, still not fixed. Annoying.

Like Derek White likes this
Pablo Roque January 12, 2024

Interesting, I thought it was me for a second, we have a different software project and it works as expected but this brand new one seems to have this issue.

 

Board is blank and things are not leaving the backlog even tho they are properly assigned and in progress

Pablo Roque January 12, 2024

Assuming that we are talking about the same issue I think I was just able to "solve it", please try going to:

Project Settings >> Features

Set your features similar to what I have below:

Planning section:

Timeline: ON

Backlog: ON

Goals: ON

Issue Navigator: ON

The other ones Off

After changing this I can now move items out of the backlog and see them within the issue board

Adam DerMarderosian
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
January 24, 2024

We also use Kanban and have this same issue.  QA creates a ticket and it goes to the backlog.  They send us a link to the ticket.  We load the detail page of the ticket. Decide that it needs to be worked on immediately. Assign it and mark it in progress.  Then it would be nice to be able to move the ticket to the board so it can start the workflow but...  You have to go to the backlog, find it again, highlight it, select the context menu, choose move and then to the board.  Even a menu item for 'show this on the board would kill two of those steps and be generally helpful.

Like # people like this
tomasfejfar September 2, 2024

Yes, Atlassian certainly does not dogfood their own product! 

Ridiculously complicated workflow for a simple thing. I spend a lot of time trying to find a workaround. What I found is that we may use automations, which are accessible in the detail sidebar, but haven't test it yet. 

Like Holger Lange likes this
Holger Lange
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
October 11, 2024

Work for us:

Screenshot 2024-10-11 at 13.41.50.png

Created using the AI automation feature

Suggest an answer

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

Atlassian Community Events