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

Workaround for Custom Field Working with Comparison Operators

Becky October 23, 2023 edited

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
TAGS
atlassian, team '25, conference, certifications, bootcamps, training experience, anaheim ca,

Want to make the most of Team ‘25?

Spend the day sharpening your skills in Atlassian Cloud Organization Admin or Jira Administration, then take the exam onsite. Already ready? Take one - or more - of 12 different certification exams while you’re in Anaheim at Team' 25.

Learn more
AUG Leaders

Upcoming Jira Events