Issue sections

Saved searches per repository that group the issue browser and fill the sidebar, built from conditions or written as a query.

Once you've connected GitHub or Jira, Tegment organizes their issues with sections: saved searches you define per repository. Each section has a name and a search, and it groups the issue browser. The sections you pick for the sidebar are listed together in the project's sidebar, each issue once, so an issue that matches two sections doesn't show twice.

Managing sections#

Open Settings, switch to Repository, pick the repository and open Issue sections. The page has a card per source. Each section shows how it is written and how many issues it matches, and from there you:

• add one with + Section,
• reorder them with the arrows, which sets the order in the browser,
• tick Sidebar for the sections the sidebar lists,
• Edit a section to change it.

The repository's GitHub issues and Jira issues pages link here with Edit sections.

Building a section from conditions#

A new section starts as Conditions: pick a field, how it compares, and the values, and add more conditions with + Condition. All conditions must hold (they are joined by AND). Underneath, Tegment shows the exact query it sends, so you can see what you are getting.

A field is any of or none of the values you pick, and Updated is in the last day, 7, 14 or 30 days. Values come from the source, so you pick a real status or label rather than typing one. Assignee and Reporter offer Me, Assignee also Nobody, and Sprint offers Current sprint.

Start from fills a section in from a preset, such as assigned to me, in progress or bugs, for you to adjust. Expanded when the issue list opens decides whether the section starts open in the browser.

Writing the query yourself#

Switch a section from Conditions to JQL (Jira) or Query (GitHub) to write the search by hand. A query that conditions can't express stays written as a query, and the section says so.

Jira sections (JQL)

A Jira section is a JQL query. Write {project} where you want the project key: Tegment substitutes the project you linked in settings, so the same section works across projects.

# Assigned to me
assignee = currentUser() ORDER BY updated DESC

# Recently updated
project = {project} AND updated >= -7d ORDER BY updated DESC

# Open bugs
project = {project} AND issuetype = Bug AND status != Done ORDER BY priority DESC

# Current sprint
project = {project} AND sprint in openSprints() ORDER BY updated DESC

GitHub sections (search syntax)

A GitHub section uses GitHub's search syntax, the same qualifiers you'd type in GitHub's own search box.

# Assigned to me
is:issue is:open assignee:@me sort:updated-desc

# Open bugs
is:issue is:open label:bug sort:updated-desc

# Unassigned
is:issue is:open no:assignee sort:updated-desc

Search#

Each integration's sidebar header has a search action that opens a search view, so you can look up a specific issue on demand without adding a permanent section for it.