View Issue Details

IDProjectCategoryView StatusLast Update
0016324mantisbtcustom fieldspublic2017-01-18 17:19
Reporterrafacamargo Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status confirmedResolutionopen 
Product Version1.2.15 
Target VersionFixed in Version 
Summary0016324: History record inconsistent
Description

The Issue history is being inconsistent when you create a custom field named "status"

Steps To Reproduce
  • Create a custom field named status and link it to a project and mark it to be shown on issue updating
  • change the issue status
  • edit the "status" custom field on the same issue and put a number (one like the statuses options preferably)
  • check the Issue history

The system is treating the status custom field in the same way as the Status field, formatting its values like statuses.

Additional Information

I checked the database and found out that in the mantis_bug_history_table the status changes are registered as "field_name" = "status", the same way as the custom field is registered.

I could not check it with other fields with the same name as system fields, but I guess the same thing should happen (or the validation made in this fields is not being made in the status field)

The best solution, IMHO, is to block the creation of a custom field named "status".

TagsNo tags attached.

Relationships

related to 0004409 acknowledged Support intelligent issue history 

Activities

atrol

atrol

2013-08-21 15:58

developer   ~0037909

The same applies to all field names which are hardcoded in function history_localize_item

Issue History

Date Modified Username Field Change
2013-08-21 15:38 rafacamargo New Issue
2013-08-21 15:58 atrol Note Added: 0037909
2013-08-21 15:58 atrol Status new => confirmed
2013-08-21 16:02 atrol Relationship added related to 0004409
2017-01-18 17:19 atrol Severity major => minor