View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004285||mantisbt||feature||public||2004-08-06 09:33||2005-01-15 10:20|
|Target Version||Fixed in Version|
|Summary||0004285: the ability to define a roadmap for a product and version it.|
the ability to define a roadmap for a product and version it.
|Tags||No tags attached.|
You can currently create one 'master issue' for a version, and have all the bugs that need to be fixed for that version and features that need to be added for that version as children (see 0003987 here). Is that sufficient, or is there any other functionality you need?
Sorry I probably didnt explain.
When developing a product we often define a roadmap. For example, http://www.mantisbt.org/roadmap.php. Where we define what is in each release for the major versions.
Its that functionality with the type of view on roadmap.php.
One way to archive it would be with a parent and children but it would be nice to have an overview like on roadmap.php for printing and giving to clients.
Seems like this can be done with something very much like the ChangeLog, but it can't use the fixed_in_version column (since it is not fixed/done)... it would have to be something like a hope_to_be_fixed_in_version column...
Although, come to think of it.. if there were release dates associated with the versions, then it could use the fixed_in_version, and a version with a future release date would be used for a roadmap and the changelog could ignore it.
Sounds good to me =)
Agreed. DGtlRift, do you want to implement this? ;-)
|2004-08-06 09:33||chrisbond||New Issue|
|2004-08-06 09:40||jlatour||Note Added: 0006695|
|2004-08-06 09:40||jlatour||Status||new => feedback|
|2004-08-06 10:03||chrisbond||Note Added: 0006700|
|2004-08-06 10:36||DGtlRift||Note Added: 0006702|
|2004-08-06 10:38||chrisbond||Note Added: 0006703|
|2004-08-06 12:11||jlatour||Note Added: 0006727|
|2004-08-06 12:11||jlatour||Status||feedback => confirmed|
|2005-01-15 10:20||gtomlin||Note Added: 0009028|