Bug 160650 - allow to set comments/descriptions for conditional formattings
Summary: allow to set comments/descriptions for conditional formattings
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
24.2.2.2 release
Hardware: All All
: low enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 162026 (view as bug list)
Depends on:
Blocks: Conditional-Formatting
  Show dependency treegraph
 
Reported: 2024-04-13 04:45 UTC by Christoph Anton Mitterer
Modified: 2024-10-25 20:25 UTC (History)
5 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 Christoph Anton Mitterer 2024-04-13 04:45:18 UTC
Hey.

Conditional formattings can get quite complex, and especially in the overview dialogue (from Format / Conditional Manage), which shows only the range and the first (but not further) conditions, it's often not easy to see what a certain condition does.

It would be nice if one could add a comment/description to each entry and that would be shown in that list.

Thanks,
Chris.
Comment 1 Stéphane Guillou (stragu) 2024-05-15 15:53:38 UTC
Thanks for the suggestion.
Let's see what the UX/Design team thinks.
Comment 2 Heiko Tietze 2024-05-16 08:00:07 UTC
Sounds like a plan. But we have to consider cross-platform and -application compatibility. And the CF-name is probably not (yet) defined in ODF neither you can assign it in Excel, for example. 

Let's keep the ticket with low importance. The idea is to add another column to the Manage CF dialog that provides a user-defined name for CF rule-set.
Comment 3 Regina Henschel 2024-05-16 15:34:11 UTC
A conditions is defined as <style:map> child element of a <style:style> element of style:family="table-cell". I see no problem to add an optional attribute, e.g. style:comment, to the <style:map> element. Of cause, initially it has to be in loext namespace.
Comment 4 Stéphane Guillou (stragu) 2024-07-29 12:39:05 UTC
*** Bug 162026 has been marked as a duplicate of this bug. ***