Lock for Tickets

I understand the need, recorded it as ticket #1015.
But I am not sure locking is the answer.

In this case people will never able to add comments, analysis, or change the status for example...

Neither will it be possible with locked tickets ...

It is easier to lock when ticket confirmed and selected for the project and unlock to close it

But how will developers be able to work on ticker ?
=> start work
=> add comments
=> resquest for notes for completion
=> change status
=> enter result description
...

That is the object of my question :

What do you mean by "scope of the project"

It means, instead of locking, it could be better to "fix scope".
But what would it cover ?
Fix description section...
Fix target version ...
Fix links ...
Not fix result...
Not fix status...
Allow new notes...

The idea I have from your request is to have some "scope fixing".
It may fit some need I have heard of

As I imagine it :
- Add a button "fix scope" on a version
- When scope of a version is fixed :
=> no new item can be linked to this version as target version
=> no item can be removed from this target version
=> "Description" section is locked for all items linked to this version as target version (not only tickets !)
=> "Treatment" section is open for all items linked to this version as target version, except "target version" ) and possibly estimated work, priority, initial due date time and some others to define.

This way you really fix a scope :
=> not only fix some elements, but also fix the list of the elements in the scope
=> not blocking resource to continue to work on elements of the scope

What do you thing about this solution ?