Tickets vs Tasks
This is a question we get asked quite often, mostly because at a first glance tasks and tickets do seem to work in similar ways. They are certainly not the same, however. Tickets (or issues, as they're commonly known in the software development world) are used to document defects with a given project. Since this is easier to understand using examples, see a few below:
Tasks are typically used to describe things that need to be done in a project to meet a certain goal. Here's a list of potential tasks in a category
"Make an espresso":
- Verify the machine has enough water
- Turn machine on
- Add coffee to espresso machine
- Place cup in the correct spot
- Push "Espresso" button
Tasks can have deadlines (you may need an espresso in 5 minutes), and can be assigned to certain people (you can assign John with the task of turning the machine on, and Jane of pushing the "Espresso" button).
Tickets are a great fit when you are dealing with a project that may have defects, issues or bugs. Keep in mind this doesn't apply only to software projects. Below is an example of possible tickets in a
"Make an espresso" project:
- Machine doesn't turn on
- Espresso button is stuck
- Espresso cup is broken
Tickets can, much like tasks, have an assignee (who'll be in charge of fixing the related issue), but unlike tasks, have no due date. They do, however, have a set priority, so that you can sort by priority when trying to see which bugs to fix next.