Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Getting started
    • Introduction video
      Welcome to OpenProject Community
      Get a quick overview of project management and team collaboration with OpenProject. You can restart this video from the help menu.
    • Help and support
    • User guides
    • Videos
    • Shortcuts
    • Community forum
    • Professional support
    • Additional resources
    • Data privacy and security policy
    • Digital accessibility (DE)
    • OpenProject website
    • Security alerts / Newsletter
    • OpenProject blog
    • Release notes
    • Report a bug
    • Development roadmap
    • Add and edit translations
    • API documentation
  • Sign in
      Forgot your password?
      Create a new account

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
  • Roadmap
  • Work packages
  • Calendars
  • Team planners
  • Boards
  • Forums
  • Wiki
    • Table of contents
      • Expanded. Click to collapseCollapsed. Click to showDeveloper
        • Hierarchy leafAccessibility Checklist
        • Hierarchy leafCode Review Guidelines
        • Expanded. Click to collapseCollapsed. Click to showContribution
          • Hierarchy leafGit Workflow
          • Hierarchy leafTranslations
        • Expanded. Click to collapseCollapsed. Click to showDeveloping Plugins
          • Hierarchy leafDeveloping an OmniAuth Authentication Plugin
        • Hierarchy leafRelease Process
        • Hierarchy leafReport a bug
        • Hierarchy leafSecurity
        • Hierarchy leafSetting up an OpenLDAP server for testing
        • Hierarchy leafTheme Features
      • Hierarchy leafDownload
      • Expanded. Click to collapseCollapsed. Click to showFeature tour
        • Hierarchy leafRelease Notes OpenProject 30
        • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 30 - Overview
          • Hierarchy leafGlossary
          • Hierarchy leafRelease Notes - Accessibility
          • Hierarchy leafRelease Notes - Accessibility changes
          • Hierarchy leafRelease Notes - Add work package queries as menu items to sidebar
          • Hierarchy leafRelease Notes - Copy projects based on Templates
          • Hierarchy leafRelease Notes - Design changes
          • Hierarchy leafRelease Notes - Fixed Bugs
          • Hierarchy leafRelease Notes - Keyboard Shortcuts
          • Hierarchy leafRelease Notes - Project settings
          • Hierarchy leafRelease Notes - Ruby&Rails Update
          • Hierarchy leafRelease Notes - Security
          • Hierarchy leafRelease Notes - Timelines
          • Hierarchy leafRelease Notes - Work packages
      • Hierarchy leafHowto create animated gifs
      • Hierarchy leafMigration Squashing
      • Hierarchy leafMod security
      • Hierarchy leafNew work package page
      • Hierarchy leafOP3 to OP4 Debian upgrade
      • Hierarchy leafOP4 Ubuntu1404 Stable with MySQL in production
      • Hierarchy leafOpenProject 40 Development Setup
      • Expanded. Click to collapseCollapsed. Click to showOpenProject Foundation
        • Hierarchy leafBoards
        • Hierarchy leafMembers
        • Hierarchy leafOPF-Meetings
        • Hierarchy leafStatutes
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes
        • Hierarchy leafOpenProject released on Bitnami
      • Expanded. Click to collapseCollapsed. Click to showRelease Notes OpenProject 40 - Overview
        • Hierarchy leafRelease Notes OpenProject 40 - Accessibility improvements
        • Hierarchy leafRelease Notes OpenProject 40 - Column header functions in work package table
        • Hierarchy leafRelease Notes OpenProject 40 - Improved Design
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated query title on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - Integrated toolbar on work package page
        • Hierarchy leafRelease Notes OpenProject 40 - OmniAuth integration for OpenProject
        • Hierarchy leafRelease Notes OpenProject 40 - Work package details pane
      • Expanded. Click to collapseCollapsed. Click to showSecurity and privacy
        • Hierarchy leafFAQ
      • Expanded. Click to collapseCollapsed. Click to showSupport
        • Expanded. Click to collapseCollapsed. Click to showDownload and Installation
          • Hierarchy leafInstallation MacOS
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 3 0
            • Hierarchy leafDebian Stable with MySQL in production
            • Hierarchy leafInstallation Ubuntu
            • Hierarchy leafInstallation Windows
            • Hierarchy leafInstallation on Centos 65 x64 with Apache and PostgreSQL 93
          • Expanded. Click to collapseCollapsed. Click to showInstallation OpenProject 40
            • Hierarchy leafOP4 Debian Stable with MySQL in production
          • Expanded. Click to collapseCollapsed. Click to showMigration paths
            • Hierarchy leafFrom Chilliproject to OpenProject
            • Hierarchy leafMigration 15 to 30
            • Hierarchy leafMigration 24 to 30
            • Hierarchy leafMigration Redmine 2x › OpenProject 30
            • Hierarchy leafOpenProject 3 Migration
          • Hierarchy leafOpenProject 40
        • Expanded. Click to collapseCollapsed. Click to showNews
          • Hierarchy leafNew OpenProject Translations Plugin
          • Hierarchy leafNew Plugin on OpenProjectorg Local Avatars
          • Hierarchy leafNew design for OpenProject
          • Hierarchy leafNews Accessibility workshop for OpenProject
          • Hierarchy leafNews Glossary for OpenProject
          • Hierarchy leafNews Heartbleed fixed
          • Hierarchy leafNews Icon Fonts
          • Hierarchy leafNews OpenProject 30 Release
          • Hierarchy leafNews Release GitHub Integration Plugin
          • Hierarchy leafNews Success Story Deutsche Telekom
          • Hierarchy leafNews Timelines
          • Hierarchy leafOpenProject 3013 released
          • Hierarchy leafOpenProject 3017 released
          • Hierarchy leafOpenProject 40 released
          • Hierarchy leafOpenProject 40 will be coming soon
          • Hierarchy leafOpenProject 405 released
          • Hierarchy leafOpenProject and pkgrio
          • Hierarchy leafOpenProject news moved to a new blog
          • Hierarchy leafOpenProjectBitnami
          • Hierarchy leafPackager version with plugins released ("Community edition")
          • Hierarchy leafRegistration OpenProject-Foundation
          • Hierarchy leafRelease OpenProject AuthPlugins
          • Hierarchy leafUpdates on OpenProject
          • Hierarchy leafWe need your feedback for the the new fullscreen view for work packages
        • Hierarchy leafOpenProject Plug-Ins
      • Expanded. Click to collapseCollapsed. Click to showWiki
        • Hierarchy leaf2nd Level Support
You are here:
  • Developer
  • Report a bug

Content

Report a bug

  • More
    • Print
    • Table of contents

Report a bug

How to report a bug?

  1. Follow the link below to create a new work package.
  2. Set Type to “Bug”.
  3. Add a detailed Description.
  4. Attach a File (optional).
  5. Choose Priority (Standard: normal).
  6. Set Version to “Bug Backlog”.
  7. Set Module to the module in OpenProject affected by the bug (e.g. Work package tracking).
  8. Set Bug found in Version to the OpenProject version in which the bug occurs (e.g. 4.0.0).
  9. Set Non Functional Aspects to the area which is impacted (e.g. Design).
  10. Press Create.
  11. Note: Consider the Bug Reporting Guidelines below.

Follow the link below to report a bug:

  • Link to report a bug

  • 1Report a bug
  • 2Guideline Bug-Reporting
    • 2.1Example Bug-Reporting
    • 2.2Bug title
    • 2.3Bug description
      • 2.3.1Preconditions to reproduce the bug
      • 2.3.2Steps to reproduce the bug
      • 2.3.3Actual behavior
      • 2.3.4Expected behavior
    • 2.4Screenshots

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

  1. Assign work package to version
  2. Click on Roadmap in left navigation
  3. (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:
  1. Assign work package to version.
  2. Click on Roadmap in left navigation.
  3. (“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:


Loading...