https://bugs.documentfoundation.org/show_bug.cgi?id=171447
--- Comment #5 from Nera <[email protected]> --- Created attachment 206390 --> https://bugs.documentfoundation.org/attachment.cgi?id=206390&action=edit Proposed solution Hi Heiko, I agree it makes sense to include user-defined conditional formatting presets, especially if it's a shortcut (which I tried to achieve via macro). That would be a meaningful improvement. I would suggest: store user-defined CF and list it under (Format >) CF menu directly, just add a separator line before "Manage", I attached an image as example (I believe most efficient and minimal approach). I'd like to clarify that this report is a broader experience consisting of related issues: 1 Conditional formatting workflow (enhancement, as categorized) -> main focus of this report //goal 2 Macro (bug) -> currently non-functional as a workaround for this action 3 Web navigation -> friction as a new user 4 Bug reporting UX -> friction in the reporting process Also I should clarify, the example I provided was from Excel Online (cloud), which is more limited (intentionally since it's free). The desktop version still offers both flexibility and a streamlined workflow: 1 CLICK on Conditional Formatting (also shows on hover description) displays a menu including: -> HOVER on Color Scales -> shows commonly used presets =efficiency /AND/ option "More Rules" -> opens dialog = freedom/flexibility -> CLICK either "New Rule" /OR/ "Manage Rules" -> direct access to full dialog (so 2 clicks total, same as Libre Calc) = freedom/flexibility So "focus on freedom" can come across as a false trade-off with efficiency. Presets (built-in or user-defined) would not reduce freedom, but rather complement it. From a UX perspective (following Nielsen principles https://wiki.documentfoundation.org/Design/Principles) this affects: ux-efficiency: minimizing steps and time for frequent tasks ux-minimalism: avoiding unnecessary interaction ux-consistency: aligning with user expectations from similar tools I think user-defined presets (and potentially toolbar/notebookbar integration) is a great direction and would address the main workflow concern I raised. Generally, I also feel that the UI would benefit from hover states throughout, as they can significantly improve efficiency and discoverability, without adding visual clutter, or big changes in code. For example: previews, descriptions, or quick access to common options, which reduces the need for additional clicks, opening/closing dialogs... This aligns with: ux-efficiency: reducing interaction cost for frequent actions ux-discovery: enabling users to explore functionality visually rather than relying on memory ux-feedback: giving immediate, contextual information about available actions If you don't have telemetry, aligning with MS is a practical proxy for real usage patterns. If possible, why not include a lightweight opt-in telemetry? It would help objectively inform such decisions in the future. I believe LibreOffice has established a strong level of trust as an open-source project, which makes this more feasible. For example, instead of that "Did you know?" window that is as helpful as Clippy, a transparent opt-in prompt on first launch could allow users to explicitly choose to participate, something along the lines of: "LibreOffice is a community-driven, free and private open-source project. We want to make everyday workflows faster, easier, and more enjoyable for all users. You can help by sharing ANONYMOUS usage data. This would include only features and actions, for example: - toolbar clicks - menu choices - dialog interactions This DOES NOT include your personal information, documents, or any content. Your data is private and secure. This is completely optional and you can change it at any time in the settings." -- You are receiving this mail because: You are the assignee for the bug.
