Skip to content
GitStart's Documentation

Assign Tickets

Like most software development teams, GitStart works with tickets. Tickets are the way you assign us work. This section explains how to assign us tickets and check on their progress. GitStart works with tickets. Tickets are the way you assign us work, like most development teams. This section explains how to assign us tickets and check on their progress.

What makes a good ticket?

GitStart isn’t too different from other development teams, with one exception: we’re remote and don’t know your codebase so well in the beginning. We can’t walk over to your desk and ask you questions, and we’d rather not interrupt you repeatedly with questions. So we need to be able to work independently, and well-scoped tickets are a part of that.

We’ve written a guide on how to write good tickets, and we hope you’ll check it out before you start assigning us work.

Assigning tickets

There are two ways to assign us tickets, depending on your plan:

  • From the dashboard, via a form. This is available to all clients on all plans.
  • From the comfort of your issue-tracking system, we’ll synchronize them with our app. This is only available for Team & Enterprise plans.

Creating tickets through our dashboard

You can create tickets from the dashboard using the ‘Create new ticket’ button in your instance home. The wizard will guide you through the process.

When you create a ticket from the dashboard, two things will happen:

  • We create a PR in your repository, which you can use to communicate with our developers.
  • If you made an initial estimate, our developers will review it. They may reject it if they think it is too low or too high, and you will be notified. A negotiation process will start, and you will be able to approve or reject the new estimate.

Remember to come back to the dashboard to check on the status of your ticket.

Importing tickets from issue-tracking software

For Team and Enterprise plans, you can import tickets from your issue-tracking software. Our team will help you set this up. In short, it works like this:

  1. Invite our bot account to your issue-tracking software. Ensure the bot has view permissions for the relevant ticket(s).
  2. Assign issues to it as you would to any team member. Wait for the bot’s confirmation message in your issue-tracking software.
  3. We synchronize assigned tickets into the app. Ticket details, including title, work description, and media, will be reflected in the Ticket View on the dashboard within minutes.

Supported issue-tracking tools

If your tool doesn’t show up here, feel free to contact

Ticket priority

Want to indicate something is urgent or important?

For Team and Enterprise plans, ticket priority (if any) should be clear when assigned in your issue-tracking app. GitStart will take into consideration the stated priority. You may also indicate priority or dependencies in ticket descriptions.

After you assign a ticket

You’ll see the newly-created ticket in the dashboard. The ticket will have a status, which will change as our developers work on it. The status can be one of the following:

  • Available - when a ticket is assigned to GitStart and gets successfully imported, it is available for our community developers to start working on it. This is the default status for all tickets when they are imported;
  • In progress - when GitStart has verified the ticket requirements and created a pull request internally to begin technical speccing and coding;
  • Finished - when all PRs from a ticket are either Approved, Merged, or Canceled (i.e., a terminal state);
  • Canceled - when a ticket has been canceled by either party

When a ticket is In progress, it means our developers have seen it and are working on it, reviewing the requirements and drafting their approach. You can check the status of the ticket in the dashboard.

Ticket and PR costs

We typically work with and recommend one PR per ticket to meet the requirements. See the next section for more information on PRs and their cost.