Ticketworkflow
Begrijp de complete ticket levenscyclus van concept tot deployed.
Understanding the ticket lifecycle helps you work more effectively with TurtleApps. This guide covers each status and what happens at each stage.
Ticket Statuses
Ticket workflow diagram
[Screenshot placeholder]
Draft
Initial state when creating a ticket. You can edit the description, add attachments, and make changes before submitting.
Submitted
The ticket is submitted and waiting for AI review. This usually takes 1-2 minutes depending on complexity.
In Review
AI is analyzing your ticket, understanding the requirements, and creating an implementation plan.
Planning
AI has completed analysis and presents the implementation plan. You can review the plan, provide feedback, or approve it.
✨Review the Plan
Take time to review the AI's plan. If something looks off, provide feedback before starting development. It's much easier to adjust the plan than to redo completed work.
In Development
AI is actively writing code. You'll see real-time progress updates showing which files are being created or modified.
Ready for Preview
Development is complete. A preview environment is automatically created where you can test the changes.
Awaiting Approval
If approval workflows are enabled, the ticket waits for required approvers to review and approve.
Approved
All required approvals are received. The ticket is ready for deployment.
Deploying
The changes are being deployed to your target environment.
Deployed
Changes are live. The ticket is complete.
Rejected
The ticket was rejected during review. Check the feedback and create a new ticket addressing the concerns.
Workflow Actions
Start Development
Available in Planning status. Tells AI to begin implementing the plan.
Request Changes
Available during review or preview. Send feedback to AI for adjustments. A new development cycle begins.
Approve
Available when preview is ready. Marks the ticket as approved for deployment.
Deploy
Available after approval. Deploys the changes to production (or your configured target environment).
Reject
Closes the ticket without deploying. Use for tickets that are no longer needed.
Automatic Transitions
Some status changes happen automatically:
- Submitted → In Review (immediate)
- In Development → Ready for Preview (when code is complete)
- Deploying → Deployed (when deployment succeeds)
Notifications
You receive notifications when:
- AI review is complete
- Development is finished
- Preview is ready
- Approval is required
- Deployment completes
💡Configure Notifications
Customize which notifications you receive in Settings → Notifications. You can enable/disable email and in-app notifications separately.
Was dit artikel nuttig?