OVERALL RATINGS
INSTALLS
1
SUPPORT
- Partner Supported
TRUST SIGNALS
Key highlights of the appCreate-issue links and short request forms for Jira: fields prefilled, routing fixed, every issue lands in the right queue
One link, not a Jira tutorial
Paste it in Slack, an email, a runbook or an intranet page. It opens a short form with project, issue type and routing fields already set — the submitter answers the two questions only they can answer.
Broken links are caught before people hit them
A form is checked against Jira’s real create screen when you save it. If a required field is neither filled nor asked for, you are told then — not by a colleague whose request silently failed to file.
Routing the submitter never sees
Component, labels, priority, assignee: set once, applied on the server, never shown and never overridable. Fields you allow can be filled from the link itself, so an alert or a runbook can pass along what it knows.
Supporting media
More details
The problem
Everyone has a Jira seat. Almost nobody knows which project, issue type, component, or label the automation keys off. So requests arrive in Slack instead, and somebody re-types them.
What Prefill does
Build a form once, share a link. Pick the project and issue type, fix the fields that decide routing, and ask only what the submitter knows.
It cannot quietly break. Forms are checked against Jira's live create screen when saved, opened and submitted; what changed shows on the form's page.
Good to know
Submitters are your own Jira users, signed in, with permission to create issues in the target project. Prefill is not a portal for people outside your site.
Jira's own forms can be shared by link and, if your admin allows, answered without signing in. They fix the project and work type, not component or assignee, and ignore link parameters; Prefill does both. (Service Management request types can hide preset fields and prefill from the portal URL.)
Resources
App documentation
Comprehensive set of documentation from the partner on how this app works
Privacy and Security
Privacy policy
Atlassian's privacy policy is not applicable to the use of this app. Please refer to the privacy policy provided by this app's partner.
Partner privacy policySecurity program
This app is not part of the Marketplace Bug Bounty program.
Integration permissions
Prefill — Request Forms & Create-Issue Links for Jira integrates with your Atlassian app
Version information
Version 2.4.0•for Jira Cloud
- Release date
- Sep 28th 2026
- Summary
- Tighter form permissions, one issue per submission, date and time pickers
- Details
A form can now be changed, retired or deleted only by people who may build forms for the project it files into, checked against the form's own project. Under "Anyone who can create issues", that means people who can create issues there, not everyone. Creating and editing forms pauses while a subscription is inactive; submissions carry on. A form that no longer fits its project stops before anyone fills it in, and if Jira refuses a hidden value, submitters see a short note while the form's page shows you Jira's reason. A double-click on Submit files one issue, and opening then submitting a form counts one open. Date-and-time fields have date and time pickers and use the submitter's time zone. Label fields take more than one label. The builder searches all your projects, and the form picker can search beyond its first batch.
- Payment model
- Paid via Atlassian
- License type
- Commercial