Require Lock and Edit, locking the history

[ngong]

I read the  topic https://www.sparxsystems.com/forums/smf/index.php/topic,41273.0.html and was happy to see that others like Require Lock and Edit as I do. My reason was also mentioned: think before you change. And I do not have problems that colleagues make changes where they should not.

But I am missing one thing for several reasons (one reason is to fulfill ISO26262 change management rules).
I'd like to be able to be responsive to the question: "What has changed when by whom (for what reason)?". If this information would be stored somewhere, I could do a report, selective, as required for specific situations.

Has anyone an idea, how to log the history of locking?

[qwerty]

I think the audit log is going along those lines. Only if a lock is set you can do things that will end up in the audit log. It's a bit chatty, though.

q.

[ngong]

Thank you qwerty - I will switch auditing on. My aim is not to look at them interactively, but create reports on them for release documentation. I see that I can Save Logs for a certain time period. The chatty, the better. Parsing and transferring the log in a form that can be filtered in different ways for different reports  - that's what I will try.