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.

We’re continuing to invest in Atono’s planning tools, making it easier to track progress, coordinate timelines with release dates, and refine the data behind your estimates. These updates are part of a series of enhancements you’ll see throughout the year to help your team plan with clarity and confidence.

Total story points

Total story points show the combined size of all visible stories in a list, helping you gauge work in progress, spot overloaded workflow steps, and compare upcoming plans to your team’s usual capacity.
You’ll see these totals in the team backlog step headers and at the top of the Story size column on the Everything page.

What about unsized stories?
If a story doesn’t have a size, Atono estimates one based on the average size of completed stories from the team’s current cycle time window. This keeps totals consistent and easy to interpret—even when some work hasn’t been sized yet.

Mark releases on your timeline

Add release markers to show key launch dates right on your timeline. Each marker appears as a vertical line, making it easy to see and coordinate work against upcoming releases. You can add, rename, move, or delete markers directly on the timeline. They snap to gridlines and timebox boundaries based on your zoom level—keeping release dates anchored to your schedule.

Customize your team’s cycle time window

Cycle time tracks how long it takes your team to finish work. It’s average helps Atono estimate completion dates, highlight outliers, and spot changes in your team’s velocity.

You can now choose the window used to calculate that average:

• Stick with the default 6-month view
• Select a rolling window from 1 to 12 recent months
• Set a specific start date

This flexibility lets you adjust metrics when your workflow or resourcing changes—so your data reflects how your team works today.

We’ve introduced several updates to make creating and refining backlog items smoother and more efficient—whether you’re drafting a story, documenting a bug, or updating existing work.

Manage version history for stories and bugs

You can now review and restore previous versions of a story or bug.

Open Version history to see a full list of past versions, each showing what changed and who made the update. Click through versions to edits, then restore an earlier version if needed—it’ll appear as a new update in the Activities list, keeping your team aligned as work changes over time.

Automatic links for stories and bugs

References to story or bug IDs (for example, STORY-123 or BUG-456) in descriptions, acceptance criteria, and other freeform text are now automatically turned into links to that item in Atono. Each link shows the item type, ID, and title—and hovering lets you see key details like team, assignee, and workflow step without opening the full item.

Use your right-click menu in ACs

Right-click directly in an acceptance criterion to open your operating system’s context menu, giving you quick access to spelling suggestions, dictionary lookups, and other tools—without losing Atono’s own menu options.

Reorder attachments

You can now drag attachments into the order you want in a story or bug, making it easier to arrange images to show user flows in sequence or list reproduction steps clearly—so reviewers see the right context in the right order.

Thinking about trying out Atono? You can now import your Linear issues to see how your team’s actual data fits our way of working.

Upload a Linear CSV export and Atono will guide you through the process—mapping teams, users, issues, and product themes automatically. You’ll get validation upfront, options for handling ambiguous or duplicate items, and a preview before finalizing the import.

Highlights:

• Mapped, not messy data: Teams, users, and product themes are automatically matched or created—avoiding duplicates and keeping your setup clean.
• Smart item type detection: Atono uses your labels to classify items as stories or bugs, with the option to skip or reclassify anything unclear—so nothing ends up in the wrong place.
• Structure preserved: Original statuses, timestamps, and assignees are respected. Workflow steps are inferred from your data and adjusted to fit Atono’s model.
• Support for seat limits: If you don’t have enough seats, assigned users are imported as inactive—so you preserve assignments and can invite teammates later when there’s space.

You’ll also find helpful tips for preparing your data beforehand—so things land where they should, with less cleanup afterward.

You can now programmatically access and manage your Atono data using our public API—making it easier to automate workflows, connect with other tools, and customize Atono to fit the way your team works.

Whether you're building internal tools, syncing data across systems, or just prefer to script instead of click, the API gives you structured, authenticated access to your stories, bugs, users, teams, and feature flags.

Use it to:

• Flip feature flags programmatically
• Create or update stories and bugs from other systems
• Retrieve stories or bugs using filters like team, assignee, or date
• Synchronize users and teams with other systems

Authentication is handled with personal API keys tied to your account. You’ll only be authorized to access what you already have permission to see or edit in the Atono web UI.

Want to explore before writing code?
You can try out any endpoint right from our API docs using the Try It! feature—just enter your API key to start exploring live data and responses.

This is just the beginning. More endpoints and capabilities are on the way. Have a use case in mind? Let us know in the community—we’d love to hear what you're building.

You can now integrate GitHub with Atono to see pull requests directly on the stories and bugs they’re connected to—so you always know what’s in flight, what’s been reviewed, and what’s been shipped.

When a PR mentions an Atono item ID (like STORY-123 or BUG-456) in its title, description, branch name, or (optionally) a comment, it’s automatically linked. Atono shows the number of linked PRs on each item, and clicking reveals details like title, status, assignee, and build state—all without leaving Atono.

Highlights:

• See what’s happening in GitHub—right from your backlog. Pull request icons appear in the item detail, and backlog, with full status at a glance.
• Automatic linking that just works: Mention an Atono ID in your PR, and it links to the right item in Atono.
• Clear activity history: Key GitHub events—like PRs being opened, merged, or closed—are recorded in the item’s Activities history.
• Bi-directional awareness: Atono also comments on the PR in GitHub, linking back to the story or bug that motivated the change.
• Control over setup: Choose which repositories to connect and whether to scan PR comments

This keeps planning and development connected—so your team can track progress without switching tools.

Answers for every role—straight from your shipped work.

Ask Capy is a new assistant that reads through completed stories and bugs to help your team understand how features work, what decisions were made, and why things behave the way they do. Just ask your question in natural language—Capy finds the relevant work and shows its sources, so you can explore or verify as needed. It’s built for the moments when you need clarity—without guessing keywords or waiting on someone else to respond.

Here’s how Capy helps:

• Developers can find out how a feature was implemented without pinging a PM or digging through old stories.
• Product managers can revisit past decisions and spend less time answering questions that teammates can now look up themselves.
• QA can see what was intended behavior, helping them identify true bugs and avoid false alarms during testing.
• Support engineers can tell whether a customer-reported issue reflects intended behavior—even if they weren’t involved when the feature was built.
• Incident responders can quickly get context during triage—especially when the right expert isn’t available or ownership is unclear.

Capy also helps new teammates in any role ramp up faster by showing how things were built, without taking time from the rest of the team.

Get early access

We’re still refining how Capy interprets questions and reads your backlog, so we’re rolling it out gradually. Want to try it? Contact us in #support in the community and we’ll get you set up.

You can now add freeform text to the end of any story—perfect for context that doesn’t belong in the user story or acceptance criteria. Use it for notes, references, or any other supporting details your team needs to track.

This new section supports rich text formatting and comments. It’s included in global search results, and changes are recorded in the story’s activities history.

To access it, just click below your acceptance criteria—or press return or the down key after the last one in the list.

You can now search all your backlog items from anywhere in Atono. Just start typing in the new search bar in the header—results update in real time and include stories and bugs from team backlogs, bug triage, and story refinement.

Search looks across titles, IDs, descriptions, user stories, acceptance criteria, and comments (excluding resolved or rejected ones). Results are ranked by relevance, with exact ID matches always at the top.

Highlights:

• Smart keyword matching: Supports fuzzy matching—so even if you make a typo or aren’t sure of the exact phrasing, relevant items will still show up.
• Recent searches: Revisit your last 10 searches, with filters automatically reapplied.
• Filters: Narrow results by team, workflow step, risk, environment, and more.
• Typeahead suggestions: Predictive text helps you find what you need faster.
• Keyboard shortcut: Use Cmd/Ctrl+K to jump to search without touching your mouse.