Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0029050 | Openbravo ERP | B. User interface | public | 2015-02-24 16:52 | 2022-02-01 08:05 |
|
| Reporter | plujan | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | acknowledged | Resolution | open | |
| Platform | | OS | 5 | OS Version | |
| Product Version | pi | |
| 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 | 0029050: Behaviour of selector and parameter window modal popups is not homogeneous |
| Description | When a modal Parameter Window is open, the modal popup covers the tab Area, but not the top area, allowing to move to another window, open a new one, logging out, etc.
But when a modal Selector popup is open the whole window is greyed out, so it is not possible to do the things mentioned above.
Both modal windows should behave in the same way. |
| Steps To Reproduce | 1. Login as Openbravo user
2. Open Financial Account window
3. Select Cuenta de Banco and move to Transaction tab
4. Create a new record and select BP Withdrawal as Type
5. Click the plus icon on the Payment field to open the Add Payment selector
**First issue: Note that the greyed area does not cover the whole screen (see FIN_AddPaymentErrorMessage.png screenshot)
1. As Openbravo user, open Sales Invoice window
2. Create a new record
3. Click the Business Partner icon to open the selector
4. Check the greyed area behind the selector (see ModalSelector.png screenshot)
|
| Proposed Solution | From an end user point of view, the different behaviour between standard Selector windows and OB_Parameter windows is perceived as a GUI issue.
The solution should be to unify the behaviour. Either the standard selectors should not cover the whole screen, allowing user actions on the top navigation bar or OB Parameter window should block the whole screen. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | related to | defect | 0029048 | | closed | Sandrahuguet | It is possible to interact with background objects when Add Payment pop up is open | | related to | defect | 0029049 | | acknowledged | Triage Platform Base | It is possible to trigger an autosave in the background tab objects when Add Payment modal pop up is open |
|
| Attached Files |  FIN_AddPaymentErrorMessage.png (81,195) 2015-02-24 16:52
https://issues.openbravo.com/file_download.php?file_id=7825&type=bug
ModalSelector.png (79,787) 2015-02-26 10:01
https://issues.openbravo.com/file_download.php?file_id=7832&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2015-02-24 16:52 | plujan | New Issue | |
| 2015-02-24 16:52 | plujan | Assigned To | => dbaz |
| 2015-02-24 16:52 | plujan | OBNetwork customer | => No |
| 2015-02-24 16:52 | plujan | Modules | => Core |
| 2015-02-24 16:52 | plujan | Triggers an Emergency Pack | => No |
| 2015-02-24 16:52 | plujan | Issue generated from | 0029048 |
| 2015-02-24 16:52 | plujan | Relationship added | related to 0029048 |
| 2015-02-24 16:52 | plujan | File Added: FIN_AddPaymentErrorMessage.png | |
| 2015-02-24 19:17 | dbaz | Note Added: 0074882 | |
| 2015-02-25 10:03 | AugustoMauch | Relationship added | related to 0029049 |
| 2015-02-25 10:13 | AugustoMauch | Note Added: 0074901 | |
| 2015-02-25 10:13 | AugustoMauch | Assigned To | dbaz => plujan |
| 2015-02-25 10:13 | AugustoMauch | Status | new => feedback |
| 2015-02-25 11:06 | plujan | Assigned To | plujan => dbaz |
| 2015-02-25 12:18 | plujan | Status | feedback => scheduled |
| 2015-02-25 12:18 | plujan | Note Added: 0074905 | |
| 2015-02-25 12:18 | plujan | fix_in_branch | => pi |
| 2015-02-26 09:52 | AugustoMauch | Type | design defect => defect |
| 2015-02-26 09:52 | AugustoMauch | fix_in_branch | pi => |
| 2015-02-26 10:01 | AugustoMauch | File Added: ModalSelector.png | |
| 2015-02-26 10:10 | AugustoMauch | Summary | It is possible to interact with background objects when Add Payment pop up is open => Behaviour of selector and parameter window modal popups is not homogeneous |
| 2015-02-26 10:10 | AugustoMauch | Description Updated | bug_revision_view_page.php?rev_id=7768#r7768 |
| 2015-02-26 10:10 | AugustoMauch | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=7770#r7770 |
| 2015-03-06 10:25 | alostale | Status | scheduled => acknowledged |
| 2015-03-17 14:38 | alostale | Assigned To | dbaz => platform |
| 2022-02-01 08:05 | alostale | Assigned To | platform => Triage Platform Base |
|
Notes |
|
|
(0074882)
|
|
dbaz
|
|
2015-02-24 19:17
|
|
The proper behavior is allow the user switch between tabs even if a modal (related to the window) is opened. So the selector should be changed.
An exception of this behavior is for example the "log out" modal popup, which should freeze the whole application (it is an event that affects the whole application and not a particular window) |
|
|
|
|
|
What are the incorrect functional flows that are allowed because of this? |
|
|
|
(0074905)
|
|
plujan
|
|
2015-02-25 12:18
|
|
The mention of "wrong functional flows" refers to the fact (originally reported in the issue but clarified by previous comments) that the behaviour was different between selectors and ob parameter windows.
Since selectors exist in the application for years and ob parameter windows are kind of a recent feature, I assumed you should not be able to logout or open any other window while the pop up was opened. That are the functional flows that were stated as not correct.
As dbaz said, the issue should say now something like "in Business Partner selector you are not allowed to do some functional flows" since the intended behaviour is the one shown by ob parameter windows. |
|