Repository issues
See the repository's open issues on the same Git screen, with a filter for yours.
The Issues section shows the repository’s open issues, on the same screen where you work with Git — so you don’t switch windows just to check what is pending.
What the list brings
Each row shows the number, the title, the labels, the author and when the issue last changed. The list is virtualized and limited: it loads the most recent issues, not the whole repository.
There is a filter, Assigned to me, that narrows the list to what is under your responsibility. It is remembered per repository and filter combination, with a short cache — opening and closing the section does not trigger a new search every time.
Supported providers
| Provider | State |
|---|---|
| GitHub | Lists issues |
| GitLab | Lists issues |
| Bitbucket, Azure DevOps, Gitea | Not supported; the section explains instead of showing an empty list |
When the list appears empty
The panel distinguishes the reasons, and the difference matters because each one calls for a different action:
- No authentication with the provider — you still need to sign in to your provider account in the app.
- No network — the app did not reach the provider; Try again usually solves it.
- The folder is not a Git repository — the section has nowhere to read from.
- There are no open issues in this repository — the repository is up to date, it is not a failure.
- No permission, issues disabled or request limit — each one with its own text.
Scope and limits
- Reading, not editing. This section queries issues.
- Issues from external providers. Integrations with third-party issue tools are not part of this screen.
- The cache is short and per repository. An issue created just now may take a moment to appear, or appear after Try again.
- Nothing is written to the project by opening or filtering this section.