> For the complete documentation index, see [llms.txt](https://docs.giize.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.giize.com/product-docs/api-reference/staging-itsm-domains.md).

# Staging ITSM Domains

## Broader ITSM Families In Staging Docs

Beyond Request, the staging docs expose a full ITSM-style surface:

* Problem
* Change
* Project
* Release
* Approvals
* Task
* Worklog
* Asset
* CMDB
* Reports
* Announcements
* Software

## What This Means For Future Work

The current repo does not use all of these domains directly, but the staging docs show they are available for deeper automation if needed.

## Domains With The Best Expansion Potential

### Problem

Useful for:

* associating requests to root-cause analysis
* note and template workflows

### Change

Useful for:

* request/change association
* release planning
* approval and CAB flows

### Project And Release

Useful for:

* structured rollout workflows
* release/project association from change or request flows

### Task And Worklog

Useful for:

* richer operational tracking
* time accounting and task-level execution state

### Asset And CMDB

Useful for:

* stronger ticket-to-asset linkage
* CI-aware automation
* hardware/software inventory context

## Recommendation

Do not expand into all domains at once.

Use this order if the repo grows beyond current request-centric behavior:

1. Request metadata
2. Request notes and attachments
3. Task and worklog
4. Asset and CMDB
5. Problem / Change / Release / Project