# Oktul Regex Field for Jira

Jira fields that fill themselves in from the form, and only accept your format.

Two custom field types, a single line and a rich text paragraph. They fill themselves in on the create screen, the portal request form and transitions, from smart values for the person, the date, the space and other fields on the form, and follow those fields as people type. Jira checks every value against the rules you set per field context, on every save. With strict input, a phone number field types its own country code and spaces.

- **Host:** Jira Cloud
- **Version:** v3.1.0
- **Documentation:** https://oktul.com/docs/plugins/regex-field/
- **Video:** https://oktul.com/videos/regex-field/

## A Jira field cannot fill itself in from the form, or hold its 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, which Jira checks in the field's own validation. The single-line field can also refuse wrong characters as they are typed.

## Four things the fields do

Every rule is set per field context, so 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. https://oktul.com/docs/plugins/regex-field/prefill/

### Validation 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. https://oktul.com/docs/plugins/regex-field/configure/#rules-simple

### Strict 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. https://oktul.com/docs/plugins/regex-field/configure/#input-single-line-only

### Rich 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. https://oktul.com/docs/plugins/regex-field/configure/#show-the-paragraph-field-under-description

### Values 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.

### Every feature

**Rules**

- [Simple rules](https://oktul.com/docs/plugins/regex-field/configure/#rules-simple)
- [Regular expressions](https://oktul.com/docs/plugins/regex-field/configure/#rules-advanced)
- [Error message](https://oktul.com/docs/plugins/regex-field/configure/#error-message)
- [Scope and limits](https://oktul.com/docs/plugins/regex-field/configure/#scope-and-limits)

**Input**

- [Strict input](https://oktul.com/docs/plugins/regex-field/configure/#input-single-line-only)
- [Paragraph under Description](https://oktul.com/docs/plugins/regex-field/configure/#show-the-paragraph-field-under-description)

**Prefill**

- [What a template can hold](https://oktul.com/docs/plugins/regex-field/prefill/#what-a-template-can-hold)
- [Keep in sync](https://oktul.com/docs/plugins/regex-field/prefill/#keep-in-sync)
- [Where it fills in](https://oktul.com/docs/plugins/regex-field/prefill/#where-it-fills-in)

**Jira**

- [Automation and workflows](https://oktul.com/docs/plugins/regex-field/configure/#automation-and-workflows)

## Compared with other regex fields for Jira

Each row is one capability. An app gets a tick only when it does everything the row describes, and where it does part of it, the cell names the part that is missing.

| Capability | Oktul Regex Field for Jira (Oktul) | [RegEx & Picker Fields](https://marketplace.atlassian.com/apps/1237076/regex-custom-fields) (MOY Apps) | [Custom Fields Suite](https://marketplace.atlassian.com/apps/1224654/multilevel-select-for-jira-cascading-select-custom-field) (Appsvio) |
| --- | --- | --- | --- |
| Free | Yes | No | No |
| Runs on Atlassian | Yes | Yes | Yes |
| Fills itself in from the form | Yes | No | Partly: A separate read-only field |
| Formats as you type | Yes | No | No |
| Rich text with rules | Yes | No | No |
| Works on the customer portal | Yes | Yes | Yes |

Checked on 21.10.2026 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 and we will check it again.

- **Free:** Free on the Atlassian Marketplace at every site size, with every feature and no paid edition. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/
- **Runs on Atlassian:** A badge Atlassian grants on the Marketplace listing, one app at a time, to apps that store data only inside Atlassian and declare no external hosts. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/privacy/#4-where-the-data-is-stored
- **Fills itself in from the form:** The field opens filled in from the person, the date, the space and other fields on the form, and follows those fields as people type. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/prefill/
- **Formats as you type:** Characters the rules refuse cannot be typed, and fixed characters such as dashes or a country code are added for the person. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/configure/#input-single-line-only
- **Rich text with rules:** A rich text field in Atlassian's own editor, whose plain text is checked against a length, the allowed characters or a pattern. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/configure/
- **Works on the customer portal:** Customers fill the field in when they raise a request on a Jira Service Management portal, and the rules apply there too. How Regex Field does it: https://oktul.com/docs/plugins/regex-field/prefill/#where-it-fills-in

## Price compared with alternatives

USD a month for one Cloud site, single instance, from each app's Atlassian Marketplace pricing on 21.10.2026. Oktul's paid apps are free up to 10 users, and Atlassian bills them on the site's own Atlassian invoice.

| App | Vendor | Per user, 11–100 users | 100 users | 1,000 users | 10,000 users |
| --- | --- | --- | --- | --- | --- |
| Oktul Regex Field for Jira | Oktul | Free | Free | Free | Free |
| [RegEx & Picker Fields](https://marketplace.atlassian.com/apps/1237076/regex-custom-fields) | MOY Apps | USD 0.25 | USD 25.00 | USD 250.00 | USD 2,175.00 |

- Costs less than RegEx & Picker Fields at every size up to 10,000 users.

**Why.** Free, with every feature on every site: the rules, strict input, the paragraph field, JQL search and prefill. There is no paid edition.

## For your security review

**Runs on Atlassian.** Atlassian grants this badge per application, to apps that store data only on Atlassian's infrastructure and declare no external hosts.

[What the programme requires](https://developer.atlassian.com/platform/marketplace/runs-on-atlassian/)

**CSA STAR Level 1.** This application is listed in the Cloud Security Alliance STAR Registry at Level 1, which is a self-assessment. We completed the CAIQ Lite questionnaire, all 138 questions, and published it for anyone to read.

[Read the assessment on the STAR Registry](https://cloudsecurityalliance.org/star/registry/oktul-ou/services/oktul-regex-field-for-jira)

## The tests every release has to pass

- **Automated tests:** 555. The pattern parser, strict input, every simple rule, the editors and the settings screen.
- **Test suites:** 20. One runs the Jira validation expressions themselves against the browser's checks.

## Installation runs through the product you already administer

1. **Install from the Marketplace** A site administrator installs it and approves six permissions, each listed below with its purpose. Two are Jira configuration scopes, which Jira requires to read a field's rules.
2. **Create the field** In 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.
3. **Set the rules** In 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.
4. **Write the message** Say 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

## The questions other administrators ask most

### 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, so 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. Either way it becomes a request with a reference.

---

## Published by

- Oktul OÜ
- Oktul OÜ · Reg. nr 17589681 · Tallinn, Harjumaa, Estonia
- Email: hello@oktul.com
- Web: https://oktul.com/
- Atlassian Marketplace: https://marketplace.atlassian.com/vendors/534484195
- LinkedIn: https://www.linkedin.com/company/oktul
- YouTube: https://www.youtube.com/@OktulDevelopment
- Estonian: https://oktul.com/et/