View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0006581||mantisbt||feature||public||2006-01-11 20:13||2018-11-23 03:05|
|Target Version||Fixed in Version|
|Summary||0006581: Summary vs. Change Log entry|
When using the change log feature of mantis, I have the need to revise the bug summary quite often when I resolved the issue so the entry in the change log is very expressive for the users reading the change log. Probably this should be a completely different field based on the content of the summary because a descriptive issue summary would be something like "notification doesn't work", while the change log entry could be something like "Notification fixed for users using Firefox" for example.
|Tags||No tags attached.|
This is only about 12 years late but I'll add a +1 here.
Just look at the summary for this ticket: "Summary vs. Change Log entry". That's hardly a good changelog description if this ticket is processed, where the resolution would be more like "Added Management option to allow selection of any field (including User-Defined) for the Changelog description."
You could create a custom field of type