Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0004299 | Openbravo ERP | B. User interface | public | 2008-07-03 11:22 | 2009-02-12 09:51 |
|
| Reporter | psarobe | |
| Assigned To | anthony_wolski | |
| Priority | urgent | Severity | critical | Reproducibility | sometimes |
| Status | closed | Resolution | unable to reproduce | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.40 | |
| Target Version | 2.40beta | 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 | 0004299: Grid lose the focus of the parent record when coming from the child record |
| Description | Grid lose the focus of the parent record when coming from the child record |
| Steps To Reproduce | 1. Go to Application dictionary-> Report and process
2. In grid mode, select one record between lines 105/110
3. Move to Process class, move to all the tabs and finally move the the parent
It can happen two things:
-When clicking to the parent you lost the focus of the parent record
-The parent focus is a different one
And after all if try to find the record that it was supposed to be you get this message. SEE ATTACH
|
| Proposed Solution | |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | | depends on | backport | 0004904 | | closed | iperdomo | Grid lose the focus of the parent record when coming from the child record | | has duplicate | defect | 0007246 | | closed | alostale | Sometimes, when navigating from a child to a parent tab, the grid shows as selected a different record |
|
| Attached Files |  ERROR.PNG (9,369) 2008-07-03 11:22
https://issues.openbravo.com/file_download.php?file_id=143&type=bug
|
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-07-03 11:22 | psarobe | New Issue | |
| 2008-07-03 11:22 | psarobe | Assigned To | => dbaz |
| 2008-07-03 11:22 | psarobe | sf_bug_id | 0 => 2009544 |
| 2008-07-03 11:22 | psarobe | File Added: ERROR.PNG | |
| 2008-07-04 08:58 | cromero | Status | new => scheduled |
| 2008-07-04 08:58 | cromero | fix_in_branch | => trunk |
| 2008-07-07 21:18 | dbaz | Note Added: 0008198 | |
| 2008-07-07 21:18 | dbaz | Assigned To | dbaz => alostale |
| 2008-12-10 09:58 | alostale | Assigned To | alostale => iperdomo |
| 2009-01-19 10:26 | rafaroda | version | => 2.40 |
| 2009-01-19 10:26 | rafaroda | fix_in_branch | trunk => |
| 2009-02-03 17:48 | iperdomo | Assigned To | iperdomo => anthony_wolski |
| 2009-02-04 13:17 | alostale | Relationship added | has duplicate 0007246 |
| 2009-02-04 13:36 | plujan | Note Added: 0013135 | |
| 2009-02-04 13:36 | plujan | Severity | minor => critical |
| 2009-02-05 06:09 | pjuvara | Note Added: 0013160 | |
| 2009-02-05 06:10 | pjuvara | Priority | normal => urgent |
| 2009-02-12 09:48 | pjuvara | Assigned To | anthony_wolski => iperdomo |
| 2009-02-12 09:49 | pjuvara | Assigned To | iperdomo => anthony_wolski |
| 2009-02-12 09:51 | pjuvara | Regression testing | => No |
| 2009-02-12 09:51 | pjuvara | Status | scheduled => closed |
| 2009-02-12 09:51 | pjuvara | Note Added: 0013384 | |
| 2009-02-12 09:51 | pjuvara | Resolution | open => unable to reproduce |
|
Notes |
|
|
(0008198)
|
|
dbaz
|
|
2008-07-07 21:18
|
|
It is not a problem with the "Keyboard Shortcuts" or "Improve UI Visibility"
It is a problem with the session variables management |
|
|
|
(0013135)
|
|
plujan
|
|
2009-02-04 13:36
|
|
|
Raised priority. If do not realize that parent is not the one you were working with, you may create inconsistent data. As example, you were working on a child tab, then return to header and then moving to a different child tab. If header changed during the process, you will enter data on a tab belonging wrong parent. |
|
|
|
|
|
plujan: please notice that you did not raise priority. You raised severity. Please do not mix the two. |
|
|
|
|
|
Closing as we are not able to reproduce. If you see this defect again, please reopen. |
|