Moving tickets to another board

Question

Hi,

We want to create several boards at our account. We want to have the possibility to move tickets to another board. By moving the tickets we want to keep the original ticketnumbers.

Our developers work for 3 clients. The client adds tickets/bugs at their own Jira board and the project managers will move the tickets/bugs to the board of the developers. The developers will have 1 board with all the tickets/bugs for the 3 clients.

Can you please inform me how it's possbile to create this?

Looking forward to hearing from you.

Kind regards,

Merel Visser

Gary Pasquale · Answer

Hi @Merel Visser,

Depends if you're talking about moving issues between 'Projects' or 'Boards'. They are two different things.

If your moving issues between Projects, then the issue being moved will assume the issue key of the project it is moving to. However, it will retain it's original key in the background so can still be found when searching via JQL.

The easiest solution would be (if your developers have access to the issues in the 3 client projects), to just set up a board that displays only the issues that have been assigned to them.

If your filter was something like:

project in (ProjectA, ProjectB, ProjectC) AND assignee = Developers

This way no moving of issues is required. Issues keep the original issue keys.

Regards,

Gary

David Hazeel · Answer

Hi Merel,

Could you please clarify if you are all working off of the same project in Jira? If you are then you can adjust the queries on each client's board so that it only displays the relevant tickets. I can give you an example if this is the case.

If you are in different projects, it's a bit more manual. There's some really good discussion here: https://community.atlassian.com/t5/Jira-questions/How-do-I-move-issues-from-one-project-to-another-project/qaq-p/34401 Personally when I do this I export the ticket as a Word document or XML file and then use it to create a new ticket where I need it. Moving issues from project to project is problematic as each project is likely to have different custom fields, etc.

Hope this helps.