Sprint planning and tracking are more powerful this release, with dedicated calendars, burndown charts, and sprint-optimized views. When creating a team, you now choose between Scrum and Kanban workflows—so your tooling matches how your team works.

Plan and manage sprints from your backlog

For Scrum teams, the Backlog view now organizes work by sprint, letting you plan sprints, manage scope, and view capacity at a glance. Current and upcoming sprints appear in order, with names, dates, item count, and total story points visible—so commitments are clear without switching views. Items not assigned to a sprint appear in an Unscheduled section below planned work.

Drag items into sprints, move work between sprints as priorities change, and create new sprints as needed. Atono prevents overlapping sprints and warns when scope or duration changes mid-sprint, helping protect burndown accuracy.

Focus on current work

The In progress view shows only your current sprint, creating a focused workspace for daily execution. Track what’s committed, monitor progress, and adjust work as needed to achieve your sprint goal. From the same view, you can edit sprint details and check the burndown chart—keeping everything you need for the current sprint in one place.

See progress with burndown charts

Burndown charts show whether your sprint is on track. They plot daily progress against a guideline and project your finish date based on actual velocity—helping teams spot early signs of underestimation, discovery, capacity changes, or shifting priorities while there’s still time to respond.

Hover over any day to see points completed, remaining work, and how far ahead of or behind schedule you are. Historical burndown charts support retrospectives and velocity planning for future sprints.

Sprint calendar for timeline planning

Scrum teams also get a dedicated Sprint calendar to visualize all sprints on a timeline, plan releases, spot capacity constraints, and communicate projected delivery dates to stakeholders.

The calendar prevents overlapping sprints as you adjust dates, shows weekday counts while dragging sprint edges, and lets you rename sprints inline.

Switch workflows as your needs change

You can switch teams between Scrum and Kanban workflows after creation, so your tooling adapts as your process changes. You’re not locked into a choice—when your teams’ needs change, Atono adapts with you.

Teams can now sign in using their company’s identity provider instead of email login links. SAML-based SSO centralizes access management, strengthens security, and supports enterprise compliance.

Workspace administrators can validate the SSO setup in a testing mode before enabling it for the full team. Setup instructions are provided for Okta, with support for other SAML-compatible identity providers.

Single sign-on is available for paid workspaces. Contact your workspace administrator to enable it.

Stay updated on specific stories and bugs without constantly searching or trying to remember where you last saw them.

Stay on top of what matters

Click the Follow icon on any backlog item to start tracking it.

Followed items appear in a dedicated widget on your homepage, sorted by recent activity, so updated work rises to the top automatically.Use it to keep track of work owned by other teams, requested features, or bugs affecting your customers—all from your dashboard.

Find and manage followed items

Filter the Everything page to see only items you're following, or add the Following column to spot tracked work across your entire backlog. Your view preferences stay with you across sessions, so your workflow stays consistent.

See exactly where each activity came from—whether it was performed in the Atono interface, triggered by an integration, sent through the API, or completed by the MCP server. You can filter the Activities list by source to focus on specific origins.

Source filtering helps when reviewing imports, debugging automation, or understanding how different tools and AI-driven actions are affecting your backlog.

Common planning tasks get faster with tools that help you break down work, organize around themes, and understand bug priority at a glance.

Split stories faster

Break large stories into smaller ones without losing context. The new Split story feature lets you move selected acceptance criteria into a new story, with key details—like team, product theme, and timebox—carried over automatically.

When you split a story, Atono links the original and new story for traceability, and records the split in the Activities list. New stories appear at the top of your backlog (or in the same sprint for Scrum teams), keeping backlog refinement fast, work connected, and stories small and focused.

Bulk organize by product theme

Select multiple stories and assign them to a product theme in one action. This lets you group related work around strategic initiatives without editing items one at a time.

See bug status during triage

Bugs that aren’t yet assigned to a team backlog now show their triage state (Reported, More info required, Won't do) throughout Atono, giving teams clear context when reviewing new reports and deciding what to assign.

This release includes several updates to Feature engagement that give teams more control over how usage data is tracked and displayed.

Control feature engagement visibility

Show or hide the Feature engagement section on individual stories depending on what you need to see. When engagement data is relevant, use the graph icon to jump directly to it. When it’s not, hide the section to keep the story focused on work details.

Your visibility preferences are saved per story and persist across sessions, so stories stay configured the way you left them.

Remove mapped actions from stories

Actions mapped using the Atono Chrome extension can now be removed from a story’s Feature engagement settings, making it possible to correct mistakes or stop collecting data for actions that are no longer relevant.

When an action is removed, Atono stops collecting new engagement data for that action. Any historical usage remains available in charts and reports unless it’s cleared.

A set of focused improvements across Atono that make navigation, visibility, and everyday actions clearer and faster.

Jump to search instantly

Press Cmd-K (Mac) or Ctrl-K (Windows/Linux) from anywhere to open search, without breaking your flow.

Filter with fewer clicks

Filters now open with all options visible, so you can narrow results immediately instead of drilling into search fields first. Multi-select checkboxes and an optional search make it faster to refine results as you work.

Discover attachments more easily

New visual cues clarify where attachments can be added—whether you’re creating a draft, updating an existing item, or attaching files to specific acceptance criteria.

A paperclip icon in the header and inline prompts in drafts indicate the appropriate place to add attachments, helping ensure files are associated with the right part of a story.

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.