Link with a task key
Refer to the Taskonio key in development work so the branch or pull request has an explicit connection to the task.
The task explains why. The pull request shows how.
Connect GitHub branches and pull requests to the Taskonio tasks they implement. Keep development context close to the specification, without asking everyone to search the repository for an update.
Why it matters
Make the work clearer, not heavier.
A task can explain the intended change while the implementation lives somewhere else. Without a clear link, reviewers search for the specification and teammates ask which pull request belongs to which ticket. Task keys connect those two views of the same work.
Designed around the way real teams decide and deliver.
Keep context together
Find the branch and pull-request context alongside the task’s description, properties, and discussion.
Scope it to the team
Organization access and team-space repository mapping keep setup tied to the repositories the team uses.
A closer look
Connect the implementation to its original intent.
01
Start with organization access
An organization admin starts the GitHub connection from Organization Settings. Complete the provider installation with the person who can approve access to the GitHub organization and its repositories.
- Open Organization Settings, then Integrations
- Connect GitHub with the required provider permissions
- Review which repositories the connection can access
02
Map repositories to the right team space
Once the organization connection is available, the team-space owner configures GitHub in Teamspace Settings. Map the relevant approved repositories so development activity has a clear home in Taskonio.
- Open Teamspace Settings, then Integrations
- Choose from the repositories available to the organization connection
- Check local workflow settings with the team-space owner
03
Use the task key in the work
Reference the existing Taskonio task key in the branch or pull-request title. For example, a task keyed DEV-301 could use a branch named DEV-301-workspace-permissions. Copy the real key from your task rather than relying on a similar title.
- Create or identify the Taskonio task first
- Use its exact task key in the branch or pull request
- Verify that the development activity appears on the intended task
04
Review the context without losing the specification
Open the Taskonio task to see the linked development context alongside the original request. Continue code review in GitHub and use Taskonio for ownership, acceptance criteria, and planning. A linked or merged pull request is not, by itself, proof that every part of the task is complete.
- Keep the specification and discussion attached to the task
- Follow the branch or pull request for development detail
- Check the team’s completion criteria and configured status rules
How it works
From setup to useful work.
- 01
Connect GitHub
An organization admin sets up provider access and reviews the available repositories.
- 02
Map the team’s repositories
A team-space owner configures the connection for the repositories their team uses.
- 03
Reference the task
Use the task key in the branch or pull request, then check the linked context in Taskonio.
Taskonio’s approach
A connection, not a second code-review tool.
Keep implementation and review in GitHub. Bring the branch and pull-request context back to the task so engineers and their teammates can connect the change to the reason for making it.
- Starting point
- An existing Taskonio task and its task key.
- Development context
- Linked branches and pull requests.
- Organization setup
- Provider access managed by an organization admin.
- Team setup
- Repository mappings configured in Teamspace Settings.
- Working boundary
- Code review stays in GitHub; task ownership and planning stay in Taskonio.
Compare this workflow with the tools your team already knows.
Taskonio vs JiraNeed sprint planning, not a configuration project? Compare Taskonio’s built-in workflow with Jira’s deeper customization and governance.Read comparisonTaskonio vs TrelloOutgrowing a board? Add a backlog, sprint planning, estimates, and epics with Taskonio, or keep Trello’s open-ended lists and cards.Read comparisonTaskonio vs NotionCompare an opinionated engineering workflow with a flexible workspace that combines databases, documents, knowledge, projects, and AI.Read comparison
Considering another tool? Explore the full set of guides to find the right fit for your team.
View all comparisonsRelated features
Keep exploring the workflow.
Sprint planning
Sprint planning that doesn’t slow you down
Plan sprints in minutes with three focused modules - Backlog, Planning, and Sprint - plus live scope totals and flexible views for every planning conversation.
ExploreTask view
The context belongs with the task
Keep the description, attachments, links, sub-items, comments, and task activity together. Open the work and get the information needed to move it forward.
ExploreSlack integration
Work moves in Taskonio. Your team hears about it in Slack.
Receive Taskonio updates directly in Slack. Keep your team informed where the conversation happens, while tasks and planning stay in Taskonio.
ExploreQuestions
Know before you switch.
What does Taskonio’s GitHub integration connect?
It connects branch and pull-request activity to existing Taskonio tasks. The task remains the place for the specification, owner, properties, and planning context.
How do I link a pull request to a Taskonio task?
Use the exact Taskonio task key in your branch or pull-request title, in a repository configured for the team space. Then open the task and verify that the intended development activity is linked.
Who can set up the GitHub integration?
An organization admin connects GitHub and manages provider access. A team-space owner then configures the available repositories in Teamspace Settings. GitHub may require approval from someone with the appropriate organization or repository permissions.
Why is a repository missing from the team-space settings?
Ask the organization admin to check whether the GitHub connection has access to that repository. The team-space owner can then review its mapping. A team-space mapping does not itself grant access to a repository the provider connection cannot use.
Is this the same as syncing GitHub Issues?
This page describes linking GitHub branches and pull requests to Taskonio tasks, not a two-way GitHub Issues sync. Keep your Taskonio task as the reference for the work being implemented.
Do we need Slack or MCP connected as well?
No. The GitHub integration connects development activity independently. Slack delivers Taskonio updates to your team, while MCP lets an authorized AI client work with Taskonio tools.
Keep the reason and the implementation connected.
Plan the task in Taskonio. Link the development work in GitHub.