Skip to content
Atlassian Marketplace (opens in a new tab)

Oktul Regex Field for Jira

Two Jira custom fields that fill themselves in from the person, the space and other fields on the form, and check every value against your rules.

Atlassian reviews this documentation before the listing goes live, so there is nothing to install yet.

Pending Atlassian approvalCSA STAR Level One: Self-Assessment
What the video shows
  1. A create dialog opens in a service space with the Paragraph field already reading IT Support, filled from the space. In the Advanced edition.
  2. Once the summary is typed and the person moves on, the paragraph takes it too.
  3. The phone number takes +372 as its first digit is typed: strict input types the fixed characters.
  4. The field's rule, a regular expression, is checked as it is written, and a value is tried before saving.
  5. On the work item, both values as Jira saved them, checked on every save.
  6. Oktul, Atlassian Marketplace Partner.

Open the video on its own page

A Jira field cannot fill itself in from the form, or hold its format

  1. 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.

  2. 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.

  3. 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.

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.

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.

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.

AI context at scale

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.

Read how it works

Every feature

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. Select a row's name to read its definition.

Checked on against each product's published documentation and its Marketplace listing. A dash means the feature is in neither.

CapabilityOktul Regex Field for JiraOktulRegEx & Picker Fields (opens in a new tab)MOY AppsCustom Fields Suite (opens in a new tab)Appsvio
YesNoNo
YesYesYes
YesNoPartly: A separate read-only field
YesNoNo
YesNoNo
YesYesYes

Free

Free on the Atlassian Marketplace at every site size, with every feature and no paid edition.

How Regex Field does it

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

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

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

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

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

If a row no longer matches what an app does, write to hello@oktul.com and we will check it again.

The tests every release has to pass

These figures belong to this application only. Suite sizes differ between applications.

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

There is no Oktul infrastructure to set up, which makes the application simpler to adopt.

  1. 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. 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. 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. 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 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.
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.

Explore Oktul's other applications

Free on the Atlassian Marketplace

There is no paid tier and nothing is added to your Atlassian invoice. The install opens from the Marketplace listing once Atlassian has approved it.