Question

We use the XML API a lot to create cases in Fogbugz. We've recently noticed that several of these cases cannot be searched for when applying a filter in Fogbugz.

For example: We click on the filter settings drop-down, select project, and then select the project we put the bug in, then do a search. Several of the bugs will show up correctly, but the rest appear as "[X Subcases not matching filter]", even though all of those sub-cases are also in the project we selected.

I did some searching in the database and confirmed that these particular bugs were correctly created, they just wasn't being found, or being matched with our filters.

This issue appears to be isolated to sub-cases of bugs created using the XML API. This behavior is observed in the same bugs no matter what filter criteria we apply. There does not seem to be any missing or incorrect information in the database when I look at the Bug table.

I wonder if there's something we might be doing wrong when creating the sub-cases using the API, or if this may be a known issue in Fogbugz at the moment. Has anyone else noticed this behavior before?

Thank you for any suggestions or feedback ;)

Answer 1

There are no known issues with cases created via the XML api being different from those created in the web UI.

Can you try making sure your filter is set to flat view (not outline view) and sort it by case number? Check the bottom of the list and make sure it's not showing you only the first 200 cases. If it is, click "list all" and see if all the cases are there.

If you have it in outline view and the subcases match the filter, but are gouped under a different heading (e.g. you're sorting on Project or Assigned-to or another column which groups results), the subcases may be grayed in one section and show in another (where they match the sort).