Openbravo Issue Tracking System - Openbravo ERP | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0018982 | Openbravo ERP | B. User interface | public | 2011-11-05 17:12 | 2022-02-01 08:09 |
| Reporter | johnfandl | ||||
| Assigned To | Triage Platform Base | ||||
| Priority | normal | Severity | major | Reproducibility | have not tried |
| Status | new | Resolution | out of date | ||
| Platform | OS | 5 | OS Version | ||
| Product Version | |||||
| Target Version | Fixed in Version | ||||
| Merge Request Status | |||||
| Review Assigned To | |||||
| OBNetwork customer | No | ||||
| Web browser | |||||
| Modules | Core | ||||
| Support ticket | |||||
| Regression level | |||||
| Regression date | |||||
| Regression introduced in release | |||||
| Regression introduced by commit | |||||
| Triggers an Emergency Pack | No | ||||
| Summary | 0018982: Add "Saved Views" to High Level Menu & Workspace to make them more accessible | ||||
| Description | The saved views feature in MP4 is great to allow users to personalize their ERP; however, you can't quickly find and access your saved views (across functions) from the workspace. | ||||
| Steps To Reproduce | I have a set of saved views, but no way to easily access them. Since the views are buried inside the functions, I have to remember which view is associated with which function. | ||||
| Proposed Solution | At the very least, QuickLaunch should be made SavedView-aware, as follows: - the type-ahead logic should consider the views that I have access to - a view vs. a function should be differentiated in some way (and perhaps the view should be listed with the function to the right of it--since you can specify the same view name on different screens) it would also be nice to have a "Recent User Views" section. Perhaps integrate it into the current Recent Views section--so, if a recent view had a saved view, display the saved view (with the system menu option name in parenthesis or a flyby or something). Another idea (this one is a no-brainer) is to include named views in the Application (menu system). So, when I hover on Sales Order, it shows me the 5 saved views I have, with the default one first. This let's me immediately select the view directly, and not have to wait until the default view (which maybe I use only 50% of the time) processes. With large datasets, it can take a while, and that time eats at productivity. | ||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2011-11-05 17:12 | johnfandl | New Issue | |||
| 2011-11-05 17:12 | johnfandl | Assigned To | => dbaz | ||
| 2011-11-05 17:12 | johnfandl | Modules | => Core | ||
| 2011-11-05 20:29 | rgoris | Issue Monitored: rgoris | |||
| 2011-11-05 22:35 | dbaz | Assigned To | dbaz => mtaal | ||
| 2016-10-21 11:04 | mtaal | Status | new => closed | ||
| 2016-10-21 11:04 | mtaal | Resolution | open => out of date | ||
| 2016-10-21 13:17 | mtaal | Tag Attached: MT_closed_out_of_date | |||
| 2016-10-21 14:08 | mtaal | Assigned To | mtaal => platform | ||
| 2016-10-21 14:09 | mtaal | Status | closed => new | ||
| 2016-10-21 14:10 | mtaal | Tag Detached: MT_closed_out_of_date | |||
| 2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base | ||
| There are no notes attached to this issue. |