Manually mark comments as "outdated" in pull request (BB-8303)

Sandvine Professional Services avatarSandvine Professional Services created an issue

I'm requesting the ability to mark inline comments as outdated manually, as we have workflows where comments are made to one section of code which actually require a fix in another section of code. We'd prefer to manually mark the comment as addressed/outdated even if the LOC in question wasn't modified by any commit.

The current workaround is to just reply to the message with a "fixed" or something to that effect, which we'd do anyway, but after a long review with many of these, the inline code gets polluted with many stale comments. Deleting is not desirable as we'd like an audit trail of the comments made.

Thanks

Comments (3)

  1. Brodie Rao

    Hi,

    That sounds like a good idea. Our algorithm for determining if a comment is still relevant can only do so much inference, so it'd be useful to have something like this. I've put an issue for this in our internal backlog, hopefully we'll look into it soon.

    Thanks for the report!

  2. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.