It joins the toolchain. It does not replace it.

Jira

Jira is how Scrumbee understands the plan: which projects exist, which issues are in play, who they belong to, and how status is moving through the sprint.

• Projects and issue keys
• Status and assignment
• Sprint membership and progress
• Blockers and tickets that have gone quiet

That is what lets a standup mention AUTH-221 instead of a vague “still working on auth,” and what lets a sprint summary count completed versus blocked work.

GitHub

GitHub tells Scrumbee what is happening in the code: repositories the workspace connected, pull requests, commits, and review activity around that work.

• Repository context
• Pull requests and their state
• Commits linked to ongoing work
• Reviews that are still waiting

Development activity is treated as a work signal, the same way a Jira transition is — not as a replacement for GitHub itself.

Bitbucket

Bitbucket covers the same kind of development signal when that is where the team hosts code: repositories, pull requests, commits, and related activity in the connected workspace.

Teams can use GitHub, Bitbucket, or both. Scrumbee maps those events into the same Slack conversation rather than asking anyone to live in a third code host.

Slack

Slack is the room. Scrumbee is installed into the workspace, speaks in the channels you map to projects or repositories, and DMs people when a standup or a follow-up is personal.

Connecting Slack is the starting action. Jira, GitHub, and Bitbucket are authorized afterward so Scrumbee has work to observe. There is no parallel “create an account with email” product.

How those connections are authorized, and which permissions are requested, is documented on Security.