Top Menu

Jump to content
Home
    Modules
      • Projects
      • Activity
      • Work packages
      • Gantt charts
      • Calendars
      • Team planners
      • Boards
      • 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
    • Upgrade to Enterprise edition
    • 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?

      or sign in with your existing account

      Google

Side Menu

  • Overview
  • Activity
    Activity
  • Roadmap
  • Work packages
    Work packages
  • Gantt charts
    Gantt charts
  • Calendars
    Calendars
  • Team planners
    Team planners
  • Boards
    Boards
  • News
  • Forums

Content

Support Installation & Updates
  1. OpenProject
  2. Forums
  3. Support Installation & Updates
  4. progress of child workpackages were not able to be changed anymore

progress of child workpackages were not able to be changed anymore

Added by Andreas Wagner over 4 years ago

Hi,

with the latest update (11.0.1) we are facing the issue that the progress of child workpackages were not able to be changed anymore. The failure message mentiones: Version needs to be identical to the Version of the superordinate story. (Picture1)

When the error message occured, the „Version“ dropdown was automatically selected. Using the dropdown and selecting a different Version (e.g. the same Version as the superordinate workpackage) results in a second error message: The change of Version is blocked for the ressource. Either this attribute is derived from a relation (e.g. Child) or it is not configurable. (Picture2)

The only thing that was possible is to change the Version in the absolut project top level workpackage. This results in changing all Versions of related child workpackages. Now, it is possible to change the progress of child workpackages again but we are loosing the visability of the Roadmap that shows us the status of Version based grouped workpackages.


Replies (2)

RE: progress of child workpackages were not able to be changed anymore - Added by Andreas Wagner over 4 years ago

Oh it seem's that the pictures are not shown correctly

RE: progress of child workpackages were not able to be changed anymore - Added by Max Mutzge over 4 years ago

Hi Andreas, the fastest way of solving this could probably be to deactivate the backlogs module, as it can cause problems of such kind.
[not sure if this exactly fits your situation:]
If you are actively working with the backlogs module in the project, you could then e.g. move the parent Epic from the parent project to the project where the tasks are located. Alternatively, you could change the type "Task" to a different type (e.g. "User Story"). This should also resolve the issue. For context: On the backlogs page you can switch to the "Task board". The task board shows the work packages assigned to a sprint (e.g. Epic, User Story) as well as the associated tasks. The task board however can only display tasks located in the same project as the (parent) work package (Epic, User story). Therefore, to avoid showing limited data, tasks and their parent work packages must be located in the same project and have to be assigned to the same version.

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