nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Jira can't find Filters with an underscore on filters name's

Rodrigo Fonseca de Campos

Hi,

So if I create a Jira Filter with the name that contains an underscore, for example:

Filter: "Xpto_A"

And then I try to create a new board and apply this filter to the board, the filter won't be found during a simple search, but if I change the name removing the underscore:

Filter: "Xpto A"

Now Jira is able to find the filter and now I can apply it to my board.

Is this a Jira bug or I can't add underscore to filters name's? If yes, shouldn't Jira warn the user about this?

Thank you,

Rodrigo Campos

Accepted answers

All comments

Nic Brough -Adaptavist-

The search ignores non-text things like underscores. The best thing to do is not use pointless things like underscores when giving something a human-readable name.

Rodrigo Fonseca de Campos

So maybe the user should be warning about that and Jira shouldn't allow the user to create filter name's with "pointless things like underscores" right?

Nic Brough -Adaptavist-

You should be allowed to name things whatever you want. Warning people of the hundreds of quirks of language and how computers work with them is not an essay I'd put in front of people every time they're filling in a field.

Rodrigo Fonseca de Campos

Sorry, but I don't agree, the user can't use any name, because there are security concerns to address like SQL Injection attacks for instance, they could try, but they shouldn’t be allowed to do it, a warning should pop-up explaining the problem.

I think that a simple validation for special characters would do it and this is not a difficult thing to do, at the business layer, so this rule would be applied automatically to all “Filter” textboxes, even a message saying that special characters aren't searchable, otherwise you are passing the burden of the issue into the customer and he/she have to find out by himself what is the problem of Jira and this doesn’t seems to me the right way to do it.

Is just my point of view.

unknown

I was just recognising similiar problem (Jira 8.5.4).

I have 2 test filters
a) XYZ-123
b) XYZ_123

Searching for "XYZ*" does NOT find any of the filters, but with "xyz*" (lower case + wildcard) both filters are found.

Also "XZY" and "xyz" (both without wildcard) find both filters.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-software