2. Via the View Tickets entry on the menu bar and then choosing the Active
Tickets by Milestone report.
Having raised our ticket and decided when we are going to do it, we need to decide
who will implement it. We do this by assigning the ticket to someone, who then
becomes responsible for executing any actions required by the ticket, including
closing it when complete. This is also known as resolving the ticket. We do this by
editing the ticket and either accepting it??”if we are going to perform the work??”or
assigning it to a valid user name of someone in our development team.
Once tickets have been assigned to someone they can easily view their tickets via the
View Tickets entry on the menu bar and then choosing the My Tickets report. Now
our developers have a simple job of working through the open tickets on their list.
Chapter 7
[ 77 ]
As already discussed, each ticket should have its own branch. We do this so that
changes made are isolated from the development trunk and from other branches.
This means that we are always developing against a known quantity??”the trunk. Our
branches are created exactly as shown in the previous chapter, except that the branch
name and commit log should make a reference to the ticket number, e.
Pages:
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106