You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Would it be possible to query for any issues where, say, description is empty OR has a length less than X?
We've discovered that in certain exceptional situations, users have bypassed required text fields by entering "." or "tbd" or something similar. Since the forcing function of a required field has introduced bad behavior, I'd like to instead create a filter to identify empty or incomplete fields so that I can reach out and prevent them from remaining in that state.
Instance in question is self-hosted(aws), JIRA Software server 7.4.2.
Jira Query Language doesn't support that kind of text search natively.
However, ScriptRunner provides a search function that supports regular expressions, so maybe the following query returns all issues from FOO project with a description of less than 10 characters:
issueFunction in issueFieldMatch("project = FOO", "description", "^.{0,10}$")
Alternative methods at your disposal are:
Hope it helps.
For anyone (like me) still looking for this functionality (please?) several years later, it's one of the things you can hack your way around with Jira Automation and smart values, which do support text field length comparisons. No plugins required. I talk about this workaround process for date comparisons as a answer to this question.
For example, I have a comment that runs when an action is performed include the following line:
{{#if(issue.Description.length.lte(400))}}*Description seems a little short*.{{/}}
The key here is that {{issue.Description.length}} is something you can access and work from within the automation, which you could set to trigger on an action or schedule to run against a query of issues.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.