Product Idea

Expand all | Collapse all

Simplify item locking

  • 1.  Simplify item locking

    Posted 06-08-2016 15:43
    Locking items is great for teams working together when they are concerned about compliance or stepping on each other.  Locking items is not great for teams moving at high speed, especially when items are unintentionally locked by users and prevent other users from getting their job done.

    We have this issue come up every day, users accidentally leave an item in edit mode and forget to close edit mode and now the item is locked somewhat indefinitely until an admin unlocks it.  This adds a lot of admin overhead and prevents users from getting their job done.

    There are many viable solutions to this problem for our use cast
    1. Turn off automatic locks all together.  If multiple people edit at the "same" time, just create a version for every edit.  Sure someone's edits will get trumped by another user, but the reality is that multiple users rarely edit the same item at the same time.
    2. Offer a lock timeout.  If a user hasn't done anything with the item in some specified number of minutes, release the lock
    Im sure there are many other solutions, but either of these approaches would work for us to get locks out of the way and let us use the system more productively.

  • 2.  Re: Simplify item locking

    Posted 06-08-2016 17:21
    You raise a good point, as far as agile/kind of agile teams are concerned—Locking items is not great for teams moving at high speed—so thanks for bringing this up. As Jama moves to more stringent compliance I don't think we'll change this radically (if at all), but I think your point is definitely one we need to keep in mind when Jama is part of an agile workflow.

  • 3.  RE: Re: Simplify item locking

    Posted 04-26-2017 12:48


    Bumping this back up, now that we are finally on a more recent version .With inline editing available, we are running into a lot of locking issues. I would be very interested in the ability to set a default "unlock" period, especially since now, I try to just go through and unlock things every few days as I remember. Having a default unlock time would take a lot off my effort as admin. 


    Jennifer Leitch
    Jackson National Life Insurance Company

  • 4.  RE: Re: Simplify item locking

    Posted 04-27-2017 04:03
    +1 from us.

    The fact that items can't be unlocked by anyone other than org admins is bad. Project admins should be able to unlock items in their projects.

    I really like the idea of a lock timeout. We default unlock all items after 3 months because MOST of them are erroneous locks due to people timing out sessions.

    Might be a good idea to separate:

    1. Items that have been INTENTIONALLY locked by a user (which probably shouldn't be unlocked by the timeout)
    2. Items that have been locked due to edits (which probably should).

    In any case, good topic and one which we support!


    Grant More
    Head of Systems Engineering
    Analog Devices

  • 5.  RE: Re: Simplify item locking

    Posted 04-28-2017 07:09
    Not sure I agree with proposed solution, but agree with the problem. I often find requirements that are locked and no one can figure out why. Likely the reason Grant explained in his post (thanks for the insight).

    Adam Wuerl
    Spaceflight Industries
    Seattle WA

  • 6.  RE: Re: Simplify item locking

    Posted 06-20-2017 15:48
    Our teams are also running into the problem of having too many locked items that are not being actively worked on.  Project leaders managing content in Jama are becoming increasingly frustrated as more users interact with the tool.

    Any update on plans to address this behavior?

    Tom Green
    Thermo Fisher Scientific

  • 7.  RE: Re: Simplify item locking

    Posted 06-21-2017 07:14
    Kind of on the same token, when a moderator for a review is sick or has an unplanned absent, the administrator and / or the project manager should have the right to moderate the review in the original moderator's absence.

    Ken G

  • 8.  RE: Simplify item locking

    Posted 12-04-2017 06:36
    This is a daily occurrence for us.  We keep the "time out" fairly short because the licenses are expensive.  So what happens is we get a lot of items that are "locked out" due to time out while in edit mode.  We're spread out around the globe, so often offices just coming online in the morning will be unable to access "locked out" items from those who timed out in edit mode at the end of their day.  I like the idea of treating those items that are deliberately "locked" differently than those which are not.  Also, I think it would be a good idea to list out all the locked items that you have locked out in the home page when you first log on.

    Steve Miller
    Caterpillar Trimble Control Technologies, LLC

  • 9.  RE: Simplify item locking

    Posted 12-05-2017 00:00
    This answers a question that I've had on why items are locked by me when I didn't lock them. I would like this also.

    Cynthia Weber
    Software Test Lead
    ProQuest LLC
    Ann Arbor, MI

  • 10.  RE: Simplify item locking

    Posted 12-10-2017 15:09
    Having a lock item count or summary on the homepage would is a great idea.  +1

    Also, we see 3 types of lock - 1, item currently being edited; 2, item edited and session has timed out; 3, user has locked the item to prevent further changes.  It would be great to see/know the difference.  We'd like the ability to have timeout locks automatically unlocked after 24 hours.  This provides a balance (for us) between allowing the user time to refresh the session and complete what they were doing and releasing the item for others to work on.

    Warm regards,
    Gavin Ryan-Keenor
    Business Analyst

  • 11.  RE: Simplify item locking

    Posted 12-06-2017 06:28
    ​A possible suggestion is to notify the user they have an item locked....a section located on the Jama Homepage that notifies the user of items locked or have an option in Configure Project to list items lock so the Project Manager can unlock without having the Org Admin involved.

    John Sarafin