Glossary
Key terms to help you navigate Atono with confidence.
A
Acceptance criteria (ACs)
A set of specific, testable conditions that define when a story is complete. Acceptance criteria describe the expected behavior or outcomes of a feature and are used to validate that requirements have been met. For more details, see Acceptance criteria.
Acceptance criterion (AC)
A single condition that must be met for a story to be considered complete.
Acceptance criterion URL
A unique, persistent link to a specific acceptance criterion within a story. Acceptance criterion URLs remain valid when criteria are reordered, allowing teams to reliably reference specific requirements. For more details, see Copy an AC URL.
Active sprint
The current sprint a Scrum team is working in. Items in the active sprint appear on the team's In progress page and contribute to sprint scope, burndown charts, and velocity tracking. For more details, see Scrum In progress.
Activities
A chronological record of changes to stories, epics, bugs, and feature flags. Activities show what changed, when, by whom, and where the change originated, including updates made with AI assistance. For more details, see Activities.
Additional content
A freeform text section in a story used to capture context that doesn't belong in the user story or acceptance criteria, such as notes, background information, or supporting details. For more details, see Notes and supporting details.
Affected environments
An optional field on a bug that indicates which environments the issue was observed in, such as development, staging, or production. Affected environments help teams understand scope and prioritize fixes appropriately.
AI context
A section on stories and bugs where research, decisions, and implementation details are preserved as work progresses. AI context helps another person or AI tool continue the work with the right background. It includes Design decisions on stories, along with Technical investigation, Technical changes, and QA analysis on stories and bugs. For more details, see AI context.
Analytics
A team-level area that provides reports for understanding how much work a team completes, how long work takes, and how delivery changes over time. For more details, see Analytics.
API key
A user-specific credential used to authenticate with the Atono API. Each API key is tied to a user and can be used to automate tasks or integrate with external systems. For more details, see Manage API keys.
Ask Capy
Atono's AI assistant that answers questions about how your product works, based on completed stories and bugs from public teams. Ask in plain language, and Capy summarizes what it finds and lists the related items as sources. For more details, see Ask Capy.
Assignee
A user assigned to a bug or story, responsible for its completion. This should not be confused with assigning a story or bug to a team's backlog, which refers to associating the work item with a team rather than an individual.
Atono Chrome extension
A Chrome browser extension that lets you report bugs, flip feature flags, and map clicks for usage tracking directly from your application. For more details, see Atono Chrome extension.
Atono MCP server
A server that connects MCP-enabled AI tools to an Atono workspace, so they can read and update backlog items, epics, subtasks, and AI context, and look up information such as timeboxes, team workflows, and the Glossary, using your own workspace access. You can connect through the hosted MCP server or run the server locally with Docker. For more details, see Atono MCP server.
Atono MCP URL
The address you add to an AI tool to connect it to your workspace through the hosted Atono MCP server. You can copy it from the 'MCP connections' section of your Integrations page. For more details, see Connect with the hosted MCP server.
Attachment
An image, video, or file added to a story, epic, or bug. Attachments provide additional context, supporting information, or documentation to help clarify or resolve an issue. They can be inserted inline within the text or uploaded to a designated area below the acceptance criteria. For more details, see Attachments.
Attachment access limited
You can access the most recent attachments in your workspace, based on when they were added. Older attachments are not deleted, but access to them may be limited depending on your plan. If you're on the free plan, you'll be able to access more attachments by upgrading your plan.
B
Backlog
A team page for planning and prioritizing upcoming work before it moves into execution. For Scrum teams, the Backlog is organized around sprints, letting you plan future iterations and manage unscheduled work. For Kanban teams, the Backlog lists every item in the team’s ‘To do’ step, including the 20 shown on the In progress page.
Backlog item
A generic name to refer to a story or bug in Atono.
Backlog management
A team setting that, when turned on, limits who can manage the team’s upcoming stories to its backlog owners, team admins, and people with higher-level workspace roles. For Scrum teams, Backlog management also limits who can manage sprints and move stories into or out of sprints. For more details, see Backlog management.
Backlog owner
A team role responsible for managing a team's planned work. When Backlog management is enabled, backlog owners control which stories are added or created on the backlog, how stories are prioritized in 'To do', and whether stories move into or out of 'Won't do' or are deleted. For Scrum teams, backlog owners also manage sprint planning, including creating and editing sprints and moving stories into or out of sprints. For more details, see Backlog owner.
Board view settings
Options to customize which backlog item details are shown in board view on a team's In progress page and in Story refinement, such as product themes, pull requests, and timeboxes. Available options may vary by team workflow type (Kanban or Scrum).
Bug
An error, flaw, or unintended behavior in software that causes it to function incorrectly or unexpectedly. Bugs are usually reported by users or identified during testing, and they're reviewed and addressed through the bug triage process. For more details, see Bugs.
Bug cycle time
The total time a bug spends in the steps in the 'In Progress' category of a team's workflow. For more details, see Cycle time.
Bug triage
A process where reported bugs are evaluated to determine their severity and priority. The triage process involves setting a probability and impact to provide a risk rating, then assigning the bug to a team for resolution. Bugs that don’t have a team follow a fixed bug workflow with the steps ‘Reported’, ‘More info required’, ‘Won’t do’, and ‘Done’. For more details, see Bug triage.
Burndown chart
A sprint-level chart that shows how many story points remain over time. Scrum teams use it to track progress during a sprint, identify delivery risk, and review how work progressed after the sprint ends. For more details, see Burndown charts.
C
Capy
Atono's mascot, and the embodiment of calm, collaborative energy. Capy is a capybara (the world's chillest rodent) chosen for its social nature, team spirit, and unfazed demeanor. Keep an eye out, since Capy appears in the app, on the website, and at events. In the app, Capy helps you with AI features such as Ask Capy and the Story assistant. For the full backstory, see Meet Capy.
Category
See workflow category.
Comments
Feedback or notes added to a story, bug, or epic to provide additional context or discuss specific details. Comments can be added generally to an item, or directly to highlighted text for easy reference. For more details, see Comments.
Completed
The date an item was last moved into a step in the 'Done' category of a workflow.
Concept
An individual entry in a Product knowledge glossary. Each concept typically includes a name, plain-English description, synonyms, and links to related concepts. For more details, see Product knowledge.
Condition
A condition is used to define a slice for a feature flag. Conditions consist of an attribute (such as Customer or Location), an operator, and a value. They help determine how feature flags are applied to specific users or locations based on the defined attributes.
Configuration
The current setup of a feature flag in a given environment, showing whether it's ON, OFF, or varies based on slicing rules. A flag's configuration determines how and when a feature is delivered to users or systems. For more details, see Flag configuration.
Copy URL
A control that copies a direct link to a story or bug to your clipboard. These URLs are helpful for sharing specific items in conversations or documentation.
Copy ID
A control that copies an item's unique ID (like STORY-123 or BUG-456) to your clipboard. These item IDs are used to link work across Atono and connected tools like GitHub.
Create before
A right-click option that creates a new story directly above the selected item in the list. This option is available in team backlogs and in-progress views, depending on the team's workflow, and in list view in the 'Idea' step of Story refinement.
Create after
A right-click option that creates a new story directly below the selected item in the list. This option is available in team backlogs and in-progress views, depending on the team's workflow, and in list view in the 'Idea' step of Story refinement.
Create with AI
A story creation flow that uses the Story assistant to help turn an initial idea into a title, user story, and acceptance criteria.
Created
The date an item was created.
Creator
The person who creates a story or bug.
Cycle time
The amount of time it takes for a story or bug to move through the steps in a team's 'In Progress' workflow category. A team's average cycle time for stories and bugs helps project completion dates for these items in the 'To do' category. For more details, see Cycle time.
Cycle time by workflow step
An analytics report that shows the average cycle time for each story size and for bugs, broken down by the steps in a team's workflow. For more details, see Cycle time by workflow step.
Cycle time over time
An analytics report that shows how average cycle time changes over time for each story size and for bugs. For more details, see Cycle time over time.
Cycle time window
The historical period Atono uses to calculate a team's cycle time metrics and related estimates. Teams can configure the window used for these calculations. For more details, see Configure the cycle time averaging window.
D
Design decisions
A type of AI context on stories that captures product and scope decisions, including trade-offs, constraints, acceptance criteria choices, and work explicitly deferred. Design decisions reflect the story's current intent and can be used by the Story assistant and connected AI tools as the work evolves. For more details, see Design decisions.
Docker MCP server
A version of the Atono MCP server that runs locally using Docker and authenticates with an API key. Use it if your AI tool needs to run the server locally or can only connect with an API key. For more details, see Connect with the Docker MCP server.
Duplicate
Create a copy of a story or bug to reuse its details for similar work. For more details, see Copy a story or Copy a bug.
Duplicate bug suggestions
Automatic suggestions shown while creating or editing a bug when Atono detects a potential match with an existing bug in the workspace. Duplicate bug suggestions help reduce redundant reports and make it easier to link related issues. For more details, see Duplicate bug suggestions.
E
Engagement
Visualizes your top features by real usage. The Top features graph highlights adoption trends across your product, helping you see which features are most used, how engagement changes over time, and where to focus next. For more details, see Engagement.
Environment
An environment is a specific setting configured for different stages of the software lifecycle, such as development, testing, staging, and production. Each environment simulates the conditions under which the software will run, allowing for controlled and systematic development, testing, and deployment of applications.
Environment key
A unique identifier used to link your application code to a specific environment in Atono. Environment keys are required when implementing feature flags, ensuring actions are evaluated in the correct environment (such as development, testing, staging, or production). For more details, see Environments.
Epic
A planning item that groups related stories under a shared goal. Epics capture why a body of work exists, describe the user journeys involved, and track delivery progress across the stories within them. For more details, see Epics.
Estimated size
A relative measure of effort required to complete a story, typically based on complexity or scope. Teams can assign sizes (Unsized, XXS, XS, S, M, L, XL, XXL) to stories during planning to prioritize work and improve projected completion date forecasting. Atono converts these sizes to Fibonacci-based story points for use in Total story points, linking qualitative estimates to quantitative forecasting.
Evaluation context
Information your application passes to the Atono SDK when it evaluates a feature flag, such as the customer and location for the current request. Atono uses it to decide which of a flag’s slices apply. For more details, see Set evaluation context.
Everything
A centralized view of all the stories, bugs, and epics in your workspace, spanning teams, projects, and workflows. Use it to locate specific items using search and filters, monitor progress across teams, and customize views to suit your needs. For more details, see Everything.
External ID
An identifier from another system, such as the original Linear issue ID, stored on imported items. Use it to trace items back to their source or cross-reference them outside of Atono. You can filter by External ID or add it as a column on the Everything page. For more details, see Everything.
F
Fallback value
The value the Atono SDK returns if it can’t determine a feature flag’s value, such as when the flag doesn’t exist. You set it in your code, and it’s separate from an environment’s default value. For more details, see Fallback value.
Feature engagement
Shows how often people use a feature from a specific story, based on real interactions like clicks, taps, or other tracked events. The feature engagement graph helps teams see how a feature is performing, where it's being used, and how usage changes over time. For more details, see Feature engagement.
Feature flag
Feature flags allow you to turn features and functionalities associated with your stories on and off in different environments, or slices of customer or regions without deploying new code. This is helpful for controlling who sees a new feature, to perform A/B testing, or to roll out features gradually to users. It also enables you to quickly roll back a story if issues arise after deployment. For more details, see Feature flags.
Feature flag update notifications
Messages automatically posted to connected Slack channels when a feature flag is flipped or its slices are updated. These notifications help keep teams informed about configuration changes, especially during testing or gradual rollouts. For more details, see Configure feature flag notifications.
Finding
An issue identified by a story review. Each finding has a category, a severity (Critical, Moderate, or Minor), and a suggested direction for addressing it, and it's closed when you reject it or accept a change suggested by the Story assistant. For more details, see Understand review findings.
Flag owner
The person or team responsible for managing and maintaining a feature flag. The flag owner has full control over the flag, including the ability to modify its configuration, set conditions, assign permissions to other users, and delete it. For more details, see Flag permissions.
Flag status
A summary of a feature flag’s configuration and evaluation history that helps you tell whether the flag is still in use and safe to delete. For more details, see Flag status.
Flag user
A person or team with permissions to use a feature flag. Flag users can toggle the flag on or off and configure slices based on the conditions defined by the flag owner but do not have the ability to manage or change ownership of the flag. For more details, see Flag permissions.
Follow
An option that lets you 'star' a story or bug to easily find it later. Followed items appear in the 'Following' widget on your Home page, and you can filter the Everything page to show them. For more details, see Follow a story or Follow a bug.
G
Glossary
The workspace-level part of Product knowledge, a structured list of your product's key concepts, including features, workflows, roles, and domain-specific terms. Each concept has a definition, synonyms, and related concepts. You build the Glossary by having Atono crawl your documentation or by uploading a TSV file, and there's one Glossary per workspace. For more details, see Glossary.
Glossary contributor
A person with permissions to add, edit, delete, and restore concepts in the Product knowledge glossary. For more details, see Glossary permissions.
Glossary owner
A person responsible for managing the Product knowledge glossary. Glossary owners can manage glossary concepts, permissions, and delete the glossary. For more details, see Glossary permissions.
H
Handle
A nickname for an item ID (for example, STORY-123 or BUG-456).
Hosted MCP server
A version of the Atono MCP server that Atono hosts for you. You connect an AI tool by adding your Atono MCP URL and authorizing it with your Atono account, without running anything locally or using an API key. For more details, see Connect with the hosted MCP server.
I
Identity provider (IdP)
A system that manages user identities and authentication for an organization. When SSO is enabled, Atono relies on the identity provider to authenticate users and confirm their email address.
Impact
The severity of the effect if a user encounters a bug. In the bug triage process, impact is rated on a scale from 1 (Negligible) to 5 (Severe). It is multiplied by the probability to calculate the overall risk rating of the bug.
In progress
A team page where teams update progress, move items between workflow steps, and manage active work. For Scrum teams, In progress shows the current sprint and focuses on sprint execution. For Kanban teams, it shows work flowing continuously through the team's workflow.
Integrations
A page, opened from your user menu, that brings together the tools connected to Atono, the AI tools you've connected through the hosted MCP server, and your API keys. For more details, see Manage your integrations.
Item ID
A unique identifier assigned to each story, bug, and epic in Atono. Item IDs follow a format based on the item type, such as BUG-47 for bugs, STORY-13 for stories, or EPIC-12 for epics, making it easy to reference and track individual items.
Item type
The kind of work an item represents. Atono has three item types. Stories represent new features, tasks, or improvements, bugs represent defects or issues that need fixing, and epics group related stories under a shared goal. Stories and bugs are backlog items that move through team workflows, while epics don't have a workflow step of their own.
K
Kanban
A team workflow type that manages work as a continuous flow rather than in sprints. For more details, see Kanban.
L
Last evaluated
The most recent time a feature flag's value was evaluated across all environments. This timestamp indicates when the system last checked the flag's conditions to determine its current value, regardless of the specific environment.
Last updated
The date an item was last updated. For more details, see What counts as an update?
Linked items
Stories or bugs connected to each other to show relationships such as dependencies, duplicates, or related tasks. Linking items helps teams track connections, manage dependencies, and ensure all aspects of a feature or issue are addressed. For more details, see Linked items.
List view settings
Options to customize which backlog item details are shown in list view on a team's In progress page and in Story refinement, such as product themes, pull requests, and timeboxes. Available options may vary by team workflow type (Kanban or Scrum).
M
Mapped action
A recorded association between a user interaction in an application and a story in Atono, created through click mapping in the Atono Chrome extension. For more details, see Map clicks for usage tracking.
Mark as an outlier
The control to mark a story or bug as an outlier to exclude it from cycle time reporting, staleness indicators, and projected completion dates. For more details, see Outliers.
Model Context Protocol (MCP)
An open protocol that allows AI tools to securely connect to external systems and use their data and actions in context.
MCP connection
An AI tool you've authorized to access your workspace through the hosted Atono MCP server. Each connection acts with your account and permissions, and you can rename or revoke it from your Integrations page. For more details, see Manage your MCP connections.
MCP-enabled tool
An AI development tool that supports the Model Context Protocol and can connect to an MCP server to access external systems like Atono.
Metatag
A snippet of HTML added to the <head> of a webpage, providing key information like the application environment and customer details for tools like the Atono Chrome extension. For more details, see Metatags.
More info required
An option in the bug triage process. Selecting this option moves the bug into the 'More info required' section and assigns it to the person who reported it, indicating that additional details are needed before the bug can be fully triaged or resolved.
Multi-tenant application
An application that serves multiple customers or organizations from a single deployment. In Atono, multi-tenant applications use customer-based slices for feature flags and require a tenancy meta tag for tools like the Atono Chrome extension to apply actions to the correct customer.
My timelines
A filter option on the Timelines page that displays only the timelines you've created. This helps you quickly find and manage your own timelines without sorting through those shared by others. To view all timelines, clear the My timelines checkbox. For more details, see View your timelines.
O
Outlier
An item with a cycle time significantly longer than the team's average for similar items. Outliers can distort performance metrics, so Atono allows you to mark items as outliers to exclude them from cycle time calculations while retaining their data for reference. For more details, see Outliers.
P
Persona
A type of user or audience represented in a user story. Personas help describe who needs a feature or outcome and can be reused across stories in a workspace. For more details, see User story.
PR
See pull request.
Private team
Private teams are invite-only, meaning the team admin or a member must add you. These teams are ideal for projects that need to stay confidential, like sensitive work or security-related tasks. Only team members, team admins, that team's backlog owners, and users with higher-level workspace roles can access a private team's backlog. For more details, see Public vs. private teams.
Probability
The likelihood that a user will encounter a bug. In the bug triage process, probability is rated on a scale from 1 (Impossible) to 5 (Certain). It is multiplied by the impact to calculate the overall risk rating of the bug.
Product knowledge
Product context that Atono makes available to people and AI tools at two levels. The Glossary provides workspace-level context about your product's terminology, features, roles, and workflows, while AI context preserves the decisions, research, implementation changes, and test planning recorded on individual stories and bugs. For more details, see Product knowledge.
Product Manager
Workspace role that controls who can manage product themes for a workspace. For more details, see Product Manager.
Product theme
A group of related stories that represents an area of investment, showing how development effort is distributed across your priorities. A theme can include stories from many epics and teams, and each story can belong to only one theme at a time. For more details, see Product themes.
Projected (Story throughput)
An estimate of how many stories or story points a team is expected to complete by the end of the current reporting period, based on the team’s average in earlier full periods. For more details, see Story throughput > Projections.
Projected completion dates
Projected completion dates forecast when items in your team's 'To do' workflow category are likely to be completed, based on the team's past cycle time data and the current queue order. Dates dynamically update in real-time as you reorder the list, helping to plan and prioritize work. In the In progress view settings, the option to show or hide them is called ‘Estimated completion dates’. For more details, see Projected completion dates.
Projection (Sprint calendar)
An estimate of how many story points a team is likely to complete in a future sprint, based on the team's historical velocity and the sprint's duration. For more details, see Understanding sprint capacity and projections.
Projection (Burndown chart)
A best-fit line shown on active sprint burndown charts that projects when the remaining story points will reach zero at the current pace. Once the sprint is halfway through, hovering over the line shows whether the sprint is on track, ahead, or behind. For more details, see Projection (active sprints only).
Public team
A team that is open to everyone in the workspace. Any workspace member can join, add or remove members, and view the team's backlog, including the names and content of the stories. Public teams are fully accessible unless changed by the team admin. For more details, see Public vs. private teams.
Pull request
A pull request represents a proposed code change and its review in Git-based version control systems. Atono can automatically link PRs to stories or bugs that are mentioned by ID in the PR's title, branch name, or description. For more details, see GitHub integration.
Q
QA analysis
A type of AI context on stories and bugs that records what should be tested, potential risks, and edge cases to cover. It lets QA tools and coding agents build on existing test planning instead of starting from scratch. For more details, see QA analysis.
R
Rate it for me
An option available when setting a bug's risk rating that suggests Probability and Impact values based on the bug's description. You can accept the suggested rating, adjust the values, or dismiss the recommendation before saving. For more details, see Suggested risk ratings.
Release
A workspace-level marker representing a key date, typically a product release, that stays in sync across every timeline it's added to. For more details, see Releases.
Reported bugs
A section of Bug triage that contains bugs waiting to be triaged, including newly reported bugs and bugs returned to triage. A bug stays here until it has both a risk rating and a team backlog. Bugs in this section are ordered by the date they were reported, from newest to oldest.
Reporter
The person who is recorded as reporting the bug (this may not be the same person who created the bug in Atono). For more details, see Bugs > Change the reporter.
Restore default workflow
An option that resets a team's workflow to the default configuration, undoing any customizations such as renamed steps, reordered steps, changed step categories, colors, or step applicability to stories and bugs. Items within the workflow remain unaffected, ensuring no data is lost during the reset. For more details, see Restore the default workflow for a team.
Reject (Bug triage)
An option in the bug triage process used to dismiss a bug. When selected, the bug is moved to the 'Won't do' section of the triage, indicating that it will not be addressed or resolved.
Reject (Story review)
An action in a story review used to dismiss findings you don't want to address. Rejected findings move to 'Closed findings' and aren't raised again when you refresh the review. For more details, see Reject findings.
Risk rating
A numerical value used to assess the overall risk of a bug. It's calculated by multiplying the bug's probability (the likelihood of it being encountered) by its impact (the severity of the issue). The risk rating is on a scale of 1 to 25, with 25 representing the highest risk, helping prioritize which bugs to address first.
Role
A named entity that grants users access to specific features or areas in Atono. Roles determine what a user can see or do and are assigned at different levels. Workspace roles apply across the entire workspace, team roles apply within specific teams, and feature flag permissions are separate from both. For more details, see Roles and permissions.
S
SAML
Security Assertion Markup Language (SAML) is a standard used for exchanging authentication information between an identity provider and a service provider. Atono supports SAML 2.0 for single sign-on.
Sample data
Read-only example teams, stories, bugs, and other items that support the onboarding tours on your Home page. Each user can hide sample data for themselves. For more details, see Sample data.
Saved view
A customized set of filters, sorting, and layout options that you can save and return to later. Saved views help you quickly switch between different perspectives on your work. For more details, see Saved and shared views.
Scope
The work currently included in a sprint. On a burndown chart, the Scope line shows the total amount of work in the sprint and changes as stories are added or removed. For more details, see Scope changes.
Scrum
A team workflow type that organizes work into time-boxed sprints. Scrum teams in Atono can use sprint planning, burndown charts, sprint calendars, and sprint-based analytics. For more details, see Scrum.
Search
A keyword search that finds stories, bugs, and epics from anywhere in Atono. It matches Item IDs, titles, and the content of items, tolerates small typos, and lets you narrow results with filters. Press Command+K (Mac) or Ctrl+K (Windows) to open it. For more details, see Search.
Seats
The number of users your plan allows. Active users and pending invitations each use a seat. For more details, see Invite users.
Served value duration
The amount of time a feature flag has consistently returned the same value ('On' or 'Off') in a given environment. This helps track how long a flag has been stable in its current configuration, supporting audits, cleanup decisions, and release planning. For more details, see Flag configuration.
Settings
The configuration area where Workspace Owners and Administrators manage workspace details, integrations, and access controls, and where Workspace Owners also manage billing. The Settings page includes sections for managing your workspace name, owners, plan, and connected services like Slack. For more details, see Workspace settings.
Shared view
A saved view that has been shared with other users in your workspace. Shared views let teams align around common perspectives while still allowing individuals to customize their own. For more details, see Saved and shared views.
Single sign-on (SSO)
An authentication method that allows users to sign in to Atono using their organization's identity provider instead of email-based login links. Atono supports SAML 2.0-based SSO for workspaces on paid plans, enabling centralized access control and improved security. For more details, see Single sign-on (SSO).
Size it for me
An option when estimating a story's size that suggests a relative size based on similar completed stories in the team's backlog. You can apply the suggestion, adjust it, or dismiss it before saving.
SDK
A set of tools and libraries from Atono that helps developers integrate and interact with the system's feature flags and other functionalities. The SDK (software development kit) allows developers to implement Atono's capabilities in their applications, such as toggling features on or off and evaluating conditions based on user-defined slices.
Slice
A segment of users or environments defined by specific conditions, such as Customer or Location, in Atono's feature flag system. Slices allow you to target feature flags to particular groups, enabling more tailored feature rollouts and experiments within different environments or user groups. For more details, see Advanced configuration (slicing).
Snooze
A feature that temporarily hides a staleness indicator for a specific item in a specific workflow step. Once the snooze period ends, the staleness indicator reappears if the item is still stale. For more details, see Snooze the staleness indicator.
Source
A filter in the Activities list that lets you see where changes originated, such as from a User in the web user interface or Atono Chrome extension, Story assistant, an integration, the API, or the MCP server. Source filtering helps you focus on activities created through a particular tool or workflow.
Split story
An action that divides a story into two stories by moving selected acceptance criteria into a new story. If the original story belongs to an epic, the new story is added to the same epic, but the two stories aren’t linked to each other. For more details, see Split a story.
Sprint
A time-boxed iteration used by Scrum teams to plan and deliver work. A sprint defines a fixed scope and duration for stories and bugs the team commits to complete. Once work moves into an active sprint, it appears on the team's In progress page.
Sprint calendar
A Scrum-only team page that shows upcoming, current, and past sprints in a calendar view. The Sprint calendar helps teams understand sprint timing, sequence, and boundaries at a glance. For more details, see Sprint Calendar.
Sprint capacity
The number of total story points a sprint can hold based on the team's historical velocity.
SSO mode
A workspace setting that controls how users authenticate in Atono when single sign-on is configured. Available modes include On, Off, and Testing, allowing administrators to control whether SSO applies to all users, no users, or only workspace owners and administrators. For more details, see Single sign-on modes.
Stakeholder
A user with a critical role on a team (a team admin or backlog owner) who is not a team member. Stakeholders appear in the Stakeholders section of the Team overview page to ensure visibility into who holds key responsibilities, even if they aren't directly part of the team. For more details, see Teams.
Staleness indicator
A red hourglass icon that appears when a story or bug has spent statistically longer than expected in its current In progress step. An item is flagged when its time in the step is more than three standard deviations above the average for similar items on the same team, meaning items of the same type and, for stories, the same size. The comparison uses completed items from the team's cycle time window, needs at least five of them, and excludes outliers. For more details, see Staleness indicator.
Standard user
The workspace role for users who aren’t Workspace Owners, Administrators, or Product Managers. Standard Users can gain additional permissions for specific teams or feature flags, for example as team admins, backlog owners, or flag owners, without changing their workspace role. For more details, see Standard users.
Step
See workflow step.
Story
A story is the smallest unit of work in Atono, representing a user-focused task or feature to be developed. Each story includes a title, user story, and acceptance criteria, helping teams deliver value incrementally while staying aligned with user needs. For more details, see Stories.
Story assistant
An AI-assisted authoring tool that helps users define, write, and refine stories through conversation. It uses the story's existing content, epic and related stories, Glossary, and design decisions to generate user stories and acceptance criteria, and it can run a story review to find issues before development begins. For more details, see Story assistant.
Story cycle time
The total time a story spends in the steps in the 'In Progress' category of a team's workflow. For more details, see Cycle time.
Story point
A numerical value that represents a story's estimated size. In Atono, story sizes map to Fibonacci-based story points used for sprint planning, capacity, and reporting. For more details, see How total story points are calculated.
Story refinement
A workspace-wide backlog for capturing and preparing stories before they’re assigned to a team. Stories move through the fixed steps ‘Idea’, ‘Refinement’, ‘Ready for assignment’, and ‘Won’t do’. For more details, see Story refinement.
Story review
An AI review of a story that identifies gaps, inconsistencies, and other issues before development begins. It checks the story's title, user stories, acceptance criteria, and scope, and compares the story against its epic, peer stories, Glossary, and design decisions when they're available. For more details, see Review a story.
Story throughput
An analytics report that shows the number of stories or story points a team completes over time. Use it to compare delivery between periods and understand whether the team's delivery rate is changing. For more details, see Story throughput.
Subtask
An individual step or implementation task attached to a story or bug. Subtasks can be used as a simple checklist or given an assignee, status, and description for more structured tracking. For more details, see Subtasks.
T
Tag
A key:value pair applied to a story, bug, or epic to classify and organize work across the workspace. For example, component: api or severity: high. For more details, see Tags.
Tag key
The category represented by a tag, such as component, severity, or customer.
Tag value
One of the options available for a tag key. For example, the component key might include api, mobile, and delivery. By default, an item can have one value per tag key, but a tag can be set to allow multiple values.
Team
A team is a group of users who plan and deliver work together in Atono. Each team has members and one or more team admins, who don't need to be team members. Teams use either a Scrum or Kanban style, have their own workflows and backlog, and track metrics based on how stories and bugs move through workflow steps. For more details, see Teams.
Team admin
A user who has been granted administrative privileges for a specific team, whether or not they’re a member of it. Team admins can manage team membership, modify team settings, and perform actions such as deleting the team or managing its backlog. However, their permissions are limited to the team they administer and do not extend to other teams or global workspace settings. For more details, see Team admins.
Team backlog
Each team has a designated backlog which contains the stories and bugs that the team is responsible for completing. The backlog can be used to prioritize the order in which these items should be worked on, and track their status throughout the development lifecycle (for example, if they're ready to do, in design, development, testing, or done). For more details, see Scrum Backlog and Kanban Backlog.
Team member
A user who has been added to a specific team. Team members can edit the team's name and description, connect or remove the team's Slack channel, and, on private teams, access the backlog and manage team membership. This role is granted automatically when a user joins a public or private team. For more details, see Team roles.
Team overview
A screen that provides a summary of a team's activity, including its members, backlog, and general information. The team overview allows users to quickly view key details about the team, including its goals, recent progress, and access to its general Slack channel, if integrated. For more details, see Team overview.
Team roles
Team roles only apply within a specific team. They allow users to manage team settings and backlogs without granting workspace-wide permissions. For more details, see Team roles.
Team time zone
A time zone setting applied to your team so that burndown charts and Analytics reports, such as Story throughput and the cycle time reports, display consistently for all members, regardless of where they're working. For more details, see Set team time zone.
Team workflow type
A setting chosen when creating a team that determines how work is organized and which pages are available. Teams can be set up as Scrum or Kanban, affecting how work is planned, tracked, and displayed throughout Atono. Team members and roles work the same regardless of team type, though Scrum teams include sprint-based planning features. For more details, see Teams.
Technical investigation
A type of AI context on stories and bugs that captures research, discoveries, constraints, and open questions gathered during implementation. It helps later work build on what is already known instead of repeating the same investigation. For more details, see Technical investigation.
Technical changes
A type of AI context on stories and bugs that summarizes implementation changes, including updated behavior, code, tests, and outcomes. It reflects the current state of the work rather than serving as a running history. For more details, see Technical changes.
Testing mode (SSO)
A single sign-on mode used to validate an SSO configuration before enabling it for all users. In Testing mode, only Workspace Owners and Workspace Administrators authenticate using SSO, while other users continue signing in with email-based login links. For more details, see Single sign-on modes.
Timebox
A period with a start and end date, such as a release window or milestone, that groups the stories and bugs planned for it, so teams can see what's planned when and which work may not finish in time. A timebox can appear on several timelines and is the same everywhere it's used. For more details, see Timeboxes.
Timeline
Timelines organize timeboxes into a visual schedule, helping you plan workloads, coordinate releases, and share roadmaps with stakeholders. For more details, see Timelines.
Title
The name or label given to a story, bug, or other items in Atono. A title provides a brief, descriptive summary that helps users quickly understand the purpose or content of the item.
Top customers
A default Feature engagement view that ranks up to 10 customers by usage for a story, based on recorded interactions. For more details, see Feature engagement.
Top features
An Engagement view that ranks up to 10 features by usage across your product, based on recorded interactions. Top features helps teams understand which features are most used and compare adoption trends over time. For more details, see Engagement.
Total story points
The combined size of the stories in a column, section, sprint, or timebox. Column and section totals reflect your current view and filters, while sprint and timebox totals always include every story. Helps teams assess scope, balance workloads, and plan work within a sprint or against typical capacity. For more details, see Total story points.
Triage
See Bug triage.
TSV
A tab-separated values file format used to upload or export Product knowledge glossary concepts. Upload a TSV to populate your glossary when documentation isn't publicly hosted or crawlable. Export your glossary as a TSV to share concepts with AI tools outside Atono. For more details, see Product knowledge.
U
Unassign to team
To remove an item from a team's backlog. Bugs that are unassigned to a team are moved to the 'Reported bugs' section of Bug triage. Stories that are unassigned from a team are moved to Story refinement.
Unavailable (cycle time)
Indicates that cycle time cannot currently be displayed for an item. This may happen because the item hasn't entered any 'In Progress' steps or has returned to 'To Do' after being in progress (temporarily hiding its accumulated cycle time). For more details, see Unavailable cycle time.
Unfollow
An option that removes a story or bug from your followed items. Unfollowing doesn't affect the item itself or other users, and only changes what you see on your Home page and the Everything page.
Unmark as outlier
The control to unmark a story or bug as an outlier and include it in cycle time reporting, staleness indicators, and projected completion dates. For more details, see Outliers.
Unscheduled
A section of a Scrum team's Backlog that contains stories and bugs not yet assigned to a sprint. Unscheduled items are prioritized and moved into future sprints during planning. For more details, see Scrum Backlog.
Updated
The date an item was last updated in Atono.
Usage tracking
Captures real interactions with your product's features, such as clicks or taps, and sends them to Atono for analysis. Usage data powers Feature engagement graphs in stories and the Engagement view, showing how often features are used and where. Tracking requires the Atono SDK or mapped clicks from the Atono Chrome extension. For more details, see Set up usage tracking.
User
Anyone with access to your Atono workspace. Every user has the Standard User role and can also have other workspace roles. Users with a status of ‘Not invited’ have been added but haven’t been sent an invitation yet. For more details, see Roles and permissions.
User profile
The user profile helps manage personal details and integration settings within the workspace. It displays key information about a user, such as their email address, role, and name. Users can edit their name and connect their Slack account if the integration is enabled. For more details, see User profile.
User roles
User roles, officially known as Workspace roles, define what a user can do across the entire workspace, from managing settings to controlling access for other users. For more details, see Workspace roles (user roles).
User story
The part of a story or epic that describes who needs something and why, usually written as “As a [persona], I want [goal], so that [benefit].” For more details, see User story.
V
Velocity
The number of story points a Scrum team completes in a sprint. Atono uses historical velocity to help project capacity for future sprints.
Velocity projection
A forecast showing how many story points a team is likely to complete in future sprints based on average velocity from completed sprints. Appears on the Sprint calendar as a capacity bar, and in sprint detail views and team backlogs as a percentage showing how full the sprint is relative to projected capacity.
Version history
A record of changes made to a story, epic, or bug's content over time. Version history lets you view earlier versions, compare changes, and restore a previous version if needed. For more details, see Version history.
View
A customized display of stories and bugs based on filters, sorting, and layout preferences. Views help you focus on the work that matters most in a particular context. For more details, see Saved and shared views.
W
Widget
A panel on your Home page that lists stories and bugs, such as the items assigned to you, the items you're following, or the items in a saved or shared view from the Everything page. You can add, remove, or rearrange widgets at any time. For more details, see Widgets.
Workflow
A sequence of steps that guide how stories and bugs move from start to completion. Workflows are customizable, allowing teams to define the steps that best fit their process. For more details, see Customize workflows.
Workflow step
An individual stage in a workflow that represents a specific point in the process, such as 'To do,' 'Design' and 'Testing.' Workflow steps are customizable by team admins to match their team's needs, including those in the 'In progress' category, which impact cycle time calculations. For more details, see Workflow steps.
Workflow category
A fixed grouping that every workflow step belongs to. Atono has four categories (To do, In progress, Done, and Won't do), which lets each team customize its steps while Atono can still compare performance across teams. Time an item spends in In progress steps counts toward its cycle time, and moving an item into a Done step sets its completion date. To do and Won't do each contain exactly one step. For more details, see Workflow categories.
Workspace
When you log in to Atono, you're accessing a workspace. A workspace is the container for all of the teams, stories, bugs, and any other elements that relate to your company. Each workspace has a unique URL, formatted as example.atono.io.
Workspace Administrator
Workspace role with highest level of administrative privileges in Atono, but without the ability to manage plans and billing. For more details, see Administrator.
Workspace Owner
Workspace role with the highest level of permissions in Atono, including full administrative privileges, and the ability to manage plans and billing. For more details, see Workspace Owner.
Workspace roles
Workspace roles define what a user can do across the entire workspace, from managing settings to controlling access for other users. For more details, see Workspace roles (user roles).
Updated about 18 hours ago