View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006209 | mantisbt | change log | public | 2005-08-31 10:48 | 2012-12-08 15:45 |
| Reporter | nuclearspike | Assigned To | dregad | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | duplicate | ||
| Summary | 0006209: Show "feature" issues differently - highlight? | ||||
| Description | Some changelogs (in other products) will have a '+' for a new feature, '-' for a bug that was removed, and 'o' to show that an existing feature was updated. Frequently, we are asked by customers "what's changed since version x" and they are asking for new features added. Currently there is no way to distinguish a feature from a bug in the listing. Either by using the +/-/o method, or by highlighting features in a yellow bar to make them stand out would be very helpful. It would also be good just to get a feel for the release without having to read through them all. Was it mostly bug fixes or were a lot of new features added? The background color could be a config setting for each severity type so that no code is relying on "feature" to be there, or for the underlying "feature" code to have the same meaning in all implementations. We also do client mods which have their own "severity" entry, by making it configurable, we could set the color for "mod" to be a light green (money). | ||||
| Tags | No tags attached. | ||||
| duplicate of | 0007271 | new | Solution to classify in 3 groups change logs |