Content
View differences
Updated by Niels Lindenthal over 2 years ago
**As** a user of OpenProject
**I want to** NOT be confused as to where I am in the navigation
**so that** I can work effectively
For non-technical users, the OpenProject navigation is very hard to understand. There are a few small tweaks that would go a long way:
1. Always keep the top-level menu showing (Overview, Work Packages, Boards, etc). The menu could collapse down to just the row of icons when a second-level menu is showing, but it just needs to be there the whole time. Many users find it hard to remember that they need to click the arrow to get back to the menu. This would also make it easier to navigate easily between different parts of a project.
2. Always show the top-level menu of a work packages project, even if a user clicked a work package name in an email, for example. GET RID of the work-around message that displays on a work package in this case "The work package is part of bla bla bla, click here to open the work package in that project". That message is very confusing for all users.
3. Rename the "Work Packages" menu to LISTS. There is a logical disconnect between the "Work Packages" name and the other view names... Boards, calendars, and team planners also contain Work packages.
<mention class="mention" data-id="32764" data-type="work_package" data-text="#32764">#32764</mention>
**I want to** NOT be confused as to where I am in the navigation
**so that** I can work effectively
For non-technical users, the OpenProject navigation is very hard to understand. There are a few small tweaks that would go a long way:
1. Always keep the top-level menu showing (Overview, Work Packages, Boards, etc). The menu could collapse down to just the row of icons when a second-level menu is showing, but it just needs to be there the whole time. Many users find it hard to remember that they need to click the arrow to get back to the menu. This would also make it easier to navigate easily between different parts of a project.
2. Always show the top-level menu of a work packages project, even if a user clicked a work package name in an email, for example. GET RID of the work-around message that displays on a work package in this case "The work package is part of bla bla bla, click here to open the work package in that project". That message is very confusing for all users.
3. Rename the "Work Packages" menu to LISTS. There is a logical disconnect between the "Work Packages" name and the other view names... Boards, calendars, and team planners also contain Work packages.
<mention class="mention" data-id="32764" data-type="work_package" data-text="#32764">#32764</mention>