Retain updated_at when an issuable is mentioned

What does this MR do and why?

When an issuable is referenced in another issuable, we should not bump the updated_at timestamp of the mentioned issuable since this is not considered an update.

References

Related to #560190 (closed)

How to set up and validate locally

  1. Create a new issue
  2. In the new issue, create a note referencing some old issue
  3. In the old issue, a "mentioned in ..." system note should be created
  4. View the issue list and confirm that the "last updated" value of the old issue didn't change

MR acceptance checklist

Evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.

Edited by Heinrich Lee Yu

Merge request reports

Loading