View Issue Details

WikiJump to Notes
IDProjectCategoryView StatusDate SubmittedLast Update
0004066mantisbtfeaturepublic2004-07-11 02:012004-07-18 11:34
Reportervboctor Assigned Tovboctor  
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
Fixed in Version0.19.0a2 
Summary0004066: Support "future" versions and a description field
Description

Given that now the version field is used for both "Product Version" and "Fixed in Version" and maybe in the future it will be used in "Target Version", we need a way to differentiate future versions from released versions.

  • Product Version: Should only show released versions.
  • Fixed in Version: Should include both released and future versions.
  • Target Version: Should include either future only or future + released. This is to be decided when Target Release is implemented.

Also it would be useful to allow the associate of a description field which includes detailed information about the version. This is to be shown at the top of the version section in the changelog.

TagsNo tags attached.

Relationships

has duplicate 0004007 closedvboctor Allow adding future versions to project versions 

Activities

vboctor

vboctor

2004-07-11 02:08

manager   ~0005980

  • Added id as a primary key to mantis_version_table (however, this will not be used to refer to versions).
  • Support "released" flag, this will determine whether a version is a released version or a future version. Product version field will only show released versions, but "fixed in version" will show all.
  • Added description field, and show it in Changelog before the actual list of entries.
  • Use version id in the edit/delete version pages to refer to a specific version.
  • Use version id in the version_api to refer to a specific version.
  • Use a version information class in version_api.
  • Support caching in versions_api.
vboctor

vboctor

2004-07-11 03:03

manager   ~0005984

The description field was requested in 0004057.