Welcome to the FogBugz Knowledge Exchange

Question

1

[Fogbugz Online]

Hi there - I have added a custom field called "JIRA Issue" which we use to link issues that have come in through the help desk. According to everything that I have read, I should be able to search this field using the search axis "jiraissue:123", but I keep getting the "The requested search axis 'jiraissue' is not recognized" message.

I have reset the search index, but to no avail.

For reference, the filter I want to get out of this is all items that have something in that field - i.e. everything that is linked to a JIRA issue.

Obviously I could change the text field to a yes/no and filter on that, but I'd rather get this working instead.

Is it possible / what should I be doing instead?

(I read this thread, which seems related, but they seem to starting from a point at which their custom field is searchable, and I can't even get that far - http://fogbugz.stackexchange.com/questions/516/how-do-i-search-for-a-custom-field-custom-fields-plugin )

flag	asked Feb 25 2011 at 11:54 Hugo Rodger-Brown 11●2

db · Answer 1 · 2011-02-28 19:30:20Z UTC

2

The thread you linked to mentions that you need to search using the "simple name" for the custom field. This is the custom field's name with any non-letter characters replaced with x's. This makes it sound like you should be searching for jiraxissue:123. Also be careful that there aren't multiple consecutive spaces as each of those will be replaced with x's.

Does search work if you use jiraxissue as the search axis?

edited Feb 28 2011 at 19:30

answered Feb 25 2011 at 13:37

db♦♦
13.2k●8●15

	OK - my mistake - I (accidentally) typed in <code>jiraxxissue:123</code> and it worked! I obviously put a double-space in by mistake. Thanks for the "x" tip - although the documentation is ambiguous on that front - it suggests that spaces are simply removed, not replaced, but there you go - it work :-) – Hugo Rodger-Brown Feb 28 2011 at 9:46
	Thanks for the feedback! I've updated my answer here and also looked over the linked documentation. The accepted answer on that question shows spaces being converted into x's as far as I saw. Or am I missing something? – db♦ Feb 28 2011 at 19:33

Are custom fields searchable?

1 Answer