View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0006035 | mantisbt | custom fields | public | 2005-07-28 11:21 | 2013-10-24 07:10 |
Reporter | zecty | Assigned To | |||
Priority | normal | Severity | major | Reproducibility | always |
Status | acknowledged | Resolution | open | ||
Product Version | 1.0.0rc1 | ||||
Summary | 0006035: Custom fields are not supported for group actions | ||||
Description | When doing a "resolve" and/or "close" for a group of bugs/issues. None of the custom fields I have designated as "required on resolve" and/or "required on close" show up. | ||||
Steps To Reproduce | 1) Create a custom field that has "Required On Resolve" and "Required On Close" options enabled. | ||||
Additional Information | Affected files: | ||||
Tags | No tags attached. | ||||
Nice - One obvious question would be 'how to handle someone going to ALL PROJECTS, selecting bulk resolve on 5 different bugs from different projects with different fields... |
|
Additonally the custom function "custom_function_default_issue_update_validate" is not called. The other update methods include a call to this hook. Specifically for requiring a "fixed in version" entry on resolving or closing. |
|