Databases Reference
In-Depth Information
Figure 4-17.
Data model of Bugs
All information regarding To Do's is exposed through the
APEX TEAM BUGS
view, which is mainly
based on the
WWV FLOW BUGS
table.
A Bug has a Status, a Severity, and a Priority. The values in these select lists are defined in the views
WWV FLOW BUG STATUS CODES
,
WWV FLOW BUG SEVERITY
, and
WWV FLOW BUG PRIORITY
. When resolving a bug,
it's assigned to a person and planned to be fixed by some release, milestone, and/or date. Furthermore
you can add a lot more information on the bug itself, like the platform, browser, or operating system.
Figure 4-18 shows an example of a filed bug.
Figure 4-18.
Example of a Bug
Because a Bug only contains a Fix Date—and no start date or effort—you have to link a Bug to a To
Do in order to use a reported Bug in your customized Gantt Chart. The Bug section is intended for
capturing issues that might be customer browser- or operating system-specific.
