Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0003356Openbravo ERPB. User interfacepublic2007-07-02 12:162013-12-02 17:42
Reporterplujan 
Assigned Torgoris 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Review Assigned Toplujan
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0003356: GUI issue on Business Partners addresses
DescriptionDescription:
When creating a new address of a business partner, the Location / Address field looks like a non-editable field.

Enviroment:
OS: Windows XP SP2
DB: Oracle XE
Browser: FF2
Openbravo: 2.31 Beta
Language: English

Steps:
1. Go Master Data Management > Business Partner
2. Select a valid Business Partner
3. Move to Address/Location tab
4. The Location/Address field is non-editable, but it is possible to change it by selecting the Location button. It is an UI issue.
Steps To Reproduce
Proposed Solution
Additional Information
TagsClean-up, ReleaseCandidate
Relationships
has duplicate defect 0007445 closed rafaroda Field Location/Address background color wrongly in gray in page Warehouse Management || Setup || Warehouse and Storage Bins 
blocks feature request 0006443 closed rgoris Search and Filter - umbrella 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-07-01 19:47pjuvaraStatusnew => acknowledged
2008-07-01 19:47pjuvaraTag Attached: ReleaseCandidate
2008-11-16 07:44pjuvaraAssigned Todbaz => pjuvara
2008-11-16 08:21pjuvaraTag Attached: Clean-up
2008-12-10 10:53pjuvaraAssigned Topjuvara => rgoris
2008-12-10 15:31rgorisRelationship addedblocks 0006443
2009-02-17 17:54rafarodaRelationship addedhas duplicate 0007445
2013-01-10 15:25rgorisAssigned Torgoris => plujan
2013-01-16 11:51plujanAssigned Toplujan => rgoris
2013-12-02 17:41rgorisStatusacknowledged => scheduled
2013-12-02 17:41rgorisfix_in_branch => pi
2013-12-02 17:42rgorisStatusscheduled => resolved
2013-12-02 17:42rgorisFixed in SCM revision => na
2013-12-02 17:42rgorisResolutionopen => fixed
2013-12-02 17:42rgorisReview Assigned To => plujan
2013-12-02 17:42rgorisStatusresolved => closed

Notes
(0006945)
user71   
2005-06-01 00:00   
(edited on: 2008-06-12 09:44)
This bug was originally reported in SourceForge bug tracker and then migrated to Mantis.

You can see the original bug report in:
https://sourceforge.net/support/tracker.php?aid=1746385 [^]
(0003887)
psarobe   
2007-07-03 21:08   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500703
Originator: NO

This is not a bug.

Explanation:
This is the behaviour for this kind of field. This field shows you a collection of data from another table (first line, second line, region, zip). So is not possible to edit all this staff directly from the field. You have to click on the button and then edit all what you want. To understand it, figure out that this fields only shows you some information
(0003888)
plujan   
2007-08-09 13:54   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1759992
Originator: YES

Please take it as a user interface problem and find a way to solve it. I understand that DB design is a limiter, but a bad design should not be an excuse for a inconsistent UI.
(0003889)
dbaz   
2008-04-23 18:45   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500873
Originator: NO

The way of the field behaviour is defined in the database. If this field should be in any other way should be a DB/WAD correction.
(0003890)
cromero   
2008-04-23 19:06   
(edited on: 2008-06-12 09:26)
Logged In: YES
user_id=1500614
Originator: NO

This control needs a review in order to look for a right solution for this type of field and even for the attribute selector.
Now, as they are show as readonly, you can not distinguish when the field is mandatory.
One possibility could be show the field as updatable but not enable to write in: when you try to write in, the selector is opened.
Need to be discussed.
Carlos