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

Stories, bugs, and epics: 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.

Search activities

Quickly locate specific activities by searching for a keyword in titles or descriptions, or in the names of environments, workflow steps, feature flags, or GitHub requests or repositories.

Click the search (magnifying glass) icon at the top of the Activities list.
Enter a search term. The list automatically updates to show matching activities with the search term highlighted.

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, Story assistant, integration, API, or MCP server).

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

Filter by type

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

Stories, bugs, and epics

Filter	Available for	Description
Assignee	Stories, bugs	Changes to the assigned user or 'No assignee'.
Attachment	Stories, bugs, epics	Adding or removing attachments.
Backlog	Stories, bugs	Movement between team backlogs or to 'Unassigned to team'.
Comment	Stories, bugs, epics	Adding, editing, accepting, rejecting, or deleting comments.
Content	Epic	Edits to the content of an epic.
Description	Stories, bugs	Edits to the content of a story or bug.
Environment	Bugs	Changes to the affected environment reported for the bug.
Epic	Stories	Adding or removing the story to an epic
Feature flag	Stories	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').
Linked items	Stories, bugs	Adding or removing linked stories or bugs.
Outlier	Stories, bugs	Item marked or unmarked as an outlier, which excludes it from average cycle time calculations, cycle time reports, and staleness indicators.
Product theme	Stories	Adding, editing, or removing the story from a product theme.
Pull request	Stories, bugs	Opened, merged, closed, or linked PRs from connected GitHub repositories (requires GitHub integration).
Reporter	Bugs	Changes by or to the bug's reporter.
Size	Stories	Updates to the estimated story size.
Sprint	Stories, bugs	Changes to the sprint the item is assigned to or 'No sprint' (for items assigned to Scrum teams).
Step	Stories, bugs	Workflow step transitions (for example, from 'To do' to 'Design').
Story	Epics	Stories added or removed from the epic.
Subtasks	Stories, bugs	Creating, assigning, updating the status of, or deleting subtasks.
Tag	Stories, bugs, epics	Adding or removing tags from the item.
Timebox	Stories, bugs	Adding or removing the item from a timebox.
Title	Stories, bugs, epics	Updates to the item title.
Triage	Bugs	Updates to probability, impact, or risk rating.

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:

User – Actions performed by a user directly in Atono, including updates made through the Atono web application or the Atono Chrome extension.
Story assistant – Changes applied from the Story assistant on behalf of a user, such as updates to a story's title, user stories, or acceptance criteria after the user accepts the suggested changes.
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).

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 items in activity entries

If an activity includes a story, bug, or epic ID (for example, STORY-123 , BUG-456, or EPIC-789), 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 are performed by AI on a user's behalf, either by the Story assistant or Atono MCP server.

Story assistant changes are applied when a user accepts the assistant's suggested updates to a story's title, user stories, or acceptance criteria.
MCP server actions happen when an AI tool performs a task for a user, such as creating or updating a story, changing an item's workflow step, or updating bug details.

Entries created this way show a sparkle (✦) icon next to the user's name with a tooltip identifying the source (for example, Performed by MCP server or Performed by Story assistant)

This makes it easy to see which updates involved AI, and to filter for them using the Source filter.