Documentation / Manual catalog

Maintain a manual catalog

1. Open app settings and choose Manual configuration.
2. Select Add service, enter a name and optional group, then add versions in the details panel.
3. Use the arrow controls to reorder entries, edit names in place, or select Remove. Removing a service removes its versions from the active draft.
4. Select Save configuration. Changing the source or editing the draft alone does not change the saved catalog.

Names, search, and limits

The service list shows 20 entries per page and version lists show 10. Search finds older entries. Names are trimmed and must contain 1–300 characters; optional groups may contain up to 300 characters. Group and service name pairs must be unique, and version names must be unique within a service. Duplicate validation is case-sensitive.

Import JSON

Download Template, select Import JSON, review the added, updated, and removed counts, select Apply to draft, and finally save the configuration. Import replaces the catalog represented by the draft, so omitted entries can be removed.

{
  "schemaVersion": 1,
  "services": [
    {
      "name": "payments-api",
      "group": "Payments",
      "versions": [
        {"name": "2.4.1", "createdAt": "2026-09-01T00:00:00Z"}
      ]
    }
  ]
}

Import files are limited to 10 MiB, catalogs to 1,000 services, and each saved service record to 200 KiB. Empty catalogs and services without versions are allowed. Duplicate group/name records keep the last complete record with a warning; duplicate version names are rejected.

Export and identity

Export JSON downloads a portable catalog. Export excludes internal IDs; import ignores supplied IDs and matches services by group/name and versions by name. Renaming in JSON creates new records. An export is not an identity-preserving backup of Jira values, API credentials, or old revisions.

Switching to manual mode retains saved API settings and credentials. Removing an active option does not rewrite existing Jira field values.

Automatic cleanup of replaced catalog records

VersionSelect saves manual catalogs as immutable records so a failed or concurrent save cannot corrupt the active catalog. Editing, importing, or replacing a catalog can therefore leave internal rows, indexes, or expired save sessions that are no longer referenced.

Automatic background maintenance runs daily in bounded batches. It removes eligible records only after they have remained unchanged for at least 24 hours and are not referenced by the active catalog or a valid draft. There is no cleanup button or maintenance workflow in app settings, and background maintenance does not pause configuration saves.

Automatic cleanup does not delete the current catalog, recent or active draft records, Jira field values or history, API credentials, caches, logs, external catalog records, or downloaded exports. It is storage maintenance rather than a revision restore or complete customer-data deletion tool. Review data deletion and retention for those separate responsibilities.