Requests Inbox
Requests Inbox
The Requests Inbox is the DevOps ticket queue across services and environments. Aiden imports matching tickets from connected trackers, triages them against workspace workflows, and waits for you to approve execution.
Open Aiden DevOps -> Requests Inbox (under Track). Subtitle: DevOps request queue across services and environments.
Inbox toolbar
| Control | What it does |
|---|---|
| Refresh Requests Inbox | Reloads the queue |
| List view | Card-style request list (default) |
| Table view | Table layout for the same queue |
| Configure Inbox | Opens the Configure Inbox dialog for pull filters and tracker options |
Search and filters
- Use Search request ID, summary, service... to find requests.
- Open Inbox queue to filter by status. Options include:
- All
- Unassigned
- Assigned to me
- Awaiting approval
- Blocked
- Resolved
- Ignored
- Use Source, Service, and Priority to narrow the list further.
Each request card shows priority (for example P1 or P2), title, age, source ticket link (for example Linear · STA-164), and triage tags such as service and environment. Status on the card can include New or Awaiting approval.
Select a card to open the request detail panel.
Configure Inbox
Click Configure Inbox. Dialog title: Configure Inbox. Description: Choose which tickets Aiden pulls into the Inbox from each tracker.
| Setting | What it does |
|---|---|
| Auto post to ticket | Automatically post the Ops Inbox link to the source ticket when a request is first added (sync or webhook). You can still post manually from the request detail. |
| Auto-mark ticket status | When a request is first added, move the source ticket to a chosen status (for example In Progress). Failures are logged and do not block triage. |
For each connected tracker (for example Linear):
- Expand the tracker row. The summary can show teams, assignees, and labels (for example Teams STA · anyone · incident, help-needed labels).
- Use the enable switch (Disable ... in inbox when on) to turn that tracker on or off for the inbox.
- Set Teams, Assignees (for example Anyone (default)), and Labels (for example incident, help-needed).
- For Linear live tickets and triage replies, configure a Linear webhook:
- Create a Linear webhook and select Issues and Comments under Data change events.
- Paste the Webhook URL from Aiden (copy with Copy webhook URL).
- Enter the signing secret (leave blank to keep the current secret).
- Use Clear if you need to reset the secret field.
- Use Connect Jira or Connect ServiceNow from this dialog when you need another tracker, or finish setup under Integrations.
- Click Save inbox filters to apply, or Cancel / Close to leave without saving.
Request detail
Selecting a request opens the detail panel with priority, title, ticket ID, source link, requester, and age.
Request actions
Open Request actions (⋯) for:
| Action | What it does |
|---|---|
| Copy request link | Copies a link to this inbox request |
| Post to ticket | Posts the Ops Inbox link to the source ticket |
| Delete from inbox | Removes the request from the inbox |
Close detail panel dismisses the panel.
Original request
Shows the text from the source ticket.
Aiden's Triage
Aiden classifies the request and shows a confidence score (for example 68%).
| Control | What it does |
|---|---|
| Re-run triage | Runs classification again |
| Change Category | Override the triage category chip |
| Change Priority | Override priority (for example P1, P2) |
| Change Service | Override the extracted service |
| Change Environment | Override the extracted environment |
Triage includes a short analysis and Extracted details such as Service and Environment.
Workflow to run
When no workflow matched, the panel shows: No workflow matched. Describe your team's workflow and Aiden will build a reusable workflow suggestion.
| Control | What it does |
|---|---|
| Describe Workflow | Opens a flow to describe a reusable workflow for this kind of request |
| Workflow to run on approve | Override or pick the workflow used on approve |
| Why this workflow? (optional) | Optional note (placeholder example: Same access pattern as last week's ticket) |
| Approve & execute | Approves the chosen workflow and starts execution |
Matching uses workflow descriptions. Keep descriptions clear and distinct so similar workflows do not confuse triage. Browse the catalog under Workflows.
Chat about this request
Ask follow-up questions without starting execution.
- Type in Message about this request (Ask Aiden about this request...).
- Click Start chat when enabled.
- Hint text: Enter to send · Shift+Enter for a new line.
Execution history
Timeline of inbox events for the request, for example:
- Request imported into the inbox
- Aiden classified this request
Expand a row for more detail when available.