Project:
View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||||
ID | |||||||||||
0030067 | |||||||||||
Type | Category | Severity | Reproducibility | Date Submitted | Last Update | ||||||
defect | [Openbravo ERP] A. Platform | minor | sometimes | 2015-06-01 17:00 | 2022-02-01 08:05 | ||||||
Reporter | egoitz | View Status | public | ||||||||
Assigned To | Triage Platform Base | ||||||||||
Priority | normal | Resolution | open | Fixed in Version | |||||||
Status | acknowledged | Fix in branch | Fixed in SCM revision | ||||||||
Projection | none | ETA | none | Target Version | |||||||
OS | Any | Database | Any | Java version | |||||||
OS Version | Database version | Ant version | |||||||||
Product Version | SCM revision | ||||||||||
Review Assigned To | |||||||||||
Web browser | |||||||||||
Modules | Core | ||||||||||
Regression level | |||||||||||
Regression date | |||||||||||
Regression introduced in release | |||||||||||
Regression introduced by commit | |||||||||||
Triggers an Emergency Pack | No | ||||||||||
Summary | 0030067: Changing the order of the menu entries using tree view sometimes fails | ||||||||||
Description | When changing the order of the menu entries using the menu view sometimes the entries are properly moved but other times after refresh the item is on the same position that it was before | ||||||||||
Steps To Reproduce | -Create a template and define it as indevelopment -Go to the menu window -click on the toolbar icon to move to tree view -MOve the product,partner, and sales order entries out of the folder to be on the root node. -Then make different movement using the tree view and see that sometimes it does not work | ||||||||||
Tags | No tags attached. | ||||||||||
Attached Files | |||||||||||
Relationships [ Relation Graph ] [ Dependency Graph ] | ||||||||
|
Notes | |
(0078314) caristu (developer) 2015-06-16 13:21 |
This problem is only reproducible for the Menu tree. There exists a logic which avoids the increasing of the sequence number for the menu entries that belong to a module not in "in development". This causes that some nodes can have a duplicated sequence number after moving them, which is the cause why those nodes can't be sorted when moving them again. |
Issue History | |||
Date Modified | Username | Field | Change |
2015-06-01 17:00 | egoitz | New Issue | |
2015-06-01 17:00 | egoitz | Assigned To | => platform |
2015-06-01 17:00 | egoitz | Modules | => Core |
2015-06-01 17:00 | egoitz | Triggers an Emergency Pack | => No |
2015-06-05 08:53 | alostale | Relationship added | related to 0029562 |
2015-06-05 08:54 | alostale | Status | new => acknowledged |
2015-06-16 13:21 | caristu | Note Added: 0078314 | |
2015-11-11 11:37 | alostale | Priority | high => normal |
2017-10-16 19:58 | ahernandezgil | Issue Monitored: ahernandezgil | |
2022-02-01 08:05 | alostale | Assigned To | platform => Triage Platform Base |
Copyright © 2000 - 2009 MantisBT Group |