View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0024795 | mantisbt | bugtracker | public | 2018-09-20 12:52 | 2018-10-01 15:23 |
Reporter | simonegirlanda | Assigned To | atrol | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 2.13.0 | ||||
Summary | 0024795: Custom field row in mantis_custom_field_string_table is not inserted when field value is empty/null | ||||
Description | I suppose that mantis behaviour was changed by 0023998 ( Implement IssueAddCommand and use it from SOAP, REST and Web UI) I need even empty custom fields in mantis_custom_field_string_table because another application look for them. | ||||
Tags | No tags attached. | ||||
3rd party applications should not depend on internal implementation. I think Mantis should not be changed back as long as there is no issue in Mantis itself or any of the API's. Do you agree that we can resolve this issue and your application should be changed to treat non-existent custom field values the same way as empty ones? |
|
You've cornered me... As a Programmer, I must agree. I've made a little change in the bug_report source to solve my issue (quick&dirty solution), meanwhile I'll study a SOAP / REST approach. Thank you for your excellent work. |
|
Thanks for the feedback. I'm resolving the issue as no changed required. |
|