Problem description: It is very time consuming copying and inserting lines . Steps to reproduce: 1. construct a typical line item spreadsheet , 2. within the line item area create a line item - a regular purchase - eg. lunch or dinner . 3. make 20 copies of that line item - inserting them - eg. between line items above and below . Current behavior: 20 operations of :- 1) highlight and copy the line item . 2) paste special and insert . Expected behavior: Multiple lines should be able to be copied and inserted . The whole operation should be much quicker than it is . Operating System: Windows XP Version: 3.5.7.2 release
I am not sure if I understand your problem correctly, however: to insert multiple empty rows in calc, I can select the number of rows (e.g. click and drag from "1" to "10" in the bar on the left side of the screen), then select "insert->rows" to insert 10 empty rows at that position, moving the rest of the content downward to fill the lines with the same content as an existing line I can select a single row (click on it on the left side of the screen) copy that, then select the empty rows and insert it in all rows in one step or simply select the fields I want to copy, then drag the handle in the bottom-right corner of the selection downwards
Not a valid bug report, I have no idea what reporter thinks what "a typical lline item" is and what reporter's problem might be. @reporter: Thank you for your report – unfortunately important information is missing. May be hints on <http://wiki.documentfoundation.org/BugReport> will help you to find out what information will be useful to reproduce your problem? If you believe that that is really sophisticated please as for Help on a user mailing list Please: - Write a meaningful Summary describing exactly what the problem is - Attach a sample document (not only screenshot) or refer to an existing sample document in an other Bug with a link; to attach a file to this bug report, just click on "Add an attachment" right on this page. - Attach screenshots with comments if you believe that that might explain the problem better than a text comment. Best way is to insert your screenshots into a DRAW document and to add comments that explain what you want to show (attachment 68877 [details], attachment 68490 [details]) - Contribute a document related step by step instruction containing every key press and every mouse click how to reproduce your problem (similar to example in Bug 43431) – if possible contribute an instruction how to create a sample document from the scratch - add information -- what EXACTLY is unexpected -- and WHY do you believe it's unexpected (cite Help or Documentation!) -- concerning your PC -- concerning your OS (Version, Distribution, Language) -- concerning your localization (UI language, Locale setting) –- Libo settings that might be related to your problems -- how you launch LibO and how you opened the sample document –- Whether your problem persists when you renamed your user profile before you launch LibO (please see <https://wiki.documentfoundation.org/UserProfile#User_profile_location>) –- If you can contribute an AOOo Issue that might be useful -- everything else crossing your mind after you read linked texts Even if you can not provide all demanded information, every little new information might bring the breakthrough. May be you want to test <https://www.libreoffice.org/get-help/bug/> for submitting bug reports? You reach that Bug Submission Assistant via LibO menu 'Help -> Feedback / Bug Report'. The assistant will collect and insert such information automatically. May be you can test <http://wiki.documentfoundation.org/BugReport_Details> for submitting bug reports? Please submit Bug reports with status UNCONFIRMED if your are not absolutely sure that you contributed all required background information, that the problem will be reproducible with information you can provide or that your enhancement request will be accepted! Thank you!
Dear Bug Submitter, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INVALID due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/FDO/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team
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 FDO