Customers have installed this add-on in at least 20 active instances.
    by Koncis Softwarefor JIRA Server 7.0.0 - 7.3.1 and more versions
    Versions available for JIRA Server 6.3 - 6.4.14
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Koncis Software supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Finally let an issue be locked down for edit, one user at a time

    Finally let an issue be locked down for edit, one user at a time

    Acquiring for lock

    Issue Acquired


    An ”Acquiring for lock” icon will be shown in bottom left corner

    An ”Lock acquired” icon is shown in bottom left corner

    Lock for issues in a project must be enabled in the administration section

    More details

    There are no additional details.

    User reviews

    Sign in to write a review »
    by T4G on 2017-01-13
    Works great from Issues tab. When issue is selected have option to Lock or Release as you click on each. Using from Board worked well when editing tickets individually. Is nice application, but have 2 areas would like to see a bit different. 1. Lock take effect on bulk change 2. Lock status bar at bottom of board. 1. Had issue arise if performing Bulk edits, these edits ignored the lock. - User A grabbed tickets 1-4 and started bulk assign. - User B grabbed ticket 4 and assigned to self, this locked ticket 4 for User B. - Bulk change finished and tickets 1-4 were assigned to User A. Ticket 4 reassigned to User A, but User A was unable to access ticket 4 because it was locked by User B. - User B was still able to edit ticket 4 because they locked it before User A completed bulk change. - User A board showed ticket assigned to User A, and User B saw it assigned to User B on their board. User A had to refresh. 2. The lock bar across bottom of screen mostly hides the Refresh notification on the board. - If user tries to edit an item that is locked by another user the lock bar notifies them it is currently locked (like this part), however, they don't have an option to abandon it. Would be nice if user could have a cancel type option to go along with waiting in queue, so when moving on to another issue they don't still see Item is locked warning. After getting this notification, and selecting a new ticket on the board, it looked like the second ticket was locked too, because the warning was displaying. Overall is a good add-on, and pros outweigh the cons.
    Was this review helpful?YesNo
    by deZem GmbH on 2016-01-20
    In our company, we often stepped on each other's feet by trying to edit an issue (for instance the description) simultaneously and the changes of the one who was done editing first would be lost. Since this feature is not built into JIRA itself, we were quite happy to see such a plugin turn up. It does help us prevent messing up our edits. However, it's not ideal yet, as it keeps the issue locked for the person who edited if she doesn't browse away from the page, which is a bit annoying.
    Was this review helpful?YesNo

    Koncis Software

    Hello there, Thank you

    You can set the time that must pass before a user looses the lock if he e.g. browses to another page, or close the browser.


    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).

    You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.

    How do I determine my server pricing tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications on your instance. For example, if you're running JIRA Software (50 users) and JIRA Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons for my legacy JIRA Server or Confluence Server license?

    If you own a legacy JIRA Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more


    Koncis Software supports Issue Lock for JIRA. You can visit the support site to get help.

    Get support


    Version 1.4.4 JIRA Server 7.0.0 - 7.3.1 Released 2016-04-28


    Fixed a bug


    Fixed a bug where lock functionality would execute on a project where it was not enabled


    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Issue Lock for JIRA via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Issue Lock for JIRA. You're prompted to log into MyAtlassian. Issue Lock for JIRA begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your JIRA instance.

    To find older Issue Lock for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons