Bug 105542 - First condition is not a good way to identify conditions in Manage Conditional Formatting(MCF)
Summary: First condition is not a good way to identify conditions in Manage Conditiona...
Status: RESOLVED WONTFIX
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.3.0.2 rc
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Conditional-Formatting
  Show dependency treegraph
 
Reported: 2017-01-26 14:34 UTC by pajaro
Modified: 2017-04-14 09:29 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 pajaro 2017-01-26 14:34:41 UTC
MCF only shows the first condition, which is insufficient to identify them. 

For example, I have several ColorScale on the same sheet. It only shows ColorScale

Either allow naming them, or show all the conditions or a third better option I cant think of :)
Comment 1 Buovjaga 2017-02-02 11:01:58 UTC
Yeah, I noticed this when testing a ColorScale report. Let's set to NEW.
Comment 2 Markus Mohrhard 2017-02-18 02:39:03 UTC
There is not a better solution. Just use the range to identify the format. The shown condition is just a helpful addition.
Comment 3 pajaro 2017-04-02 10:42:40 UTC
Please, could you reconsider adding a description field to the conditions?

When Having a few more conditions than normal in multiple parts is really a mess of a dialog

This coupled with the fact that when you copy/paste cells with CF, multiple new CF are added, subdividing new cell ranges, the dialog gets reaaally messy

This is really a hindrance for CF in general
Comment 4 Buovjaga 2017-04-13 10:50:34 UTC
(In reply to pajaro from comment #3)
> Please, could you reconsider adding a description field to the conditions?

You could create a new report and include a proposal of how it should look.
Comment 5 pajaro 2017-04-13 13:33:46 UTC
I created a mockup in #107141

Although I thought this wasnt necessary... due to being a disagreement on this being useful and not on how it could look like