Generally, an axis is often shaped within the title of any column within the grid see by removing the spaces e.g. the "Assigned To" column gets to be the "assignedto:" axis.
To check Should you be subscribed to the circumstance, use cmd=look for&q=xxx&cols=fSubscribed (the place xxx is the situation selection)
FogBugz has pretty strong filters and look for functionalities, find out how to implement it at its ideal WIKI
If That is still left off, then the API assumes you are searching for assignments which you can at the very least study. ixProject -- optional, if included will normally listing a minimum of this project even if it is deleted)
cmd=viewHoursRemainingReport - See the distribution of projected overall several hours remaining to accomplish this milesone at this Priority. This can be the info which is aggregated as time passes during the Burn up Down Chart.
FogBugz is speedy and simple to use. It offers basic configuration and optimized workflows to jumpstart little teams.
2) Productive logon - you have back an opaque string token which you'll use for all subsequent requests:
If this returns an HTTP error (file missing) it is possible to properly presume that both FogBugz just isn't put in at that location, or else it really is put in, but it's a Variation of FogBugz that does not consist of the API.
Any lookup may be saved to be a filter, both by clicking around the disk icon within the Research Tools box in the upper suitable corner of the outcome page, or with the Filters menu.
You'll be able to manage your whole task backlog in FogBugz. Your staff gets notifications given that the bugs move through the workflow.
3) Ambiguous logon - There may be more than one FogBugz user with that electronic mail tackle. FogBugz will provide you with a list of full names; you must deliver the suitable total identify to log on.
Check out Settings
sort is "builtin", "saved", or "shared". FogBugz end users will probably count on to see the a few different types of filters grouped as They can be in FogBugz by itself. The listing of filters is now in the same get that end users are used to looking at it while in the FogBugz user interface and may be preserved.
The minversion area is accustomed to alert you if The present version of the API is not really backwards suitable. As an example, if this Variation is 3, and it is actually backwards compatible with shoppers composed for Variation 2 but not backwards https://searchtech.fogbugz.com/default.asp?Suggestions.1.523613.0 suitable with Variation one, you'll see:
All API requests will need to have a token argument indicating the logon session except cmd=logon. The token may be used indefinitely, and may only be invalidated by executing a logoff command with that token.
All API requests should have a cmd argument indicating what you wish to try and do, like cmd=logon during the logon illustration.