How to order Kanban-Backlog list without impact on other boards within the same project

[Bettina]

Imagine, you have one Jira-Project and three Kanban-Bocklogs:

• In one Backlog, there is a list of all requirements in a project nobody is working on (status 'pending'). It will have to be sorted by priority of working on during the next iteration.
• In the two other Backlogs, requirements are filtered by component. Team A works on component A and team B works on component B. For planning the next steps, each team would like to set the order of its own backlog based on their wishes for priority.

Unfortunately, each movement of a requirement in a team backlog will have impact on the overall backlog of all requirements. This is totally legitimate since all requirements are from the same project.

But: Is there a way to work with Kanban-Backlogs without this impact? E.g.:

• Blocking the impact on the order of other lists (so team A can move requirement-1 to the top on their list without moving it on the overall list)
• Blocking the ability to move requirements up and down in several boards
• Any other ideas how different teams can order their requirements for themselfes in order to plan the iteration based on their different views?