Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0008813 | Openbravo ERP | B. User interface | public | 2009-04-28 17:28 | 2022-02-01 08:08 |
|
| Reporter | plujan | |
| Assigned To | Triage Platform Base | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| 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 | |
| Web browser | |
| Modules | Core |
| Support ticket | |
| Regression level | |
| Regression date | |
| Regression introduced in release | |
| Regression introduced by commit | |
| Triggers an Emergency Pack | No |
|
| Summary | 0008813: Management Module Console layout is not consistent regarding packages |
| Description | I've installed a package. The package installs as a monolithic object, for example, I can not uninstall a single module of the package. So I cannot select it neither. All this seems to be consistent.
But I have links to rebuild on each one, what means that they are separate objects.
User interface should state clearly whether the ERP considers packages as a single entity or not.
"Can I install/rebuild/uninstall/update "portions" of a package?" should have a single unique answer.
See attach. |
| Steps To Reproduce | |
| Proposed Solution | |
| Additional Information | |
| Tags | OB3-Reviewed |
| Relationships | |
| Attached Files |  BUG_250PI_ManagementModuleConsole.PNG (57,627) 2009-04-28 17:28
https://issues.openbravo.com/file_download.php?file_id=1236&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2009-04-28 17:28 | plujan | New Issue | |
| 2009-04-28 17:28 | plujan | Assigned To | => rgoris |
| 2009-04-28 17:28 | plujan | File Added: BUG_250PI_ManagementModuleConsole.PNG | |
| 2009-04-28 17:28 | plujan | Regression testing | => No |
| 2009-04-28 18:41 | rgoris | Note Added: 0015878 | |
| 2009-04-28 18:42 | rgoris | Status | new => scheduled |
| 2009-04-28 18:42 | rgoris | fix_in_branch | => pi |
| 2009-04-28 20:57 | plujan | Note Added: 0015887 | |
| 2009-04-28 21:30 | rgoris | Note Added: 0015888 | |
| 2011-10-28 13:13 | psarobe | Assigned To | rgoris => alostale |
| 2011-10-28 13:13 | psarobe | fix_in_branch | pi => |
| 2011-10-28 13:13 | psarobe | Tag Attached: OB3-Reviewed | |
| 2011-11-16 14:45 | alostale | Type | defect => design defect |
| 2017-03-31 14:36 | alostale | Status | scheduled => acknowledged |
| 2017-04-10 14:35 | alostale | Assigned To | alostale => platform |
| 2022-02-01 08:08 | alostale | Assigned To | platform => Triage Platform Base |
|
Notes |
|
|
(0015878)
|
|
rgoris
|
|
2009-04-28 18:41
|
|
Agree. The way it was designed is that the link "Changes pending, rebuild now" or whatever action there is, is only available on package level.
My suggestion is to remove all individual action links on module level. |
|
|
|
(0015887)
|
|
plujan
|
|
2009-04-28 20:57
|
|
|
Please note that a single module (i.e. not included in any package) can be installed as well. In the attached image you can see a Skin Module at the bottom. So, as a rule of thumb, I would say that if has a checkbox to select it, should have a link to rebuild it. |
|
|
|
(0015888)
|
|
rgoris
|
|
2009-04-28 21:30
|
|
|