Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Work items from visualstudio.com should not be visiblewhen they are in a resolved or fixed state. #57

Closed
cj13579 opened this issue Oct 25, 2016 · 4 comments

Comments

@cj13579
Copy link

cj13579 commented Oct 25, 2016

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.

vs-code-resolved

bug1_vs_resolved

@jeffyoung
Copy link
Contributor

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.

@cj13579
Copy link
Author

cj13579 commented Oct 25, 2016

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:

{
    "team.pinnedQueries": [
        {
            "account": "account.visualstudio.com",
            "queryPath": "My Queries/OpenItems"
        }
    ]

}

@jeffyoung
Copy link
Contributor

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?

@cj13579
Copy link
Author

cj13579 commented Oct 25, 2016

It was my bad again. I didn't have my account specified correctly. I am now seeing what I expect. I'll close this issue now.

Thanks for the help.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants