83
Customers have installed this app in at least 83 active instances.
    by Koncisfor Jira Server 7.0.0 - 8.2.4 and more versions
    Versions available for Jira Server 6.3 - 6.4.14
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Supported
    Koncis supports this app.

    Get support

    Jira Service Desk
    This app is compatible with Jira Service Desk.
    Unsupported
    Jira Service Desk
    This app is compatible with Jira Service Desk.

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

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

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

    More details

    The plugin gives you, your employees and clients a way to lock down issues for edit. This means that an issue can be edited by one user at a time. This avoids simultaneous updates, and therefore loss of information in your company.

    The issue view is added with a Lock UI box (see docs). This is visible for all issue views (e.g. Search for issues), including Kanban/Scrum boards and Service Desk views (e.g. from queues).

    Locks can be enabled on all projects (or a sub set), and has a number of options available per project:

    • Instant fetch of lock when user opens issue.
    • Instant release of lock when user updates something or cancels edit.
    • For a service desk project, a column in a queue can show the current user holding the lock.

    Any issue update operation is captured by the lock:

    • inline/window edit
    • attachment operations
    • worklog operations
    • transitions
    • move issue
    • clone issue
    • delete issue

    We hope you enjoy the functionality of Issue Lock for Jira.

    Reviews for cloud

    (4)
    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.
    2 out of 2 found this review helpful
    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

    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.

    Reviews for server

    (4)
    Sign in to write a review
    by Martin Runge on 2018-01-26
    Sadly the documentation site is on 404. Could you pls fix that one? Thanks! cheers!
    Was this review helpful?YesNo
    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.
    2 out of 2 found this review helpful
    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

    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.

    Reviews for Data Center

    (4)
    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.
    2 out of 2 found this review helpful
    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

    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.

    Cloud Pricing

    Server Pricing

    Data Center Pricing

    10 users$1025 users$4550 users$75100 users$175250 users$400500 & upAdditional pricing details

    Pricing FAQ

    How does server app pricing work?

    Server products and apps are hosted on your servers. This app is sold as a perpetual license, and the purchase price includes 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 Atlassian product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If app 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?

    Apps are billed based on the number of users in your Atlassian product. For Jira 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (500 users) and Jira Service Desk (25 agents) on the same instance, you should purchase the 500-user tier for apps. For versions of Jira prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly. Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.

    Can I install this app in a Data Center product?

    This app does not have a Data Center approved version. Only apps meeting a set of performance requirements for large, clustered environments are approved for Data Center.

    However, while server apps are built for single-server deployments, many customers successfully install them in Data Center products. If you're using a Data Center product, Atlassian recommends you contact the vendor to determine compatibility at scale.

    Learn more about Data Center approved apps

    What type of license do I need if I'm using this app in a Data Center product?

    Because this app does not have a Data Center approved version, you should purchase a Server license if you decide to install this app in a Data Center product.

    Learn more about Data Center licensing

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

    For server apps, academic licenses are available at a 50% discount if you have an academic license for your Atlassian product.

    Community and open-source licenses are available for server apps. Learn more about community and open source licenses.

    Can I extend my free trial?

    For server apps, you can extend your app 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 app listing in UPM from your Atlassian product, and you're all set.

    How can I buy apps 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 app pricing is no longer available. You have two options for app purchasing:

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

    Learn more

    Koncis provides support for this app.

    Vendor support resources

    Documentation

    Find out how this app works.

    See existing Q&A in Atlassian CommunityAsk a question in the Atlassian Community

    Atlassian-hosted discussions connect you to other customers who use this app.

    Versions

    Version 4.1.1 Jira Server 7.0.0 - 8.2.4 Released 2019-04-26

    Summary

    4.1 did not install properly

    Details

    For some customers the 4.1 failed installation. This should work now.

    Installation

    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 apps or Find new add-ons from the left-hand side of the page.
    4. Locate Issue Lock for Jira (who's editing) via search. The appropriate app 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 (who's editing). You're prompted to log into MyAtlassian. Issue Lock for Jira (who's editing) 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 (who's editing) versions compatible with your instance, you can look through our version history page.

    Similar apps