Problem description: The letter assistent for a formal personal letter creates a sender field without the first name and the last name. The same for the field above the address field of the letter. Steps to reproduce: 1. Call File - Wizards - Letter (your personal data has do be added to tools - options before) 2. Choose private letter - formal letter 3. Click through the steps of the wizard 4. Choose a name for your template and finish the wizard dialog. 5. A new letter will be created from the template (created with the wizard) 6. Your first and last name will not be in the sender fields of the letter. Current behavior: Expected behavior: Operating System: All Version: 4.2.4.2 release
Assistent don`t works!!!
** 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) 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-06-08
Same as bug 66454?
** 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 (5.4.1 or 5.3.6 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 helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170929
Dear Andreas Mantke, 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
It's really disillusioned, if the only response from an open source project on a bug report after nearly seven years is such a mass pinging. It seemed nobody has really touched this bug report during the last seven years. This is particularly sad because the project pays staff for the work on bug reports and this bug had been introduced by one of this persons. Recommendation to the project: drop the writer wizard for letter, because it is useless in the current state (since seven years now) and nobody seemed to be keen to work on fixing this wizard.
(In reply to Andreas Mantke from comment #6) > It's really disillusioned, if the only response from an open source project > on a bug report after nearly seven years is such a mass pinging. Is it really disillusioned, when experiments have shown that once-per-year re-testing typically results in 25% of the reports being closed as worksforme? > It seemed nobody has really touched this bug report during the last seven > years. This is particularly sad because the project pays staff for the work > on bug reports and this bug had been introduced by one of this persons. How do you know who introduced this bug? Do you have a commit id?
(In reply to Buovjaga from comment #7) > (In reply to Andreas Mantke from comment #6) > > It's really disillusioned, if the only response from an open source project > > on a bug report after nearly seven years is such a mass pinging. > > Is it really disillusioned, when experiments have shown that once-per-year > re-testing typically results in 25% of the reports being closed as > worksforme? but if a source code in this area had never been touched by a developer after the bug report, how would one expect that the bug had been gone? Self healing? > > > It seemed nobody has really touched this bug report during the last seven > > years. This is particularly sad because the project pays staff for the work > > on bug reports and this bug had been introduced by one of this persons. > > How do you know who introduced this bug? Do you have a commit id? You are familiar with the structure of the LibreOffice source code as far as I know. You are able to look at the area where this code live and are able to read the source code. I'm not a LibreOffice coder (but I'm able to read the commit history on e.g. Github). Thus it is clear who introduced the code that causes the bug and made the wizard feature unusable.
(In reply to Andreas Mantke from comment #8) > (In reply to Buovjaga from comment #7) > > (In reply to Andreas Mantke from comment #6) > > > It's really disillusioned, if the only response from an open source project > > > on a bug report after nearly seven years is such a mass pinging. > > > > Is it really disillusioned, when experiments have shown that once-per-year > > re-testing typically results in 25% of the reports being closed as > > worksforme? > > but if a source code in this area had never been touched by a developer > after the bug report, how would one expect that the bug had been gone? Self > healing? That was not the point. You can freely ignore these pings, if you feel certain that an area was not touched by anyone. All I want you to do is to stop disparaging a practice that has a proven beneficial effect on the tidiness of the bug tracker. > > > > > It seemed nobody has really touched this bug report during the last seven > > > years. This is particularly sad because the project pays staff for the work > > > on bug reports and this bug had been introduced by one of this persons. > > > > How do you know who introduced this bug? Do you have a commit id? > > You are familiar with the structure of the LibreOffice source code as far as > I know. You are able to look at the area where this code live and are able > to read the source code. I'm not a LibreOffice coder (but I'm able to read > the commit history on e.g. Github). > Thus it is clear who introduced the code that causes the bug and made the > wizard feature unusable. If it is clear to you, then please give me a link to the commit. You are claiming that someone from the TDF staff introduced this problem 7+ years ago and it would be nice to have verification from you.
(In reply to Buovjaga from comment #9) > (In reply to Andreas Mantke from comment #8) > > (In reply to Buovjaga from comment #7) > > > (In reply to Andreas Mantke from comment #6) > > > > It's really disillusioned, if the only response from an open source project > > > > on a bug report after nearly seven years is such a mass pinging. > > > > > > Is it really disillusioned, when experiments have shown that once-per-year > > > re-testing typically results in 25% of the reports being closed as > > > worksforme? > > > > but if a source code in this area had never been touched by a developer > > after the bug report, how would one expect that the bug had been gone? Self > > healing? > > That was not the point. You can freely ignore these pings, if you feel > certain that an area was not touched by anyone. All I want you to do is to > stop disparaging a practice that has a proven beneficial effect on the > tidiness of the bug tracker. > the most effective result of such mass ping is: annoying those taking time to report a bug (and never get an individual reply, a confirmation of the bug etc.) A lot of them will never ever take their spare time to report a bug in the bug tracker again. And they will also tell their colleagues and friends about their experience. > > > > > > > It seemed nobody has really touched this bug report during the last seven > > > > years. This is particularly sad because the project pays staff for the work > > > > on bug reports and this bug had been introduced by one of this persons. > > > > > > How do you know who introduced this bug? Do you have a commit id? > > > > You are familiar with the structure of the LibreOffice source code as far as > > I know. You are able to look at the area where this code live and are able > > to read the source code. I'm not a LibreOffice coder (but I'm able to read > > the commit history on e.g. Github). > > Thus it is clear who introduced the code that causes the bug and made the > > wizard feature unusable. > > If it is clear to you, then please give me a link to the commit. You are > claiming that someone from the TDF staff introduced this problem 7+ years > ago and it would be nice to have verification from you. Sorry, but you will find out yourself without my support from a non-coder.
(In reply to Buovjaga from comment #3) > Same as bug 66454? Bug #134071 might also be related.
Thanks Dennis, you have spotted duplicated of this bug. Marking them as such. *** This bug has been marked as a duplicate of bug 66454 ***