Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0045316Openbravo ERPA. Platformpublic2020-10-28 11:532022-01-27 20:09
Reporterleyre-iriarte 
Assigned Tomeriem_azaf 
PrioritynormalSeverityminorReproducibilityalways
StatusscheduledResolutionopen 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Statusopen
Review Assigned To
OBNetwork customerGold
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0045316: The preference header must display the property name instead of the preference code as it is now.
DescriptionIn the preference window (backend), when you click on a record, the header (name of the window) displays the attribute code and not the property name. Is the preference name the one thant should be shown. In case the is not a preference name, the attribute code should be chosen.

Steps To Reproduce1.Log-in in backend.
2.Open preference window
3.Click on a record, with preference name. The preference name is not shown in the name of the window, but the attribute is.
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
Attached Filespng Screenshot from 2020-10-28 11-52-56.png (133,757) 2020-10-28 11:53
https://issues.openbravo.com/file_download.php?file_id=15052&type=bug
png
Issue History
Date ModifiedUsernameFieldChange
2020-10-28 11:53leyre-iriarteNew Issue
2020-10-28 11:53leyre-iriarteAssigned To => Retail
2020-10-28 11:53leyre-iriarteFile Added: Screenshot from 2020-10-28 11-52-56.png
2020-10-28 11:53leyre-iriarteOBNetwork customer => Gold
2020-10-28 11:53leyre-iriarteResolution time => 1605049200
2020-10-28 11:53leyre-iriarteTriggers an Emergency Pack => No
2020-10-28 11:58leyre-iriarteSummaryPreference window name => The preference header must display the property name instead of the preference code as it is now.
2020-10-28 11:58leyre-iriarteDescription Updatedbug_revision_view_page.php?rev_id=21830#r21830
2020-11-04 06:54marvintmProjectRetail Modules => Openbravo ERP
2020-11-04 06:55marvintmModules => Core
2020-11-04 06:55marvintmAssigned ToRetail => platform
2020-11-04 06:55marvintmCategoryWeb POS => A. Platform
2020-11-04 07:05alostaleResolution time1605049200 =>
2020-11-04 07:05alostaleNote Added: 0124140
2020-11-04 07:05alostalePriorityhigh => normal
2020-11-04 07:05alostaleSeveritymajor => minor
2022-01-18 13:35AugustoMauchDescription Updatedbug_revision_view_page.php?rev_id=23533#r23533
2022-01-18 13:36AugustoMauchNote Added: 0134361
2022-01-27 17:24hgbotMerge Request Status => open
2022-01-27 17:24hgbotNote Added: 0134623
2022-01-27 20:09AugustoMauchAssigned Toplatform => meriem_azaf
2022-01-27 20:09AugustoMauchStatusnew => scheduled

Notes
(0124140)
alostale   
2020-11-04 07:05   
Downgrading severity from major to minor according to Bug Reporting Guidelines [1].

[1] http://wiki.openbravo.com/wiki/Bug_Reporting_Guidelines#How_to_Choose_the_Right_Severity [^]
(0134361)
AugustoMauch   
2022-01-18 13:36   
We will review how this could be fixed. But, even if it could be fixed we are not sure if we should do the change, because it would change the identifier of existing records, and that has several secondary effects, some of them potentially breaking
(0134623)
hgbot   
2022-01-27 17:24   
Merge Request created: https://gitlab.com/openbravo/product/openbravo/-/merge_requests/516 [^]