View Issue Details

IDProjectCategoryView StatusLast Update
0004409mantisbtbugtrackerpublic2013-08-21 16:02
Reportervboctor Assigned To 
Status acknowledgedResolutionopen 
Product Versiongit trunk 
Summary0004409: Support intelligent issue history

Currently the history is stored as strings. So for example, if you change the version field from X to Y, then X and Y are stored as strings. Renaming version X or Y will not reflect in the history.

Also if we format a history event in a specific way today, then we change the formatting in the next version, then the old entries will still have the same formatting.

In my opinion, history entries should be stored as logical entries that include the information about the change using change type, codes, ..etc. Then it is the task of the latest code to resolve the code to names, and to display it accordingly to the latest format.

TagsNo tags attached.


related to 0016324 confirmed History record inconsistent 
child of 0004181 closed Features in Mantis 1.1 release 




2004-08-29 15:47

reporter   ~0007285

I think the easiest way is to just store serialised values. We'll need to figure out what to do with existing entries though. Try to convert them, taking in account other languages if possible.

Issue History

Date Modified Username Field Change
2004-08-26 17:31 vboctor New Issue
2004-08-29 15:47 jlatour Note Added: 0007285
2004-08-29 15:47 jlatour Status new => acknowledged
2004-08-29 15:47 jlatour Relationship added child of 0004181
2013-08-21 16:02 atrol Relationship added related to 0016324