View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004218 | mantisbt | relationships | public | 2004-07-29 09:03 | 2024-04-19 08:04 |
Reporter | DGtlRift | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | always |
Status | new | Resolution | open | ||
Product Version | 0.19.0a2 | ||||
Summary | 0004218: Issue found/fixed & version/build relationships with Changelog | ||||
Description | When we go to a new version, we split the code (let's say version 3.0 (patch 14) to 4.0 (patch 0)) so that we can start including new core features in the 4.0 version. The issue arrises when a few months later an issue is found in version 3.0p15, and testers have found that it goes back to before the code split so it is also in version 4.0p2. So it is possible to have the same bug in multiple versions, and fixed at diffrent patch levels for those versions. If version and fixed_in_version were dependancy keys on another table for a join, that could give the versions the issue was confirmed/fixed in for multiple major versions. In addition, the build (what we use to indicate patch-level) could also be used for this information if instead of being in the mantis_bug_table it This would also allow for (thanks to Wanderer for the suggestion) the possibility for multi-level ChangeLog where the ChangeLog could show: | ||||
Additional Information |
This could be the relationships between the tables. I think this would work, but I'm not sure how much code change would be involved. The foundORfixed entry would just be a boolean type to indicate if it was ... well, fixed or found. I didn't think it should be a key since I don't think it is possible to find and fix a bug in the same version (unless it is not a bug, or wont be fixed.) | ||||
Tags | No tags attached. | ||||
related to | 0003638 | closed | vboctor | the bugtracker should be able to produce a changelog |
related to | 0004841 | closed | atrol | We should be able to report the version,revision and build where the bug occured. |
related to | 0006593 | closed | grangeway | Allow a bug to be resolved for multiple versions |
child of | 0004181 | closed | Features in Mantis 1.1 release |
Ack... My relationship diagram fell apart in the additional comments... but I think you should be able to cut and paste it to view the fixed type font... OR are there tags to include into submission that would force text to be fixed type? This is related to issue 3638
Thnx thraxisp edited on: 07-29-04 11:47 |
|
(Note: Text fields do support the HTML {pre}{/pre} construct.) edited on: 07-29-04 10:11 |
|
Unassigned after having been assigned for multiple years without progress. |
|