Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Workaround for Custom Field Working with Comparison Operators


Hello Atlassian Community,

We are currently looking to implement a new Jira field that can store multiple values of our product versions. We have the following requirements for this field:

  • Multi-select
  • Support comparison operators such as <, >, <=, >= in JQL queries. For example, we should be able to use queries like VersionField >= 2023.1.1.
  • Extra credit for regex-style matching, as provided by versionMatch(). It would be helpful to be able to use expressions like "2023.3.*"

In my research, I have found that meeting these expectations within the constraints of Jira's provided field types can be challenging. Is it possible to create a custom field from scratch, where we can explicitly define how it can be interacted with Jira as well as how it can be searched using JQL?

If creating a custom field is not an option, are there any workarounds or alternative approaches that can help us achieve our desired functionality?


Your insights and suggestions would be greatly appreciated.

0 answers

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events