Initial setup

Language, project type and required entries

Purpose

Before installing you decide three things: the content language, the project type and the responsible person. Without these, the install buttons stay disabled — the app states the reason in each case.

Who can do this

Jira administrators only.

Setup blocks “Step 1: Choose your language”, “Step 2: Choose the project type” and “Step 3: Person responsible” — Setup & Configuration: the three preparatory steps “Step 1: Choose your language”, “Step 2: Choose the project type” and “Step 3: Person responsible”.

Step 1: choose the language (mandatory)

Open Setup & Configuration in the hub (or click Go to setup on the start view).
In the highlighted block “Step 1: Choose your language”, click English or Deutsch.

Everything created afterwards — project, issue types, fields, statuses, workflows, filters and Confluence pages — is created in that language. There is deliberately no silent default: without a language choice the install buttons stay disabled (hint: “Please choose a language first (step 1 above).”) and the server rejects the installation.

Step 2: choose the project type

The block “Step 2: Choose the project type” offers two buttons:

Choice	When it makes sense
Jira (Business) — default	“Recommended. The ISMS runs as a regular Jira project — no JSM licence required.”
Jira Service Management — opt-in	“Only choose this if your site is licensed for JSM and you want queues and the customer portal.”

Step 3: name the responsible person

In the card “Step 3: Person responsible”, enter the person in the field Information security officer (CISO) — or click That's me.
Click Save. The card badge switches from open to ✓ named.

Without a named person the server refuses the installation; the buttons show the hint “Please name the person responsible first – otherwise nobody but you can see the ISMS issues.” Background: the app derives the project and space permissions from the role register — one person is enough to start, and you can maintain all further roles any time under Roles & responsibilities (Assigning roles and go-live checklist).

Only on sites with a legacy installation: confirm the move

If the app finds one of the four legacy projects (ISMSANF, ISMSAUN, ISMSMM, ISMSRISK) on your site, the card “📦 Earlier ISMS projects on this site” appears, listing the found keys and explaining what the installation does — and what it does not:

It creates the new “ISMS” project, adopting the issue types, fields and statuses your existing installation already has.
It points the 30 app filters at the new project — until you have moved your issues, those filters return no results.
It does not move any issues: the four old projects, with all their data, history and attachments, stay untouched.

Read the notice and tick “Understood — create the ISMS project now, leave the old projects unchanged”.
You see “✓ Confirmed — installation is unlocked.”

You bring your issues along later yourself, using Jira's “Move issues” bulk change — one issue type at a time, with a 1:1 mapping. The app ships the guide “Moving from four projects to one” for this. The app's recommendation: move your issues, then delete the four old projects — but only once you have verified the hand-over.

Expected result

In the checklist “What's left to do”, the steps Choose the language, Choose the project type, Name the responsible person (and, if shown, Confirm the move) are ticked; Install the ISMS project is now marked “Do this next”.

Checklist “What's left to do” (3/5 done): language, project type and responsible person ticked, “Install ISMS project” is “Up next” — Setup & Configuration: “What's left to do” checklist after the required entries — “Choose the language”, “Choose the project type” and “Name the responsible person” are ticked, “Install the ISMS project” is marked as up next.

Screenshots from the development environment with sample data.

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