Questions worth answering first

Yes, and this is the most important thing to know before you install. Fulfilra runs entirely inside Atlassian, which is what keeps your data in your own tenancy — and it means there is no external portal. Everyone who raises a request is a licensed user of your Jira site.

If a large population without Jira seats needs to raise requests, Fulfilra is not the right tool for them, and we would rather you found that out here than after installing.

JSM's portal is built around the issue. Fulfilra is built around the request: it holds the answers, the approval chain and the requester's conversation, and files a Jira issue for the work.

Concretely: sequential named approvers that nothing can bypass, a form editor an administrator can use without touching issue schemes or custom fields, and a requester view that hides the internal states rather than showing a workflow.

Any Jira project. Fulfilra creates ordinary issues, preferring the "Task" type and falling back to the project's first non-subtask type. A JSM project is the usual choice because of its queues and SLAs, but a Software project works exactly the same.

Not itself. A Forge app running entirely inside Atlassian has no mail transport of its own — that is the same property that keeps your data in your tenancy.

What happens instead: every update writes a row to the in-app inbox, always. When the request has a linked Jira issue, Fulfilra asks Jira to notify the person, and Jira sends its own email subject to that person's Jira notification settings. A request type that creates no issue notifies inside the app only — and the admin screen says exactly that, at the moment you configure it.

To the linked Jira issue, yes. To the Fulfilra form, no — the Forge UI toolkit has no file input.

Be aware that a file on a Jira issue is visible to anyone who can browse that project, which is usually wider than the people handling the request. Fulfilra says so on both the admin screen and the request itself.

The request follows, within limits. Mapping is by Jira status category — In Progress starts work, Done resolves, To Do deliberately does nothing — so renaming statuses on a board changes nothing.

Jira is never allowed to approve, reject, close or cancel a request, or to move one that is already finished. Those are decisions people make in Fulfilra. A refused event is recorded with its reason for an administrator, not dropped in silence.

Fulfilra reads account status from Atlassian, so an approval waiting on a deactivated person is flagged to administrators rather than sitting silently. An administrator changes who the request type names, and new requests go to the right person.

There is no delegation and nothing is reassigned automatically — an approval is a named person's decision, and quietly moving it to somebody who was never asked would be worse than the stall.

Not as a bulk import. Install the starter pack closest to what you have and edit — most teams find the 20 templates cover the majority of what they were already asking, and the editing is faster than a mapping exercise.

In a database Atlassian provisions for your installation, inside your own Atlassian tenancy. Not shared with other customers, and not copied anywhere else — the app makes no call to any service outside Atlassian at all. See Security & data.

Atlassian deprovisions the database with the installation, and your requests go with it. There is no copy elsewhere, because there was never anywhere else. Export anything you need to keep first.

About ten minutes to a working catalog: install, name an agent, install a starter pack, point it at a Jira project. The setup tab tracks those four against your real configuration.

Tuning the forms to your organisation takes longer, and is the part worth spending time on.

No. Fulfilra is a Forge app, and Forge is Jira Cloud only.

Email at support@fulfilra.com, and the Marketplace listing. There is deliberately no in-app support desk: sending your ticket text to a vendor's system would be exactly the data egress we promise does not happen.