For bug reports, AskLibO, etc very often the detailed version information is needed. It requres always a selection and copy ot the character string.
Add a simple button with the function "copy version number into clipboard" to the About LibO screen. This would
1 - motivate people to provide the version information in the first run
2 - reduce for frequent reporters the workload
Additional a tool bar button with the same functionality can be created and located in the Standard tool bar of each LibO component to optimize things even more.
Operating System: Windows XP
Version: 220.127.116.11 release
But that information is already selectable and copyable (bug 46193). Was this bug motivated because that feature is not discoverable for users? If not, I don’t think it’s worth to add more clutter. (Of course, we could redesign it so it looks good…)
I frequently try to answer questions in AskLibO. Very often the question for the version pops up. Thus making it easy to find, easy to copy to the clipboard would also help the people in AskLibO.
as pointed out in previous comment by Fitoschido the version number is already selectable and copyable. it's quite easy now and
so I don't think it's worth it to adding a button to it.
I propose a WONTFIX status
I also oppose a button.
But a nice solution would be: If the user clicks on the version info at the top of the about window it automatically gets copied to his clipboard.
That way we don't clutter the about window with a button and yet still provide the most quick possible way to copy that information. I agree that while marking the version info and hitting cmd + c to copy to clipboard, a simple click would be much more effective.
Imo a valid enhancement request. Adjusting title though.
Great! This proposal is even a better one. I hope it can be realized.
** 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.3 or later)
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)
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-06-08
Should be enhancement.