View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0028515 | mantisbt | custom fields | public | 2021-05-06 03:03 | 2022-01-05 14:53 |
Reporter | mdkhamruddin | Assigned To | dregad | ||
Priority | high | Severity | block | Reproducibility | always |
Status | closed | Resolution | no change required | ||
Product Version | 2.24.1 | ||||
Summary | 0028515: APPLICATION ERROR 0001300 Custom field not found. | ||||
Description | Hello Team Facing issue with Mantis Custom field, kindly help | ||||
Tags | No tags attached. | ||||
mdkhamruddin, The provided information is not sufficient to provide any help in resolving the issue. A complete and detailed description is required for the support team to get a clear understanding of the problem. Please explain what you do, what are the results you expect to get and what you actually get. Also provide detailed, step-by-step instructions to reproduce the issue; the additional information listed below may also be useful:
|
|
Hello Dregad While try to access Manage Custom Fields( manage_customfield_page.php ) kindly check below snip attached 1) 2)Relevant customizations nothing done 3) plugin using 4) MantisBT source code not modified |
|
You missed the most important bit of information
As for
Really ? I would expect at least information about your custom field. |
|
1) i suspect that the custom field configurations are stored in the database 2)please check the snip from working mantis site ( are you looking for more info ?) |
|
any luck for me ? |
|
Luck has nothing to do with it. Start by answering 0028515:0065485 |
|
Hello thanks for replying to the person who has manging the mantis has left the organisation ,sorry no information on this can you please assist how to fix this |
|
the issue had to do with records in the mantis_custom_field_project_table that referenced field_id values that didn’t exist in the mantis_custom_field_table - this is presumably some sort of missing RFI in the Mantis schema… but the simple solution was simply to delete these invalid mappings from the association table. no idea how the orphaned mappings got in there in the first place. |
|
Thanks for the feedback. I'll resolve this as "no change required" then. |
|