nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best way to copy 400+ issues from one project to another?

Ken Uehling

Right now I am working on creating a new software project kanban board to combine two other software project kanban boards. What would be the best way to copy the tickets / issues from the two boards into this new one? From reading suggestions online, it seems the best way would be to use a plugin? Any recommendations? Thank you!

Accepted answers

Alexey Matveev

Hello,

Tickets do not belong to boards. Tickets are selected by boards according to the filter, defined for the board. Just make a filter, which combines the two filters, defined for the first two boards, with the OR clause and you will have, what you want.

All comments

Alexey Matveev

Hello,

Ken Uehling

Hello Alexey,

Thank you for your prompt response.

I am not understanding your answer. Right now I have two projects that issues can be created in. How would I use a filter to have the issues in both those two projects show up on this new project kanban board that I created? We want to merge these two projects for better record keeping and to have everything in one board.

Thank you.

Ken

Walter Buggenhout

@Alexey Matveev is suggesting that you keep both projects and configure your existing kanban board to display issues from both projects. In order to do so, you would go into your board configuration, locate the current board filter and then edit this to something like:

Project in (ProjectA, ProjectB)

All your issues will remain where they are, your board will just display them all.

Alexey Matveev

If you want to merge two projects into one of the two projects, you can use the bulk edit feature to move all issues from one project to the other:

https://confluence.atlassian.com/jiracoreserver073/editing-multiple-issues-at-the-same-time-861257342.html

Go to the Move Multiple Issues part.

Gabriel Tessarini

Hello Ken, there a Groovy script called "scriptJiraCopyIssueToOtherProject" for Script Listener of Script Runner in this GIT repo bellow that automatically copy as issue with same name and type from one project to other when it reach some specific status like... "Version of Production" from project called "DEV" to project "Production", for example.

In your case, i think that just setting the code on Script Console and passing a get for all issues on project you can copy then to the other project.

https://github.com/GTessarini/JiraAutomations

I hope help you!

Regards

Gabriel Tessarini.