Ticket Workflow » 履歴 » リビジョン 2
リビジョン 1 (Kousuke Ebihara, 2009-09-23 14:28) → リビジョン 2/7 (Kousuke Ebihara, 2009-09-23 14:35)
h1. Ticket Workflow h2. Overview All of tickets have a status. You can change a ticket status on the updating ticket page. Your usable statuses are restricted by some reasons. For example, a reporter of the project can't use the "Accepted" status, and the "Rejected" status can't change to the "Fixed" status. h2. Detail Description of workflows h3. Bug The following image explains the workflow of bug ticket. !スライド1.png! !http://op3.ebihara.redmine.dazai.pne.jp/attachments/5/%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%891.png! h3. Enhancement The following image explains the workflow of enhancement ticket. !スライド3.png! !http://op3.ebihara.redmine.dazai.pne.jp/attachments/6/%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%893.png! h3. Back Port Back port ticket is used for defect ticket or enhancement ticket that is for multiple versions. You must deal such a ticket on the current development version first, you fix that, another developer reviews that, a tester tests that, and you create a related ticket to back port to old version (s). The ticket on the current development version is called as "original ticket". The original ticket must be dealt as normal bug ticket or enhancement ticket. Also the back port ticket is dealt as normal ticket. It means a change for the back port ticket must be reviewed and be tested. Because that change doesn't work in old version correctly even if it works original version fine sometimes. The following image explains the workflow of back port ticket. !スライド5.png! !http://op3.ebihara.redmine.dazai.pne.jp/attachments/7/%E3%82%B9%E3%83%A9%E3%82%A4%E3%83%895.png!