Your Jira and GitHub issues, ranked with everything else.

Connect Jira, GitHub and Slack. Import the issues you choose and read Slack channel activity as signals. Each one runs when you ask; nothing syncs in the background. Integrations come with the Individual and Business plans.

The panel is the import flow: tick what should land, settle the one conflict, apply. Nothing moves until you do.

GitHub · acme/billing · preview
5 issues · 1 need you
2 new · 2 updated

Three connections.

Available now

GitHub

Import the issues you choose, preview updates before they land, and keep the repository as the system of record.

Individual and Business plans.

Available now

Jira

Bring selected issues into a workspace for ranking. Jira keeps the ticket; TaskSaber decides what’s next.

Individual and Business plans.

Available now

Slack

Pick a message in Slack and choose Add to TaskSaber; it becomes one task under your account, linked back to the thread. Name channels to read as signals with a stated rule and a weight. Message text never reaches the browser.

Individual and Business plans.

Preview, then apply.

You run each import. There is no two-way sync, and TaskSaber does not read pull requests or commits.

  1. Choose a sourceA repository or a Jira project the connected account can see.
  2. PreviewNew issues and updates appear as a list before anything changes.
  3. Review conflictsWhere a task and its issue disagree, you decide which wins.
  4. Apply your selectionOnly what you ticked lands. Check for updates when you want them.

Connections belong to the person who authorizes them. Importing into a shared workspace requires that person to have access to the destination; teammates do not inherit the provider credential.

Slack, read as signals.

Name the channels. Three rules, each with a weight you can see, decide what counts, and the strongest signals show on your Insights page. Mark a channel as an incident channel and watch the list change.

Channels you watch
  1. 1.00 An active thread in a channel you marked as an incident channel
  2. 0.70 A thread of 3 or more people that mentions you
  3. 0.45 A message that mentions you
Signals · strongest first
  • 0.704 people discussing this in #payments12m ago
  • 0.45You were mentioned in #design3h ago

This list is what the app shows on Insights. Signals never change a task’s score; you decide what to act on. Message text is read on the server and never sent to the browser; the app receives a label and a weight.

You choose a message; TaskSaber makes it a task. From any message’s menu, Add to TaskSaber opens a short form (title, project, due date) and files one task under your account with a link back to the thread. TaskSaber never reads your channels to invent tasks, and only the person who connected Slack can use the shortcut.

Read the permission grant.

What GitHub is asked for

Classic repo scope includes write permissions; TaskSaber uses read operations. Review the provider consent screen before connecting. Removing a connection from TaskSaber is not proof that the provider has revoked the grant; check the provider’s own settings too.

Slack activity stays in context

TaskSaber reads activity only in the channels you name, and only as signals with a stated rule. Signals inform you; they never change a task’s score on their own. Anything untouched for 24 hours drops out.

Integrations are optional. TaskSaber uses an account and stores your workspace on our servers. Your browser or app may keep a local cache. An internet connection is required to sign in and sync.

Integrations · TaskSaber