Should watchlists be frozen when a ticket is closed?

[Blobbo]

For non-admins it seems that the watchlist field becomes read-only when a ticket is no longer Active (e.g. when an Incident is in state Closed).

This means agents can't remove the ticket from their watchlist, ever.
They can only hide it by filtering on Active=True.

Is there a reason for this?
Would it matter if the Watchlist field remained read-write when the ticket has reached its final state in the workflow? 
 

[Sandeep Rajput]

@Blobbo This is an OOTB behaviour where all the fields of a ticket become non editable when the state changes to Closed for a non admin user. You can change this by creating a write ACL on the watchlist field with your fulfiller role to allow them to edit the watchlist field even if the ticket is closed,

Hope this helps.

[Blobbo]

Thanks. Changing the behaviour is always possible, but it's hard to understand why it is so. An oversight or deliberate? We are not keen to diverge from OOTB so we'll just ask agents to use filter conditions to hide watchlist items that are in a non-active state. Messy, but standard.