View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004409||mantisbt||bugtracker||public||2004-08-26 17:31||2013-08-21 16:02|
|Product Version||git trunk|
|Summary||0004409: 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.
|Tags||No tags attached.|