Plnnrly work items, boards and sprints

A Plnnrly tab lets you work a Plnnrly project inside Plexus — its backlog, its board, its sprints and every work item in it — and start a session from any work item that stays linked to it.

Everything the tab does goes from your machine straight to your own Plnnrly organization, with the sign-in you connected under Settings → Integrations. It never passes through us, and nothing about it — the work items, what you edit, how often you look — reaches us. See Privacy.

Connect your organization

A Plnnrly organization has its own address — usually acme.plnnrly.com, sometimes a domain of its own — and Plexus connects to each organization separately.

1. Open Settings → Integrations and select Add Plnnrly organization.
2. Type the Organization address — the organization's name, its plnnrly.com address, or its own domain — and press Continue. Plexus checks that the organization is there and that its API is on.
3. Press Sign in with Plnnrly. Plexus opens the organization in your browser to approve Plexus, and brings you back once you have. Signing in is the only way to connect — there is no token to create or paste.

The organization then has a row of its own on the page, with your name — Alex Smith, say — or Signed in when the organization does not tell Plexus who you are. Connect as many organizations as you work in; each keeps its own sign-in.

The sign-in is kept in your operating system's keychain, never in a file and never in Plexus's database, and it is never sent to us. Plexus renews it on its own while it is in use, so there is nothing for you to rotate. A sign-in that goes unused for 30 days expires in Plnnrly; Reconnect signs in again.

Reconnect and disconnect

Select an organization's row to see who is signed in and since when, with two buttons:

• Reconnect signs in to the same organization again — what you need when a sign-in has expired or was revoked in Plnnrly.
• Disconnect asks first, then forgets the organization's sign-in, and asks Plnnrly to revoke it where the organization supports that. Plnnrly tabs on the organization's projects stay attached and ask you to connect again.

You can also cut Plexus off from inside Plnnrly, under API access → Connected apps in your user menu. Plexus then asks you to reconnect the organization.

Connections belong to this machine. They are not part of cross-device sync, so connect again on each computer you use.

Attach a project

Open the Toolchain page — the Settings button at the right end of a project's or a workspace's tab strip — and press Install (or Configure) on the Plnnrly card, under Work management.

Pick the Organization, then the Project: the search lists the organization's active projects, most recently active first, each with its code, its title, and whether it runs in Sprints or as a Board. Press Attach and a tab named after the project — Plnnrly · Storefront, say — appears on the strip. Attach a Plnnrly project to a workspace and it is shared with every project in it, exactly like a GitHub tracker.

The views

Across the top of the tab are the project's views, the same ones Plnnrly shows:

Backlog lists the work items in no sprint, in Plnnrly's order, with the upcoming sprints above them; All work lists every work item in the project, most recently updated first. A row shows the item's type, its key (such as OPTH-186), its title, its labels, its comment count and who is assigned — plus the Sessions already started from it and Start session. Click a row to open the work item.

Open in Plnnrly in the tab's header opens the project in your browser, and New work item creates one: a title, a description, and optionally its type, priority, assignee, labels and sprint. Create work item saves it to Plnnrly and opens it.

Filters

The list views have a toolbar:

Plexus reads up to 500 work items at a time; when a project holds more, the tab says Only part of the list was fetched — narrow it with a filter or the search.

How often it refreshes

The tab asks Plnnrly again about every minute while Plexus is the focused window, every five minutes while it is visible but not focused, and not at all while it is hidden. Refresh asks now, and every change you make refreshes it.

If the sign-in stops working — it expired, or it was revoked in Plnnrly — the tab says Plexus can't reach this Plnnrly organization with the saved sign-in. with a Reconnect Plnnrly button that opens the organization's row in Settings → Integrations. Anything else Plnnrly answers is shown as it comes, with Retry.

Opening a work item

Click a row or a card and the tab shows the work item in place of the list, with Back to return:

• the title with the item's key, the status, who reported it, Open in Plnnrly and Start session;
• the description, rendered from Plnnrly's own formatting. Images and other remote media are left out on purpose — Plexus never loads anything from the web into the app on your behalf — and a link opens in your browser;
• a side column with Assignee, Priority, Type, Labels, Sprint, Due date and Estimate;
• the comments, oldest first, and a box to write one.

What you change is saved to Plnnrly the moment you do — the change shows at once and is undone with a message if Plnnrly refused it:

The status menu appears only when your account may move the item in Plnnrly. If somebody changed the work item in Plnnrly while you were editing it, Plexus says This work item changed in Plnnrly — reloaded. and shows the current version, so you never overwrite their change unknowingly.

The board

Active sprint (or Board, in a project without sprints) shows the work items as columns — one per status of the project's workflow, in Plnnrly's order — and a card per item. An item whose status belongs to no column sits in a trailing Other column.

• Drag a card to another column and its status changes in Plnnrly. The move has to be one the workflow allows: an illegal one snaps back with Plnnrly's workflow doesn't allow In progress → Done. (naming the two statuses). Nothing can be dropped into Other.
• Drag a card up or down within a column to reorder it — only where your Plnnrly organization supports reordering. Where it doesn't, the card stays put and Plexus says This Plnnrly organization doesn't support reordering yet.; a card moved to another column then lands where Plnnrly puts it.

Click a card to open the work item; every card can start a session too.

Sprints

In a project that runs in sprints:

• The sprint bar above the Active sprint board names the running sprint, its dates and how many of its work items are done, with Complete sprint. Completing asks where the unresolved work items go — Move to the backlog, or into the next sprint by name — and then closes the sprint in Plnnrly.
• Backlog lists the upcoming sprints with Start sprint. Plnnrly runs one sprint at a time, so while one is running the button says to complete it first. With no sprint running, the Active sprint view says No sprint is running. and points you to Backlog.
• Move to sprint — on a Backlog row and on a board card — moves a work item into a sprint, or back with Move to backlog. The Sprint field of an opened work item does the same.

Plexus does not create sprints, statuses, labels or projects — do that in Plnnrly, and it shows up here at the next refresh.

Start a session from a work item

Every row, every card and the opened work item have Start session. It opens the New session dialog with:

• the name filled in as OPTH-186 The work item's title — a suggestion, which you can change;
• a Linked to OPTH-186 · acme.plnnrly.com chip under the name;
• a checkbox, on by default, Send the issue to the agent as the first prompt. Leave it on and the agent's first prompt is the work item's title, its link and its description as plain text, with a request to reference OPTH-186 in its commit messages. If you also pick a template, the template's prompt goes first.

The branch comes out as plexus/opth-186-the-work-items-title, because Plexus names a branch after its session. The link to the work item is written together with the session, so it stays whatever you rename the session to.

From then on the session's context bar shows an OPTH-186 chip, and a Work item button sits at the right end of the session's tab strip; either opens the work item in a sidebar beside the agent — the same view as the tab, editable, with Open in Plnnrly in its header. See the issue sidebar. The work item's row in the Plnnrly tab lists the session under Sessions.

What a plan gates

The tab needs a plan — an individual plan, or a seat on an organization's. It is part of your issue tracker in Plexus, the same thing a plan unlocks for GitHub issues and boards: listing, opening, editing, commenting, creating, moving cards and starting or completing sprints all go from your machine to Plnnrly with your own sign-in, and every one of them is behind that gate.

Related

• Toolchain — attaching tools at the workspace or the project
• Issues — the same thing for a repository's GitHub issues
• Sessions & worktrees — the session a work item starts, and the sidebar that shows it
• Settings — the Integrations page
• Plans, seats and billing — what a plan unlocks