View Issue Details

IDProjectCategoryView StatusLast Update
0007851mantisbtadministrationpublic2019-12-03 10:47
Reporterzend Assigned To 
PrioritynormalSeverityminorReproducibilityhave not tried
Status acknowledgedResolutionopen 
Product Version1.1.0a1 
Summary0007851: Separate Entities for Bug & Feature & Change Request (not with severity)
Description

We would like to have the option for a few TYPE of records.
Separate Entities for Bug & Feature & Change Request that is handled not with the field severity.

TagsNo tags attached.

Relationships

has duplicate 0008712 closedvboctor add Issue Type field 

Activities

vboctor

vboctor

2007-03-24 20:46

manager   ~0014243

The first step in implementing this would be to do the following:

  • Add an enum that specifies the supported issue types.
  • Add a type field to the issue table.
  • Support a type file in the View Issues table.
  • Support a type field in the view, update, report pages (simple/advanced).
  • Support the type field in the filters.
  • Add an upgrade step that adds the field to the schema and default it for existing issues.
  • The first stage of implementing this will assume that all issue types will have the same fields (i.e. attributes of an issue doesn't depend on it's type).