From The Document Foundation Wiki
< QA
Revision as of 2011-10-07T10:52:58 by Loic (Talk | contribs) (Add "Consistency" section)

Jump to: navigation, search



The Bug Submission Assistant helps the libreoffice user to report a problem with one of the libreoffice components (Writer, Presentation etc.). One step at a time, it asks the information that will help the developer to understand the problem. It is a substitute to the bugzilla form which is better suited for experts. As can be seen in the screenshots below, the Bug Submission Assistant is a subset of the bugzilla form where only the required information is shown. They are presented to the user one by one to emphasize that they are necessary to properly fill a bug report. The Bug Submission Assistant needs to be continuously improved. A list of small tasks is available to the contributors, as well as detailed implementation notes to help her/him figure out how it is structured. Patches can be sent to Libreoffice Q&A mailing list. If provided with associated tests and screenshots demonstrating cross browser compatibility, they can be commited and published with a minimal effort.


To measure the effectiveness of the Bug Submission Assistant compared to the regular bugzilla form, each bug filled with it has the status_whiteboard field set to BSA.

Weekly statistic (last 7 days)


If you have found a problem, please report it, preferably with a screenshot and as much details as possible using bugzilla

Release plan

Milestone 0.1

A simple placeholder, so that a "Report a bug" link added to LibO Help menu will not lead to Nirvana, but to an existing Web page with a forward-link to he LibO bug submit page, eliminating some problems: The Submission page for all Projects is Projekt LibO there has a link to That's not good, Initial status should be UNCONFIRMED, and user should select a LibO version, not report with random Version from Bugzilla. That will be reached with;bug_status=UNCONFIRMED;version=?. I simply added ";bug_status=UNCONFIRMED" to define Initial Status and ";version=?" to delete any Versions selection from picker.

The only thing the bug reporter / user will see of that all is "if forward will not work please click here".

For that we need some Webspace on the LibO servers(?), the rest can be done easily. For later milestone some administrative questions will have to be kept in mind, for example admin permissions for Porgrammer, ... .

Release date: never. There has been some discussions about it but no URL was ever published. Milestone 0.2 was completed before Milestone 0.1.

Milestone 0.2

Minimum Version, Automated proceeding of BugReport_Details:Selection of correct Component and Subcomponent, user can only submit if he checked for DUPlicates before. The Assistent should have "LibO Website look"

Planned release date: September 23rd, 2011

Milestone 0.3

Adding features as shown in first example with influence to Severity / Priority pickers and and and (additional search in OOo, ...)

Planned release date: none



The following should contain all the information a developer need to know to work on the implementation of the Bug Submission Assistant. It covers all that cannot be easily deduced from reading the code or the associated tests. The general idea is to create a web application that fits in a single HTML page. This page ( ) is added to the regular bugzilla web site ( ). However, because it would make no sense to insert such a specialized page to, it is done using a [#SystemAdministration|reverse proxy] assembling the two together. This server side setup allows the web application to query bugzilla without violating the origin policy and does not require any server code.


  • All the sources are in JavaScript
  • It uses JQuery
  • Each line of code must be tested
  • The core is in bug.js
    • The behavior of each step is encapsulated in a state_XXXX function that is called by the previous step and is responsible for invoking the state_YYYY function of the next step when it is finished.
    • A state function is not given any argument and must not provide any argument to the next state function. For instance, the state_subcomponent will retrieve the name of the component from the DOM and not from its arguments.
    • The general idea is to be able to develop within the context of a state function without knowing the behavior of the previous state functions nor trying to figure out an API between state functions.
    • The error model is to throw after displaying a message in the .error element
    • The $.bug.ajax function is a wrapper for $.ajax function that throw on error and display a message in the .error element
    • The $.bug.lookup_result function analyzes a page returned by bugzilla, looking for an error pattern. If one is found, it display a message in the .error element and throws. Otherwise it returns the string found by the first capturing parenthesis of the success pattern.
    • The code does not contain or generate any markup.
    • The ajax calls must use the ajax().pipe() form for consistency. It is not a cosmetic point, it has impact on the code structure.
    • The compatibility function is designed for code that needs to be run once, when the page is loaded, to help with cross browser compatibility
  • The dropdown selections ( version, component etc. ) are implemented in select.js
  • The tests are implemented in test.js.
    • There is at least one test function per function found in the bug.js file.
    • The test.html file partially copies the markup from bug.xhtml. It is intentional and no attempt must be made to run the tests using the exact same markup.
    • The test.html file must include the same CSS as bug.xhtml because it will have consequences on the position and visibility of the elements and such consequences must be tested.

Cross browser

  • If javascript is disabled, a link to bugzilla is shown
  • If the browser version is known to fail, a link to bugzilla is shown
  • For each supported browsers, the tests are run, each ?skin=XXX URL is checked, a fake bug is reported and then deleted from bugzilla. A permanent item is set in the TODO list as this work must be done on a regular basis.

CSS/HTML integration

Installation and maintainance integration

The official entry point (in the draft site before it is published) is implemented as a JS Pagecontaining an iframe within silverstripe

<iframe src="" width="850" height="800" frameborder="0"> </iframe>

Note that the space before the </iframe> is required to prevent silverstripe from editing the inner HTML.

System Administration

The host name is defined as a reverse proxy to on kermit

<VirtualHost *:443>
   DocumentRoot       /var/www/sites/

   ProxyPass           /libreoffice !
   ProxyPass           / retry=1
   ProxyPreserveHost   On
   SSLProxyEngine      On
   SSLEngine on
   SSLCertificateFile /etc/ssl/certs/
   SSLCertificateKeyFile /etc/ssl/private/
   SSLCertificateChainFile /etc/ssl/certs/
   CustomLog /var/log/apache2/ vhost_combined


  • proposed to relay the need for translation, both on * and the wiki.
  • When the page content is modified, it must be copied over to the * sites which are separate silversite instances. The URL in the iframe must be copied over and the bug-XX.html changed to the matching locale in the wiki. For instance,
<iframe src="" width="850" height="800" frameborder="0"> </iframe> 

must be replaced by

<iframe src="" width="850" height="800" frameborder="0"> </iframe>


<div class="component"> ... </div>

that can be found in the source of the page. These elements must be preserved and not translated so that the software can identify which texts must be used.

Data sources


Sanity checks are run each time the Bug Submission Assitant is generated:


  • From February to March 2011, discussion is launched and a draft implementation of the logic related to crash and problematic documents is developped in JavaScript
  • In September 2011 The first implementation of the Bug Submission Assistant is completed, matching the Milestone 2.0 and is published.

Additional information