Content
What is the procedure to add a task/milestone at the correct position in the work packages list?
Added by M S over 1 year ago
Hi all,
I just installed OpenProject on my server and playing around with it now to see how I like it and if I could use it for work.
Overall, I like it a lot. But I'm running into the following issue:
After adding a couple of tasks, I added two milestones called "Project Start" and "Orientation Phase Completed". These milestones should not be at the bottom of the list. But in the correct places. So the "Project Start" should be at the top. And "Orientation Phase Completed" should be right after the Orientation Phase. But because the list is sorted by ID, and that ID cannot be changed, it looks like this now:
When I simply drag the milestones to the correct positions, It creates a new (private) view and stays the same in the main view. What is the correct procedure to add tasks or milestones in a different place than at the bottom of the list? For example, I have completed a project plan. And then I remember I forgot to add some tasks or milestones. How would I add those in the correct places without deleting everything and starting over?
For example, in MS Project, I can just move all tasks wherever I want in the list. How can this be achieved in OpenProject?
Thanks in advance! I'll keep playing around with it.
Replies (4)
I think I figured it out. In the "Sort By" section, there is an option to disable automatic sorting and set it to manual. Then you can reorder the tasks without problem.EDIT: No, I was wrong. It still creates a new view as soon as I set the sorting to manual. So not solved yet.
I guess, what you are trying to do is to create a custom "default" view for your project. Every view has its own sorting, be it by ID, some other columns or manual. So this is regular behavior.
If you have a specific requirement on where your milestones or other work packages are located, you should consider sorting the work packages to your liking (effectively creating manual order) and save this as a new view. To give you an example: I usually create the "project plan" view for all of my project. This view only contains phases, WPs and milestones. This view is always sorted manually so that I have full control over how my project plan actually looks.
Thanks Jan,
I guess that is the way to go. So just creating a new view immediately and ignoring the default views.
I guess it would also be a nice feature to be able to hide the default views, to prevent accidentally working there instead of in the custom "Project Plan" view.
I have thought about that as well. In practice, I would think that this may be less relevant though. If you manage your projects, you would usually have different requirements for information. For example:
Because of that, you would always create specific views anyway and the whole project team would usually have their way on how to deal with these views.
Takeaway is: I do not disagree with you. Looking at daily practice, you might find that you end up with custom views anyway and ignore other views automatically. The gap from ignoring standard view to hiding them seems minimal.