0

Hi, We installed fogbugz 8 yesterday and our code using xml api is now broken. We use xml api's cmd=Search function to get all the cases associated with our lead from fogbugz, to show them in our internal client services tool.

Eg. my search query is

tag:l2275- tag:l22750- tag:l22751- tag:l22752- tag:l22753- tag:l22754- tag:l22755- tag:l22756- tag:l22757- tag:l22758- tag:l22759

which worked well on fogbugz 7 until yesterday and today, when I type this query in fogbugz UI, it resolves to

tag:"l2275-" tag:"l22750-" tag:"l22751-" tag:"l22752-" tag:"l22753-" tag:"l22754-" tag:"l22755-" tag:"l22756-" tag:"l22757-" tag:"l22758-" tag:"l22759"

and returns 0 results.

Any help is greatly appreciated. Thanks,

flag

2 Answers

1

Are those your full tag names or just prefixes? If you want to find all tags that start with l2275-, search for tag:l2275-*.

Unfortunately, we went back and forth on whether tag search would be partial match or exact match in different versions, but it's exact match in FogBugz 8 and forward.

link|flag
1

Thanks Ted for the update. The problem I was having was not just in xml api, it was on the search box on fogbugz UI. If I try to search for tag:l2275- tag:l22750- tag:l22751 it will get resolved to: tag:"l2275-" tag:"l22750-" tag:"l22751" and gives 0 results.

Instead if I type tag:l2275 -tag:l22750 -tag:l22751 it will get resolved to: tag:"l2275" -tag:"l22750" -tag:"l22751"

and gives the correct results.

It is the positioning of the "-" which was messing me up. Also, I realized that in fb8, I dont need ther - since I am trying to do exact match of the tag.

link|flag
Interesting. I didn't even know that used to work. (I don't think it was supposed to work like that.) Glad you figured it out. – Ted Oct 18 2010 at 17:28
I got help from fogbugz customer support :) – saritha Oct 18 2010 at 19:50

Your Answer

Not the answer you're looking for? Browse other questions tagged or ask your own question.