Add a project setting to keep "mentioned in commit" completely out of an issue's timeline

Problem to solve

Sorting issues by "last updated" should be unaffected by "mentioned in commit".

In my projects, most participants (developers and reporters) prefer having the issue list sorted by "last update". But in our understanding, "last update" means direct user interactions such as commenting, editing labels, updating assignee, and other status changes made directly in the UI.
But as development goes by, the order is affected by commits mentioning an issue. We still want to have commit messages containing the issue number, it should just not affect the "last modified" date of the issue.
I am aware that I can switch an issue to "Show comments only", but that does not help in the issue list's sort order.

Intended users

Developers, Reporters.
Probably more interesting for smaller projects with limited number of developers.

User experience goal

Separation of project management and development:

When I want to know where comments were added or status was changed, I look at the issues list.
When I want to see what happened in the code, I do "fetch" and look at the "git log" view of my IDE.

Proposal

Add a project setting to keep "mentioned in commit" completely out of an issue's timeline:

not affecting the "last updated" anymore
never show up in an issue's detail view

Availability of the setting:

This setting should be available to existing projects.
No cleanup of existing issues needed.
Effective from the moment when it is selected.

Further details

n/a

Permissions and Security

n/a

Documentation

Availability & Testing

What does success look like, and how can we measure that?

success metrics:

Saved project management time

acceptance criteria:

The setting is there, and (if selected) subsequent commits do not affect the "last updated" sort order.