You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
I think that the item is visible in vscode because there is no filter on the list and it is showing all items that are assigned to me (as per the notes in the README) but it makes it seem like there are many more outstanding bugs on an application than there really are.
The text was updated successfully, but these errors were encountered:
Hi Christopher. Thanks for trying out the extension!
Have you see the ability to provide your own query (a pinned query) in the User Settings? You can write whatever query you want and it'll use it as the default to show in the status bar.
Ah-ha, I didn't see that. I've created a query "OpenItems" under "My Queries" but I can't seem to get is to come through to vscode. Perhaps I am doing something incorrectly? I have the following in my settings.json:
Can you be a bit more specific by what you mean regarding that you "can't seem to get it to come through"?
If the query can't be found, you'll get an error message with a 404. Is that what you get? Otherwise, if it can find the query, it should run it and display the count on the status bar. When clicking on the status bar, the QuickPick menu will open and display the results of the query. If there are > 200 items, only 200 will be shown with an additional item that will take you to the query results in the web. If there's more than the server max (~20,000), you'll get a different error. Or is it not showing you the results that you expect?
I think that the item is visible in vscode because there is no filter on the list and it is showing all items that are assigned to me (as per the notes in the README) but it makes it seem like there are many more outstanding bugs on an application than there really are.
The text was updated successfully, but these errors were encountered: