Issue lock - old
- Kristian Thomsen
Issue Lock for JIRA
(who's editing)
Click here to view the plugin on the official marketplace page.
Introduction
JIRA Issue Lock solves the problem that many companies face. Namely that a JIRA issue cannot be locked down for edit by only one user.
The plugin features an issue lock management tool, that when enabled on a JIRA project, makes sure that a user requesting to edit an issue, must acquire the edit lock first. If a user has acquired the lock, then other users must wait in a queue to acquire the lock.
Any issue edit update needs a lock. This is required within Service Desk agent view/queues, Scrum or Kanban boards as well as the standard views.
An issue update includes all operations on an issue (also deletion/move/clone of the issue and workflow transitions), except the functionality concerning voting and watching.
Behaviour
An edit-session starts when a user has acquired the lock (user must have some kind of edit permission on the issue). When the session ends the lock is released, and other users may now acquire it.
The lock can be acquired from e.g. the Issue view page, a SCRUM board (e.g. performing workflow transition) or another page in JIRA that contains the possibility of executing issue updates. Only one lock can be acquired in a single web browser window.
Having acquired the lock, only that user can perform issue updates. Note that the configuration includes the option of letting system and project administrators bypass the lock (they will not observe the lock graphically).
When attemping to acquire a lock, or having acquired a lock, an info text box is visible beneath the issue key (when scrolling down it will show in the right bottom corner).
For a user viewing an issue (and having edit permission, and not owning lock), the user that is currently editing is shown in the info box.
If a user browses away from the issue view (having acquired the lock for it), the edit-session times out after a given time interval (configurable, default is 30 seconds). This gives the user some time to get back to the issue before he looses the lock.
Note that if no user has acquired the lock, and the user performs an issue update, then no non-default JIRA behavior can be observed, except if on the Issue-view page.
Remarks
The plugin does only work within the JIRA User Interface. Issue updates performed through REST/SOAP calls, and other API methods (e.g. from custom JIRA plugins), are not supported, and thus, needs no lock.
Supported Applications
JIRA Core, Software and Service Desk.
Installation
Installation works by either downloading the addon from Atlassian Marketplace and uploading it, or by installing it directly from the Addons section of JIRA.
Configuration
To enable Issue Lock for a project, open the administration section of the project, and click JIRA Issue Lock at the bottom of the left side menu.
A configuration screen is shown. Enable the functionality here.
Other options include to let admins bypass lock, auto acquire of lock when viewing an issue and setting the session timeout interval.
We hope you enjoy the functionality of JIRA Issue Lock.