Quick filter for searching BE in summary not working

[Kyle Wilz]

I've created a quick filter to display FE and BE tickets separately so we can better plan our sprints. We will typically put either [FE] or [BE] at the beginning of the ticket summary so we know which end it's on. For some reason using the same logic, the FE filter works perfectly, but the BE filter does not work at all. Any idea or solutions on this?

FE working:

BE not working:

[Kelly Arrey · Accepted solution]

Captain Obvious here.  If you're just getting started with Jira, one way to get around this is to use the component field - create components BE and FE, and set the component value for all your tickets appropriately. Now you can filter on `component = BE` to your heart's content.

[Kyle Wilz]

Appreciate that Captain Obvious ;)

Thank you for the help

[Trudy Claspill · Accepted solution]

Hello @Kyle Wilz 

Welcome to the Atlassian community.

Looking at this document:

https://support.atlassian.com/jira-software-cloud/docs/search-syntax-for-text-fields/

..."be" (case insensitive) is a reserved word and will be ignored with included in a text search filter.

[Kyle Wilz]

That makes sense... thank you Trudy