View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0017484mantisbtcustom fieldspublic2014-07-03 14:082015-01-02 13:13
Reporterralph.rassweiler Assigned Todregad  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSUbuntuOS Version12.04
Product Version1.2.17 
Summary0017484: Custom field name not shown
Description

I created a custom field called "modulo" type enumeration.

Then i configure Mantis to show this field on "view issues" and on all the reports.

On the "view issues" the custom field label and values are shown as "@modulo@" but when i click on "print reports" and then export to word or browser, the values are correctly there.

When i export to XLS or CSV the same problem occurs: "@modulo@" instead of the values.

I already try to add the custom field on "custom_strings_inc.php" but there is no difference.

Steps To Reproduce
  1. Create a custom field type enumeration
  2. Connect the field to a project
  3. Define some bugs with the field
  4. Configure view issues to show the custom field
  5. Access view issues
Additional Information

Enumeration values: |Comissões|Compra|Configuração|Contabilidade|Estoque|Faturamento|Financeiro|Pessoa|Sistema|Venda|Segurança|Serviço

TagsNo tags attached.
Attached Files
view_issues.png (23,474 bytes)   
view_issues.png (23,474 bytes)   
exported_issue.png (31,016 bytes)   
exported_issue.png (31,016 bytes)   
exported_excel_issue.png (15,211 bytes)   
exported_excel_issue.png (15,211 bytes)   

Activities

dregad

dregad

2014-07-04 11:10

developer   ~0040875

Don't have time to test atm. Did you read the manual [1] ? Does the issue also occur if you switch to English ?

[1] https://www.mantisbt.org/docs/master-1.2.x/en/administration_guide/admin.customize.html#ADMIN.CUSTOMIZE.CUSTOMFIELDS.LOCALIZE
ralph.rassweiler

ralph.rassweiler

2014-07-04 14:43

reporter   ~0040877

Yes, i read the manual. Yes, i add the code on custom_strings_inc.php. And yes, the problem still continues if i switch to english.
ralph.rassweiler

ralph.rassweiler

2014-12-11 07:55

reporter   ~0041999

The problem was the capital "M" on the custom field name. Change it to lowercase solved the issue.
dregad

dregad

2014-12-11 11:13

developer   ~0042000

Many thanks for your feedback. Glad to hear you found a solution to your problem.