View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0006051 | mantisbt | reports | public | 2005-07-30 17:13 | 2014-10-24 06:47 |
| Reporter | steffi | Assigned To | grangeway | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Platform | AMD | OS | Windows XP | OS Version | SP2 |
| Product Version | 1.0.0rc1 | ||||
| Summary | 0006051: Possibility of snapshots and specific time priods for bug summaries | ||||
| Description | During the usage of mantis, my manager requested a lot of different analyses of the bug situation. It becomes more and more important to show the change of new and resolved bug during a specific time period. e.g.
Example for snapshots
Those statistics should be diplayed in graphs, too. | ||||
| Tags | No tags attached. | ||||
|
Unlikely we'd add some snapshot functionality to core: since original report, we've added 'revisions' functionality to store revisions of summary/description, and also increased what gets logged under bug history i believe. Whilst it would be feasible to useful to submit places where bug history could be improved. So it would be a case of either: a) making an analytical plugin that stores snapshots of status at which point, it woudl be useful to have individual specific examples of what would be required as new work items. |
|