Skip to content
Fulfilra logo: a white butterfly on a green tileFulfilraby ITSM Ltd
Releases · current version 4.3.0

Release notes

What changed, version by version — newest first. Written for administrators, so you can read a release before you take it.

Version 4.3.0 · 2 November 2026

Satisfaction question and defect fixes

New Features

  • Fulfilra can now ask the person who raised a request how satisfied they are, once, when it is resolved: one question on a five-point scale, which they can answer or decline for 14 days, including after they close the request. It is off until a site administrator switches it on, on the Reporting tab, and nobody is asked about a request they worked themselves.
  • Agents and administrators see each answer on the request. Approvers do not, and answers are never written to Jira.
  • Reporting gains a Satisfaction tile and panel: how many were asked and answered, the response rate, answers by rating, low scores to follow up, and a month-by-month table. Below ten answers it gives a count rather than a percentage, and it compares periods only from thirty answers in each.
  • If a requester reopens a request they had rated, their rating is withdrawn and they are asked again when it is next resolved. A request an agent reopens keeps its answer.

Improved Features

  • The Setup tab points to the satisfaction question as an optional step.

Security Fixes/Patches

  • None in this release.

Defect Fixes

  • The Jira issue created for a request no longer doubles the punctuation of a question: “What do you need help with?” is followed by the answer, not by “?:”.
  • Requesters whose Jira licence does not include Jira Service Management now get a Jira issue for their request when it is raised in a service project. The issue is created by Fulfilra on their behalf, so Jira emails and published status work for them as for everyone else.
  • Pressing Submit twice now shows the request already created, instead of an error.
  • Adding a catalog category whose name is already taken now says so, instead of a general failure.
  • An issue that has already been linked is no longer reported as “could not be linked”.
  • A comment that reaches Fulfilra twice from Jira is no longer reported under Sync problems.
Version 4.2.0 · 5 October 2026

Priority, targets and approval reminders

New Features

  • 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.

Improved Features

  • 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.

Security Fixes/Patches

  • 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.

Defect Fixes

  • 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.

How each release is written up

Every entry here carries the same four sections:

New Features

Something you could not do before.

Improved Features

Something that worked, and now works better.

Security Fixes/Patches

Named even when there is nothing to say — silence there would be the wrong kind of quiet.

Defect Fixes

Something that was wrong, in plain words, not commit messages.

Marketplace apps built on Forge update in place, so you are always on the current version — there is nothing to download and nothing to schedule.

Looking for the app itself?

Install Fulfilra from the Atlassian Marketplace listing, or email support@itsm-ltd.com with any questions about a release.

Install it, and raise a request five minutes later

No editions and nothing to unlock: every installation has every feature. Everyone on your Jira site can raise a request the moment it is installed.