Openbravo Issue Tracking System - Openbravo ERP |
| View Issue Details |
|
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0000457 | Openbravo ERP | J. Demo data | public | 2008-05-27 18:40 | 2009-03-18 11:02 |
|
| Reporter | plujan | |
| Assigned To | pjuvara | |
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | no change required | |
| Platform | | OS | 5 | OS Version | |
| Product Version | 2.40alpha-r2 | |
| 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 | 0000457: Review focused fields at window load |
| Description | Since 2.40 it is possible to assign a field to get focus at window load. But is not clear at all why some fields were assigned. As example, on Business Partner window, focus is on Name field, but if I want to create a new Business Parnter, I need to go back to Search Key, since is the first mandatory.
Remember that most users always fill forms top to down and left to right (if they use a "left to right" language) |
| Steps To Reproduce | |
| Proposed Solution | Change current default settings so first mandatory field get focus on load. In case there are no mandatory, go to the first editable field. If no editable field, focus should remain on Tab. |
| Additional Information | |
| Tags | No tags attached. |
| Relationships | |
| Attached Files | |
|
| Issue History |
| Date Modified | Username | Field | Change |
| 2008-05-27 18:40 | plujan | New Issue | |
| 2008-05-27 18:40 | plujan | Assigned To | => cromero |
| 2008-05-27 18:41 | plujan | Assigned To | cromero => pjuvara |
| 2008-05-27 21:56 | pjuvara | Note Added: 0000366 | |
| 2008-05-27 21:56 | pjuvara | Status | new => feedback |
| 2008-05-27 22:43 | plujan | Note Added: 0000367 | |
| 2008-05-27 22:43 | plujan | Status | feedback => new |
| 2008-05-27 22:44 | plujan | Status | new => closed |
| 2008-05-27 22:44 | plujan | Note Added: 0000368 | |
| 2008-05-27 22:44 | plujan | Resolution | open => no change required |
| 2008-05-29 12:32 | psarobe | Note Added: 0000384 | |
| 2009-03-18 11:02 | anonymous | sf_bug_id | 0 => 2691316 |
|
Notes |
|
|
|
Is this a systematic problem or an isolated one? How many screens have the wrong initial focus?
The analysis you describe has already been done for 2.40 by PMA and reviewed by PSA so I would hope this applies only to a few screens and does not require a full rework.
In any case I would treat this as a bug since the intention in 2.40 is to have the most reasonable field as initial focus. |
|
|
|
(0000367)
|
|
plujan
|
|
2008-05-27 22:43
|
|
|
Ok, I will report a bug for Business Partner and an extra bug for any other window with the same behavoir. |
|
|
|
(0000368)
|
|
plujan
|
|
2008-05-27 22:44
|
|
|
individual bugs will be opened. |
|
|
|
|
The decision of not selecting the search key as first focus field is because although this field is mandatory not too many people fill it. If you keep it blank the application automatically fills it. If you see the online help says:
"A search key allows you a fast method of finding a particular record. If you leave the search key empty, the system automatically creates a numeric number. The document sequence used for this fallback number is defined in the "Maintain Sequence" window with the name "DocumentNo_TableName", where TableName is the actual name of the table (e.g. C_Order)."
It seems that in 2.3x or above doesn't work |
|