Content
Report a bug 
How to report a bug?
- Follow the link below to create a new work package.
- Set Type to “Bug”.
- Add a detailed Description.
- Attach a File (optional).
- Choose Priority (Standard: normal).
- Set Version to “Bug Backlog”.
- Set Module to the module in OpenProject affected by the bug (e.g. Work package tracking).
- Set Bug found in Version to the OpenProject version in which the bug occurs (e.g. 4.0.0).
- Set Non Functional Aspects to the area which is impacted (e.g. Design).
- Press Create.
- Note: Consider the Bug Reporting Guidelines below.
Follow the link below to report a bug:
Guideline Bug-Reporting
Example Bug-Reporting
Title: [Work package tracking] Translation missing for closed work packages in Roadmap
Preconditions
- Version exists
- Module “Work package tracking” is activated
Steps to reproduce
- Assign work package to version
- Click on Roadmap in left navigation
- (translation missing is displayed below progress bar of version)
Actual behavior
- In Roadmap status below version is missing translations:
- translation missing: en.label_x_closed_issues_abbr (Language setting: English)
- translation missing: de.label_x_closed_issues_abbr (Language setting: German)
Expected behavior
- In Roadmap status of version should be translated correctly.
Screenshot
Bug title
- The title of the bug should be as concise and crisp as possible.
- The respective module is specified in brackets in front of the title (optional).
- Example:
[Work package tracking] Translation missing for closed work packages in Roadmap_
Bug description
- The bug description should be concise and expressive.
- In addition to the description, there should be additional information on the occurence of the error:
- When did the bug occur? (Example: The bug occured on October, 7th 2013 at 11:34 am)
- Which browser was used when you experienced the error?
- The bug should be tested across multiple browsers in order to determine whether the error is browser-specific.
- The browser version in which the error occured should be named. (Example: Firefox 24.0)
- Do you use any plugins? Please provide a list of plugins used (ideally the content of your Gemfile.plugins).
- Do you receive any error messages in the rails console or browser console when the error occurs? Please include the error message if applicable.
Preconditions to reproduce the bug
- Prior to detailing which steps to take to reproduce the error, the necessary preconditions which have to be met should be stated.
- Example:
- A version exists
- Module “Work package tracking” is activated
Steps to reproduce the bug
- The steps that led to the bug should be listed in the description in order to replicate the bug and determine the underlying problem.
- Example:
- Assign work package to version.
- Click on Roadmap in left navigation.
- (“Translation missing” is displayed below progress bar of version.)
Actual behavior
- The actual, erroneous behavior should be stated briefly and concisely.
- Example:
- In Roadmap status below version is missing translations:
- translation missing: en.label_x_closed_issues_abbr (Language setting: English)_
- translation missing: de.label_x_closed_issues_abbr (Language setting: German)_
Expected behavior
- If known, the expected behavior of the application should be described concicesly.
- Example:
- In the Roadmap the version status should be translated correctly.
Screenshots
- If applicable, a screenshot should be added to the bug report in order to explain the bug visually.
- The unintended behavior should be marked in the screenshot (e.g. by using red color).
- The screenshot can be attached as a file and can be integrated in the description with the following syntax: “
” (without quotation marks)
(Notice: Name_of_screenshot should be replaced with the respective name of the file. The file ending (here: .png) has to be adjusted to the appropriate file type of the screenshot.)
- Example: