Bug 162423 - Ability to assign tracked change to different author
Summary: Ability to assign tracked change to different author
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Track-Changes DoAsMacro
  Show dependency treegraph
 
Reported: 2024-08-10 18:10 UTC by Eyal Rozenberg
Modified: 2024-08-23 07:51 UTC (History)
1 user (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 Eyal Rozenberg 2024-08-10 18:10:58 UTC
Sometimes, you want to keep some tracked changes to a document as such, but have them show as your changes; or even - as changes by someone else. This is already "possible" today, in a crooked way:

* Change your user details to the desired change author details
* remember the changes to be made
* Reject the changes
* Make the changes again, as "yourself"
* Change your user details back

but this is silly. Instead, we should be able to change the tracked-change author identity:

1. In the Edit > Track Changes > Manage... dialog
2. Via the context menu for a change (with a dialog opening up for choosing/typing in author details)
Comment 1 Heiko Tietze 2024-08-12 04:31:52 UTC
(In reply to Eyal Rozenberg from comment #0)
> Sometimes, you want to keep some tracked changes to a document as such, but
> have them show as your changes...
Why would I want to change the authorship? Likewise for comments I would rather prevent this (modifying the content.xml is pretty simple).
Comment 2 Heiko Tietze 2024-08-23 07:51:39 UTC
(In reply to Heiko Tietze from bug 162424 comment #9)
> We discussed the topic in the design meeting.
> 
> The use case might be reasonable but not every possible function should be
> implemented. The integrity of authorship outweighs the flexibility and
> convenience. => WF
> 
> Nevertheless this is just the recommendation for the core application. The
> feature can easily implemented per extension.