Description: cells formatted as text are handeled wrong? or the yellow 'hint' how far you are is wrong? correct: take a cell formatted as 'number - standard' key in '-307', click the small black square bottom right corner of the cell and pull down some rows, observe a small yellow hint telling you which value will be filled in the last cell, release the mouse button and observe appropriate fill, fail: take a cell and format it to '@' - 'text', (do not! only change the format of the previously used cell, it will fail - to fail - unless you at least do a 'non changing edit' or similar as 'formatting doesn't adapt value' (a big pitfall imho)), key in '-307', click the small black square bottom right corner of the cell and pull down some rows, observe a small yellow hint telling you which value will be filled in the last cell, release the mouse button and observe opposite! of appropriate fill, (filling downwards, despite the yellow hint told 'upwards'), Steps to Reproduce: see above description Actual Results: filled 'downwards' despite hint showed 'upwards', Expected Results: filling upwards or correct hint Reproducible: Always User Profile Reset: No Additional Info: Version: 7.2.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 62dff2844b0bf1d1bcb8eb4d6db529ef4a31bee4 CPU threads: 8; OS: Windows 6.1 Service Pack 1 Build 7601; UI render: default; VCL: win Locale: de-DE (de_DE); UI: en-US Calc: didn't test linux, assume 'all', didn't reset user profile as showing up in different installs,
Hello newbie-02@gmx.de, Thank you for reporting the bug. it seems you're using an old version of LibreOffice. Could you please try to reproduce it with the latest version of LibreOffice from https://www.libreoffice.org/download/libreoffice-fresh/ ? I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' if the bug is still present in the latest version.
Thank you for reporting the bug. Please attach a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO'. Please change it back to 'UNCONFIRMED' once the requested document is provided. (Please note that the attachment will be public, remove any sensitive information before attaching it. See https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F for help on how to do so.)
@xisco: sorry, sample sheet won't help, to see the yellow hint one needs to follow the description, imho it's simple, easy and clear, don't hesitate to ask if you run in any difficulties ... best regards, b.
Confirm Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 2761545769ef564b14fc8cd854a35c42bc269f02 CPU threads: 4; OS: Linux 5.11; UI render: default; VCL: gtk3 Locale: cs-CZ (cs_CZ.UTF-8); UI: en-US Calc: threaded Jumbo
This seems to have begun at the below commit. Adding Cc: to Eike Rathke ; Could you possibly take a look at this one? Thanks 2521c529b0124a0c4c500cf4a63e1e5ca4d5699c is the first bad commit commit 2521c529b0124a0c4c500cf4a63e1e5ca4d5699c Author: Jenkins Build User <tdf@pollux.tdf> Date: Mon Dec 4 12:00:10 2017 +0100 source 87efbdb1ae5a73d081667e10f1571f1e523c1b9c https://gerrit.libreoffice.org/c/core/+/45742 tdf#105268 - Auto Fill: Fix The Next Value for 001-001-001
Still repro as of a recent LO Dev 24.2.
Dear b., 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