Creating an Issue
Issues are the core unit of work in DevShip. Each issue tracks a discrete piece of work with its own type, status, priority, assignee, and timeline.
Creating an Issue
- Navigate to a project's issue list.
- Click New Issue.
- Fill in the issue fields.
- Click Create Issue.
Issue Fields
Title
A short, descriptive summary of the work. Required.
Description
An optional detailed description. Supports rich text with formatting, code blocks, and links.
Type
Categorises the nature of the work:
| Value | Label |
|---|---|
bug | Bug |
tweak | Tweak |
feature_request | Feature Request |
chore | Chore |
other | Other |
Status
The current position in the workflow:
| Value | Label | Meaning |
|---|---|---|
triage | Triage | Newly created, not yet assessed |
open | Open | Assessed, waiting to be worked on |
in_progress | In Progress | Actively being worked on |
testing | Testing | Work complete, awaiting verification |
closed | Closed | Complete |
Priority
| Value | Label |
|---|---|
low | Low |
normal | Normal |
high | High |
urgent | Urgent |
Assignee
The team member responsible for the issue. Only members with access to the project appear in the assignee list.
Estimated Date
An optional target completion date. Useful for planning and filtering.
URL
An optional external URL to link to (e.g. a Figma design, a GitHub PR, a support ticket).
Reference Codes
Every issue is automatically assigned a reference code on creation — for example, BACKENDAPI-42. The prefix is derived from the project name and the number is sequential within the project. Reference codes are permanent and cannot be changed.
Use reference codes to link to specific issues in commit messages, PR descriptions, or external tools.
Tags
Tags can be applied to an issue after creation from the issue detail page. Tags are project-specific and are managed by project admins from the project's Tags page.