where is my ticket located on the backlog (middle? bottom?)

[Peter]

I have almost 1000 tickets on the backlog

I want to know if a certain ticket is a few tickets away from the top of the backlog, in the middle or at the bottom

How do I know?

-------

Till now I did the following and it worked:

1. I showed ALL ticket from the backlog (so not limited to 50 or 100 tickets)

2. I used the search functionality from my browser (Chrome) to search the ticket number

3. The browser showed me the part of the backlog the ticket was in

4. Based on the position of the slider (scroll bar) on the right of the screen it was visible where it was

5. For example: if it was quite close to the top then it was fine for me, if it was in the middle I would ask the product owner to move it to the top

So far, so good.

--------

I have now switched to the "Enhance my board and backlog" view and the browser will not give any search result when the ticket number is not currently on my screen. Lazy loading or something similar probably?

Does anyone have a good suggestion for an alternative / workaround?

[Steve Myers]

I agree this is problematic, even if you choose to show all.

Jira's backlog search will find it, but it displays it filtered to it, so you only see the ticket is in the backlog and don't get the context of where it is in the backlog.

Using Browser search doesn't work because the page is rendered as you scroll down, so it won't find it.

I tried creating my own filter to mimic the backlog contents, but that didn't work either as Jira chooses to page the results 250 at a time.

       Filter: Sprint is empty and resolution is empty and type != "Epic" order by rank

This page is indicating there is a way to remove the pagination, but I don't appear to have access to it.   I'll be following up with our Admin to see if this is reasonable to do.

Remove Pagination from Filter Results View (atlassian.com)

[Chris Buzon]

use ORDER BY KEY ASC  (or desc) in the query for that board/backlog. You can use other criteria as well, but KEY is clear and easy to understand.

[Peter]

Thanks for replying Chris!

You probably mean ORDER BY RANK? My goal is to see how high it is on the backlog and ordering by key would mean that I will see them in order of their generated number:

FW-1234

FW-1235

FW-1236

But you inspired me to just have a JQL in place ordered on rank and when I choose Bulk update I get the full list (the filter itself only shows the first 100) in which I can easily use the browser search.

It is not optimal but good enough for now!

Cheers!