View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0004842mantisbtfeaturepublic2004-11-09 22:042005-04-18 10:29
Reporterpracette Assigned Tovboctor  
PrioritynormalSeveritytweakReproducibilityalways
Status closedResolutionfixed 
Fixed in Version1.0.0a1 
Summary0004842: we should be able to giva a target for a given bug.
Description

This way we can do a better organizing of bug assignation...
So we can delay a bug witch is next version and get right to the next revision one.

TagsNo tags attached.

Relationships

related to 0005180 closedvboctor Support custom fields with dynamic possible values 
has duplicate 0004518 closedvboctor It would be nice to know in which version the feature is going to be implemented if it is acknowledged 

Activities

vboctor

vboctor

2004-11-10 05:25

manager   ~0008319

At the moment, people do this using custom fields. You can create an enumeration custom field and populate it with the list of planned releases. Then you can assigned target releases to issues.
thraxisp

thraxisp

2004-11-22 19:24

reporter   ~0008404

We have also accomplished the same thing without custom fields by setting the fixed in version before the issue is resolved. This sets a target to fix in.
vboctor

vboctor

2005-01-29 09:06

manager   ~0009146

This was implemented as part of 0005180. The possible values for the custom field should be set to "=future_versions". This will show only the versions that are not yet released. You can also use "=versions" and "=released_versions" as needed.