Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0004998Openbravo ERP00. Application dictionarypublic2008-09-10 09:592009-02-10 17:35
Reporterpsarobe 
Assigned Togorka_gil 
PriorityhighSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version2.40beta 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0004998: don't fire the call-out when clicking new in a tab
DescriptionWhen clicking new in a window and if exists a field that is filled with a default value the call-out for that field does not fire unless you change the value
Steps To Reproduce# Go to Production management->Transactions->Work Effort->Work effort
# Click New and fill:

    * Movement date= Current date
    * Starting Time: 08:00:00, Ending time: 16:00:00

# Move to Production Run tab and click new
# Select the "WR Phase" and verify:

    * The fields "Required quantity", "cost center", "Process unit" and "Conversion Rate" are filled based on the WR phase

Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
blocks defect 0004277 closed gorka_gil don't fire the call-out when clicking new in a tab 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2008-09-10 09:59cromeroNew Issue
2008-09-10 09:59cromeroAssigned To => gorka_gil
2008-09-10 09:59cromeroStatusnew => scheduled
2008-09-15 17:32gorka_gilRegression testing => No
2008-09-15 17:32gorka_gilStatusscheduled => closed
2008-09-15 17:32gorka_gilNote Added: 0009021
2009-02-10 17:35jpabloaeResolutionopen => fixed
2009-02-10 17:35jpabloaefix_in_branch2.40-installer =>
2009-02-10 17:35jpabloaeProposed Solution updated

Notes
(0009021)
gorka_gil   
2008-09-15 17:32   
The fix affects all callouts of readonly fields and it's risky to commit in 2.40 installer. It will be fixed in maintenance packs of 2.40