fix(issues): update issue timestamp when adding comments

[fallenbagel]

Description

Adding a comment to an issue didn't update the issue's updatedAt timestamp because TypeORM only cascades the insert into the comments table without touching the issue row itself. This meant the "Last Modified" sort order wouldn't reflect recent comment activity. This fix explicitly sets updatedAt on the issue when a new comment is saved, restoring the expected behavior.

• Fixes Commenting on Issues does not make them move to the top of "Last Modified" #2608

How Has This Been Tested?

Screenshots / Logs (if applicable)

Checklist:

• I have read and followed the contribution guidelines.
• Disclosed any use of AI (see our policy)
• I have updated the documentation accordingly.
• All new and existing tests passed.
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

Summary by CodeRabbit

• Bug Fixes
  • Issue last-updated timestamps now properly reflect when new comments are added.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between c23117e and 5edc82c.

📒 Files selected for processing (1)

• server/routes/issue.ts

---

📝 Walkthrough

Walkthrough

A timestamp update is added to the POST comment endpoint in server/routes/issue.ts. When a comment is posted to an issue, the updatedAt field is now set to the current time before persisting the issue, ensuring the modification timestamp reflects comment activity.

Changes

Cohort / File(s)	Summary
Comment Timestamp Update server/routes/issue.ts	Added issue.updatedAt timestamp update when a comment is posted to an issue, ensuring the issue's last modified time reflects comment activity.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰✨ A comment springs forth, fresh and new,
The timestamp ticks—now issues stay in view!
No more lost in the list so deep,
Your recent chats—the system will keep! 📝

🚥 Pre-merge checks | ✅ 4

✅ Passed checks (4 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: updating the issue timestamp when comments are added, which directly addresses the pull request's core objective.
Linked Issues check	✅ Passed	The code change updates issue.updatedAt when a comment is added, directly satisfying the requirement that commenting on issues should move them to the top of 'Last Modified' sort.
Out of Scope Changes check	✅ Passed	The changes are limited to a single file with a one-line modification updating the issue timestamp on comment insertion, remaining entirely within the scope of fixing the 'Last Modified' sort issue.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}