most recent 30 from http://fogbugz.stackexchange.com 2013-05-22T07:39:49Z http://fogbugz.stackexchange.com/feeds/question/10871 http://www.creativecommons.org/licenses/by-nc/2.5/rdf http://fogbugz.stackexchange.com/questions/10871/support-sfilter-as-param-in-the-search-endpoint Chad Scira 2012-10-16T00:46:05Z 2012-10-16T12:02:19Z

<p>I haven't figured out how to use a shared filter through the api search endpoint without setting it and having to set it back to the users default.</p> <p>It would be really nice if you could just do this:</p> <p>api.asp?cmd=search&amp;sFilter=123</p> <blockquote> <p><img src="http://www.gravatar.com/avatar/baf927dcc0b0c5d0f41dece1e575aa0f?s=32&amp;d=identicon&amp;r=PG" alt="Fog Creek"> <a href="http://fogbugz.stackexchange.com/questions/1023/whats-that-kiwi-logo-and-case-number-at-the-bottom-of-my-feature-request" rel="nofollow">Case FC2345413</a></p> </blockquote>

http://fogbugz.stackexchange.com/questions/10871/support-sfilter-as-param-in-the-search-endpoint/10873#10873 db 2012-10-16T11:45:57Z 2012-10-16T11:45:57Z

<p>The <code>sFilter</code> argument is only used by the <code>listCases</code> command not the <code>search</code> command. The <code>search</code> command only uses the <code>q</code> argument.</p> <p>While looking into this, I discovered a bug that was preventing <code>listCases</code> from loading saved filters as intended. I've fixed this bug and it will go out in an upcoming FogBugz release. Once this fix has been released, you should be able to obtain your desired results via the following endpoint:</p> <p><code>[your FogBugz]/api.asp?cmd=listCases&amp;sFilter=123</code></p> <p>To see a list of valid <code>sFilter</code> arguments, take a look at the <code>listFilters</code> endpoint.</p>