Workaround for Custom Field Working with Comparison Operators

[Becky]

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.
  
  • According to Advanced searching - fields reference ,it seems like a standard Jira version-picker or any other custom fields may not meet our needds
• 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.