View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0009095 | mantisbt | feature | public | 2008-04-21 15:12 | 2009-05-15 00:23 |
Reporter | joshr | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Product Version | 1.1.1 | ||||
Summary | 0009095: Standardize use of Version and Build fields | ||||
Description | This is a feature request regarding adding a "Build" field, currently only found as the "Project Build" field when reporting an issue, to all places requesting a "Version" number. I realize this issue already exists, but none of the found ones request the field in all cases, or quite like this issue. I believe this field should be standardized across all locations. Any time you place a "Version" field of any type, it should have an accompianing "Build" field. In other words, "Product Version" has "Product Build" (as it currently does). "Fixed in Version" has "Fixed in Build". "Target Version" has "Target Build". etc. I believe this will fix both the issues I'm personally having as well as prevent future "Please add a build field" mantis issues from appearing if a "Version" field is added to a new page. Reasoning: The Build number is part of our version numbers: Major.Minor.Build. These numbers change every time we do a build (logically). Additionally, we track what items are fixed in each build. I'm running into issues where we have hundreds of version numbers for software (because of the build numbers) that's been tracked in our installation of Mantis for years. This makes the version list quite large. Finally, I believe the Build number should be tracked as part of the Change Log (Fixed in Build), and possibly the Road Map (Target Build). | ||||
Additional Information | Finally, I want to say this is an excellent piece of software we've been using for years. We just recently upgraded to 1.1.1 from 1.0.5. Marvelous work, everyone. | ||||
Tags | No tags attached. | ||||