Tickets are a mechanism used in project management and software development to log and respond to issues. This means tickets are typically used to document defects in a given project. To see the difference between tickets and tasks, see this page.

Tickets typically benefit from having an associated priority. Goplan sorts them by priority by default when viewing the ticket list. This means that the most pressing current issues in your project will always be at the top of the list.

Creating a Ticket

  1. Navigate to your project
  2. Click Tickets on the top navigation menu
  3. Click New Ticket on the sidebar or use the Quick Ticket form in order to quickly create a new ticket.

Creating a Ticket by email

The first thing you should do in order to create tickets by email, is find out the email address you should send tickets to. You can find the address by following the steps below:

  1. Navigate to your project
  2. Click Tickets on the top navigation menu
  3. Click New Ticket on the sidebar.
  4. On the sidebar of the New Ticket screen you'll find the email address you should use to email tickets to.

Once you have the email address you should use, you can send email to it and tickets will be created. The ticket description will be the email body, and the ticket title will be the email subject.

Ticket attributes

Tickets have the following attributes which you can set and edit from the New Ticket and Edit Ticket screens respectively.

  • Title - briefly describes the issue (used on the ticket list)
  • Description - a longer description of the issue. In many cases (particularly in software development projects) this includes steps in order to reproduce the issue the ticket relates to.
  • Priority - describes how important the ticket might be. Priorities can be Highest, High, Medium (also the default), Low and Lowest. Highest priority tickets should typically be addressed first, as they have higher impact.
  • Assignee - the person who the ticket is assigned to
  • Milestone - if the ticket should be solved before the project it belongs to hits a specific milestone

Tickets can also have attached documents and tags. Documents (usually screenshots or QA documentation) are typically used to further document the issue.