Skip to main content
Ticket drafts provide a way to prepare and collaborate on tickets before they are officially created. This feature is particularly useful for complex tickets that require multiple edits or team input before being submitted.
Drafts can be either private (visible only to the creator) or public (visible to all team members), allowing for flexible collaboration while maintaining control over work in progress.

​
Understanding drafts

​
Draft types

Private drafts

• Visible only to the creator
• Perfect for personal work
• No team visibility
• Convert to public when ready

Public drafts

• Visible to all team members
• Enables collaboration
• Team can provide input
• Ready for group review

​
Draft lifecycle

1

Creation

  • Start new draft
  • Set visibility (private/public)
  • Add initial content
  • Save progress
2

Collaboration

  • Share with team (if public)
  • Gather feedback
  • Make revisions
  • Track changes
3

Finalization

  • Review final content
  • Validate required fields
  • Get approvals if needed
  • Prepare for submission
4

Submission

  • Convert to actual ticket
  • Assign appropriate team
  • Set initial status
  • Begin ticket lifecycle

​
Draft management

​
Core capabilities

  • Start from scratch
  • Save progress
  • Rich text editing
  • Share with team
  • Track changes (coming soon)
  • Mention colleagues (coming soon)
  • Request reviews (coming soon)
  • Categorize drafts (coming soon)
  • Set priorities (coming soon)
  • Add labels (coming soon)
  • Group related drafts (coming soon)
  • Archive old drafts (coming soon)

​
API endpoints

​
Draft ticket

{
  "title": "Customer reported login issue",
  "description": "User unable to access mobile app",
  "isPrivate": true,
  "draftScope": "personal",
  "teamId": "team_123",
  "requestorEmail": "customer@example.com",
  "submitterEmail": "agent@thena.ai",
  "statusId": "status_new",
  "priorityId": "priority_high",
  "typeId": "type_bug",
  "accountId": "account_456",
  "assignedAgentId": "agent_789",
  "customFieldValues": [
    {
      "fieldId": "field_123",
      "value": "iOS 15.0"
    }
  ],
  "metadata": {
    "browserVersion": "Chrome 120",
    "deviceType": "Mobile"
  }
}
When creating a draft, use isPrivate: true and draftScope: "personal" for private drafts visible only to the creator. For team-wide visibility, set isPrivate: false.

​
Available operations

# Create a new ticket draft
POST /v1/tickets/draft
Content-Type: application/json

# Get all draft tickets
GET /v1/tickets/draft

# Get draft ticket by UID
GET /v1/tickets/draft/{uid}

# Update draft ticket
PUT /v1/tickets/draft/{uid}
Content-Type: application/json

# Delete draft ticket
DELETE /v1/tickets/draft/{uid}

# Publish draft ticket
POST /v1/tickets/draft/{uid}/submit
Content-Type: application/json
All endpoints require authentication with Bearer token, API key, and Organization ID in the headers.
For detailed API specifications, see Draft Management

​
Best practices

Draft creation

• Use clear titles
• Include key details
• Set appropriate visibility
• Use templates when available

Collaboration

• Share early for feedback
• Use clear comments
• Track major changes
• Set review expectations

​
Tips for effective draft management

1

Organization

  • Use consistent naming
  • Categorize appropriately
  • Clean up old drafts
  • Document decisions
2

Collaboration

  • Share context early
  • Request specific feedback
  • Set review timelines
  • Track feedback status
3

Quality control

  • Review required fields
  • Validate information
  • Check attachments
  • Test links and references

Ticket overview

Learn about ticket management

Fields

Understand ticket fields

Teams

Team collaboration

Best practices

Ticket management guidelines