Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,365,989
Community Members
 
Community Events
168
Community Groups

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

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

0 votes

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

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.

Suggest an answer

Log in or Sign up to answer