Click a field on the issue page and edit it there.
Click any issue field and change it in place. No edit mode, no full-page reload, no scrolling to a form at the bottom. It sounds minor until you count how often a triage pass touches twenty issues to change one field on each. Fields that are quick to correct get corrected, which is the difference between a tracker that reflects reality and one nobody trusts.
Quick Edit takes the Edit form out of a one-field change. You click a field on the issue page and edit it there. No round trip, and no losing your place on a long ticket.
What it does not change is the rules. Every change it makes is an ordinary Redmine issue update: the same permissions, the same workflow rules, the same validation and the same history. There is no parallel edit path. One field goes through the same attribute assignment and save that the form uses, with the editing user, and a test asserts that the history entry of an inline edit is byte-identical to the same change made on the form. The history does not reveal which path was used.
There is nothing to turn on and nothing to configure. It is available on every issue to everyone whose permissions already let them edit that issue.
Quick Edit works on the issue page, on everything in the issue's attribute panel plus the subject. The core fields are status, assignee, priority, category, target version, parent task, start and due dates, estimated time, percentage done and the subject.
Custom fields are editable too: text, long text, integer, float, date, boolean, list in both its single and multiple forms, key and value list, user, version and link.
The description keeps the full editor. It is long-form text with a toolbar, a preview and attachments, and an inline box would be a worse version of what is already there. Attachment custom fields get no inline affordance at all, rather than an editor that cannot save what it shows.
Click a value, such as the status, the dates, percentage done, estimated time or the subject, and it becomes an editor. Fields that are links keep their link. Clicking an assignee still opens their profile, so the assignee, target version and parent are edited from the pencil that appears when you hover. The pencil is on every field, so the affordance is the same everywhere. One gesture never means two things.
Dropdowns save the moment you choose. Text, number and date fields save when you confirm or press Enter, and cancel when you dismiss them or press Esc. Nothing ever saves on blur. Clicking away, opening another field or losing your connection cancels the edit and never commits it, because a stray click must not change a due date.
Assign to me appears only when it would do something: when you are a valid assignee and are not already assigned.
After each save the field flashes briefly, as the receipt that says that is what changed, and a toast offers Undo for a few seconds. From the keyboard, Tab reaches every pencil, Enter opens the editor and Esc closes it. Editors and the toast carry ARIA labels. The toast announces politely, so it does not interrupt a screen reader mid-sentence, while a validation error does.
Change the status, then the assignee, then the due date, and the history shows one entry with three changes. Watchers get one email, not three.
Consecutive inline edits by the same person on the same issue, within about three minutes, join the entry already written. Anything at all closes that window: somebody else's edit, a note from anyone, an edit through the full form, or the three minutes running out.
This is not a special notification mode. Redmine sends issue mail when a history entry is created, and adding to an existing one is an update, so there is simply no second mail to send. The entry moves to the time of the last change and is not marked as edited, because nobody edited anything. The burst grew.
Undo puts a field back by making the opposite change. The history keeps both halves, because an issue's history is a record of what happened, and an issue that was assigned to you for ninety seconds is something that happened. Undo takes back one field, the most recent, which is what the toast offered when that field saved. In a burst of three, Undo takes back the third. It is refused, with a reason, if something else has changed since, if the change was not made with Quick Edit, if the change was somebody else's, or if more than five minutes have passed. Edit the field again instead.
There are no permissions to configure, and that is deliberate. Quick Edit changes how you make an edit Redmine already allows, never whether you may make it. A field is editable here exactly when it is editable on the issue form.
Edit issues, or Edit own issues, gates everything per project. Workflow field permissions apply, so a field that is read-only for your role in the current status gets no pencil, and is refused if asked for anyway. Required fields apply in the same way. Quick Edit never routes around a workflow rule. The status options are the transitions your role may make from the current status, the same list the issue form shows, not every status in the workspace. Editing the parent needs Redmine's Manage subtasks permission. Issues you cannot see are not found, and visitors who cannot edit get a page with no affordances at all rather than a disabled interface.
A separate permission could only ever disagree with Redmine's own. A workspace where someone may quick edit a field they may not edit is a bug with a settings page in front of it. The page is told which fields to draw affordances for, but that is presentation, not security. Every save is authorised again on the server, so a crafted request is refused on its own merits.
If the issue changed after your page was loaded, your save is rejected and nothing is written, so somebody else's work is never silently overwritten. You are told so. The check is Redmine's own optimistic locking, the same mechanism that protects the full edit form, and nothing partial is ever written.
It runs no background work: no jobs, no scheduler and no polling. Its two assets load only on the issue page, with no external request.
On your own Redmine, the plugin needs Redmine 6.0 or newer and no additional gems, and removing it loses nothing. Every change it made is an ordinary entry in Redmine's own issue history and stays there.
Quick Edit is on every plan, from Startup. Every plan keeps full Redmine administrator access.
See what each plan includes, or look at the rest of what RedminePRO adds to Redmine.
Set-up and permissions: Quick Edit in the Knowledge Base. Install it on your own Redmine.
7-day trial on any plan. Full Redmine administrator access from the first day.