View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0013494 | mantisbt | bugtracker | public | 2011-11-07 16:03 | 2011-11-21 14:04 |
Reporter | vincent_sels | Assigned To | atrol | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | closed | Resolution | duplicate | ||
Product Version | 1.2.8 | ||||
Summary | 0013494: Allow configuration of which custom fields to display/require upon which status changes | ||||
Description | For custom fields, you can now configure whether to display or require the custom field upon <i>resolving</i> and upon <i>closing</i>. Wouldn't it be better to replace these two with a generic table, allowing to specify upon which status change, the field should be displayed and when it is required ? To store this, you could simply use one database field, with an array of key-value pairs, one key per status, and as value: Checking required but not checking display is pointless anyway. | ||||
Tags | No tags attached. | ||||
duplicate of | 0005744 | new | Managing custom fields in the workflow |
This was more or less asked in ticket 0005068 but i see that ticket was closed (even though imo not completely solved). |
|
An extra step would be to allow this configuration to be overwritten per project and user. |
|
This is a duplicate of 0005744 |
|
Yes, that is indeed an exact duplicate, strange that I've missed that in my search, sorry. I'll take a look and see if I can continue the development suggested there (migrate it to v1.2.8). |
|