Lock the issue while you work on it.
Say why and for how long. Everyone sees who holds the lock, why, and until when, before they start editing.
- Expires on its own, with a reminder first
- Admins can force-unlock, so locks never get stuck
- Each project chooses which fields are protected
Changes by others are put back.
If someone edits a protected field while you hold the lock, Lockwise restores it within seconds and emails you both.
- Every undo goes in an audit log you can export
- Stops after 3 undos in an hour and tells the lock holder
- Rich text, dates, people and select fields come back exactly
Only the lock holder can move it to Done.
Add Lockwise's rule to a transition in your workflow. While the issue is locked, only the person holding the lock gets that transition.
- You choose which transitions
- Unlocked issues work as normal
- Find your locks any time with JQL
The problem
While someone reviews a contract, a release setup or audit evidence, others can change the same issue at the same time. Lockwise lets one person check the issue out, with a reason and an expiry, and keeps it steady until they are done.
What it does
Lock with a reason and an expiry
Every lock says who, why and until when.
A clear banner on the issue
Everyone sees who holds the lock before they start editing.
Changes by others are undone
Edits to protected fields are put back, both people are told, and it is logged.
Admin force-unlock and auto-expiry
Locks never get stuck, and holders get a reminder before expiry.
Stops edit wars
After 3 undos in an hour, Lockwise stops and tells the lock holder.
Find your locks with JQL
Search lockwiseHolder = currentUser() in filters and dashboards.
Audit log you can export
Every lock, unlock and undone change, as CSV.
Guides
All guides- Guides for Lockwise arrive with its release.