Synch/Lock bug

Rory Duncan
Rory Duncan Member Posts: 30
edited March 13 in Peer-to-Peer Support Forum
So we just had an interesting thing happen, and im pretty sure this is a bug.
User 1 has an object open on their computer.
User 2 edits the same object on their computer making a user lock.
User 1 does not refresh their browser, and transitions the lifecycle/workflow to a state that creates a system lock
Jama does not give an error. It creates the system lock, performs the transition, but does not refresh the screen.
After a refresh, the lifecycle/workflow transition is now grayed out, even though User 2 and Org Admin have a valid transition available because user 1 has the object locked still.
This fact is not visible to admins/anyone but User 1.
I had to as org admin, go clear the system lock manually, which revealed the user lock "underneath" which I then removed. (User 1 was gone for the day)

Its weird to me that a user locked item can be transition out from under their change.

FYI, we are running self hosted Jama Connect 8.66.1
If it matters, (I havent tested, but I don't know why it would) I am running firefox.


I also tested that if I have two tabs open, and I edit on one, and transition on the other, it works fine. It has to be 2 different users.


RAD

------------------------------
Rory Duncan
NASA
Kennedy Space Center FL
------------------------------

Comments

  • [Deleted User]
    [Deleted User] Posts: 152
    edited October 2022
    Hi Rory, 

    Quick question here -- is User 1 in this case set as an org admin, or are they set differently?

    ------------------------------
    Carly Rossi // she/her
    Community Manager // Jama Software
    Portland, OR
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 10-03-2022 09:06
    From: Rory Duncan
    Subject: Synch/Lock bug

    So we just had an interesting thing happen, and im pretty sure this is a bug.
    User 1 has an object open on their computer.
    User 2 edits the same object on their computer making a user lock.
    User 1 does not refresh their browser, and transitions the lifecycle/workflow to a state that creates a system lock
    Jama does not give an error. It creates the system lock, performs the transition, but does not refresh the screen.
    After a refresh, the lifecycle/workflow transition is now grayed out, even though User 2 and Org Admin have a valid transition available because user 1 has the object locked still.
    This fact is not visible to admins/anyone but User 1.
    I had to as org admin, go clear the system lock manually, which revealed the user lock "underneath" which I then removed. (User 1 was gone for the day)

    Its weird to me that a user locked item can be transition out from under their change.

    FYI, we are running self hosted Jama Connect 8.66.1
    If it matters, (I havent tested, but I don't know why it would) I am running firefox.


    I also tested that if I have two tabs open, and I edit on one, and transition on the other, it works fine. It has to be 2 different users.


    RAD

    ------------------------------
    Rory Duncan
    NASA
    Kennedy Space Center FL
    ------------------------------
  • Alessandro Valli
    Alessandro Valli Member, Data Exchange, Jama Connect Interchange™ (JCI) Posts: 789
    edited October 2022
    Interesting,
    I had a similar issue some time ago. In my understanding it was related to SOS-DEF-5196 (fixed in 8.62).
    @Carly Rossi it is my past ticket at Jama Support #57052 (2nd part of ticket ...). Maybe it helps ...


    ------------------------------
    Alessandro
    Systems Engineer
    SICK AG
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 10-03-2022 09:06
    From: Rory Duncan
    Subject: Synch/Lock bug

    So we just had an interesting thing happen, and im pretty sure this is a bug.
    User 1 has an object open on their computer.
    User 2 edits the same object on their computer making a user lock.
    User 1 does not refresh their browser, and transitions the lifecycle/workflow to a state that creates a system lock
    Jama does not give an error. It creates the system lock, performs the transition, but does not refresh the screen.
    After a refresh, the lifecycle/workflow transition is now grayed out, even though User 2 and Org Admin have a valid transition available because user 1 has the object locked still.
    This fact is not visible to admins/anyone but User 1.
    I had to as org admin, go clear the system lock manually, which revealed the user lock "underneath" which I then removed. (User 1 was gone for the day)

    Its weird to me that a user locked item can be transition out from under their change.

    FYI, we are running self hosted Jama Connect 8.66.1
    If it matters, (I havent tested, but I don't know why it would) I am running firefox.


    I also tested that if I have two tabs open, and I edit on one, and transition on the other, it works fine. It has to be 2 different users.


    RAD

    ------------------------------
    Rory Duncan
    NASA
    Kennedy Space Center FL
    ------------------------------
    Alessandro
    Systems Engineer
    SICK AG
  • [Deleted User]
    [Deleted User] Posts: 152
    edited October 2022
    Thanks for sharing that, Alessandro! It's helpful in digging in here, and it sounds like they're adjacent (though I'm not sure they're related).

    In SOS-DEF-5196, user locks were able to be added on top of in-place system locks and, in this case, it sounds like the user lock was in place through User 2 before User 1 transitioned the project and creating the system lock. @Rory Duncan, is my understanding accurate?

    ------------------------------
    Carly Rossi // she/her
    Community Manager // Jama Software
    Portland, OR
    ------------------------------
    -------------------------------------------
    Original Message:
    Sent: 10-05-2022 14:58
    From: Alessandro Valli
    Subject: Synch/Lock bug

    Interesting,
    I had a similar issue some time ago. In my understanding it was related to SOS-DEF-5196 (fixed in 8.62).
    @Carly Rossi it is my past ticket at Jama Support #57052 (2nd part of ticket ...). Maybe it helps ...


    ------------------------------
    Alessandro
    Systems Engineer
    SICK AG
    ------------------------------

    Original Message:
    Sent: 10-03-2022 09:06
    From: Rory Duncan
    Subject: Synch/Lock bug

    So we just had an interesting thing happen, and im pretty sure this is a bug.
    User 1 has an object open on their computer.
    User 2 edits the same object on their computer making a user lock.
    User 1 does not refresh their browser, and transitions the lifecycle/workflow to a state that creates a system lock
    Jama does not give an error. It creates the system lock, performs the transition, but does not refresh the screen.
    After a refresh, the lifecycle/workflow transition is now grayed out, even though User 2 and Org Admin have a valid transition available because user 1 has the object locked still.
    This fact is not visible to admins/anyone but User 1.
    I had to as org admin, go clear the system lock manually, which revealed the user lock "underneath" which I then removed. (User 1 was gone for the day)

    Its weird to me that a user locked item can be transition out from under their change.

    FYI, we are running self hosted Jama Connect 8.66.1
    If it matters, (I havent tested, but I don't know why it would) I am running firefox.


    I also tested that if I have two tabs open, and I edit on one, and transition on the other, it works fine. It has to be 2 different users.


    RAD

    ------------------------------
    Rory Duncan
    NASA
    Kennedy Space Center FL
    ------------------------------

Categories