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