1. SR 重點
 欄位
SR Number
Customer Name
Product Name
Create Date
Creator
Build Complete Due
QA Complete Due
Shipping Date
Status
Comments
Responsible person
File Uploads
 關聯資訊
VIP 列表
TR 列表
 動作
Edit/Cancel/Close SR
Add Comment
Edit Response Person
Create TR

2. TR 重點
 欄位
Product Name
Project Name
TR Code
Create Date
Creator
Program Path
Build by
Due Date
Close Date
Issues
Status
Status Log
Result
File Uploads
 關聯資訊
Bugs from which this Testing Request is created (本張TR所送測的VIP/ebug, 若此
TR 是主線初次送測，不會有要驗證之 ebug，則無此資訊)
This TR Generated the following eBug (本張 TR 送測後所測到新的 ebug)
This eBug requested to be Resolved by these shipping requests: (來源 SR, 若不是
從 SR 開出，則無此資訊))

3.  動作
請與 QA 討論
 其他: 其他如 QA report 等相關功能是否有需要，請直接與 QA 討論

4. VIP 重點
 欄位
Product Name
Project Name
Bug Code
Issue Type
Creator
Creation Date
Closed Time
Short Description
Description
Priority
Severity
Status須整理狀態清單，與每個狀態可以到哪些下個狀態，整理成 flow
Status Log
Comments 須指定是否能給客戶看到
File Uploads
 關聯資訊
This eBug generated the following Testing Request & QA Report: (此 VIP/ebug 所被
加入過的 TR)
This eBug requested to be Resolved by these shipping request(s): (此 VIP/ebug 被
包含在哪些 SR)

5.  動作
動作繁多，各種狀態底下，不同角色會有不同動作按鈕，需要花些時間分析