View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0026151 | mantisbt | custom fields | public | 2019-09-17 08:04 | 2020-06-22 06:05 |
Reporter | cproensa | Assigned To | |||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | new | Resolution | open | ||
Product Version | 2.23.0 | ||||
Summary | 0026151: Custom fields required but not displayed should be filled with the default value | ||||
Description | As a follow up to 0026140: In the scenario where a custom field:
When submitting the changes for the issue, the custom field should be created with the default value. | ||||
Tags | No tags attached. | ||||
related to | 0026140 | new | Custom fields are displayed on issue report even if they have disabled "Display When Reporting Issues" | |
has duplicate | 0025372 | closed | dregad | custom fields with default value unable to saved ot database if they are not on the report issue page |
related to | 0016011 | new | Readonly custom fields and default value |
I agree that this should be the system's behavior. |
|
When is this feature planned to be implemented? Just for clarification. |
|
@vboctor @atrol any objection to this? |
|
No objection from my side. |
|
Any idea when this bug will be fixed? It's been a few months since this was reported, and this really affects usability, as we use the default text to provide guidance to our users. |
|
I would like to know aswell. It would still be a great change. |
|
Any updates on this? |
|