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?

[Jack Brickey]

@Bettina, welcome to the community. I believe you can meet your goal by simply setting up the Kanbans to only include the issues that apply. That is...

1. Pending Kanban ~ project = abc and status = Pending. In this board you will stack rank your issues. Once they are ready for development they are moved to the appropriate status, e.g. "Ready4DEV"
2. Component A ~ project = abc and status != Pending and component = A. In this board the component A dev team can order their board as they wish.
3. Component B - same as #2 but w/ B.

hope this helps. if i have missed your requirement please LMK.

[Bettina]

thanks for your Reply.

with "order" I actually ment "rank". Sorry for that. So what I'd like to have are two boards were requirements in a backlog can be ranked differently. 

As far as I'm concerned, my configurations are exactly as you described - what then causes Problems with ranking backlogs on several boards...

Maybe there is a solution using structures. I'm trying to figure out how right now.

[Jack Brickey]

@Bettina, yes I understood order to be rank. My point here is that if you have them setup the way I suggested then you will never have the same issues on more than one board at a time. This allows the 'owner' of each board to rank them how they want. In my proposed example all issues enter the 'planning board' where they are ranked and moved to Ready4DEV at which point they disappear for the planning board and appear on one of the dev boards. At that time the dev board owners can rank their own backlogs.

To be clear - There is only one Rank value in Jira so if an issue appears on multiple board any change in the rank will result in a change to all boards where the issue exists.