Unstep for Jira: documentation

Public help pages (no login). Publish at https://greatwork.company/apps/unstep/docs.

Get started

1. Install Unstep from the Atlassian Marketplace (Jira admin).
2. Open any issue, choose ... (more actions) > Undo last transition.
3. If the dialog says "No way back in this workflow", a Jira admin opens Jira settings > Apps > Unstep > Workflows, picks the project, and adds the hidden undo transitions (see below).

Undo a transition

Open the issue, then ... > Undo last transition. The dialog shows:

• the status the issue moves back to, who made the change and when;
• every other field that transition changed (resolution, fix versions, assignee, story points, select lists, fields on the transition screen) with the old value and the current one. Ticked fields are put back. Fields someone changed again after the transition are flagged and left unticked;
• fields Unstep does not put back (rich text such as Description, worklogs, comments, attachments), with the old value so you can fix them by hand.

Choose Undo. If you change your mind, open the menu again: the action now reads Redo.

Unstep refuses if the issue changed status again after you opened the dialog, so you never undo something you did not see.

Who can undo

• Anyone with the Transition issues permission can undo their own last transition.
• Jira admins can undo anyone's.
• Project admins can undo anyone's in their projects (switch off in Settings).
• Project roles and groups you list in Settings can undo anyone's, including changes made by Automation rules and bulk changes. Groups are saved with their Jira group id, so renaming a group keeps it working. A deleted group gives nobody rights, and Settings names it so you can pick it again.
• Optional: limit undoing your own changes to some project roles, or to a time window (15 minutes to 7 days).
• Putting back fields other than Resolution needs Edit issues.

Workflows with no way back

Jira only changes a status through a transition in the workflow. If the workflow only goes forward, Unstep has nothing to run. In Settings > Apps > Unstep > Workflows, pick a project: the table shows each workflow and which statuses have no Unstep transition yet. Tick workflows and choose Add hidden undo transitions. Jira validates the change; review the result and confirm.

What gets added: one global transition per status, named "Unstep: back to ", with Jira's "Hide transition from user" condition. People never see them on issues, boards or bulk change; only Unstep runs them through the API. Nothing else in the workflow changes. Remove Unstep transitions takes them out again.

When Unstep uses these transitions, the issue history shows Unstep as the author of the status change. The comment (if enabled) and the audit log name the person who asked for the undo.

Limits: read-only workflows (Jira's built-in "jira" workflow) and team-managed project workflows cannot be changed by apps. Copy the workflow, or add a backward transition yourself.

Bulk undo

Settings > Apps > Unstep > Bulk undo (Jira admins) or Project settings > Unstep (project admins, limited to that project).

1. Enter JQL, for example project = OPS AND status = Done.
2. Narrow it down: last transition made by a person (for an automation, pick its actor), made in the last 15 minutes to 7 days, moved to a given status.
3. Choose what else goes back: the resolution only, or every field the transitions changed.
4. Preview lists each issue with its move back, or why it will be skipped.
5. Undo N issues runs in the background. Every issue is checked again right before it changes; anything changed since the preview is skipped. Follow progress, stop the job, or copy the results as CSV.

Up to 1,000 issues per run. You must be an admin of every project involved.

Audit log

Settings > Apps > Unstep > Audit log (all projects) or Project settings > Unstep > Audit log (one project). Each entry: time, issue, who undid it, from and to status, whose change it reversed and when, fields put back or failed, and whether it was part of a bulk undo. Export as CSV. Entries are kept for 30 to 365 days (Settings).

Settings reference

Troubleshooting

• "You can't undo this one": see Who can undo; ask a project admin.
• "Jira refused the transition": a validator or required field on the way back. Use the hidden undo transitions (they have no screen or validators) or fill the field and transition by hand.
• A field was not put back: Jira rejected it (field configuration, context, validators); the dialog and audit log show Jira's message.

Privacy

Unstep runs on Atlassian. See the privacy policy at https://greatwork.company/apps/unstep/privacy. Support: hello@greatwork.company.