Can someone explain 'backlog' priority when you have multiple views of the backlog in same project?

[David Collins]

I have a process whereby we have:

A backlog view (1st)

A Kanban design process

A backlog view (2nd)

A Scrum development process

Issues start in the first backlog, and progress through the design and development processes... (Done is at the end of the development process)

The first backlog shows only issues in the status of 'backlog' i.e. stuff that still needs to be designed.

The second backlog shows every issue (obvs not yet done)... The reason the second backlog shows everything is because the PO wanted 1 place to prioritise everything regardless of status... i.e. just because something hasn't yet been designed doesn't mean it isn't the most important thing, (and then we work to try and help design get those items ready for dev quicker)...

What I want to understand is how, or what JIRA does when the PO changes priority in the first backlog?

It doesn't seem that that priority is carried through to the first backlog... So are both backlogs independently holding a prioritisation ranking? Or something else?

...and on a similar not how is that ranking treated when those issues could be in different statuses. So if my backlog is made up of issues in different statuses.. if I have a view 'kanban board' that shows each of those statuses, how does JIRA choose to display the order of the issues? Is it the same prioritisation as the backlog? ...and if you have multiple backlogs which one wins?

Any help clarifying the above much appreciated.

Thanks 

[Jack Brickey]

Hi David, ranking is global. Rather than attempting to regurgitate things let’s start with a couple existing resources to see if it helps:

old post
documentation 

[David Collins]

Hi Jack, 

Thanks for that, I think I have found the issue... Or at least in part so I still need further clarification / info.

On 'backlog 2'... We have some 'future Sprint' containers... So we have a rough forecast of what we will be doing over the next 6 weeks.

Each of the Sprint containers contains a number of issues. Plus the 'backlog' container below it.

On 'backlog 1' (which is a 'kanban backlog') the issues are correctly ordered as per the 'container' they sit within on 'backlog 2'. However those containers haven't maintained order...

So 'backlog 2' has this order:

'Sprint 2 container issues'

'Sprint 3 container issues' 

'Backlog issues'

On 'backlog 1' the issues are in this order:

'Sprint 3 container issues'

'Backlog issues'

'Sprint 2 container issues'

I have looked at the Rank field in issue search but couldn't quite make sense of the hexoranking... particularly the bit pre and post the colon... Post colon didn't seem to be covered in the links sent across.

Thanks