The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

is there automation to migrate epics, issues, within a board to a new project

Mason Vieley
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!
September 21, 2022

there is a kanban board (one board only) created with

multiple "projects" containing epics, user stories, tasks, sub-tasks, bugs

that are categorized / separated only by title

I want to migrate / copy all the JIRA objects within all the separate titles

to separate projects in JIRA from the original one kanban board.

is there an automated way to do this, or is it all manually done through

Clone & Move operations?

 

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Trudy P Claspill
Community Champion
September 21, 2022

Hello @Mason Vieley 

Welcome to the community.

Do you really want the issues moved to different projects, or do you just not want the issues from all these different projects displayed in the one Kanban board?

0 votes
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 21, 2022

Welcome to the Atlassian Community!

Moving an issue is not a trivial action, you could (and usually are) changing the whole structure of the issue.  It's not like moving furniture from one house to another, it's like converting a terraced house into a detached one.

There's no automation for anything but the most simple case of structural change (where two project/issue types have identical configurations)

You will need to use (bulk-)move - this can check all the configurations and take you through the most simple path for changing project and issue type without breaking anything.

You may note I did not mention boards.   They are an irrelevance here, a board is just a view of a set of issues, it's not a container.  The board may lose sight of the issues if you move them, and it may show you different information about them because you've had to change the data on them during the move, but the board doesn't matter for issue move.

TAGS
AUG Leaders

Atlassian Community Events