Atono now connects more directly to your development workflows with the launch of our Model Context Protocol (MCP) server, expanded REST API capabilities, and new GitHub commit linking. Together, these updates strengthen automation and transparency across AI-assisted work, integrations, and code activity.

Introducing the Atono MCP server

Your AI coding assistant can now talk directly to Atono.

The Atono MCP server connects tools like Claude, Windsurf, Cursor, and VS Code with GitHub Copilot straight to your backlog. Your AI assistant can read stories and bugs, update workflow steps, manage assignments, and document fixes without leaving your editor.

How teams use it:

• Developers pull acceptance criteria while coding, update story status after pushing changes, or document bug fixes automatically.
• QA engineers access bug reproduction steps and acceptance criteria, then update status as they verify fixes.
• Product managers summarize completed work or check status across teams without leaving their AI workspace.
• Documentation and marketing teams generate changelogs and feature content based on what actually shipped.

See when MCP works on your behalf

Actions performed through the MCP server now appear in Activities with a unique icon and tooltip labeled “Performed by MCP server.” This lets teams trace which changes came from their AI assistant, keeping automation visible and accountable.

For configuration details across different AI coding tools—and a full list of the Atono tools available through the MCP server—see the help documentation.

GitHub commit linking

Atono now links pull requests to stories and bugs when backlog item IDs appear in commit messages, extending the existing GitHub integration. Previously, PRs were detected only when an item ID (like STORY-123 or BUG-456 appeared in a pull request’s title, description, branch name, or comments.

With this update, commit messages are included too—so links appear as soon as code is committed, even before a PR is opened. That means teams can see development activity sooner and stay aligned from commit to release.

Expanded REST API endpoints

Story and bug endpoints in the Atono API now include workflow step information, giving integrators the context they need to build smarter automations. The GET stories endpoint also returns an HTML version of each story, supporting richer integrations with tools that use formatted content.

Two new endpoints—GET workflow step and GET workflow steps—let integrations understand team workflows directly, so automation stays aligned with how each team actually works.

Understanding who’s using your features and how that changes over time helps your team learn from real behavior. This release adds a Top customers view to a story’s feature engagement, showing usage by customer alongside the existing environment view.

Top customers

Feature engagement now defaults to showing usage by customer, helping you identify your most engaged users and understand adoption patterns across your customer base. It highlights the top 10 customers for each feature, showing who’s interacting most and who’s best positioned to provide meaningful feedback.

You can select a graph type to visualize your data:

• Bar chart: shows total usage counts for the selected period. It’s a quick way to see which customers use a feature most.

• Line graph: tracks engagement trends over time for each customer. Toggle individual customer lines on or off to focus on specific segments, and filter by location or environment to see how adoption varies across different contexts.

These views work together to reveal both overall usage and engagement trends, helping product and customer teams connect real adoption with customer insight.

Backlog management and day-to-day planning now flow more naturally with clearer separation between planning and active work, faster loading, and new controls for prioritization and visibility. These updates help teams stay organized and responsive as their backlogs grow.

Dedicated Backlog and In progress pages

Your team now has two focused pages for managing work:

• Backlog - everything in To do, designed for prioritization, sprint planning, and release planning.
• In Progress - all active work across workflow steps (formerly called Backlog), including the top 20 items from To do for visibility into what’s next.

This separation reflects how teams naturally plan and deliver work—keeping long-term planning out of the way of day-to-day execution. It also lays the groundwork for upcoming sprint and Kanban capabilities that will build on these distinct spaces.

Cleaner, faster board and list views

To keep performance high and maintain focus on current work, Atono now limits how many items appear at once in several places:

• On the In progress page, the To do step shows only the first 20 items from the Backlog. A quick link takes you to the Backlog page if you need to see all items.
• Workflow steps in the Done and Won’t do categories display only the 20 most recent items. A quick link from any of these sections opens the Everything page filtered to the same team and workflow step when you need full history.

Board and list views also load faster overall, so even as your backlog grows, planning stays responsive.

Add items to the top of your backlog

You can now add new stories directly to the top of the Backlog and In progress pages, making it faster to place work where it belongs.

As you’re reprioritizing, you can also right-click any existing backlog item and choose Move to top to bump it into the first position—no dragging required.

Duplication improvements

You can now duplicate stories and bugs from any workflow category, including Done and Won’t do. This makes it easier to reuse well-defined backlog items without recreating them from scratch.

When duplicating items, the workflow step, timebox, and assignee are cleared so the new item starts fresh in Story refinement or Bug triage. All other fields, like title, description, and acceptance criteria, are carried over exactly as before.

Customize what details you see

Settings menus on Backlog and In progress pages now show only the options relevant to each view. Both include new toggles for Story size and Risk rating, with preferences saved per team to maintain the right level of detail for your workflow.

More precise date and time filters

You can now filter by exact times—not just dates—when narrowing results by Created, Last updated, or Completed. Start and end times can also be left open for broader searches—for example, view everything updated after 3 p.m. yesterday without setting an end time.

Relative date filters like today, yesterday, this week, or last month make it faster to find recent activity without manually setting ranges. These filters stay relevant over time, so saved filters using relative dates continue working as expected.

This gives you more control when reviewing activity within a specific window, comparing updates across time zones, or quickly accessing common date ranges your team uses regularly.

Atono’s AI support continues to evolve, with updates that help you triage faster and make Capy feel more like part of the team.

Suggested risk ratings for bugs

When triaging a bug, you can now click ✦ Rate it for me to have Atono suggest probability and impact values based on similar issues your team has rated before.

Each suggestion includes a short explanation, so you can understand the reasoning and adjust either value before saving. It’s a faster way to reach consistent, informed triage decisions—without losing human judgment.

A smoother Ask Capy experience

Ask Capy now opens in a partial-screen window, so you can keep working while checking answers. You can view cited sources, interact with the rest of Atono, and return to your chat anytime before it times out. Starting a new conversation is also clearer, with simpler options for ending or resuming chats.

Shipping is just the start. These updates help you see how features are used once they’re live and refine how they’re released—so you can learn faster and improve with every rollout.

Do even more with feature engagement

Last release, we introduced Feature engagement—a way to see whether shipped features are actually being used. From a story, you can display a usage graph that shows adoption trends over time and how they vary across environments, customers, and locations.

This release adds two major enhancements:

Spot your most-used features

The new Engagement page highlights your ten most-used stories. Adjust the timeframe or filter by product theme, team, environment, customer, location, or completed date. The graph updates instantly to show the top features in your selection, helping you see where usage is strongest and how it shifts across segments.

Map user engagement without code

Once the Atono SDK is set up, there’s no additional developer work required to capture user engagement. With this release, the Atono Chrome extension now enables product managers and other non-technical roles to map a click in your product directly to a story. Every subsequent click is tracked as usage in Atono, tying real interactions back to the work that delivered them.

Cleaner slice defaults

When configuring a feature flag, the default condition now appears last in the list of slices. Because slices are checked first and the default only applies if none match, this order makes rollout plans read chronologically so they're easier to understand at a glance.

If you’ve been considering a move away from Jira, you don’t have to leave your work behind. With our Jira import, you can bring your stories and bugs into Atono with their history intact—titles, descriptions, statuses, assignments, and comments all come with you.

That means your team keeps the context that matters while moving into a tool built for modern, cross-functional teams. Instead of managing complexity, you get a backlog that’s easier to understand, easier to share across roles, and better suited for planning and building together.

Highlights

• Team assignments preserved: Jira users and teams are matched or created in Atono. If you don’t have enough seats, assigned users are imported as inactive and you can invite them later.
• Workflows aligned: Jira statuses are mapped to Atono’s To Do, In Progress, and Done categories, so work carries forward in the right place.
• Risk ratings unlocked: Jira bug priorities are translated into probability and impact, which Atono uses to calculate risk.
• Duplicate handling built in: If duplicates from earlier imports are detected, Atono flags them and lets you decide whether to import again or skip.

The result is a clean handoff: your work comes with you, the clutter stays behind, and your team gets a backlog designed for how you actually build.

We’ve made backlog items easier to write, review, and connect across your workflow— rom capturing different perspectives to adding richer context and improving how key details are referenced.

Write multiple user stories per story

Features are often used by more than one type of user. You can now capture those different perspectives in a single story by including multiple user stories. This shared context gives teams a fuller picture of how a feature should work and helps guide better decisions.

Enhanced product themes

Product themes now support descriptions, making it easier to explain their goals. You can also navigate directly from a story to its theme for context, and the product themes list is sorted by recent activity so the most relevant ones stay visible. These changes make product themes clearer and more practical for grouping stories around broader objectives.

Improved acceptance criteria highlighting

When you open a link to a specific acceptance criterion, Atono highlights it clearly and keeps that highlight visible long enough for you to spot it quickly—even when a story has many acceptance criteria. That makes it easier to find what’s being discussed and keep collaboration focused on the right details.

Automatically link stories and bugs in comments and activities

Building on last release’s automatic linking in descriptions, acceptance criteria, and other freeform text, Atono now also links story and bug IDs (like STORY-123 or BUG-456) in comments and activity entries. That makes it faster to navigate between related work and trace context across backlog items without breaking your flow.

We’ve refined key parts of planning to make it easier to understand scope, spot stalled work, stay focused on what’s current, and keep your workspace responsive as it grows.

Assigned to me staleness indicators

Items assigned to you that have gone stale now show a clear indicator in the Assigned to me widget on the Home page. It’s an at-a-glance reminder to follow up on work that hasn’t moved recently, helping you stay on top of what needs attention.

Story point totals in timelines

Story point totals now appear directly in timelines and timeboxes, giving you visibility into total scope alongside your release plans. This makes it easier to gauge workload, compare it against past velocity, and project how much your team can deliver in upcoming releases.

Faster board and list views

Board and list views now load faster, keeping planning and refinement quick and responsive—even as your workspace grows. It’s part of our ongoing focus on speed, so larger backlogs don’t slow your team down.

Timeline auto-scroll

Timelines now open with today’s work or the nearest timebox already in view, giving you instant context and keeping the focus on what matters most.

See how often users interact with a feature—right from the story it was built from.

You can now display a usage graph on stories to show how frequently a feature is used over time, across different environments, with filters for customer and location to reveal adoption in different segments.

Use Feature engagement to:

• Confirm that shipped features are being used as intended—or spot where they fall short
• Detect drops in usage after a release or change
• Identify engagement patterns across environments, customers, or locations
• Prioritize high-use features for future investment—and reconsider those with low engagement

Tracking is powered by the Atono SDK and takes just a few lines of code. Once set up, your developers can include a usage call for each feature with its story ID (for example, STORY-123).

Because it’s built into Atono, you can skip external tagging tools or disconnected dashboards—keeping all your data in one workflow and visible to your entire product team, not just those with access to an external tool.

We’ve added three new AI-powered features that surface helpful suggestions—right where you’re already working. Whether you’re sizing a story, linking related work, or reporting a bug, these enhancements help you move faster and make informed decisions without breaking your flow.

Suggested story size

On request, Atono can suggest a size for a story by comparing it to similar past work.

It shows examples of stories that were smaller, larger, or about the same—so you can see how it reached that estimate. You can accept the suggestion, skip it, or review it alongside your team’s estimate to see how they compare.

Suggested links

When you open the Linked items section in a story, bug, or draft, Atono now adds a set of suggestions to the top. These highlight items that might be related based on content, context, and past patterns. Suggestions appear alongside recently created work, making it easier to find and link related items without searching.

Similar bug suggestions

Whether you're drafting a new bug or editing an existing one, Atono checks your backlog for similar reports and surfaces them automatically.

If there's a potential match, you can:

• Stop typing and use the existing bug
• Link them if they should be addressed together
• Dismiss the suggestion if it’s not a match

These suggestions reduce duplicate work and keep related bugs connected so they can be resolved more efficiently.