Openbravo Issue Tracking System - POS2 | |||||
View Issue Details | |||||
ID | Project | Category | View Status | Date Submitted | Last Update |
0051326 | POS2 | Core | public | 2023-01-11 10:21 | 2023-01-13 00:49 |
Reporter | caristu | ||||
Assigned To | gdagnesses | ||||
Priority | high | Severity | major | Reproducibility | have not tried |
Status | scheduled | Resolution | open | ||
Platform | OS | 5 | OS Version | ||
Product Version | |||||
Target Version | Fixed in Version | ||||
Merge Request Status | |||||
Review Assigned To | |||||
OBNetwork customer | |||||
Support ticket | |||||
Regression level | |||||
Regression date | |||||
Regression introduced in release | |||||
Regression introduced by commit | |||||
Triggers an Emergency Pack | No | ||||
Summary | 0051326: Inherited records in User Action Access subtab must be read only | ||||
Description | The fields of the inherited recods in the User Action Access subtab of the Role window must be all read only. Note that this is the behavior of the rest of inherited records in the other subtabs of this window. | ||||
Steps To Reproduce | 1) Login in an environment with core2 module installed 2) Go to the [Role] window 3) Create a new role marked as template 4) Add two different permissions for the new template role 4.1) Create a new record in the Org Access window 4.2) Crate a new record in the User Action Access window 5) Create a new role to inherit the permissions of the newly created template role 5.1) Define this new role as manual and as not template 5.2) Go to the Role Inheritance subtab and create a new record selecting the template role in the "inherit from" field 6) Once the role is created check the following: 6.1) The inherited record in the Org Access subtab is shown as read-only --> Correct 6.2) The inherited record in the User Action Access subtab is NOT shown as read-only --> Incorrect | ||||
Proposed Solution | |||||
Additional Information | |||||
Tags | No tags attached. | ||||
Relationships | |||||
Attached Files | ro.png (22,741) 2023-01-11 11:03 https://issues.openbravo.com/file_download.php?file_id=18009&type=bug non-ro.png (29,220) 2023-01-11 11:03 https://issues.openbravo.com/file_download.php?file_id=18010&type=bug | ||||
Issue History | |||||
Date Modified | Username | Field | Change | ||
2023-01-11 10:21 | caristu | New Issue | |||
2023-01-11 10:21 | caristu | Assigned To | => Triage Platform Base | ||
2023-01-11 10:21 | caristu | Triggers an Emergency Pack | => No | ||
2023-01-11 10:23 | caristu | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=25367#r25367 | ||
2023-01-11 10:23 | caristu | Steps to Reproduce Updated | bug_revision_view_page.php?rev_id=25368#r25368 | ||
2023-01-11 11:01 | caristu | Summary | Fields of User Action Access inherited records must be read only => Inherited records in User Action Access subtab must be read only | ||
2023-01-11 11:01 | caristu | Description Updated | bug_revision_view_page.php?rev_id=25370#r25370 | ||
2023-01-11 11:03 | caristu | File Added: ro.png | |||
2023-01-11 11:03 | caristu | File Added: non-ro.png | |||
2023-01-12 21:59 | hgbot | Note Added: 0145363 | |||
2023-01-13 00:49 | AugustoMauch | Assigned To | Triage Platform Base => gdagnesses | ||
2023-01-13 00:49 | AugustoMauch | Status | new => scheduled |
Notes | |||||
|
|||||
|
|