How can you keep 2 users from editing the same asset?
Hi,
I have a question from my team. They are concerned that when you are editing a Test Plan or Test Case, anyone else could open and edit that same Test Plan or Test Case at the same time, without warning to either user. Is there a way to fix that?
I guess some way to "Check Out" or lock for editing. I know there is a lock feature, but that keeps anyone from editing, including the person who locked it.
I have a question from my team. They are concerned that when you are editing a Test Plan or Test Case, anyone else could open and edit that same Test Plan or Test Case at the same time, without warning to either user. Is there a way to fix that?
I guess some way to "Check Out" or lock for editing. I know there is a lock feature, but that keeps anyone from editing, including the person who locked it.
3 answers
I have had the same issue. Have had people finding the need to redo their work because of it. This is the most screwed up implementation of a basic feature that all applications use, pathetic.
For a workaround, lock everything and when you go in to edit ensure you get lock notification. If not then do not edit as someone else most likely is. If you do get notification then unlock and edit. Just remember to lock when done.
Another team with the same question more than 2 years later ...
We are going to start using RQM 3.0.1.1 and would like a user to be able to lock and edit a test case, preventing anyone else from editing it at the same time. (The "lock" function still just puts the test case in read-only mode.) Is there a way to do this? What have we missed?
We are going to start using RQM 3.0.1.1 and would like a user to be able to lock and edit a test case, preventing anyone else from editing it at the same time. (The "lock" function still just puts the test case in read-only mode.) Is there a way to do this? What have we missed?
If two persons are editing same artifact in parallel, one one will succeed to save it. However if you think Lock should provide the user to edit it (user who locked it), I think you can file an enhancement request for it.
file issue
file issue