Moving cards between boards

[David Azar]

How can I move a card between boards within the same project?  

• I pull up the card and click on three dots in upper right
• I select "Move"
• I only get options in the dropdown of other projects to move it to
• I need to move it to a different board within the same project

[Jack Brickey]

You don’t move cards between boards. Boards are simply displaying issues based upon the filters that define them. So to have an issue displayed on another board look at the boards filter and adjust the issue to align. Hope this makes sense. 

[Diatta Harris]

That doesn't help with reporting, burn down or sprint health.

[Jack Brickey]

@Diatta Harris , I don't understand your point or how this is relative to the OP.

[Diatta Harris]

It is relevant because if a board is addressing multiple initiatives and you only want to see reporting on a single one, filtering doesn't work.  That is probably why they want to move cards to its own board.

[Jack Brickey]

I'm sorry but I still am not following. What is displayed on a board is completely driven by filters. If you wish to change what you see on the cord change the filter. This could be the general board filter or quick filters, etc.

this original post was talking about attempting to use the move command to move it issue between boards. The move command is not used for that. It is only used to move it to a different issue type that has a different workflow or to a different project. If you have multiple boards associated with your project, for whatever reason, and you wish to 'move' an issue from board A to board B then you need to understand the different filters so that you can modify the issue such that it disappears from board A and appears on board B.

[Diatta Harris]

Not always.  Some boards need not filter on anything and show only the cards assigned to that sprint.  Additional filters may apply to exclude or include specific cards tagged with that filter value.  BUT if someone is using a combined board and trying to get specific metrics based on the filtered value, it doesn't allow one to see burn down, sprint health based on that filter because those reports are at the board level.

[Diatta Harris]

Basically you will have to create a new project with it's own board.  You sound like us, we have multiple items on the board between multiple teams and the team operates differently.  The Scrum Master can't get to her true burn down or sprint health because everyone's cards are on the board and one can not filter at the burn down or sprint health level just at the project level so it's limiting.

[Jack Brickey]

@Diatta Harris , every board has an underlying filter regardless of whether you can access/visualize or not. Sprints are indeed based upon a filter. Well actually two. The primary filter illustrates what shows up in the backlog. The second 'sub-filter' is created when you create a sprint and drag issues from the backlog and into the sprint. Then when start the sprint those issue appear on the active sprint board.

example....

• go into your backlog, for a given project and click on the … in the upper right and choose configure board.
• In the general view, you will see the filter and you can edit that filter. This filter can represent one or more projects if you desire. This will define what issues show in the backlog.
• Create a sprint and drag issues into it. In so doing, you are adding the sprint name to all of the issues that you put into that sprint.
• Once you start the sprint, the board will illustrate those issues with that sprint name. So if you wanted to use JQL to illustrate those issues you could do so simply by saying sprint = XYZ. 
  
  So just to reiterate, all boards are based on one or more filters.

[Diatta Harris]

I understand things are filtered.  Our issue is at the project level our burn down rate reflects all tickets affiliated with that board.  Are you saying there is a way to recreate the board and use special filter to include the tickets they want to see?  If so, that doesn't sound like we will only see burndown and sprint health with that data filter and the project level.

[Jack Brickey]

No. I was just commenting on the fact that all boards are based on filters.

if you want to isolate Burndown, etc to a subset of a board/sprint you have two(?) options. Either you create different boards and run different sprints or you 'label' the issues to compartmentalize them then export the results and analyze using something like excel. There may also be an addon option to consider.

[Diatta Harris]

Re:  Creating a new board, it will create it's own burndown even if under the same project?

[Jack Brickey]

Yes. You can run parallel sprints too. The burndown is specific to a board not a project.