Fieldkin documentation
Fieldkin adds twelve custom field types to Jira Cloud. Create fields from them like any other custom field, set rules per project and work type, and search them with JQL.
Create a field
- Open Jira settings > Apps > Fieldkin, pick a type, type a name and press Create field. (Or use Jira settings > Work items > Fields > Create field; every Fieldkin type is listed there.)
- Add the field to the screens of the spaces that need it, and to request types for the JSM portal.
- Optional: open the field's Contexts and default value, edit the context's configuration and set its rules. Each context (project and work type) can have different rules.
Fields can be edited on the issue view, in the create dialog, on transition screens and on the portal request form. Change stamps are read-only.
The field types
| Type | What people enter | Rules you can set | JQL search names |
|---|---|---|---|
| Yes/no | Yes or No | Labels for yes and no | Answer ("Yes" / "No") |
| Rating | 1 to N stars | Number of stars (3 to 10, default 5) | Stars |
| Progress bar | A percentage | Red below, green from (default 25 and 75) | Percent |
| Status light | Green, amber, red, blue or grey, and a note | Which colors, their labels, which need a note | Color, Text (label and note words) |
| Money | An amount and a currency | Allowed currencies, default and base currency, rates, lowest and highest amount | Amount, Currency, Base (in the base currency) |
| Links | Up to 20 links with labels | Most links per work item, allowed sites | Host, Text, Count |
| An email address | Allowed domains | Address, Domain | |
| Phone | A phone number (extension optional) | Default country code | Number (like +14695551234), Code (country code) |
| Validated text | Text that matches a format | Ready-made format or your own pattern, ignore case, save in capitals, message, example | Value, Valid (1 or 0) |
| Countdown | A target date | Days before it turns amber (default 7) | Date |
| Change stamp | Filled in automatically | Field to watch (default Status), only changes to these values | By, At, To, Changes |
| Checklist | Items with a done tick | Starting items | Done, Open, Total, Percent, Text |
Every type also has Problem (1 when a value breaks the field's rules, for example after an
import).
Searching with JQL
Put the field name and the search name together in one pair of quotes:
"Health.Color" = "Red"
"Rollout progress.Percent" < 50
"Contract value.Currency" = "EUR" AND "Contract value.Amount" > 10000
"Contract value.Base" >= 50000
"Design links.Host" = "figma.com"
"Vendor email.Domain" = "acme.com"
"Go-live.Date" <= 14d
"Status changed.By" = currentUser() AND "Status changed.At" >= -7d
"Definition of done.Open" > 0
"Asset tag.Problem" = 1
"Health" is EMPTY
ORDER BY "Rollout progress.Percent" DESC
List view, filters, notifications, history and CSV export show a one-line summary: the progress bar with its percentage, the status label with a colored dot, the amount with its currency, and the countdown computed when it's shown ("2026-10-20 (18 days left)").
Rules and imports
Jira checks each type's rules on the server for every client: the issue view, the create dialog, the portal, REST, automation and imports. A value that breaks a rule is refused with the field's message.
Text written by CSV import, bulk edit, automation or REST is accepted and turned into a full
value within seconds. Fieldkin understands, for example: yes / no / true / 1; ★★★ or 3; 45%;
"red: blocked by legal"; "EUR 1.250,50", "$99", "(250)"; "Label https://..." and
"Label" separated by semicolons; "Name ana@acme.com"; "+44 20 7946 0000 ext 12";
"20 Dec 2026", "12/20/2026", "20.12.2026"; "[x] Done item; [ ] Open item". Anything it can't read
is kept, shown as "Not understood" and searchable with "Field.Problem" = 1.
Money and rates
Each money value keeps its own currency. Set the currencies people can pick, a base currency
and how much one unit of each currency is worth in the base currency. Base is the amount
converted at the rates on the context when the value was saved. Fieldkin never fetches rates;
after you change rates, save a value again to refresh its Base.
Change stamps
A change stamp watches one field per context (Status unless you pick another: priority, assignee, sprint, a select list or any custom field). Each time that field changes, the stamp records who changed it, when (UTC), the old and new value, and counts the changes. With "only stamp changes to these values" set to Done, it records when work was last done and by whom. Stamps start with the first change after the field exists; earlier history is not filled in.
Validated text patterns
Ready-made formats: IPv4 address, IPv4 network (CIDR), MAC address, version number (semver),
hex color, IBAN (checksum checked), US ZIP, UK postcode, Canadian postal code, domain name, git
commit hash, and "2 to 4 letters, dash, digits". Your own pattern is a regular expression
matched against the whole value. Use plain character classes ([0-9], [A-Z]); look-behind,
named groups, back-references, inline flags and nested repeats like (a+)+ are refused so the
editor and Jira's server always agree.
Subscription
Fieldkin is billed by Atlassian. If the subscription or trial lapses, values stay readable, the editors can't save, and change stamps and import completion pause until it's active again.
Privacy
Fieldkin runs entirely on Atlassian (Runs on Atlassian). Values live in Jira's own field storage; nothing is sent outside Atlassian. See the privacy policy.
Support
hello@greatwork.company or the Great Work help desk (choose Fieldkin).