Skip to content
Zide Zide Zide

Issues

You can browse and manage all GitHub issues in a repository from Zide.

The line above the list says how many issues there are. With no filter conditions it says N issues. With any condition, the default open state included, it says N matches. Each condition shows as a chip above the count. To remove all of them, click Clear filters at the end of the count line. In a narrow panel the button says Clear. Warnings still explain incomplete data.

To open Issues, click its activity-bar icon or click DevOps > Issues.

Issues are listed numerically and display the following information.

  • State badge: The badge that indicates if an issue is open or closed.
  • Issue number: The number of the issue.
  • Issue title: The title of the issue.

The Issues activity first lists enough issues to fill the panel, so the first issues show sooner. Zide then reads the next page in the background, and more pages as you scroll toward the end of the list. Click Load more at the end of the list to read the next page at once.

When a project is shown, Zide reads this first page in the background, so Issues shows it at once when you open it. Zide then reads the page again and updates the list only if it changed. Until that read is done, Load more is not available. If the read fails, the list keeps the issues it shows.

To open an issue in a separate tab, right-click the issue and click Open in New Tab.

Issue view

Click an issue to open the issue in the Issue view. The Issue view displays the issue and the following information.

  • State: The status of the issue, if the issue is open, closed as complete, or closed as not planned. Click the pill to change the state. Click it again, click outside the menu, or press Escape to dismiss it without changing the issue.
  • Type: The type of issue.
  • Milestone: The milestone associated with the issue.
  • Assignee: The users assigned to the issue.
  • Labels: The labels attached to the issue.
  • Project: The project the issue is a part of.
  • Related: The issues related to the current issue.

Click Commits to see the commits linked to the issue. Click a commit to open it. The button is dimmed when the issue has no linked commits.

To change the issue title, select More actions > Edit title in the header. Select More actions > New issue to open the issue form with the current issue’s labels, assignees, milestone, type, and project already set.

Click Quicktree to work on an issue in a Quicktree.

When an issue is locked on GitHub, a notice above the comment box shows the lock and its reason, for example This conversation is locked as too heated. Only people with write access to the repository can comment on a locked issue. If you have write access, the comment box works as usual. Zide Assist also reads the lock when it reads the issue.

To move through a long discussion, use the minimap beside it. Blocks shows one mark for the description and one for each comment. Each mark reflects the length of its entry. Point to a mark to preview the author and the start of the text. Click the mark to scroll to that entry. To show or hide the minimap, choose Blocks or Hidden under Minimap in More actions in the issue header, or right-click the discussion or the minimap.

Discussions start with Blocks. Your choice applies to every issue discussion, including GitLab, and Zide keeps it after a restart. A discussion that fits in the pane shows no marks.

To copy text from the description or a comment, select it, right-click on it, and click Copy. See Copy selected text.

Select issues for bulk actions

Use the shared gestures described in Select more than one item. The gestures work across the supported Issues views.

When issues are selected, the selection toolbar displays the selection count and provides Select All, Clear, Bulk Edit, and Open All. Bulk Edit provides the supported State, Type, Assignee, Milestone, and Labels operations. Operations have selection limits; controls are disabled when the selection exceeds the applicable limit.

Issue report

To open GitHub issue reports, choose DevOps > Issue Report and select a report from the Report Gallery. While a report is open, choose Change Report to select another report. Use the filter control to change the issues summarized by the report. For details, see Issue report.

Create an issue

To create a new issue in the repository, complete the following steps.

  1. Click DevOps > New Issue, or click New Issue in the Issues activity. From the activity, the form starts with the labels, assignees, milestone, issue type, and project that the current filter sets. Values under None of are not used.
  2. In the New Issue tab, enter the issue name in the Title field.
  3. Optional: Add labels, milestones, and assignees to the issue in the Metadata section.
  4. Enter the issue description in the Description field and click Create Issue.

The new issue will open in the Issue view.

A red asterisk (*) marks a required field. Create Issue is unavailable until the Title field has text, and while an attachment uploads. Point to Create Issue to see the reason. If you leave the Title field empty, a message shows below it.

Filter issues

By default, the Issues activity displays all open issues in a repository. Click the filter selector, the filter name after Filter:, to choose another filter. See Saved filters.

Click Show or hide filters to open the filter panel. It shows the common filters first: Search, State, Assignee, Label, Milestone, and Author. Click Advanced Options to show the other filters, in alphabetical order. Each tab remembers whether Advanced Options is open. You can combine filters: an issue must match all of them. Press Ctrl+F (Cmd+F on macOS) to open the panel with focus on Search.

Each filter takes one value. Click a filter, then click a value. The value replaces the filter’s current value, and the list closes. The current value is highlighted. To remove the filter, click Clear at the bottom of the list, or click the x on its chip. To use several values or exclusions, see Several values and exclusions.

To search issues, click Search and type the words. Choose In titles, descriptions, and comments (the default), In titles, or In descriptions, then press Enter or click Apply. The chip reads Text, Title, or Description. In the default scope, GitHub shows the issues that contain all the words. Zide searches for each term as words: it puts quotation marks around a term such as label:bug or OR, so the term does not filter the list. To filter, use the filter buttons. In titles and In descriptions search for the words together as one phrase, so they cannot contain quotation marks; Zide removes them. A filter has one search, so a new search replaces the current one. Click the chip to change the words or where to search.

Created, Updated, and Closed show issues created, updated, or closed in the last 7, 30, or 90 days, this year, or more than one year ago. To use other dates, set From, To, or both, and click Apply. The range includes both dates. You can type a date, choose it from the calendar, or paste it in the form 2026-01-31 or 1/31/2026.

Type lists the issue types of the repository, including custom types. Issue types belong to organizations, so in a repository without them Type is unavailable, with the reason This repository has no issue types. Close Reason shows issues closed as Completed, Not planned, or Duplicate. Closed and an included close reason find only closed issues, so first choose All Issues or set State to Closed. With All Open, the list is empty. A reason under None of only hides issues closed for that reason.

Comments shows issues with None, 1 or more, 5 or more, 10 or more, or 25 or more comments. Reactions uses the same choices for reactions. Locked shows locked (Yes) or unlocked (No) issues. Commenter shows issues that a user commented on. Involves shows issues that a user created, is assigned to, commented on, or is mentioned in. Mentions shows issues that mention a user. These three lists start with Me (@me).

Zide applies the In Hierarchy and named Project filters itself, so it reads more pages of issues to find matches. The matches found so far show while the search continues. The count says N matches so far, with a spinner beside it, and Load more is unavailable until the search stops. Each search reads up to 10 more pages after the first one, and stops earlier when it has enough matches to fill the panel or no issues remain. If more issues remain, click Load more to search further.

Saved and recent filters keep the In Hierarchy and Project filters.

To find issues where a field is empty, open Milestone, Assignee, Label, Project, or Type and choose No milestone, No assignee, No labels, No project, or No type. To find issues where it is set, choose Has milestone, Has assignee, Has labels, Has project, or Has type. The choice replaces the other values of that filter. Click Clear or the chip’s x to remove the condition.

In Linked PR/Issue, choose Has no linked PR to find issues without a pull request linked to close them. Older saved queries keep no:milestone, no:assignee, no:label, no:project, and -linked:pr as these conditions.

Several values and exclusions

To use more than one value in a filter, or to hide issues that have a value, click Advanced Options and check Show Any / All / None. Then the Assignee, Author, Close Reason, Commenter, Involves, Label, Mentions, Milestone, and Type filters show their values with two columns of checkboxes:

  • Any of: shows items that have at least one checked value. For labels, click the Any of heading to change it to All of. Then the list shows only items that have all the checked labels.
  • None of: hides items that have any checked value.

A value can be checked in one column only. The list updates after each change, and the list of values stays open. To show only the items with one value, click the name of that value. This clears the other checkboxes of that filter and closes the list. When you point at a name, the checkboxes show the result before you click. In long lists, such as labels, type in the search field to find a value. Click x in the field to clear the search. Click Done or press Escape to close the list. Clear removes all values of the filter.

To keep the exclusions, select the checkbox or round button beside Has …. This clears the named values but keeps the values under None of: Has labels with bug under None of shows labeled issues that are not bugs. Clicking the name Has … makes it the filter’s only condition, as clicking any name does. Choosing an included value replaces the No or Has condition, and choosing a value under None of keeps Has ….

Each filter shows as one chip, for example Label: bug or regression, not blocked. Click a chip to change its values. Click the x on a chip to remove the filter.

Point at Show Any / All / None to see which filters it changes: their borders change color. Other filters keep one value. Each tab remembers this setting.

If a filter has more than one value, or a value under None of, Show Any / All / None stays checked and is unavailable. The text below it names those filters, for example Keep at most one value and remove exclusions in Label to turn this off. This also happens when you choose a saved filter with such values. When those filters have at most one value and no exclusions, you can clear the checkbox. Clearing it does not change the filter or the list.

Query text in older filters

A filter saved with Switch to Advanced Query in an earlier version of Zide keeps its query. Terms that the filters can show become their chips. For example, -label:docs shows as Label: not docs, and label:bug OR label:ui shows as Label: bug or ui. Other query text, such as -team:octo/docs, shows as one chip with a dashed border, and Zide still sends it to GitHub. To change that text, remove its chip. The Issues list does not show a query field.

A term becomes a chip only when the filter can show all of it. Text in quotation marks stays as written: "label:bug" in:title is a title search, not a label filter. Saved title and full-text searches open as Title and Text chips of the Search filter. A date range such as created:2026-01-01..2026-01-31 becomes a Created chip. A term that a filter can show only in part, such as created:2026-01-01..*, stays whole in the dashed chip. The filter selects the same issues when you choose it again from Saved Filters or Recent.

Filter choices

Filter choices refresh after Zide Assist changes repository metadata and when you refresh the list. Your current filters stay selected. If a selected milestone is deleted, its filter remains until you change or remove it. Click that filter to see the milestone marked unavailable and choose a replacement.

If you open a filter before its list has loaded, the choices that need no list work at once, and a line such as Loading labels… (or users, milestones, projects, types) shows until the list arrives.

The Project list shows the open GitHub projects that are linked to the repository. If there are none, it says No open projects are linked to this repository. If Zide cannot read the projects, the list says why, for example that the GitHub token needs the read:project scope. Click Retry to read them again. When the cause is the account or its token, click Open Git Accounts to open Settings on Git Accounts.

If you choose another GitHub remote for Issue Tracking in DevOps > Configure…, the list and its filter choices reload for that repository. Your filters stay selected.

Saved filters

Click the filter selector to see these groups:

  • Built-in Filters: filters that Zide provides: All Issues, All Open, and My Open Issues.
  • Saved Filters: filters that you saved for this project. Save Current Filter As… at the top of this group saves the current filters with a name that you enter, and selects the new saved filter.
  • Recent: filters that you used recently but did not save.

A check mark shows the selected built-in or saved filter. Ctrl+click (Cmd+click on macOS) a filter to open it in a new tab.

When you change a saved filter, the list updates at once, but the saved filter does not change. The selector shows the filter name followed by (modified), or an asterisk in a narrow panel. The filter list then starts with two items:

  • Save Changes saves your changes to the saved filter.
  • Discard Changes restores the saved filter and refreshes the list.

If you choose another filter without saving, Zide keeps your changes in Recent under the filter name followed by (modified). Recent keeps one such entry for each saved filter: newer unsaved changes replace the older ones. To keep a variant, save it with Save Current Filter As…. Choose the entry to continue: the saved filter opens with your changes, ready to save or discard. If the saved filter was deleted, the entry opens as an unsaved filter.

A filter that is not saved, such as a built-in filter that you changed, is named after its filters. Recent uses the same name.

To rename or delete a saved filter, click the More actions button (⋮) next to it in the list, then click Rename… or Delete…. These actions apply to that filter, also when you use another filter. Deleting a saved filter does not delete or change any issues. If you delete the filter that you use, the list changes to All Open.

In the list, the arrow keys move between filters, and Shift+F10 opens the More actions menu of a saved filter.

Saved filters belong to the project. The activity and the Issue Report tab use the same saved filters. Pull request filters are saved separately.

Assist with This

Right-click an issue and point to Assist with This. In the Issue view, you can also right-click the content header or an ordinary background area, or click More actions.

Under Zide Assist, click Add to Conversation to attach the issue to a Zide Assist tab. You can also drag the issue into a Zide Assist tab. To attach several issues, select them first and point to Assist with Selection. For more information, see Attach items to a message.

Under Ask Zide, click Open Ask Zide. Zide opens the issue in the Issue view with an Ask Zide panel beside it. In the panel, click Summarize Issue or Suggest Next Steps. These commands need one issue. See Ask Zide beside a tab.