Bug 170113 - AutoSum ignores calculated cells when determining range in LibreOffice Calc
Summary: AutoSum ignores calculated cells when determining range in LibreOffice Calc
Status: RESOLVED DUPLICATE of bug 62279
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-12-24 11:01 UTC by nathanhallez59
Modified: 2025-12-25 06:38 UTC (History)
0 users

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 nathanhallez59 2025-12-24 11:01:06 UTC
Description:
In LibreOffice Calc, the Sigma (AutoSum) button is intended to quickly create formulas based on selected cells.

However, its behavior is incorrect when the selection includes both calculated cells and numeric cells.

For example:

Cell A3 contains a formula returning a number.

Cell A4 contains a numeric value.

I select cells A3 and A4 and press the Sigma button.

Resulting formula: SUM(A4:A4)
Expected formula: SUM(A3:A4)

The AutoSum function seems to ignore calculated cells when determining the range, even though they are part of the selection.

Steps to Reproduce:
1. Enter two numeric values in cells A1 and A2.
2. In cell A3, create a formula that sums A1 and A2 (=A1+A2).
3. Enter a numeric value in cell A4.
4. Select cells A3 and A4.
5. Click the Sigma (AutoSum) button.

Actual Results:
SUM(A4:A4)

Expected Results:
SUM(A3:A4)


Reproducible: Always


User Profile Reset: Yes

Additional Info:
Version: 25.2.6.2 (X86_64) / LibreOffice Community
Build ID: 520(Build:2)
CPU threads: 16; OS: Linux 6.12; UI render: default; VCL: gtk3
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 1 nathanhallez59 2025-12-24 11:08:52 UTC
For step two, the formula should be =SUM(A1;A2), the bug doesn't appear with =A1+A2.
Comment 2 nobu 2025-12-25 06:38:10 UTC

*** This bug has been marked as a duplicate of bug 62279 ***