Move issues from one Board to Another Board in Jira

[Roja Gurram]

Hi All,

Is it possible to move tickets/issues from one Kanban board to another board ?

[Nic Brough -Adaptavist- · Accepted solution]

No.  Not because the code doesn't support it, but because the concept is nonsense.

You're thinking of boards as containers for issues and that is wrong.  Boards are a view of a selection of issues.

For it to look like an issue "moves between boards", you don't move.  You change the issue in a way that means it stops matching the filter for the "source" board and starts matching the filter for the "target"

[Roja Gurram]

Hi Nic,

Thanks for the respond.

OK, Can we configure the filter of the source board same as to that of destination Board please ?

[Nic Brough -Adaptavist-]

Of course you can, but that does mean issues will appear on both boards (assuming similar config for them as well as the filter)

[Roja Gurram]

Of course you can, but that does mean issues will appear on both boards - Is it ? I thought it would appear on both boards.

Finally Is there any other possibility to achieve this please like In filter can we add specific WORKFLOW status to see the issues on Target board ?

[Nic Brough -Adaptavist-]

But you were asking how to "move" issues, which implies you want to stop it appearing on one board and make it appear on another.

Yes, you can use status in your board queries.

[Roja Gurram]

But you were asking how to "move" issues, which implies you want to stop it appearing on one board and make it appear on another. -

No, it's not entirely to stop. It should appear on both boards can't we see ?

Yes, you can use status in your board queries. -

If i use status same as the SOURCE Board  for the target board as well issues will appear on both both boards related to specific statuses ?

[Nic Brough -Adaptavist-]

I am sorry, I really cannot work out what you are asking any more.  I've explained how to make boards select what you want and how to make them look like you are "moving a card from one to the other".  I'm not sure what the question is now.

On the status, yes, that's what the filters do.  Return a list of issues that match the query.

[Avram Score]

[redacted]

@Roja Gurram You can click on the dot menu in the top right of the ticket and select "Move". Then move it to whatever board you want.

[Andy Heinzer]

@Avram Score Please review our Rules of Engagement.  It is never acceptable to use such derogatory name calling on our site.  You are welcome to disagree with other users, but name calling will not be tolerated.  I have edited your previous reply to remove this content in violation of our community rules.

For what it is worth, Nic's previous answer is technically correct.  In company managed software projects, the way boards select what issues appear there is based on the filter that board is using, more info in Configure filters.  While true that moving an issue from one project to another might have the appearance of having that issue move to a new board this is not always the case as we don't know what the filter is for every board involved.

In a team managed project, those boards only show issues in a single project.  In which case, if you're moving the issue to a team managed project, it should then always appear on that projects board.  But the same is not always true of Company managed projects, and the boards associated within them.  So I can understand why there is confusion, or dispute about the answer here.  Please try to give other users the benefit of the doubt that they are trying to help users here and working in good faith.

Thanks

Andy

[LaTisha Jenkins]

I still need help and is confused.  I have an old kanban board but the team is now sprinting.  A sprint board was created with the same filter as the kanban board.  Both of these boards are under the same project.

I would like to know if I am able to move the old kanban backlog issues to the new scrum backlog?

[Nic Brough -Adaptavist-]

No, you can't "move issues to another board".  Boards are not containers of issues, they select a set of them to work with (that applies to the backlog too - the backlog is another view of the issues the board is selecting for.

To get issues into the Scrum backlog, make sure they are selected for by your board filter, check they are not set to "done", and their status is mapped on to the board.

[LaTisha Jenkins]

I figured it out.  it was in the way I had my columns.  in the kanban board, the backlog had 'to do'.  In the scrum board, it was unmapped.  I created a column with 'To do' and now I'm able to see all the backlog items on the new scrum board.

Thank you for your help!

[Nic Brough -Adaptavist-]

Mapping the columns is the one I get wrong most often!  I keep spending ages looking at the queries and "done" settings and completely forget to check mapping.

[Kelly Lillis]

When moving a ticket from one Team-Managed project to another Team-Managed project, when the destination project has a backlog, I'd like to have the option to select if the ticket should land in the board or the backlog as part of the move. Is this possible?

[Nathan Djanogly]

It's much easier than you think.

In the settings, there's an option to move a ticket between projects. 

[david meakin]

I've just done this so I know I can move issues between projects. If you go into the ticket then click the 3 dots in the top right and then select move. You can then choose which project you want to move the ticket too.

You have to open the ticket - do not try using the 3 dots on the overview of the board tickets.

[Nic Brough -Adaptavist-]

You can also do it without opening an issue, if you use "bulk edit" in the issue navigator (search results)