Displaying message the object is locked by: <user>. in defect module
You should not change this setting. The lock is important.
You want to solve the issues that are causing you to have abandoned locks or process issues where your resources aren't playing nice together.
We have testers raising defects and by default it highlights the defects in the grid view and is creating a lock and the developers are unable to action.
Think about it. When someone edit it more than 5 minutes and it is nerly every time some other users can also edit it and the first user will be very surprised what he done.
So leave it on time that is relevant I think 2 hours are minimum but leave the default is better.
The solution is as other said. Correct the workflow script.
BTW: The admin manual states the value of this param.
ALM Version 12.53.
We are currently using 20+ machines with the same user name to upload result via automation script.
This process has been in place for 2 years+ with no issues. It was observe Early this year that results are taking an indefinite amount of time to upload. Investigating this matter have led us to the conclude that the delay is cause by "User Locks".
It is showing the error the object is locked by: <user>
I think I see this user's issue in the Defect module. We are experiencing it also.
1) No one is disputing the value of the locks for Defects undergoing edits.
2) There is an issue though when a user just highlights a Defect (clicking the far left columns of the Defect). This highlighting can even happen if one logs out and then logs back in ... ALM will return the user to that same Defect. Highlighting a Defect will cause a lock-out unless someone else has already locked that Defect. Users just viewing a Defect requires them to highlight it, and this locks the Defect from editing by anyone else. Perhaps the locking should happen only of the Defect editing commences.
This is not a workflow issue, nor a permission issue. There is no Workflow, and permissions are wide open... and this still happens.
The minimum time that the LOCK_TIMEOUT value can be set to is 1 hour. Our company has had it set to 1 for many years, without issue.
(Statements expressed here are mine alone, and do not reflect the opinions of my employer.)