View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0011551 | mantisbt | roadmap | public | 2010-02-24 19:50 | 2024-04-20 19:27 |
Reporter | micahg | Assigned To | |||
Priority | normal | Severity | feature | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 1.2.0rc2 | ||||
Summary | 0011551: Fixed In Version should supercede the Target Version entry | ||||
Description | On the Roadmap page, if Fixed In Version is set, that should supercede the entry for Target Version as it's no longer part of the targeted release version, but the fixed version. | ||||
Tags | No tags attached. | ||||
IMO roadmap should not be changed for this.
|
|
Target Version is a forcast of the handling of that issue. |
|
not sure either that this logic should be stored in the roadmap. roadmap is what you planned to do, not what you did do. tell it what you plan to do using versions and targets. how about updating your target if your plans change? |
|
atrol's suggestions are fine. I now realize that the current way of doing this is proper, so we can either convert this bug to an enhancement to offer people to change milestones or just close this. |
|
When closing or resolving an issue, we can set fixed_in_version, but not target_version. Allowing us to set target_version to blank can solve this issue... |
|
Take a look at pull request https://github.com/mantisbt/mantisbt/pull/40 It adds the config option to automatically suggest the 'fixed in version' with the 'target version' upon resolving a bug. |
|