Ticket Management

Orchestra aggregates issues and tickets from all connected platforms โ€” Jira, GitHub, and GitLab โ€” into a single unified view. Work happens in one place regardless of which tracker it originated from.

๐ŸŽซ Tickets 19 tickets
Filter โ–พ
Sort โ–พ
Title
Status
Priority
Source
Agent
Fix null ref in auth middleware
PROJ-142
In Progress
High
Jira
๐ŸŽป Maestro
Add dark mode to dashboard
#304
Open
Medium
GitHub
โ€”
Payment gateway timeout error
PROJ-139
Review
Critical
Jira
๐ŸŽต Aria
Bump Node.js to v22 in CI
!91
Open
Low
GitLab
โ€”
Update API docs for v2 endpoints
#298
Done
Low
GitHub
๐Ÿ” Orpheus
The Tickets view โ€” unified issue list across all connected integrations

Unified View

Tickets from all workspace integrations appear in the same list. Each ticket is enriched with its source platform metadata while being normalized to a consistent Orchestra model.

FieldDescription
TitleIssue or ticket summary from the source tracker
StatusNormalized status โ€” Open, In Progress, Review, Done, Blocked
PriorityNormalized priority โ€” Low, Medium, High, Critical
SourceOrigin platform (Jira / GitHub / GitLab) with external link
Assigned AgentWhich Orchestra agent is executing on this ticket (if any)
External IDThe ID in the source tracker (e.g., PROJ-123, #456)

Statuses & Priorities

Orchestra maps each tracker's native states to a common set of statuses and priorities:

Statuses

OpenNew, unstarted ticket
In ProgressActively being worked on
ReviewAwaiting code review or approval
DoneCompleted successfully
BlockedWaiting on a dependency

Priorities

LowNice-to-have, non-urgent
MediumStandard priority
HighImportant, schedule soon
CriticalUrgent, needs immediate attention

Assigning Agents to Tickets

Once an agent is deployed in your workspace, you can assign it to any ticket. Orchestra creates a background Job that the Worker service picks up and executes asynchronously.

1
Open a ticket

Click any ticket in the list to open its detail view. The full ticket description (including ADF-rendered content for Jira) is displayed.

2
Assign an agent

In the ticket detail, select an agent from the workspace's deployed agent list and click Start.

3
Monitor execution

Navigate to Jobs to watch the execution in real time โ€” each step, tool call, and sub-agent interaction is visible.

Atlassian Document Format (ADF)

Jira uses ADF for rich ticket descriptions โ€” code blocks, mentions, tables, and media. Orchestra's dedicated ADF Generator microservice handles bidirectional conversion, ensuring Jira content is rendered accurately in the UI and that agent output can be written back to Jira in valid ADF.

๐Ÿ’ก

Automatic: ADF conversion is fully transparent. When you open a Jira ticket, Orchestra fetches the raw ADF, converts it to HTML, and renders it natively. No configuration required.