Releases · Fulfilra

Version 4.2.0 · 5 October 2026

Priority, targets and approval reminders

Every request now has a priority — Urgent, High, Normal or Low. Each request type sets the priority new requests start at, and an agent can change it later, with a reason. Requesters never see it.
A request type can carry a target in working days. The date is set once work can actually start — at submission, or at the final approval for a type that needs one — against the working week you choose on the Catalog tab.
Agents can move a target date, with a reason the requester is told about in their inbox and on the customer portal.
The queue is now ordered by priority and due date, and shows which requests are due, overdue or met. Reporting gains an Overdue now tile.
The linked Jira issue’s Due date now follows the request’s target. If you publish request status to Jira, the target date can be searched there too.
Request types that create no Jira issue — confidential HR requests, say — can now reach their approvers and requesters by email, through a single notices issue an administrator creates on the Jira tab. It holds no request content, and each email names only the request’s reference.
A daily reminder can now go to the approver whose step has waited longer than a number of days you choose on the Team tab. Only the person whose turn it is is reminded, once a day. Reminders are off until you switch them on.

The “Change priority” and “Move target date” buttons now show a loading state while they save.
An empty date field now shows the format it expects, rather than a date that looked already filled in.
The warning about request types with no named approver now lists them by name.
The Jira tab’s list of events received now shows which issue a comment arrived on.
Saving the working week or the approval reminder setting now confirms it on screen.

Approval and requester notification emails now escape the request’s own text before it is placed into the email body, so a request field can no longer alter how the email itself is rendered.

Comments mirrored from a linked Jira issue now show the actual commenter’s name, instead of “Jira”.
Approval and requester notification emails now show the message itself — the approval step, a new target date and its reason — instead of only a bare link to the issue.
History entries recorded in the same moment now appear in the order they actually happened, instead of an arbitrary order.
Reopening a request now takes its linked Jira issue out of Done as well, instead of leaving the two disagreeing.
A request’s details now read in the order the form asked them, with Yes/No and plain dates, both on screen and in the Jira issue.
Moving a target date now opens on the request’s current target, instead of an empty field that looked like today.
Switching tabs on the admin screen while mid-edit now correctly returns to the list, instead of leaving a stale form behind.
Switching Fulfilra off the customer portal no longer leaves an empty panel behind for a customer who has already raised requests — they keep seeing their own requests and can still reply.
The “replace the notices issue” confirmation no longer tells an administrator to delete an issue Jira has already reported as gone.