Description: Renaming group after undoing with the same name as previously occurs an invalid name error. You should rename it with another name than previous one. Steps to Reproduce: 1. Group range from A_0 to A_2 (See Attachment) 2. Rename 'Group1' to 'A', and then 'A' to 'Group A' 3. Undo it, group name should be 'A' 4. Rename this group to 'Group A' Actual Results: Invalid name window pop up. Expected Results: Group name should change. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:54.0) Gecko/20100101 Firefox/54.0
Created attachment 135300 [details] Test file
Hi Dimitri, Should be renamed as Duplicate of Bug 92616 - PIVOTTABLE: Grouped Column Fields problems including with drill to details. Do you have a particular reason to report it separately?
(In reply to Jacques Guilleron from comment #2) > Hi Dimitri, > Should be renamed as Duplicate of > Bug 92616 - PIVOTTABLE: Grouped Column Fields problems including with drill > to details. > Do you have a particular reason to report it separately? Hi Jacques, Bug 92616 describes 4 issues. If you think about a duplicate of the fourth issue, please note that the author refers to a group loss after renaming it. Here, I am talking about a problem with undo manager and group name. In fact, steps to reproduce this bug (111511) occur group loss. Just refresh the pivot table after each group renaming. Basically, if you rename your group with name N and undo it, your group name is now N - 1. Rename it to N and an "Invalid name" window appears. Sincerely,
Created attachment 135372 [details] Test file with renamed groups Thanks for the precisions, Dimitri. Using your steps, I get the right names for the groups. See the attachment. I have to tell that Undo doesn't work with Windows 7 and LO 5.4.0.3 (x64) Build ID: 92c2794a7c181ba4c1c5053618179937228ed1fb Threads CPU : 2; OS : Windows 6.1; UI Render : par défaut; Locale : fr-FR (fr_FR); Calc: single So I use the input line to change the name. Does it work this way for you too?
> Does it work this way for you too? According to your attachment, try to rename group 'B' to 'BBB', refresh your data pivot. Undo it. At this point, your group name is 'B'. Try to rename it again to 'BBB' and you've got the same problem (Invalid name pop up). Tested on Version: 5.3.1.2 Build ID: 1:5.3.1-0ubuntu2 Not tested on Windows yet
I don't reproduce with LO 6.0.0.0.alpha0+ Build ID: 88179e3de8865ea07d5017ca0723afd10ad44ba7 CPU threads: 2; OS: Windows 6.1; UI render: default; TinderBox: Win-x86@39, Branch:master, Time: 2017-08-06_23:49:25 Locale: fr-FR (fr_FR); Calc: CL This has to be confirmed by a linux user. I set status again to Unconfirmed to allow it.
Please explain how to rename a group.
Column x: Select the three lines containing A in their name. Data menu > Group and Outline > Group You get a new Column named x2 and a name Group1 associated to the selection. Allways in Column x, select the lines containing B, and proceed the sa
the same way, and again for the lines containing C. That's all. Sorry for the break.
Select the name 'Group1'. Replace it by 'A'. Enter to valid it. Refresh to view. Select the name 'A'.Replace it by 'Group A'. Enter to valid it. Refresh to view. Use Undo to come back to the name A. Try to enter Group A. Pop up message: Invalid name appears. I didn't v before and didn't
I didn't valid before to change the name 'A' to 'Group A'. Jacques
(In reply to Jacques Guilleron from comment #11) > I didn't valid before to change the name 'A' to 'Group A'. Yes, you should valid it
Thanks, now I repro with Dimitri's steps in the description. Arch Linux 64-bit, KDE Plasma 5 Version: 6.0.0.0.alpha0+ Build ID: 507247697dc6c4a41fe17a29d522511f97040738 CPU threads: 8; OS: Linux 4.12; UI render: default; VCL: kde4; Locale: fi-FI (fi_FI.UTF-8); Calc: group Built on August 29th 2017 Arch Linux 64-bit Version 3.6.7.2 (Build ID: e183d5b)
** 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 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 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: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dimitri Bouron, 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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Dear Dimitri Bouron, 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 MassPing-UntouchedBug