Top Menu

Jump to content
Home
    • Projects
    • Work packages
    • News
    • Boards
    • Team planners
    • 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
    • Enterprise 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
  • Feature tour
    • 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:
  • Forums
  • Plugins

Content

Problems with Backlogs plugin

Added by Rob Guinness about 5 years ago

I am experiencing a lot of problems with the Backlogs plugin, especially the task board. One of the main reasons I selected open project was the advertised support for Agile/Scrum (See: https://www.openproject.org/collaboration-software-features/scrum-agile-project-management/), but it appears that it is so buggy that we will have to scrap it completely if the issues are not resolved soon.

I don’t know if others are experiencing the same issues, or if I am perhaps using it wrong. Here is a quick list of the issues I am facing:

1. Tasks randomly show up in the Sprint Impediments row, and I can’t figure out how to remove them. There doesn’t seem to be any rhyme or reason as to why they show up there.

2. (Updated) As far as I can tell, there is no good way to work with Epics that extend across multiple sprints. The entire Epic hierarchy has to be assigned to a single sprint in order to see it in the task board.

3. Tasks that are not part of a WP hierarchy (e.g. an Epic) cannot be moved across the task board according to their status. I don’t know if this is a bug or limitation of the design, but this makes the task board really unusable the way our company does Scrum. In a given sprint, we may have 5 or 10 small miscellaneous tasks that are not part of a user story. It would be burdensome to create a catch-all user story or epic to group together all these miscellaneous tasks.

4. Story points for child WPs do not roll-up into the story points for their parent. So you have to separately manage story points at each level in the hierarchy.


Replies (1)

RE: Problems with Backlogs plugin - Added by Robin Wagner about 5 years ago

Hello Rob,

sorry to hear that you experience issues with OpenProject.

Let me address the issues you mentioned:

1. Tasks randomly show up in the Sprint Impediments row, and I can’t figure out how to remove them. There doesn’t seem to be any rhyme or reason as to why they show up there.

Tasks show up in the “Sprint Impediments” row when they are assigned to a sprint but do not have a parent work package which is displayed as a story in the sprint (e.g. Epic, User Story). This is caused by the fact that “Sprint Impediments” are in fact Tasks in the background. In order to remove them from the “Sprint Impediments” you can either remove them from the sprint or assign them to a parent work package which is part of the sprint (in which case they will show up in the appropriate row in the task board).

2. (Updated) As far as I can tell, there is no good way to work with Epics that extend across multiple sprints. The entire Epic hierarchy has to be assigned to a single sprint in order to see it in the task board.

The task board is really intended to manage the user stories, features (and possibly bugs) and their tasks. Epics don’t really fit into this view since they are on a higher level. However, I understand the need to keep track of Epics and their associated user stories.
There are two helpful ways to keep track of this:

  1. You can either assign Epics to their own version / backlog (e.g. located in parent project used to higher level management). By clicking on the ID displayed next to each Epic’s name you can open the associated work package fullscreen view and use the “Relations” tab to see the associated user stories (child work packages) and their status.
  2. Alternatively, you can use the work package list for the Epic perspective. The associated user stories are then shown as children in the work package list. By displaying the “Version” as a column you can always see in which sprint the different user stories are. This way you can also display multi-project hierarchies (e.g. if you have a main project which is used for managing the Epics and different sub projects representing e.g. different development teams. The individual development teams can then of course work in the Backlogs view to manage their user stories and tasks).

3. Tasks that are not part of a WP hierarchy (e.g. an Epic) cannot be moved across the task board according to their status. I don’t know if this is a bug or limitation of the design, but this makes the task board really unusable the way our company does Scrum. In a given sprint, we may have 5 or 10 small miscellaneous tasks that are not part of a user story. It would be burdensome to create a catch-all user story or epic to group together all these miscellaneous tasks.

Tasks always require a parent (e.g. user story) to be shown in the task board. The reason being that otherwise you would not see if a sprint has been completed just by looking at the sprint on the Backlog (but you would have to always switch to the task board). By requiring a parent (e.g. user story) you can see from the backlog view if any of the user stories have not yet been completed.
In fact, if you assign tasks to a sprint without a parent they will show up in the “Sprint Impediment” row (see answer to issue 1).

4. Story points for child WPs do not roll-up into the story points for their parent. So you have to separately manage story points at each level in the hierarchy.

This is indeed a bug (tracked in #22545). Story points should be “inherited” up the work package hierarchy in a similar way as e.g. the values for “estimated time” are).

We are planning to update the backlogs view and use a similarly flexible UI as in the work package list. This way some of the issue you mentioned (such as displaying multiple hierarchies of work packages (e.g. Epic > User Story > Task)) can be displayed more easily.

Btw: Since you are using the Cloud Edition you can also contact us message us directly through our support email if you experience additional issues (this way you will receive a response more quickly).

Best regards,
Robin

  • (1 - 1/1)
Loading...