Oktul Regex Field for Jira
Oktul Regex Field adds two Jira custom fields that fill themselves in from the person, the space and the form, and check every value against your rules.
Ask for a demo (opens in a new tab) We reply within 24 hours, Monday to Friday.
What the video shows
- The title, Fields that fill themselves in, beside the prefill template.
- From the person and the date: the Request details paragraph reads Reported by Emma Paris on 30 Oct 2026.
- And from the form as you type: the summary, Laptop screen flickers after the update, joins the paragraph.
- Strict input adds the country code: the first digit of the callback number brings +372 with it.
- Try your rule before you save: in the field's Rules, a value is tried against the pattern and accepted.
- Oktul, Atlassian Marketplace Partner.
Jira fields neither prefill nor keep a format
A Jira field opens with one fixed default
It cannot start with the reporter's name, the space or what was just typed in Summary. People retype what the form already knows, and an Automation rule can fill the field only after the work item exists.
Codes and phone numbers arrive in every format
Spaces in one value, dashes in the next, a country code in a third. JQL cannot find them reliably, and an Automation rule cannot act on them.
A workflow validator misses imports and the REST API
Jira's own text fields have no format or length rule. A validator checks only at a transition, so a value written by the REST API or an import skips it.
Jira checks the value on every write, whatever wrote it
Oktul Regex Field for Jira adds field types that fill themselves in from the form and carry their own rules. Jira checks those rules in the field's own validation. The single-line field can also refuse wrong characters as they are typed.
Four things the fields do
You set the rules per field context. One field can follow different rules in different projects.
Prefill
A field opens filled in on the create screen, the portal request form and a transition. Its template takes smart values: the person, the date, the space, the work type and any other field on the form.
Set a prefillValidation rules
Simple rules set a length, a format such as 999-9999, the characters allowed, and what a value starts with, ends with or contains. Advanced is one regular expression, which the browser and Jira read the same way. Lookarounds and back references are not supported.
Write the rulesStrict input
With strict input on, characters the rules refuse cannot be typed, and fixed characters are added for you. With the format 999-9999, typing 1234567 gives 123-4567, and a pasted value is formatted the same way.
Turn on strict inputRich text paragraph
The paragraph field uses Atlassian's own editor and checks its plain text against a length, the allowed characters or a pattern. On a portal request form it is a plain text box, because the customer portal does not offer apps Jira's rich text editor.
Place it under DescriptionValues an agent can match exactly
When every value in a field has one shape, an agent, a JQL query or an Automation rule can match it without guessing. Jira refuses anything else on every save, including writes from Automation and the REST API. The app runs no AI model and sends nothing to one.
Read how it worksCompared with other regex fields for Jira
A tick means the app does everything the row describes. Where it does part of it, the cell names what is missing.
| Capability | Oktul Regex Field for JiraOktul | RegEx & Picker Fields (opens in a new tab)MOY Apps | Custom Fields Suite (opens in a new tab)Appsvio |
|---|---|---|---|
| FreeFree on the Atlassian Marketplace at every site size, with every feature and no paid edition. | Yes | No | No |
| Runs on AtlassianA badge Atlassian grants on the Marketplace listing to every app that stores data only inside Atlassian and declares no external hosts. | Yes | Yes | Yes |
| Fills itself in from the formThe field opens filled in from the person, the date, the space and other fields on the form, and follows those fields as people fill in the form. | Yes | No | A separate read-only field |
| Formats as you typeCharacters the rules refuse cannot be typed, and fixed characters such as dashes or a country code are added for the person. | Yes | No | No |
| Rich text with rulesA rich text field in Atlassian's own editor, whose plain text is checked against a length, the allowed characters or a pattern. | Yes | No | No |
| Works on the customer portalCustomers fill the field in when they raise a request on a Jira Service Management portal, and the rules apply there too. | Yes | Yes | Yes |
Checked on against each product's published documentation and its Marketplace listing. A dash means the feature is in neither. If a row no longer matches what an app does, write to hello@oktul.com (opens a new email) and we will check it again.
The tests every release has to pass
A release ships only when it passes these tests. Before each release and once a month we also scan its code for vulnerable dependencies, leaked secrets and unsafe patterns, and attack its web triggers where it has any.
Automated tests
The pattern parser, strict input, every simple rule, the editors and the settings screen.
Test suites
One runs the Jira validation expressions themselves against the browser's checks.
Installation runs through the Atlassian Marketplace
There is absolutely no infrastructure on Oktul's side. The entire application runs within your Atlassian ecosystem.
- Install from the MarketplaceA site administrator installs it and approves six permissions, each listed below with its purpose. Two are Jira administration scopes: one reads each field's rules, and the other is declared for the module that fills a field from the rest of the form, as Atlassian's documentation asks.
- Create the fieldIn Jira settings, under Fields, create a field of the type Oktul Regex Field (Single line) or Oktul Regex Field (Paragraph). It accepts any value until it has a rule.
- Set the rulesIn the field's context settings, choose Simple or Advanced, and try values in the test box before saving. The box names each rule a value breaks.
- Write the messageSay what a correct value looks like, or keep the default message, which each person sees in their own language.
Host platform and compatibility
- Host product
- Jira Cloud and Jira Service Management Cloud
- Runtime
- Atlassian Forge
- Languages
- English and Estonian
- Data residency
- Your site’s
- Version
- 3.6.0, 04.11.2026
For your security review
Send to your security team (opens a new email)CSA STAR Level 1
This application is listed in the Cloud Security Alliance STAR Registry at Level 1. We completed the CAIQ Lite questionnaire with all 138 questions, and published it for you or for your security reviewer.
Read the assessment (opens in a new tab)Questions administrators ask
How do I dynamically fill Jira fields on the portal or the create screen?
With a field of the type Oktul Regex Field. In the field context's Prefill, write a template with smart values: {{user.displayName}}, {{user.email}}, {{user.accountId}}, {{today}}, {{today.iso}}, {{now}}, {{project.key}}, {{project.name}} and {{issueType.name}}. Any other field on the form works by its id or name, such as {{summary}}, {{customfield_10070}} or {{Cost centre}}, and so does a part of its value, such as {{Reporter.emailAddress}}. The field fills in on the create screen, the portal request form and transitions. It follows the fields it names until the person changes it, and stays empty when the value would break its rules. It fills its own field, not Jira's other fields. Assets fields cannot be used yet, because Jira passes none to an app's UI modification (FRGE-2079).
How do I validate a Jira text field with a regular expression?
Jira Cloud's own text fields have no regex rule. Create a field of the type Oktul Regex Field (Single line), open its context settings, choose Advanced and enter the pattern. Jira then checks every value against it when it is saved, from any screen, the REST API, an import or Automation, and shows your message when a value does not match.
Can a Jira field format a phone number or code as it is typed?
Yes, the single-line field can. Set a format such as 999-9999 and turn on strict input. Characters that do not fit are refused and the fixed ones are typed for you: 1234567 becomes 123-4567. Strict input works where Jira shows the app's editor. Jira Forms, the mobile apps and imports use a plain text box, and the rules still apply when the value is saved.
What does a new field accept?
Anything, until it has a rule. Whether the field must be filled in stays Jira's own Required setting.
Can I search the fields with JQL?
Yes, like other text fields, with =, ~ and IS EMPTY. The paragraph field's plain text is searched with .text, so its formatting never matches by accident.
What does it cost?
Nothing. The app is free on the Marketplace, with every feature on every site: the rules, strict input, the paragraph field, JQL search and prefill.
What happens to our data if we uninstall?
The app stores nothing of its own. Field values and rules are kept by Jira, as for any custom field.
Where do I get help?
Raise a request in the Oktul Help Center, or email support@oktul.com.
Oktul's other applications
- Jira and Confluence
Code Studio
Pending Atlassian approval
Write, store and run JavaScript and TypeScript scripts in Jira and Confluence Cloud.
- Jira
Work Item Selector
Allow users to pick work items based on Jira Query Language (JQL).
Free for up to 10 users. Larger sites try it free for 30 days.
- Confluence
SignPlus
Sign a Confluence page, and prove later which version was signed.
Free for up to 10 users. Larger sites try it free for 30 days.
- Confluence
Work Item Macro
Show Jira work items on Confluence pages, any field as a column.
Free for up to 10 users. Larger sites try it free for 30 days.
Jira and Confluence
Free on the Atlassian Marketplace
The application is free and adds nothing to your Atlassian invoice. Once Atlassian has approved it, you can install it from the Marketplace listing.