Issue 59775 - copy sheet does not adjust data range of charts to reference to new sheet
Summary: copy sheet does not adjust data range of charts to reference to new sheet
Status: CLOSED DUPLICATE of issue 29848
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: OOo 2.0.1
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: spreadsheet
QA Contact: issues@sc
Keywords: oooqa
Depends on:
Reported: 2005-12-25 15:07 UTC by norbert2
Modified: 2006-02-02 15:33 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

spreadsheet (13.15 KB, application/vnd.oasis.opendocument.spreadsheet)
2005-12-25 15:08 UTC, norbert2
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description norbert2 2005-12-25 15:07:29 UTC

please ...

- open the attaches spreadsheet
- right-click the sheet-tab "Sinus) and make a copy of this sheet; it's named
- right-click the chart in the copied cheet "Modifie Data Range..."
- Note the missing blue border around the cells with the source values: Its
because the date range of the copied sheet's chart references to the "old"
sheet: "$Sinus.$A$1:$B$21".

The reference should be changed automatically set to the new sheet when copying
sheets! ("$Sinus_2.$A$1:$B$21" in this case.)

This is a big usabilty bug of Calc.

Current behaviour is not what the user expects!

(Found OOo 2.0.1 Windows, OOo 2.0 Windows, OOo 1.1.5 Windows, StarOffice 8
Windows and StarOffice 8 Linux.)
Comment 1 norbert2 2005-12-25 15:08:25 UTC
Created attachment 32689 [details]
Comment 2 norbert2 2005-12-25 15:09:28 UTC
(please correct the word "reference" in the summary, to avoid issue query problems)
Comment 3 lars 2005-12-31 22:25:13 UTC
confirmed on Windows XP Pro SP2 with OOo 2.0.1
Comment 4 frank 2006-01-31 15:05:45 UTC

this is a double to Issue 29848.

IMHO this isn't a good idea, as the addressing for the chart data area is
absolute, it couldn't be changed.


*** This issue has been marked as a duplicate of 29848 ***
Comment 5 frank 2006-01-31 15:06:13 UTC
closed double
Comment 6 lars 2006-02-02 15:33:21 UTC
*** Issue 61499 has been marked as a duplicate of this issue. ***