Ticket Workflow » 履歴 » バージョン 5
kaoru n, 2014-10-21 13:22
1 | 1 | Kousuke Ebihara | h1. Ticket Workflow |
---|---|---|---|
2 | |||
3 | h2. Overview |
||
4 | |||
5 | All of tickets have a status. |
||
6 | |||
7 | You can change a ticket status on the updating ticket page. |
||
8 | |||
9 | 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. |
||
10 | |||
11 | 3 | Kousuke Ebihara | h2. Explain of Statuses |
12 | |||
13 | Update a status of a ticket by progress of work. |
||
14 | |||
15 | h3. New(新規) |
||
16 | |||
17 | This is a default status of a ticket. A staus of new ticket is this. |
||
18 | |||
19 | h3. Pending Fixing(修正待ち) |
||
20 | |||
21 | This is a status for representing after reproducing. It can show itself that is reproduced well and has many informations, for developers. |
||
22 | |||
23 | This status is used only for bug ticket. |
||
24 | |||
25 | h3. Accepted(着手) |
||
26 | |||
27 | This status shows that a developer has started working for this ticket. Changing a status of a ticket to this, it shows "Currently working for this ticket to serve you!" and keeps away other developer works too. |
||
28 | |||
29 | h3. Pending Review(レビュー待ち) |
||
30 | |||
31 | This status shows that a developer has finished working for this ticket, and it requests reviewing. |
||
32 | |||
33 | 4 | kaoru n | If you want to use this status, "Corrected code is pull requested." must be met. |
34 | 1 | Kousuke Ebihara | |
35 | 5 | kaoru n | about 'pull request' is "here":https://redmine.openpne.jp/projects/op3/wiki/Pull_Request_Policy |
36 | 4 | kaoru n | |
37 | 3 | Kousuke Ebihara | h3. Pending Testing(テスト待ち) |
38 | |||
39 | 1 | Kousuke Ebihara | This status shows that a reviewer has finished working for this ticket, and it requests testing. |
40 | 4 | kaoru n | |
41 | h3. Pending Merge(マージ待ち) |
||
42 | |||
43 | This status shows that a tester has finished working for this ticket, and it requests merging. |
||
44 | 3 | Kousuke Ebihara | |
45 | h3. Rejected(差し戻し) |
||
46 | |||
47 | This status shows that a ticket has fault some problems. A charge of that ticket must work for problems, and change status to "Pending Review(レビュー待ち)". |
||
48 | |||
49 | h3. Fixed(完了) |
||
50 | |||
51 | This status shows that a ticket is completed. |
||
52 | |||
53 | h3. Works for me(再現せず) |
||
54 | |||
55 | This status shows that a reported phenomenon couldn't be reproduced. |
||
56 | |||
57 | If this status is used, probably a report is wrong or short. If you think that a ticket isn't wrong, please review the report and change status to "New(新規)". |
||
58 | |||
59 | h3. Invalid(無効) |
||
60 | |||
61 | This status shows that a ticket is created by a mistake. |
||
62 | |||
63 | h3. Won't fix(対応せず) |
||
64 | |||
65 | This status is used for a ticket that won't be working. For example, this is used for request of a feature that must be in plugin. |
||
66 | |||
67 | 1 | Kousuke Ebihara | h2. Detail Description of workflows |
68 | |||
69 | h3. Bug |
||
70 | |||
71 | The following image explains the workflow of bug ticket. |
||
72 | |||
73 | 2 | Kousuke Ebihara | !スライド1.png! |
74 | 1 | Kousuke Ebihara | |
75 | h3. Enhancement |
||
76 | |||
77 | The following image explains the workflow of enhancement ticket. |
||
78 | |||
79 | 2 | Kousuke Ebihara | !スライド3.png! |
80 | 1 | Kousuke Ebihara | |
81 | h3. Back Port |
||
82 | |||
83 | Back port ticket is used for defect ticket or enhancement ticket that is for multiple versions. |
||
84 | |||
85 | 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). |
||
86 | |||
87 | 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. |
||
88 | |||
89 | 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. |
||
90 | |||
91 | The following image explains the workflow of back port ticket. |
||
92 | |||
93 | 2 | Kousuke Ebihara | !スライド5.png! |