Qintorava DocsProduct documentation
Form reference

Incidents

39 declared fields for Incident. Required fields include Short description, Description.

Demo baseline · November 13, 2026
Download PDF

About this form

Use this reference to identify built-in form labels, data types, and validation. Specialized workspaces can render a subset of these fields or provide workflow-specific controls. Your role, record state and tenant configuration can change what you see.

Registry key
incident
Record label
Incident
Record prefix
INC
Workspace
Open Incidents

Field definitions

FieldType or referenceBuilt-in rulesChoices and constraints
Number
number
textRead-only
Default list field
—
Short description
title
textRequired
Default list field
—
Description
description
textareaRequired—
State
state
selectDefault list fielddraft, new, in_progress, on_hold, resolved, closed, cancelled
On Hold reason
holdReason
selectOptional by defaultRequired only while the ticket is On Hold.
awaiting_caller, awaiting_change, awaiting_problem, awaiting_vendor, awaiting_evidence, awaiting_approval, awaiting_schedule
Requester
requesterId
reference
users
Optional by default—
Opened by
openedById
reference
users
Read-onlyAutomatically set to the signed-in user.
Company
companyId
reference
companies
Optional by default—
Location
locationId
reference
locations
Optional by default—
Department
departmentId
reference
departments
Optional by default—
Cost center
costCenterId
reference
cost_centers
Optional by default—
Category
category
selectDefault list fieldHardware, Software, Network, Identity and Access, Cloud, Security, Business Service
Subcategory
subcategory
selectOptional by defaultDepends on category
Hardware allows Laptop, Desktop, Printer, Mobile device, Peripheral
Software allows Business application, Operating system, Installation, License
Network allows VPN, Wi-Fi, LAN, DNS, Internet
Identity and Access allows Account locked, Password reset, MFA, Permissions, SSO
Cloud allows Compute, Storage, Database, IAM, Network
Security allows Phishing, Malware, Vulnerability, Data loss, Policy
Business Service allows Unavailable, Degraded, Performance, Access
Impact
impact
selectOptional by defaulthigh, medium, low
Urgency
urgency
selectOptional by defaulthigh, medium, low
Priority
priority
selectRead-only
Default list field
Calculated automatically from impact and urgency.
critical, high, medium, low
Assignment group
assignmentGroupId
reference
groups
Default list field—
Assigned to
assigneeId
reference
users
Default list field—
Watch list
watchList
list_collector
users
Optional by defaultPeople who receive ticket updates.
Due date
dueDate
datetime-localOptional by default—
AI summary
aiSummary
textareaRead-only—
Resolution
resolution
textareaOptional by default—
Resolution code
resolutionCode
selectOptional by defaultsolved_permanently, solved_workaround, duplicate, known_error, user_error, no_fault_found, withdrawn
Close notes
closeNotes
textareaOptional by default—
Created
createdAt
textRead-only
Default list field
—
Updated
updatedAt
textRead-only—
Contact type
contactType
selectOptional by defaultself_service, email, phone, chat, monitoring, walk_up
Business service
businessService
reference
__business_services
Optional by defaultLookup display fields number, title
Application service
applicationServiceId
reference
__application_services
Optional by defaultRequired when the incident affects a business application. Select the service that delivers the application.
Lookup display fields number, title
Affected configuration items
affectedCis
list_collector
__cmdb
Optional by default—
Symptoms
symptom
textareaOptional by default—
Work notes
workaround
textareaOptional by default—
Customer communication
callerCommunication
textareaOptional by default—
Resolved at
resolvedAt
datetime-localRead-only—
Reopen window ends
reopenUntil
datetime-localRead-onlyThe requester can reopen this incident for five business days after resolution.
Auto-closed at
autoClosedAt
datetime-localRead-onlyAuto-closed incidents are locked and cannot be reopened.
Datacenter customer account
dcAccountId
reference
customer_accounts
Optional by default—
Demo record key
demoKey
textHidden by defaultStable identifier used by the idempotent demo fixture loader.
Demo dataset
demoDataset
textHidden by defaultSynthetic demonstration records. Not actual organizational inventory, financials or execution evidence.

Lifecycle values

These are stored values from the form definition. Workflow actions can apply additional prerequisites, approvals, and side effects. The workflow determines which transitions are allowed.

FieldValues
Statedraft, new, in_progress, on_hold, resolved, closed, cancelled

Related procedure: Resolve, reopen, and close an incident.

Verification evidence

The disposable audit exercised 12 applicable validation assertions on this definition. The authenticated collection read returned HTTP 200. See the verification matrix for scope.

Collection read results by built-in role

These statuses were observed over HTTP with one role per disposable MFA account. A successful list response can be empty and does not establish individual record, field, or write access.

RoleHTTP status
Asset Manager200
Change Manager200
CMDB Manager403
Contract manager200
Customer service agent200
Customer service customer403
Customer service manager200
Datacenter Customer403
Datacenter Fulfiller200
Datacenter Manager200
Datacenter Vendor403
EH&S auditor403
EH&S manager403
Executive Reader200
Field service dispatcher200
Field service technician200
HR case agent403
HR knowledge manager403
HR lifecycle manager403
HR profile manager403
Employee Relations investigator403
HR service catalog administrator403
Inventory Counter403
ITIL Fulfiller403
Knowledge Manager200
Business Manager200
Platform Administrator200
Service Desk Agent200
Vendor manager200
Third-party risk manager200
Employee with no workspace role403

Edit and verify

  1. Open the list from the appropriate workspace and select an existing record or a permitted create action. Confirm the intended tenant and record number.
  2. Use the visible controls for the current record type and state. For reference fields, select a returned record from the lookup. Fill visible required fields and use the dedicated workflow action when the record has approval or completion gates.
  3. After saving, reopen the record and compare its persisted values, state and activity to the intended change. Check the downstream linked record when the action creates one.

Troubleshoot

  • Missing field or control: compare the role, module, record state, form conditions and tenant overrides.
  • Lookup returns no result: check that the referenced record is active, in scope and compatible with the current field.
  • Save is rejected: keep the exact validation message and compare the field key, choice, constraints and required related records.
  • See Edit and troubleshoot records and Configuration Studio.