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

General discussion
  1. OpenProject
  2. Forums
  3. General discussion
  4. Work Packages: How to order children packages?

Work Packages: How to order children packages?

Added by Ron Black about 6 years ago

A few days after adding an initial list of child workpackages to a given work package, any new child created is put at the TOP of the children list (see attached image).  How can new children be appended to the END of the list instead?

I've tried various sorting options without success.  It's very important that we use the tree-view of the work packages, so any sorting of the view unfortunately flattens it out.


Replies (5)

RE: Work Packages: How to order children packages? - Added by Ron Black about 6 years ago

Apparently this issue is discussed in Feature #27522, but it's incomplete.  I agree that sorting a package list then expecting the sort to remain when switching to hierarchy mode is selected would be confusing.  However, the ID's should be (at least) sorted NUMERICALLY in the tree view, NOT TEXTUALLY.  I'm simply suggesting sorting by PARENT ID, then child ID numerically instead of as strings.

RE: Work Packages: How to order children packages? - Added by Zack Glennie about 6 years ago

Are you still having this issue as of version 8.3.1? When I first read your description of the issue, I thought I understood it, but I tried to reproduce it, and I don't get any of the bad behaviors you're referring to.

RE: Work Packages: How to order children packages? - Added by Ron Black about 6 years ago

Yes, it's still happening in 8.3.1.  Simply create a couple of work packages, each with 3-4 children.  When you switch into hierarchy mode everything looks  fine.  However when unordered start dates are set for the children, the order in the hierarchy remains by ID, so the gantt chart looks like crap.  Worse, if the childrens' IDs cross a decade, e.g. 98, 99, 100, 101, then the order they display is 100, 101, 98, 99 because they're sorted as text, where 1 precedes 9.
All I want is to be able to sort within the hierarchy view.  We're looking at the source code now to implement it ourselves.

RE: Work Packages: How to order children packages? - Added by Zack Glennie about 6 years ago

Sorting within hierarchy view works fine for me. This was addressed in the 8.3 release.

bug ticket

PR addressing the issue

I was running 8.2 at first, and the lack of sorting under hierarchy mode was driving me nuts. Are you 100% sure you're running 8.3.1?
It took me a little while to find where OpenProject reports what version is running -- it's /admin/info.

RE: Work Packages: How to order children packages? - Added by Ron Black about 6 years ago

I was wrong.  Even though the OpenProject info showed 8.3.1, I think I may have switched to the wrong browser tab (test/dev/prod) running 8.2.  When I upgraded prod to 8.3.1 just now, I see the issue is gone.  Thanks!

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