0014772: Excel export with custom fields are all letters converted to lower case - MantisBT

ID	Project	Category	View Status	Date Submitted	Last Update

0014772	mantisbt	custom fields	public	2012-10-04 03:22	2014-09-23 18:05

Reporter	wniva	Assigned To	dregad
Priority	normal	Severity	text	Reproducibility	have not tried
Status	closed	Resolution	fixed
Product Version	1.2.11
Target Version	1.2.12	Fixed in Version	1.2.12

Summary	0014772: Excel export with custom fields are all letters converted to lower case
Description	I have custom fields (eg "Next Step") and this field is configured for the Excel export. In the export file are all headers of my custom fields converted to lowercase ("Next Step" -> "next step"). This looks not so very good, if you send this to external persons.
Additional Information	When the custom fields configured for "View Issues Columns" then this works correctly !
Tags	No tags attached.

MantisBT: master-1.2.x 2c6a8a4a 2012-10-03 22:47 dregad Details Diff	Custom fields names in Excel export were converted to lower case This was not happening in other export functions; the root cause was inconsistent code to output the column headers in the excel API. Function excel_get_titles_row() now relies on column_get_title() to retrieve the custom fields default name, same as standard columns, and in line with CSV export. Fixes 0014772	Affected Issues 0014772
	mod - core/excel_api.php	Diff File
MantisBT: master abd079bc 2012-10-03 22:47 dregad Details Diff	Custom fields names in Excel export were converted to lower case This was not happening in other export functions; the root cause was inconsistent code to output the column headers in the excel API. Function excel_get_titles_row() now relies on column_get_title() to retrieve the custom fields default name, same as standard columns, and in line with CSV export. Fixes 0014772	Affected Issues 0014772
	mod - core/excel_api.php	Diff File

dregad 2012-10-04 05:04 developer ~0033031	I can reproduce this on latest trunk.

grangeway 2013-04-05 17:56 reporter ~0036200	Marking as 'acknowledged' not resolved/closed to track that change gets ported to master-2.0.x branch