Bug tickets going to the bottom of the backlog

[Monica Tami]

When someone creates a ticket (Ex: bug) and assigns it to a team, it goes all the way to the bottom of the backlog of that team. 

we would like to create a sprint and call it "To Groom/ To Refine" so whenever someone creates a ticket they can simply add it to this sprint so PO can clearly see it and won't fall through the cracks. 

what other possible solutions we can have to avoid this?

Thanks for your help

[John Funk]

@Monica Tami  - Did the responses above answer your question? 

[Monica Tami]

Thank you both for your answer! @Fabian Lim and @Matt Doar 

I was looking to find ways to not mess up with the velocity of my team. This items usually had been completed it on the previous sprint but carry to the next sprint and appear at the bottom of our backlog as completed items outside the sprint. However my velocity doesn't seem to be accurate, How I can set up Jira in a way it does reflect my reality?

[Matt Doar]

The hard way is to review the backlog on a weekly basis.

One way to make that a bit easier is to add a Quick Filter that shows issues created in the last week. That helps you send the new issue to the top of the backlog if it is more important.

You could also add a new status to your workflow to indicate issues that have been triaged. And then use another Quick Filter to only show the issues that have not been groomed yet

Having a sprint "To Triage" is a bit odd because it will never be completed.

[Fabian Lim]

Hi @Monica Tami

The other option is to create a new kanban board for the specific team with only the bugs as a filter.  This way they will only see the tickets they need to handle.

Regards