Glossary
Key terms to help you navigate Atono with confidence.
A
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 timeline of actions related to stories, bugs, and feature flags. The Activities section helps teams maintain transparency and track accountability by providing a detailed history of changes, including who made them and when. 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.
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 helps you understand shipped work by answering questions based on completed stories and bugs. Ask in natural language—Capy surfaces relevant items and shows its 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 local server that connects MCP-enabled AI tools to an Atono workspace, allowing them to read and update stories, bugs, and workflows using authenticated access. For more details, see Atono MCP Server.
Attachment
An image, video, or file added to a story 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 all items in the team’s 'To do' workflow step beyond the 20 most recent items shown in In progress.
Backlog item
A generic name to refer to a story or bug in Atono.
Backlog management
A team setting that controls whether the team's backlog is managed by a backlog owner. For more details, see Backlog management.
Backlog owner
A team role responsible for managing which stories a team will work on and in what order. When a team’s backlog is managed, backlog owners determine what stories gets added or created on the backlog, how stories are ordered in the ‘To do’ category, as well as which stories move in and out of ‘Won’t do’ or are deleted. This role ensures that story management remains consistent and controlled within the team. 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. 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—Capy appears in the app, on the website, and at events. For the full backstory, see Meet Capy.
Category
See workflow category.
Comments
Feedback or notes added to a story or bug to provide additional context or discuss specific details. Comments can be added generally to a story or bug, 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.
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 on a story or bug in the To do workflow category. Create before 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.
Create after
A right-click option on a story or bug in the To do workflow category. Create after 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.
Created
The date an item was created in Atono.
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 bug helps estimate completion dates for these items in the 'To do' category. For more details, see Cycle time.
Cycle time report
A report that tracks the time items spend in 'In Progress' workflow steps. It helps teams identify bottlenecks, measure efficiency, and make data-driven improvements with filters for item types, sizes, or timeframes. For more details, see Cycle time report.
D
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.
Estimated completion dates
Estimated 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. For more details, see Estimated completion dates.
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 estimated completion date forecasting. Atono converts these sizes to Fibonacci-based story points for use in Total story points, linking qualitative estimates to quantitative forecasting.
Everything
A centralized view of all the items in your workspace, spanning teams, projects, and workflows. Use it to locate specific stories or bugs 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
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, 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.
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, remove the flag from stories, and delete it. For more details, see Flag permissions.
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 can be filtered in the Everything page and added as a Home page widget, making it easier to keep track of work that matters to you.
H
Handle
A nickname for an item ID (for example, STORY-123 or BUG-456).
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 worflow 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.
Item ID
A unique identifier assigned to each story or bug in Atono. Item IDs follow a specific format based on the item type, such as BUG-47 for bugs or STORY-13 for stories, making it easy to reference and track individual work items.
Item type
A classification that defines the kind of work being tracked. Currently, Atono supports two item types: Stories (which represent new features, tasks, or improvements) and Bugs (which represent defects or issues that need fixing).
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 estimated 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-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, 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 that 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
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, and workspace Administrators 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 Manager
Workspace role that controls who can manage product themes for a workspace. For more details, see Product Manager.
Product theme
Product themes are used to group related stories to align work with strategic goals, track long term progress, and ensure deliverables support your organization's priorities. For more details, see Product themes.
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.
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.
Release marker
A vertical indicator on a timeline used to represent a key date—typically a product release. For more details, see Use release markers.
Reported bugs
A section of Bug triage that contains newly reported bugs that haven’t yet been assigned a risk rating and team backlog. Bugs in this section are ordered by the date they were reported, from oldest to newest.
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
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.
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.
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.
Search
A fast, fuzzy search tool that helps you find stories and bugs by keyword from anywhere in Atono. Results update as you type and highlight matches across fields like titles, descriptions, and comments. Use filters to narrow results, or press Cmd+K / Ctrl+K to open search quickly. For more details, see Search.
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 can manage workspace details, billing, integrations, and access controls. 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 fromAtono 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, based on the team's average time for similarly sized items in that step. Once the snooze period ends, the staleness indicator reappears if the item still exceeds the average time in that step. For more details, see Snooze the staleness indicator.
Source
A filter in the Activities list that lets you see where changes originated, such as the Atono interface, an integration, the API, or the MCP server. Source filtering helps you focus on activities created by specific tools or automation.
Split story
An action that divides a story into two stories by moving selected acceptance criteria into a new story. The original and new stories are automatically linked for traceability. 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.
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 visual clue, represented by a red hourglass, that appears when an item has remained in a particular 'In progress' workflow step longer than the team's average for similar item types and size. This helps teams identify and address potential bottlenecks in their workflows. For more details, see Staleness indicator.
Standard user
The role for users who are not workspace Administrators. Standard users have limited access but can gain additional privileges if assigned as team admins or given feature flag permissions, allowing them to manage teams and feature flags within those specific contexts. 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 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 refinement
A backlog to help product managers capture ideas and prepare stories for future work before assigning them to a team. For more details, see Story refinement.
T
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 member of a team who has been granted administrative privileges for that specific team. 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 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 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, roles, and permissions work the same regardless of team type. For more details, see Teams.
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
Timeboxes provide a snapshot of key information on a timeline, such as stories, bugs, associated themes, and teams. For more details, see Use timeboxes.
Timeline
Timelines organize timeboxes into a visual schedule, helping you plan workloads, coordinate releases, and share roadmaps with stakeholders. Fore 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 all visible stories in a column, section, sprint, or timebox, based on your current view and filters. 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.
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—it only changes what you see in filtered views and dashboards.
Unmark as outlier
The control to unmark a story or bug as an outlier and include it in cycle time reporting, staleness indicators, and estimated completion dates. For more information, 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
Any individual who has access to Atono, either as a workspace Administrator or a Standard User. Users can perform actions based on their assigned role and permissions, such as creating stories, managing teams, or configuring feature flags.
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).
V
Version history
A record of changes made to a story 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 customizable panel on your Home page that displays items from a saved or shared view. Widgets help you monitor assigned work or track specific filters at a glance. You can add, remove, or rearrange widgets at any time. For more details, see Manage 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 grouping or classification of workflow steps, used to organize different types of workflows in Atono. Categories can help differentiate workflows for various tasks, such as development, design, or testing, and support customization for specific team needs. 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 1 month ago