keelapps/Prefill
For the colleague who has a Jira seat but not the training
Give a colleague one link instead of a Jira tutorial
Paste it in Slack, an email signature, a runbook or a monitoring alert. It opens a short form with three questions instead of thirty: the project, the issue type and the fields that decide routing are already set, so the submitter answers only what they alone can answer. Submitters are your own signed-in Jira users, the issue is created as the real person, and nothing leaves Atlassian.
Free for sites up to 10 users. Above that it is priced per user per month and billed by Atlassian — see pricing on the Marketplace.
It is not an issue-template app. Templates prefill Jira's own create screen, and the submitter still has to find their way around it. Prefill's product is the entry point: a URL that opens a page somebody can complete without ever seeing Jira's create dialog.
It is not an anonymous portal, and it cannot become one. Submitters are your own Jira users — signed in, with permission to create issues in the target project. Anonymous intake needs an outbound connection to a vendor's server, and declaring one would forfeit the Runs on Atlassian guarantee that is this app's whole structural advantage. The scenario Prefill is built for is “the entire company has a Jira seat, but only a handful of people know how to file a ticket”. If you need requests from people without a seat, you want Jira Service Management.
What it does
Build a form once
Pick a project and issue type, fix the fields that decide routing, and ask the submitter only for what you actually need. Fixed fields are applied on every submission and never rendered.
Share a link
One key per form: copyable, editable, retirable. Retiring a form keeps the key reserved, so anyone still holding the link is told it was retired rather than shown a dead page.
A form with three questions
Only the fields you marked editable, with their defaults already filled in. Submitting creates the issue — with the submitter as reporter, so Jira's own permissions, audit trail and notifications all behave normally.
It cannot quietly break
A form is checked against Jira's live create screen when it is saved: a required field the form neither fills nor asks about is refused there, while the person who can fix it is still looking. It is checked again on every submission, because screens change.
Fields read, never guessed
Every field shape comes from Jira's own create metadata. Select, multi-select, cascading, user, group, date, datetime, number, labels, time tracking and rich text all work — and a type the app cannot fill honestly says so rather than failing later.
See which links work
Per-form use counts and the recent issues each link produced, so an owner can spot a form that is opened and then abandoned. Plus a project page and a site-wide admin page with a live health verdict.
From “where do I file this?” to the right queue
-
The routing is somebody's job, once
The team that owns the queue builds the form: project, issue type, component, labels and the priority the automation keys off — all fixed, all invisible to the submitter.
-
The link goes where people already are
Slack channel topic, an email signature, the runbook step, the alert payload. One URL, no instructions attached.
-
The submitter answers two questions
A short form: what happened, and which environment. They are signed in as themselves, so nothing about identity has to be asked or trusted.
-
The issue lands correctly, as them
Created through Jira's own API as the submitter: the reporter is the real person, Jira's permissions decided it was allowed, and the automation that watches that component fires exactly as it would have for a hand-filed ticket.
Against what you have today
| Question | Jira's create screen | Issue template apps | Prefill |
|---|---|---|---|
| What does the submitter see? | Thirty fields | Thirty fields, pre-typed | Three questions |
| Do they need to know the project and issue type? | Yes | Less so | No — the link decides |
| Can it be pasted into Slack or an alert? | A create screen, not an intake page | Usually not | That is the product |
| Is a broken form caught before people hit it? | — | Rarely | At save, and at every submission |
| Who is the reporter? | The submitter | The submitter | The submitter — created as them |
| Does anything leave Atlassian? | — | Depends on the vendor | Never |
Limits we state up front
Submitters are your own Jira users — signed in, with permission to create issues in the target project. Prefill does not provide an anonymous or external customer portal; that would require an outside server, and Prefill makes no external calls at all. If you need requests from people without a Jira seat, you want Jira Service Management, not this app. This matters before you buy: Marketplace apps are priced by Jira user count, and a form is only useful to somebody who already has a seat.
Prefill is not a template app. It does not prefill Jira's create screen and it does not manage issue templates. If what you want is a pre-typed description on Jira's own create dialog, this is the wrong tool.
Deep links are measured, not assumed. Appending a form's key to the app page's URL opens that form directly, and that was verified working on the site we tested on 9 September 2026. We do not claim it for every Jira Cloud tenant: community reports describe tenants where query strings are stripped, so the form picker that stands in when a link carries no key is deliberately retained as a genuine fallback rather than removed as dead code.
URL parameters are opt-in, per field. An external system can carry context into a form, but only for fields whose owner explicitly allowed it — and never for a hidden one, whose value is applied on the server and never sent to a submitter's browser.
Availability
Prefill for Jira is live on the Atlassian Marketplace. It is built and deployed on Atlassian Forge and installs into your Jira Cloud site straight from the listing.
Licensing is handled by Atlassian. Sites with 10 users or fewer pay nothing at all, with every feature included; paid tiers are priced per user and taper as the site grows.
Questions, bug reports and feature requests: raise a support request.
Found a security issue? Please report it privately rather than in a public channel.