Skip to main content
Issues are automatically assigned sequential identifiers like ISS-1, ISS-2 within each workspace for easy reference and tracking. Issues are automatically assigned sequential identifiers like ISS-1, ISS-2 within each workspace for easy reference and tracking.
The user references sequential IDs like ISS-1; the platform assigns them automatically per workspace.

Quick Start

1

Create First Issue

Create an issue and receive automatic ID assignment:
2

Create Additional Issues

Subsequent issues get sequential numbers automatically:

How It Works


Response Fields

Every issue response includes these auto-generated fields:

Common Patterns

Basic Issue Creation

Python SDK Integration

Batch Issue Creation


Customizing the Prefix

The workspace issue_prefix can be customized per workspace. After changing the prefix, new issues use the new prefix while existing issues retain their original identifiers.

Best Practices

Use prefixes that clearly identify the workspace or project type:
  • ISS - General issues
  • BUG - Bug tracking workspace
  • FEAT - Feature request workspace
  • PRJ - Project management workspace
Numbers are unique per workspace, not globally:
  • Workspace A: ISS-1, ISS-2, ISS-3
  • Workspace B: ISS-1, ISS-2, ISS-3 (separate counter)
Once assigned, issue numbers and identifiers never change:
  • Safe to reference in documentation
  • Stable for external integrations
  • Guaranteed uniqueness within workspace
Use test workspaces for development to avoid polluting production counters:

Testing

Run the platform issue numbering tests:

Platform API

Complete platform API reference

Workspace Management

Managing workspaces and settings