Databases Reference
In-Depth Information
When you press the Log as Bug button on the page in Figure 4-25, a bug is created and, apart from
the information entered in this page, some context is filled in, like the application, the page, and the
version. Figure 4-26 shows the resulting bug report.
Figure 4-26.
Bug report created from feedback
Strangely, other information that is captured by using feedback isn't automatically added to the
bug, like the platform, browser, and operating system. And even more interesting stuff, like the complete
session state, is captured but not copied to the bug description. There is also no visible reference from
the bug to the feedback to retrieve that information afterwards.
Similar to creating a bug from a feedback entry, you can also create a To Do from a feedback entry,
or even transform a feedback entry into a Feature. Remarkably, only when transforming a feedback entry
into a To Do, is there an option to delete the feedback entry. But deleting feedback before the issue is
completely solved isn't a good idea, because of all the information that's contained within the feedback
that might be relevant for sorting out the issue.
Notice that Figure 4-26 mentions “Converting feedback to a bug will set the feedback status to
closed”. Despite this message, that isn't really the case. In the current version of APEX (4.0.2 as I write
this chapter), you must change the status of the feedback by hand.
Instead of —or in addition to—logging the feedback as a Bug or a To Do item, you can also edit the
feedback. Doing so, you can change the status and add comments. See the example in Figure 4-27.
