Hi Divya, I faced a similar issue in the past, the best way to do this is to open your Case Type and go to the Settings, there you can select the Locking section, you will see two radio buttons and you can select the one that says Lock When: "An action taken on case (optimistic)". This should prevent the case from locking and multiple teams can work on the same issue without seeing that red error.

Here is a screenshot.

Hello,

Yes I agree with Nia. The behavior reported is perfectly normal with a default locking mechanism and switching to an optimistic approach might be an option.

But be careful switching the locking mechanism will have strong implications.

Optimistic locking should work for this usecase. Thanks.

Thank you all for your responses.

With Optimistic locking, I guess Assignment 1 can open by multiple users until does any action. If yes, can we enable Optimistic locking for a single stage. because we do have other assignments which gets created at later stages and those should be worked by a single user at a time.