Plexus
Download

Boards from GitHub Projects

Work a GitHub Projects board inside Plexus: attach it to a workspace or project, switch views, drag cards, open the issue behind a card, start a session.

A Board tab lets you work a GitHub project — the boards, tables and roadmaps GitHub Projects gives an organization or a user — inside Plexus: attach it to a workspace or a project as a tool, and every one of its views opens in the tab.

Like the Issues tab, everything here goes from your machine to GitHub with the account you connected, and nothing about it reaches us.

Attaching a project

Open the Toolchain page from the Settings button at the right end of the tab strip, press Install on the GitHub Projects card, and pick the project. The picker lists the projects of the repository's owner when the scope has a repository on GitHub, and lets you type any user or organization to list theirs. A Board · Roadmap tab appears on the strip, named after the project.

Access to projects

GitHub keeps projects behind a permission of their own that a repository connection does not carry. A GitHub connection made before Plexus asked for it lacks it, and the picker — or the Board tab, if the connection changed later — says so and offers Reconnect GitHub. Reconnecting is enough: GitHub grants the permissions Plexus asks for, and the boards load once you are back. Nobody is asked to reconnect until they attach a project, and a connection with no project attached is left exactly as it was.

The Board tab

The tab opens on the project's first view and lists every view along its top, in the order GitHub shows them; pick one to switch, and the choice is remembered per tool.

  • A board view renders as columns — one per option of the field the view groups by, usually Status, plus a No Status column for cards without a value — with the project's cards inside. A view grouped by something Plexus cannot lay out as columns renders as a table instead and says so.
  • A table view renders the columns the view shows on GitHub.
  • A roadmap view renders as a table too; Plexus does not draw the timeline.

A card shows the item's kind (an issue, a pull request, or a draft), its number and repository, its title, its labels and who is assigned. Click a card to open the issue behind it — the same view the Issues tab opens, with the same editing; a draft opens read-only, since a draft has no issue, and a pull request opens on GitHub. Every issue card has Start session, which opens the New session dialog exactly as the Issues tab does, linked to the issue.

Dragging cards

Drag a card to another column and its field changes on GitHub — the card moves at once and comes back with a message if GitHub refused. The one column you cannot drop into is No Status (or No ): clearing a field is not something Plexus does, so do that on GitHub. Drag a card up or down within a column and its position in the project changes the same way. Position is something GitHub keeps per project, not per view, so a view that is sorted by a field has nothing for a reorder to mean: on such a view cards can still move between columns but not within one, and the tab says why when you try.

The view's filter

A GitHub view can carry a filter — is:issue status:"In progress" -label:blocked. GitHub does not send Plexus a filtered list; it sends the filter, and Plexus applies it itself. The common parts are understood — is: (issue, pr, draft, open, closed), label:, assignee: including @me, no:assignee, no:label, any single-select field by its name such as status:, quoted values, , for or, and - for not. Anything else is left out, and the tab says Filter partly applied and names the parts it skipped, so a board never quietly shows fewer cards than GitHub does without saying so.

How often it refreshes

A board asks GitHub again about every two minutes while Plexus is the focused window, every ten minutes while it is merely visible, and not at all while hidden; Refresh asks now, and every change you make refreshes it. Projects are more expensive to ask about than issues, which is why the pace is slower than the Issues tab's. Rate limits and a rejected token are shown in a line above the board, as on the Issues tab.

What a plan gates

The Board tab is behind the same plan as the Issues tab — everything in it goes from your machine to GitHub with your own token. Attaching a project, the picker and the Share with projects switch stay free; see Issues — What a plan gates.

  • Toolchain — attaching tools and sharing them across a workspace
  • Issues — the issue view behind every card, and starting a session
  • Git providers — the GitHub connection the boards run on