I’m trying to set up a JIRA filter to catch tickets that don’t follow our naming convention. We’re supposed to start each summary with a 4-digit unit number, like 2345 or 9876.
Is there a way to create a filter that shows all issues missing this 4-digit prefix? I know I could use summary !~ "1234" to exclude a specific number, but I need it to work for any 4-digit combo.
Does JQL have some kind of wildcard for digits? Or maybe a regex-like solution? I’ve been scratching my head over this for a while now.
Here’s a simple example of what I’m after:
summary !~ "????" // Where ???? represents any four digits
Any ideas on how to make this work? It would really help us catch non-compliant tickets quickly. Thanks!
hey noah, i think i got a solution for ya. try this JQL:
summary !~ “{4}”
it should catch all issues without a 4-digit prefix. its been working great for our team. lemme know if u need any help setting it up!
I’ve faced a similar challenge in my previous role, and I found a solution that might work for you. JQL does support regular expressions, which is perfect for this scenario. You can use the following JQL query:
summary !~ “^\d{4}”
This regex pattern checks if the summary starts with four digits. The caret (^) ensures it’s at the beginning, \d represents any digit, and {4} specifies exactly four occurrences.
One caveat: make sure your JIRA instance has regex enabled. Some older versions or certain configurations might not support it out of the box.
If regex isn’t an option, you could also try a workaround using multiple OR conditions to exclude common prefixes, like:
summary !~ “0*” AND summary !~ “1*” AND summary !~ “2*” AND so on…
It’s not as elegant, but it can get the job done in a pinch. Hope this helps streamline your ticket management!
I’ve encountered this issue before, and there’s a straightforward solution using JQL’s regex capabilities. The query you’re looking for is:
summary !~ “^\d{4}.*”
This will match any issue summary that doesn’t start with four digits. The ‘^’ anchors the match to the beginning of the string, ‘\d{4}’ represents exactly four digits, and ‘.*’ allows for any characters after that.
Remember to enable regex in your JIRA settings if it’s not already active. This approach has been reliable in my experience for maintaining consistent ticket naming conventions across large projects.
If you’re still having trouble, consider reaching out to your JIRA administrator for assistance with regex configuration.