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.

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.