View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001179 | mantisbt | feature | public | 2001-11-18 16:06 | 2024-10-17 05:39 |
| Reporter | updater | Assigned To | vboctor | ||
| Priority | normal | Severity | major | Reproducibility | always |
| Status | closed | Resolution | fixed | ||
| Product Version | none | ||||
| Summary | 0001179: Would like 'fix in release' field in bug table | ||||
| Description | From a workflow point of view, I need to be able to tell developers to only fix certain bugs for a particular milestone. Right now I'm using bugnotes, but those don't appear to be searchable, and it's certainly a pain to identify a list of bugs in this fashion. | ||||
| Tags | No tags attached. | ||||
|
Me too! This is probably the biggest feature missing in terms of what I would like to see in an upcoming release :) |
|
|
just to clarify: in 0.17.3 (the latest release) the bugnotes are searchable. |
|
|
I would suggest developing this feature as part of the custom fields feature. The custom fields allows the mantis administrator to define the fields that are not supported natively. These fields should be searchable. |
|
|
My initial idea was to implement it using custom fields if we are just making it a free text field. However, according to the discussion in the mailing list, I think it needs to be a native field. |
|
|
I think this will end up being available as custom fields. We will allow free text fields and enum fields that provide a list box. My only concern is that the fields are defined site-wide and added to projects. But each project is likely going to want its own values for a field like this. This could result in an overly large number of custom fields on sites with lots of projects. |
|
|
The custom fields feature is now implemented in CVS. This will allow you to add your own fields, and link them to projects as appropriate. |
|