Bug 143351 - Conditional format rule "range" part couldn't be imported.
Summary: Conditional format rule "range" part couldn't be imported.
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-Conditional-Formatting
  Show dependency treegraph
Reported: 2021-07-14 10:07 UTC by Gülşah Köse
Modified: 2023-07-31 03:05 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:

buggy file (86.38 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2021-07-14 10:07 UTC, Gülşah Köse
The example file in Excel and Calc (182.90 KB, image/png)
2021-07-15 13:44 UTC, NISZ LibreOffice Team

Note You need to log in before you can comment on or make changes to this bug.
Description Gülşah Köse 2021-07-14 10:07:47 UTC
Created attachment 173555 [details]
buggy file

1) Open fdo87618-4.xlsx file in LibreOffice.
2) Click Format->Conditional->Manage...

Actual: Range part is empty for "No" rule.
Expected: Range part should refer to all related columns.

Additional info: Document reported in tdf#87618 for another reason that seems as resolved works for me.
Comment 1 NISZ LibreOffice Team 2021-07-15 13:44:55 UTC
Created attachment 173601 [details]
The example file in Excel and Calc

Confirming with 

Version: (x64) / LibreOffice Community
Build ID: 717dc8e3575a18e1e18dc446031e6db4e60a873d
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: en-US
Calc: CL
Comment 2 NISZ LibreOffice Team 2021-07-15 13:48:11 UTC
The range is given as $G:$G so the whole column G.

On the Calc UI I'm unable to select a whole column from the Conditional Formattting dialog. Manually entering $G:$G is converted by the OK button to G1:G1048576 - maybe the import could do this same magic.

Or just allow clicking on column/row headers in the minimized range selector.
Comment 3 Aron Budea 2021-07-30 23:51:09 UTC
Already in
Comment 4 QA Administrators 2023-07-31 03:05:31 UTC
Dear Gülşah Köse,

To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.

There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.

If you have time, please do the following:

Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.

Please DO NOT

Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not 
appropriate in this case)

If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/

2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword

Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa

Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team