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
Home Q&A Discussion groups Articles Ask a question Search
Learning
Events
Champions
Release Notes
Community
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes
Forums
Home Q&A Discussion groups Articles Ask a question Search
Learning Events Champions Release Notes

Forums

Articles
Create
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 
Q&A
See all
Community resources
Top groups
Explore all groups
Community resources
Learn
Community resources
Events
Community resources

Merging two different backlogs into a si gle backlog

kanaka prasad ponnuru
kanaka prasad ponnuru
Contributor
October 13, 2022

Hi Team,

We have around 550 tasks(including all epic, feature user Stories & subtasks) in the board. Which needs to be migrated to another board.

Is it possible to migrate all epic/user Stories/ subtasks to "Tribe backlog"?

Any precondition (eg mapping of fields between one board to Tribe board) needed?

Is it possible to maintain a single backlog/ board

Thanks.

 

Watch
Like Be the first to like this
897 views

2 answers

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Nic Brough -Adaptavist-
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.
Get recognized
October 13, 2022

Issues do not "migrate" or "move" between boards.  Boards (and their backlogs) are a view of a selection of issues, they are not containers for issues.

All you need to do is set up your "Tribe" board so that it selects all the issues you want to see on it.

View More Comments
kanaka prasad ponnuru
kanaka prasad ponnuru
Contributor
October 13, 2022

Hi @Nic Brough -Adaptavist- ,

If issues do not migrate or move between boards means then how we can achieve this 

Can you please elaborate the process what exactly needs to be done?

Thanks in advance.

Like
Nic Brough -Adaptavist-
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.
Get recognized
October 13, 2022

You cannot, as I explained already.  

"Moving between boards" is nonsense (because boards are not containers)

To set up your "tribe" board, create a filter for the issues you want to see on it, then create a new board based on that filter.

Like
Reply
0 votes
Dave Mathijs
Dave Mathijs
Community Champion
October 13, 2022

Hi @kanaka prasad ponnuru If you create a new Scrum Board containing all the impacted projects (+ necessary filters if needed), you'll have a new backlog as well. Have you tried this?

Reply
Jira
Jira
TAGS
AUG Leaders

Atlassian Community Events

    See all events
    Community
    Forums
    FAQs Forums guidelines
    Learning
    About learning Resources
    Events
    Champions
    Release Notes
    Copyright © 2026 Atlassian
    Privacy Policy Notice at Collection Terms Security