Fixing a component

[Angie Elliott]

Hello, 

I've gone through the list of component issues already discussed here but could find an answer for my case. Here is the scenario:

Someone on my team created a kanban board as a component of another kanban board. So now I have two boards with different names but all the same issues, which is a nightmare of course. However, the person who created the board as a component of the other has made changes to issues on his "component board"

Question: How can I fix this to have one board with the issues, without losing any content/changes?

Thank you!

-angie

[Nic Brough _Adaptavist_]

Ok, there's some stuff to unpick here, but I'll keep it simple:

>Someone on my team created a kanban board as a component of another kanban board

This is not a thing in Jira, there's no "board as a component of another board".  A board is a board in its own right, it has no form of inheritance, componentisation or link to another board.

Boards are a view of a set of issues.  If you copy a board, you'll find the new one selects the same issues as the old, until you reconfigure it to look at a different set.

When you make changes to an issue on a board, you are not doing it "in the board", you are changing the issue that a board selects.  So if another board selects it, you'll see the issue changes made via the first board when you're viewing the other board because they're looking at the same thing.

So, yes, you can just delete a board.  It removes all the config, but has no effect on the issues behind the board.

[Angie Elliott]

Thanks so much! This helps.

[Kagithala Babu Anvesh]

When you deleted a board , only the reports based on that board JQL will be deleted. 

Issues / tickets will not deleted from project. 

So no issues , you can delete the not needed board.