0011551: Fixed In Version should supercede the Target Version entry - MantisBT - Signup temporarily disabled due to spam

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.

atrol 2010-09-07 16:31 developer ~0026612	IMO roadmap should not be changed for this. Another idea: If someone sets "Fixed in Version" different from "Target Version" there could be a dialog to ask user whether he wants to update also "Target Version" or to take the "Target Version" instead of his selection, because he was wrong, or just set "Fixed in Version" to his desired value

Phileas 2010-09-08 02:23 reporter ~0026618	Target Version is a forcast of the handling of that issue. If an Issue is resolved, he becomes a real "fixed in version" by a vcs. In that case the "target version" becomes obsolete and is for history. So Roadmap should deal with "target version" and "changelog" should show "fixed in version".

yw84ever 2010-09-09 06:12 reporter ~0026641	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?

micahg 2010-09-12 07:10 reporter ~0026679	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.

Dentxinho 2011-09-21 14:11 reporter ~0029828	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...

vincent_sels 2012-02-01 14:50 reporter ~0031099	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.