We can not search issues on the basis of dbcf custom field value on Jira 5.1.

[swati sneha]

We have done a backup restore from Jira 4.3 to jira 5.1 version. We have older issues of Jira 4.3 having the values for DBCF custom field. We are not able to search those issues on Jira 5.1.

Please provide a quick help ASAP.

[Radu Dumitriu]

Most probably, you need a reindexing. If the problem still persists, please open up an issue on http://bugs.kepler-rominfo.com

Thanks.

[Mike A.]

forgot to mention that we did re-index. and we re-attempted the import and re-indexed. no change.

[Mike A.]

http://bugs.kepler-rominfo.com/browse/DBCF-34

opened.

What we have discovered is that after the import of 4.3 data into a new 5.1 instance, NO Database Information fields show the previous values. So this still could be a Atlassian issue possibly.

[Mike A.]

To further clarify, a custom field for "responsible team" has lots of filters running against it like Responsible Team = "Client Support". In current 4.3 production these will return related issues. After importing the production data to the 5.1 instance, they do not return matches (yet the data in the issues appears to be unchanged. We have other custom fields that seem to migrate fine.

It appears that even though in the database these fields are populated, in the issues they are not (filtering for the field empty returns issues).