Skip to content

Creating Records

2 min read

Not every sentence is a question. Let's create a test case is an instruction, and Oracle recognises it as one.


  1. Open Oracle in a project.

  2. Type what you want to start — for example, create a defect, or let's add a requirement.

  3. The real create form opens in the panel beside you, blank and ready.

Ten kinds of record can be started this way:

Test caseRequirement
Test runTest suite
Shared stepCustom field
FolderDefect
ReleaseRelease execution

Oracle takes you to the right form. It does not fill it in.

Create a high-priority login test case for checkout opens an empty test case form — not one with the priority set and the title written. Oracle read the sentence well enough to know which form you wanted, and that is where it stops.


The panel swaps the form for the record you just created, so you can check it, keep editing, or move on without hunting for it.

A folder is the exception — there is no page to open — so it closes with a confirmation instead.


A release execution asks first. It needs to belong to a release, so Oracle shows you the releases in the project and opens the form once you have picked one.

Being offered a form is not permission to save one. Oracle opens what your question named; the save is authorised separately, by the same rules that guard the form anywhere else in Hawzu.


The kinds on that list are not fixed for everyone. Oracle offers the ones your role can create in this project, so a reader-only role asking to start a defect is told it cannot rather than being shown a form that fails on save.

That check happens the same way everywhere else in Oracle: your permissions shape what is available before the question is planned, not after the answer comes back.


The header assistant does not open forms — the panel is too narrow for a two-pane form with rich-text editors. It recognises the instruction and offers you a link to the Oracle page instead, where the form has room.