The GitHub integration automatically links pull requests to stories or bugs that are mentioned by ID (like STORY-123 or BUG-456) in the PR title, description, branch name, or (optionally) comments. Linked PRs appear across Atono, with quick access to GitHub and full history in the item’s Activities list. Atono also adds a comment in GitHub linking back to the associated story or bug—so both tools stay in sync.

📘
Enable the integration for your workspace
A Workspace Owner or Administrator must enable the GitHub integration for your Atono workspace before you can view pull requests for your Atono stories and bugs.

What appears in Atono

When a pull request is linked to a story or bug, Atono shows a pull request icon in the item header and optionally in list and board view.

Clicking the icon in a story or bug opens the pull request list for the item. You'll see:

A count of all associated pull requests, grouped by status.
Details for the six most recent PRs, showing:
- Title
- PR number
- Status (open, merged, or closed)
- Assignee
- Build status (pending, passed, or failed)
- Relative creation time

You can click any pull request in the list to open it directly in GitHub.

Where pull requests appear in Atono

Once a pull request is linked to a story or bug, a PR icon appears in Atono—making it easy to see which items have development activity.

Stories and bugs

When a pull request is linked to a story or bug, you’ll see a pull request icon in the item’s header. Clicking the icon opens the pull request list for that item.

Pull request activity—like opened, merged, or closed—also appears in the item’s Activities list, alongside comments and status changes.

Board and list view

You can enable or disable pull requests from being included in a team's list or board view.

Open a team backlog in list or board view.
Click the settings (gear icon) in the backlog header.
Select or clear the Pull requests checkbox.

Once enabled, you’ll see a pull request icon on each item that has linked PRs. If an item doesn’t show an icon, it has no linked pull requests.

How Atono links pull requests

Atono detects item IDs (like STORY-123) in the following pull request fields:

PR title
PR description
Branch name
PR comments (optional)

Atono always monitors the title, description, and branch name—these fields are required and can’t be turned off. Workspace Owners and Administrators can choose whether to also include PR comments in the integration settings.

Changes to pull request fields will update linking in Atono automatically, though updates may take up to 12 hours to appear.

Timing and sync behavior

When pull requests get linked

Atono only begins linking pull requests after the GitHub integration is enabled for your workspace. Pull requests created before enabling the integration—or during a time when the integration is disabled—are not linked retroactively.

After re-enabling the integration

After the integration is re-enabled, Atono resumes syncing pull requests—but only when there’s new activity on a pull request in GitHub, such as a comment, commit, or status change. This activity triggers a refresh, allowing Atono to detect item IDs that may have been added earlier—before the integration was enabled or while it was disabled. The new activity itself does not need to contain the item ID. If a pull request remains inactive, it won’t be picked up.

Switching GitHub organizations

If you disable the GitHub integration and later enable it with a different GitHub organization, any previously linked pull requests from the old organization will still appear in Atono. These links aren’t removed automatically. New pull requests from the newly linked organization will be added normally when activity occurs in GitHub.

Deleted GitHub repositories

If a linked GitHub repository is deleted, Atono does not remove the associated pull request links. The PRs will still appear on stories and bugs. However, the links may no longer work, and Atono doesn’t indicate that the repository was removed.

GitHub comments linking back to Atono

When a pull request is linked to an Atono item, Atono adds a comment to the PR in GitHub with a link back to the story or bug. This gives developers visibility into the work driving the change—without leaving GitHub.

Integrate GitHub with your workspace (Administrators)

Only Workspace Owners and Administrators can enable or disable the GitHub integration for a workspace.

Enable the GitHub integration

A Workspace Owner or Administrator must enable the GitHub integration for the Atono workspace before users can view GitHub pull request activities in their stories and bugs.

In the Atono workspace header, click your workspace name and select Settings.
Under Integrations, click GitHub.
Click Enable.
On the installation screen, select your GitHub organization.
Follow the instructions to select which GitHub repositories you'd like the Atono app to have access to.
Review the requested GitHub permissions, then click Install (or Install & Request, depending on your access level).
On the Enable GitHub for Atono confirmation screen, click Enable GitHub integration.
By default, the integration checks for Atono item IDs in the PR title, PR description, and branch name. To also check comments, enable the Comments (optional) checkbox, then click Save configuration.

Disable the GitHub integration

In the Atono workspace header, click your workspace name and select Settings.
Under Integrations, click GitHub.
Click Remove.
In the Remove GitHub integration dialog, confirm by clicking Remove GitHub, or click X to cancel.

Troubleshooting tips

Not seeing pull requests in Atono? Here are a few things to check:

Integration not installed? A Workspace Owner or Administrator must enable the GitHub integration before PRs can be linked.
Pull request icon missing on a story or bug? Make sure the item ID (like STORY-123) appears in the title, description, or branch name of a PR in a connected repository.
Icon not showing in list or board view? Check the team backlog settings and ensure Pull requests is selected.
Comment-based links not appearing? PR comments are only scanned if that option is enabled in the integration settings.
Recent updates missing? Pull request changes—such as new links or status updates—can take up to 12 hours to appear.