I think is related to 0005689 issue .

I just installed Mantis 1.0.0a3 as a new install (no upgrade, but first install) and appear to be experiencing this. I have tried serveral times to add a custom field (Date Required set to date) and can't get it to add. Haven't checked database to see if it was added, but will check.

I checked and there are three entries in my database where I tried to add my custom field. Though all three are in the database, they don't show up anywhere. Either in the list of custom fields or on the submit issue screen where it is suppposed to be an option to fill in. Maybe I'm missing something here.

Having the same problem here. The query in the custom_field_get_ids function (custom_field_api.php) will only show custom fields already assigned to a project:

JOIN $t_custom_field_project_table as cfpt on cft.id = cfpt.field_id

I don't know whether removing just the ON condition is appropriate or not, i.e.:

JOIN $t_custom_field_project_table as cfpt #on cft.id = cfpt.field_id

So my current workaround is to comment out the JOIN line above and placing the $t_custom_field_project_table in the FROM clause:

FROM $t_custom_field_table as cft, $t_custom_field_project_table as cfpt
#JOIN $t_custom_field_project_table as cfpt on cft.id = cfpt.field_id

confirmed with last CVS Head

Fixed in CVS.

Originated from confugion / merging of custom_field_get_ids() and custom_field_get_linked_ids(). The former will now always return all ids. The latter can take a project id (or array of project ids) and returns only those fields linked to the project.

return_dynamic_filters.php -> 1.8
view_all_set.php-> 1.55
view_filters_page.php -> 1.37
core/custom_field_api.php -> 1.54
core/filter_api.php -> 1.114