Bug 68521

Summary:	Cut and Paste Control-Field does not update changed Column / Rows
Product:	LibreOffice	Reporter:	Karl <JKluth>
Component:	Calc	Assignee:	Not Assigned <libreoffice-bugs>
Status:	RESOLVED INVALID
Severity:	minor	CC:	ilmari.lauhakangas
Priority:	medium
Version:	4.1.0.4 release
Hardware:	x86-64 (AMD64)
OS:	Windows (All)
Whiteboard:
Crash report or crash signature:		Regression By:

Description Karl 2013-08-25 07:25:33 UTC

I do work with both Open-Office 4.0 Libreoffice 4.1 / as both have different bugs.

I do have a sheet with a matrix of cells, which i copy -and insert- for each new month.

Within i use "control - fields" (that with the hook for true or false 
/sorry for my english).

If i copy these and paste -insert- for the new month,
the (at least) column literals are not updated (i did not check if rows are updated).

They still refer to the cells the origins refer to 
and write their true/false to them.

I have to change their referals via design mode manually.

Bug ?

regards

Comment 1 retired 2013-08-25 09:08:48 UTC

Hi Karl and thanks for the report. Any chance, you could attach the example document (cleared of any sensitive information) so it would be much easier to have a closer look and potentially confirm this bug.

Comment 2 retired 2013-08-25 09:10:50 UTC

Also I'm not quite sure why this bug does not has the option to set to UNCONFIRMED since that is what it currently should be. Did you create this bug via BugzillaSubmissionAssistant (https://www.libreoffice.org/get-help/bug/) or directly on bugzilla?

Comment 3 Karl 2013-08-26 15:26:29 UTC

I tried to create a reduced sheet.

On this i was unable to mark and copy a cell which had an controll-field (box with hook) at all.

I dont have an idea, why in one scheet these could be copied and at the other not.

May be the sizes of the cells where not identical or not as big enough or whatever ??

But i am sure, i had to manually update the reference cells, the controll-field writes the true/ false values to, within "designer (?)".

regards
karl

Comment 4 QA Administrators 2015-07-18 17:42:51 UTC

** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice (4.4.1 or later): https://www.libreoffice.org/download/

If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior

If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2015-07-18

Comment 5 Buovjaga 2015-10-16 19:56:35 UTC

So this was never confirmed.

Is this still a problem with LibO 5?

Set to NEEDINFO.
Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.

Comment 6 QA Administrators 2016-05-09 20:07:47 UTC

Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team

This INVALID Message was generated on: 2016-05-09