Release readiness check
Maya Okafor, product manager at Acme Ltd, asked what was left in the June release. Memtro listed the release's features with workflow status and assignee, and flagged three still in development. She took the list to planning.
What is the status of the export feature on our roadmap?
Aha! shows your workspaces, then features with workflow status, assignee, release and dates, and one feature's description. It reads ideas with status and vote count, releases, epics, and the comments on a feature or idea. When asked, and once an administrator has granted the action by name, it can comment, create and update features, epics, ideas and to-dos, move features between releases, promote an idea to a feature, and permanently delete features, epics, ideas and comments. Watchers, assignees or anyone mentioned may be notified, and an idea's status change can show on a portal. Voters are never returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Aha! tool, reads what it needs, and answers with the source cited.
These tools change something in Aha!. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Aha! is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
What is the status of the export feature?
Which features are in the next release?
What are our most popular ideas right now?
Add a comment to APP-12 saying the design review is done.
Move APP-12 to the July release
Maya Okafor, product manager at Acme Ltd, asked what was left in the June release. Memtro listed the release's features with workflow status and assignee, and flagged three still in development. She took the list to planning.
Tom Reilly, head of product at Northwind, asked Memtro to turn the most-voted idea on bulk export into a feature in the Q3 release. Memtro promoted the idea in Aha!, linking it to the new feature. The idea's status changed, which its submitter and voters could see on the portal.
The teams that lean on Aha! most, a question each of them asks, and what they connect beside it.
A record in Aha! is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Aha!, open Settings → Personal → Developer → API keys, signed in as a dedicated user without administrator rights, with access only to the workspaces Memtro should use.
Choose Generate API key, name it Memtro and copy the key. It carries that user's whole access, with no scopes.
In Memtro, open Connections → Aha! and paste Account subdomain (the acme in acme.aha.io) and API key.
Ask: what is the status of the export feature?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Aha! tools are the same everywhere.
Only when you ask, and only what it has been granted: add a comment to a feature; add an internal comment to an idea; add a comment to an epic; edit or delete a comment; create a feature in a release; update a feature's name, status, assignee, release or dates; create an idea in a workspace; update an idea's name, description, status or assignee; promote an idea to a feature or epic; create an epic in a release, or update one; add a to-do to a feature, epic, release, initiative or idea; permanently delete a feature, epic or idea. Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
Account subdomain and API key. In Aha!, open Settings → Personal → Developer → API keys, signed in as a dedicated user without administrator rights, with access only to the workspaces Memtro should use.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time