Bug 294826 - Named range(s) not behaving correctly
Summary: Named range(s) not behaving correctly
Status: RESOLVED FIXED
Alias: None
Product: calligrasheets
Classification: Applications
Component: general (show other bugs)
Version: 2.4-snapshots
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: Calligra Sheets (KSpread) Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-25 20:58 UTC by Robert Downing
Modified: 2022-12-14 22:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Downing 2012-02-25 20:58:26 UTC 
Version:           2.4-snapshots (using KDE 4.8.0) 
OS:                Linux

When rows/columns inserted after ranges named, ranges are not updated with new locations of cells

Reproducible: Always

Steps to Reproduce:
Create named range in b3, b4, b5, b6
Insert row between b4 & b5
Range names for (old) b5 not updated

Actual Results:  
Range name for (old) b5 not updated to point to b6

Expected Results:  
Range name be updated correctly
Comment 1 Andrew Crouthamel 2018-11-06 15:04:34 UTC 
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 2 Andrew Crouthamel 2018-11-17 04:53:55 UTC 
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Justin Zobel 2022-12-14 03:09:23 UTC 
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 4 Tomas Mecir 2022-12-14 22:22:02 UTC 
No longer happens in a recent version.