Search field contents are not used in search all contents.
My team use a custom field to store an external feature ID (as well as the one generated and stored within Aha). Being able to search against this custom field for a ID reference would be extremely useful! Unless there's another way of achieving this?
I am in a very similar situation as Justin Woods. My team uses a custom field to store an external feature ID (OnTime Defect ID). The ability to search for these numbers stored within this field is a very high priority as we have hundreds of features in our product backlog.
I don't believe this is working even though it is marked as shipped. I still can't search for values stored within custom fields.
To search custom fields you need to click the "Search all content" button, or hit the Return key. The quick search results in that popup only consider a subset of the fields and record types in Aha!
The search of custom fields only considers fields containing string values. It will not search number or tag fields. Is your customer field a number field? If it is a string field you will need to to search for the same format that you entered in the field, including the comma.
Clicking on Search All Content also still find no results. The Custom Field is a Number Field, so that comma is being automatically added through the UI, but is not the stored value. Is there a plan to add search for Number Fields? We will definitely need this in order to integrate our engineering management software (OnTime) and store and track the Defect IDs.
Jon Betts | Product Manager, Contracts
925.660.1393 | iTradeNetwork
Any updates to this idea? It's marked as Shipped, but I can't get the search function to search custom fields - numerical, text, or otherwise.
The ability to search text custom fields was added on July 24. It is now possible to search numeric custom fields as well.
There are currently some caveats with searching the numeric fields. When searching you must enter the number without any punctuation - so no comma or decimal point. It is not possible to search for the part of the number after the decimal point. So you will find the number 1,234.56 by entering 1234 but not by entering 1,234 or 1234.56. We plan to remove these limitations in a future release.
You won't be notified about changes to this idea.