Welcome to the FogBugz Knowledge Exchange

Question

2

See Custom Fields Plugin Search for background on this question.

For custom field names that have a space in them, it would be nicer and faster when entering search parameters to not have to add the quotes or the "x". For example, for a custom field called Fixed In, searching needs to be either

"fixed in:" text

or

fixedxin:text

I'd like to change the sSimpleName field value from fixedxin to fixedin (directly in the appropriate SQL Server FogBugz table). Then I could search using:

fixedin:text

Would this change be acceptable or are there other places the sSimpleName is used that would then get broken?

edited Oct 30 2009 at 11:40

asked Oct 28 2009 at 18:05

Ken Morse♦
1,687●3●11

Brett Kiefer · Accepted Answer · 2009-10-30 12:18:54Z UTC

1

The only issue would be that you would have to rebuild the search index, because it's indexed on the old sSimpleName. In retrospect, the xs to substitute for spaces in search axes were probably a mistake (they come from an earlier use of the function).

answered Oct 30 2009 at 12:18

Brett Kiefer♦♦
2,660●2●5

	Excellent -- thanks Brett. – Ken Morse♦ Oct 30 2009 at 13:47
	Update -- this worked just fine: I updated the sSimpleName value to remove the "x", reset the search and all is well now. – Ken Morse♦ Oct 31 2009 at 19:20

Can we change a column value used by Custom Fields plugin?

1 Answer