concept ticket in category software development

This is an excerpt from Manning's book Agile ALM: Lightweight tools and Agile strategies.
When synchronizing a ticketing system with changes in the VCS (depending on the commit message), you change the state of tickets; for instance, you close or comment on them.
On the right side of the screen, the ticket reporter is listed as well as the current assignee. You can assign other people to continue the work on that issue. Voting for a ticket is a nice feature: You can vote on tickets to express the importance of the ticket and the team can determine how many developers consider the ticket important. You can watch a ticket and its progress to keep informed of ongoing activities. You’ll automatically get emails advising of any changes to tickets you’re watching. The right panel also includes information about when the ticket was created and last updated.
Ticket updates are based on Trac’s configurable status transition and workflow facility (for example, assigning tickets to other people). Tickets can be assigned to milestones. Milestones also display the ticket status; for instance, which tickets are open and which ones are closed. Besides seeing the ratio of closed to active tickets, you can see the milestone due date and can enter the milestone detail page.

This is an excerpt from Manning's book Test Driven: Practical TDD and Acceptance TDD for Java Developers.
Let’s say you had forgotten that today is your spouse’s birthday and that she’s anticipating the Knicks game[7] you promised to take her to. The problem is, you don’t have the tickets, and the game is sold out. As a last resort, you go to the black market for tickets, but you can’t come find one. What you’ve got is a case of a blocking method: BlackMarket#buyTicket.