Bug 106696 - Add ability to search for comment author in Find & Replace dialog
Summary: Add ability to search for comment author in Find & Replace dialog
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 151775 (view as bug list)
Depends on:
Blocks: Find-Search Writer-Comments
  Show dependency treegraph
 
Reported: 2017-03-22 12:37 UTC by Thomas Lendo
Modified: 2024-03-07 17:52 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Lendo 2017-03-22 12:37:37 UTC
Sometimes it would be useful to have the ability to search for a certain comment author in a document.

For example I have a Writer document with more than 50 pages and I know that a colleague added some comments. How could I easily find them?

The versioning and changes tracking system is far too complex for that simple task (and that systems ought to be activated BEFORE the search is needed or even known).
Comment 1 Heiko Tietze 2017-03-26 09:31:53 UTC
Searching for comments is addressed in bug 67044 (search ignores keywords within comments), bug 96474 (search *only* within comments), and bug 101936 (Inserting comments makes commented text unsearchable). (Checked only the meta ticket, there might be other requests.)

There is no request to search in comments with restriction to a certain author, so NEW.

If we introduce a sidebar deck for f&r results as suggested in bug 95405 we could introduce a dynamic filter. For example you search for comments, get the full list in the sidebar and have the option to refine the list temporarily with author=foo. Meaning we should keep the initial search simple and easy to use for Benjamin (and in 95% of the use cases) with more options for the result list.
Comment 2 m_a_riosv 2022-10-27 12:31:14 UTC
*** Bug 151775 has been marked as a duplicate of this bug. ***