Creating and Assigning Tickets

Tickets are the primary way you assign work to GitStart developers. This guide explains how to create effective tickets and manage the assignment process.

Ticket Creation Options

There are two ways to assign work to GitStart:

1. Creating Tickets Directly in GitStart

You can create tickets from the GitStart dashboard:

1. Navigate to your agent/instance home
2. Click the ‘Create new ticket’ button
3. Follow the guided wizard to define your requirements

When you create a ticket through the dashboard:

• We automatically create a PR in your repository for developer communication
• If you provided an initial estimate, our developers will review it and may propose adjustments
• You’ll receive notifications about any estimate changes, which you can approve or reject

Remember to check the dashboard regularly for ticket status updates.

2. Importing from Your Issue Tracking System

If you’ve already set up a ticketing system integration as described in our Ticketing System Integration Guide, you can assign tickets directly from your preferred tool:

1. Assign issues to the GitStart bot account as you would to any team member
2. Wait for the bot’s confirmation message in your issue-tracking software
3. The ticket details, including title, description, and attached media, will appear in the GitStart dashboard within minutes

Ticket Priority Management

Need to indicate urgency or importance? You can set priority levels for your tickets:

• Directly in your issue-tracking system (priority settings will be imported)
• In the ticket description using clear priority indicators
• Through the priority selector when creating tickets in the GitStart dashboard

GitStart respects your stated priorities when allocating development resources.

Understanding Ticket States

After assigning a ticket, you’ll see it in the dashboard with one of the following statuses:

• Available: Successfully imported and available for GitStart developers to pick up
• In Progress: Requirements verified and development work has begun
• Finished: All associated PRs are either approved, merged, or canceled
• Canceled: The ticket has been canceled by either party

The status will update automatically as developers progress with the work.

Ticket and PR Relationship

We typically work with one PR per ticket to meet the specified requirements. In some cases, complex tickets may require multiple PRs, which will be clearly communicated.

For more details on PR review and merging processes, see our Reviewing and Merging Pull Requests guide.

Best Practices

For guidance on creating clear, effective tickets that lead to successful outcomes, see our Writing Effective Tickets guide.

Need Help?

If you have questions about the ticket creation or assignment process, contact our support team at support@gitstart.com.