⚠️ OpenSpec-managed issue — this content is automatically synced
from the openspec/ directory. Manual edits will be overwritten on next sync.
Artifacts
Summary
Stackiq becomes the configuration management database (CMDB) for the application level: the applications an organisation uses, the components they are made of, the connections between them, and the licences and contracts behind them. A functional administrator connects stackiq to the organisation's service desk, TOPdesk or ServiceNow, through integriq. From then on the two stay in step in both directions:
- Import: a nightly run reads the service desk's application records, relations, licences and contracts, and creates or updates the matching stackiq records. A second run updates; it never duplicates.
- Export: when someone changes what stackiq owns on an application in use (owners, licences, contract, BBN level, TIME class), that change goes to the service desk record.
- Ownership decides conflicts, not time. Each mapping marks every field as owned by the service desk or by stackiq. The service desk wins for the fields it owns (name, supplier, installed version, status). Stackiq-only fields (licences, contracts, publication) always stay with stackiq. An import never overwrites a stackiq-owned field, and an export never sends a service-desk-owned field.
- No ping-pong. A write in one direction never comes back as a change in the other.
- A file import (CSV or XLSX) feeds the same flow for organisations without a service desk API.
Specs
Tasks
Design
See design.md for technical design details.
Synced from openspec/changes/sharing-itsm-exchange by OpenSpec workflow
App: stackiq
Artifacts
Summary
Stackiq becomes the configuration management database (CMDB) for the application level: the applications an organisation uses, the components they are made of, the connections between them, and the licences and contracts behind them. A functional administrator connects stackiq to the organisation's service desk, TOPdesk or ServiceNow, through integriq. From then on the two stay in step in both directions:
Specs
Tasks
tests/Unit/Settings/ItsmExchangeFragmentTest.php;ConnectionsDeclarationTest.phpcovers the itsm entry)tests/Unit/Settings/ItsmFlowTemplatesTest.php; preflight on the live instance in Task 3)tests/Unit/Service/ItsmExchangeServiceTest.php)tests/Unit/Service/ItsmFileImportServiceTest.php)tests/e2e/workflows/itsm-exchange.spec.ts)Design
See design.md for technical design details.
Synced from
openspec/changes/sharing-itsm-exchangeby OpenSpec workflowApp:
stackiq