GitHub
Import the issues you choose, preview updates before they land, and keep the repository as the system of record.
Your issues and threads, 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.
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 you2 new · 2 updated
Three connections.
Jira
Bring selected issues into a workspace for ranking. Jira keeps the ticket; TaskSaber decides what’s next.
Slack
Name the channels to read. Threads there become signals with a stated rule and a weight; the strongest one lifts the linked task. Message text never reaches the browser.
Preview, then apply.
You run each import. There is no two-way sync, and TaskSaber does not read pull requests or commits.
- Choose a sourceA repository or a Jira project the connected account can see.
- PreviewNew issues and updates appear as a list before anything changes.
- Review conflictsWhere a task and its issue disagree, you decide which wins.
- 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. Mark a channel as an incident channel and watch the signal, and the linked task’s score, change.
Channels you watch
- 1.00 An active thread in a channel you marked as an incident channel
- 0.70 A thread of 3 or more people that mentions you
- 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
89Fix the double-charge on 3 customer accounts linked to #payments+5
The strongest signal lifts the task’s context factor by at most 7.5 points. Message text is read on the server and never sent to the browser; the app receives a label and a weight.
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. A busy channel does not change every task’s priority, and 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.