The Activities section keeps a detailed, time-stamped history or all actions for stories, bugs, and feature flags.

Stories and bugs: Each item includes a dedicated Activities section with a chronological log of changes.
Feature flags: The Feature flags list includes a global Activities section of all feature flags in your system.

Each entry shows who performed the action, when it happened, and what changed. You can sort by recency and filter by type or source to focus on the details you need.

Sort activities

Click the arrow next to the Activities title to toggle between newest-first and oldest-first.

Filter activities

Use Filter by to focus the activity list on the updates most relevant to your workflow. You can filter by:

Type – what kind of update occurred
Source – where the update originated (user, integration, API, or MCP server)

You can apply one or both filters at the same time.

Filter by source

Source filtering helps you understand where an update came from—especially helpful when troubleshooting unexpected changes.

The following sources appear in this order:

Atono – Actions performed directly in Atono, including updates made through the Atono UI or the Atono Chrome extension.
Integration – Updates generated by connected systems, including the GitHub integration, Jira import, and Linear import.
API – Updates made through the Atono public REST API when no other integration or MCP source applies.
MCP Server – Automated actions completed by the Atono MCP server on behalf of a user (such as workflow step changed, story edits, or bug updates triggered by an AI tool).

Filter by type

Filter activities by action type to focus on specific types of updates.

General activities (stories and bugs)

Assignee: Changes to the assigned user or updates to 'No assignee'.
Attachment: Adding or removing attachments.
Backlog: Movement between team backlogs or to 'Unassigned to team'.
Comment: Adding, editing, accepting, rejecting, or deleting comments.
Description: Edits to user story details or acceptance criteria (ACs).
Linked items: Adding or removing linked stories or bugs.
Outlier: Item marked or unmarked as an outlier, which excludes it from average cycle time calculations, cycle time reports, and staleness indicators.
Pull request: Opened, merged, closed, or linked PRs from connected GitHub repositories (requires GitHub integration).
Step: Workflow step transitions (for example, from 'To do' to 'Design').
Timebox: Adding or removing the item from a timebox.
Title: Updates to the item title.
All Types: Full history, including item creation.

Story-specific activities

Feature flag: Additions, removals, status changes, and configuration updates (e.g., 'changed from OFF to ON for the dev environment' or 'updated the slices for the prod environment').
Product theme: Adding, editing, or removing the story from a product theme.
Size: Updates to the estimated story size.

Bug-specific activities

Environment: Changes to the affected environment reported for the bug.
Triage: Updates to probability, impact, or risk rating.
Reporter: Changes to the bug's reporter.

Feature flag activities

Add to story: Feature flag name and associated story.
Create flag: Name of the newly created flag.
Delete flag: Name of the deleted flag.
Remove from story: Feature flag name and associated story.
Update configuration: Status changes and configuration updates (e.g., 'changed from OFF to ON for the dev environment' or 'updated the slices for the prod environment').
Update details: Changes to the feature flag's name.

Linked stories or bugs in activity entries

If an activity includes a story or bug ID (for example, STORY-123 or UG-456), it appears as a clickable link. Selecting it opens the item. Items you don’t have access to, or items that have been deleted, aren’t linked.

Automated actions

Some activities in your workspace may be carried out automatically by the Atono MCP server when an AI tool performs a task for you. For example, these activities may include creating or updating a story, changing an item's workflow step, or updating bug details.

Entries created this way show a diamond (✦) icon next to the user's name with a Performed by MCP server tooltip, indicating the change was performed by the MCP server on the user's behalf.

This makes it easy to see which updates came from AI-connected tools rather than actions taken directly in the Atono application.