Administration and maintenance

Ongoing configuration and maintenance

Purpose

This page bundles the ongoing configuration and maintenance tasks in Setup & Configuration — including the effect and risks of each change.

Managing field options (Custom fields)

Under Setup & Configuration → Custom fields, administrators manage the select options of the app’s fields: add or rename options. Effect: new options are available in Jira immediately; renames affect existing issues. Deleting options is deliberately not offered.

“Custom fields” page with field cards, select options, a pencil for renaming and a “New option…” box — Custom fields: select options per field with a pencil for renaming and “New option…” for adding, above them the note about option values used in filters and queues.

Re-applying Confluence smart links

If the embedded Jira tables in the Confluence space no longer match after changes (e.g. after filter repairs), use the Confluence Smart Links card with Re-apply smart links. Effect: the app re-points the live tables at its own filters; page contents stay untouched.

“Confluence smart links” card with description and the “Re-apply smart links” button — Setup & Configuration: the “Confluence smart links” card with “Re-apply smart links”, which re-applies the embedded Jira filter links in the “ISMS Home” space.

Importing custom controls (CSV)

The card Import custom controls (CSV) creates framework controls (e.g. TISAX, customer requirements) as requirement issues: paste the CSV into Paste CSV, check the preview (“n controls recognised”), click Import. Created issues carry the label custom-control. Precondition: the “Requirement” issue type is installed.

Card “Import custom controls (CSV)” with the “Paste CSV” field (sample row as placeholder) and the “Import” button — Setup & Configuration: card “Import custom controls (CSV)” with the “Paste CSV” field and the “Import” button.

After app updates: update the configuration

For the modules ISMS Home and ISMS Confluence Toolkit, the respective card offers Update configuration:

ISMS project: “Applies fields, option values and schemes from the current app version. Existing issues and data stay untouched — no delete-and-reinstall needed.”
Confluence space: “Applies page templates and space permissions from the current app version. Pages someone has edited stay untouched — nothing is overwritten and nothing is deleted.”

Module cards “ISMS Project”, “ISMS Confluence Toolkit” and “Demo content” with the “✓ INSTALLED” badge and buttons — Setup & Configuration: module cards with the “✓ INSTALLED” badge and the “Open”, “Update configuration” and “Uninstall” buttons — the demo content deliberately has no update button.

Licence

The License block shows status and check time; Re-check license refreshes immediately. Without a valid licence, installation, repair, reports, automation runs and the write functions of document control are blocked; existing data stays readable.

“License” block in Setup & Configuration: status “valid=true” with check time and the “Re-check license” button — Setup & Configuration: “License” block with a valid licence status, check time and the “Re-check license” button.

Uninstalling

If the app itself is removed via Jira administration (Manage apps), the project, space and filters remain — the app deliberately registers no deletion automatism. For a complete cleanup: first remove the building blocks in the hub, then the app.

Card “Remove the ISMS completely” with warning text and the red “Uninstall” button — Setup & Configuration: card “Remove the ISMS completely” with its warning text and the “Uninstall” button.

Screenshots from the development environment with sample data.

Documentation baseline: app version 1.1.15 · 2026-08-20