Getting started: open the app, configure it and load demo data

Outcome: you can open the app, find your way around the interface, set the language and the basic settings and – for a trial run – load the built-in demo data.

Prerequisites

• A Jira Cloud site on which the app DORA Register of Information is installed. A site administrator installs it and, during installation, consents to the app’s external connection to api.gleif.org (required for the GLEIF LEI check) and to the app permissions (read and write Jira work, app storage).
• A Jira user account on that site. The app appears in the Jira Apps menu. Your Jira administrator controls who can see the app – the app has no roles of its own.
• A current browser that allows downloads (the export triggers a browser download).
• For the Jira workflow (optional): a Jira project in which the app may create issues, with the issue types Epic and Task (or the names entered in the settings) – see Jira workflow: annual-report epic, finding issues and the “RoI Record” issue panel.

Open the app

1. Log in to Jira and click Apps in the header.
2. Click DORA Register of Information (the app name is the same in both languages).
3. The app opens as a page of its own with a left navigation bar (header: DORA RoI) and starts on the Cockpit. There is no Jira sidebar on this page.

First orientation in the interface

Cockpit

• Five tiles: ICT service providers, Contractual arrangements, Business functions (number of records in B_05.01, B_02.01, B_06.01), Validation (number of errors; badges No findings or “n errors”/“n warnings”) and Submission deadline. Every tile is clickable and opens the matching area.
• Table Completeness per template: per template the number of records, the share of filled mandatory fields (per ITS) across all records and a status: empty (no records), complete (all mandatory fields filled), in progress (mandatory fields missing). Clicking a row opens the template.
• Recent exports: the last five generated packages with file, date and validation status (“no errors” or “n errors”); before the first export it reads “No xBRL-CSV package generated yet.”.
• Tile Submission deadline: No deadline configured while no date is saved; afterwards n days remaining (more than 30 days), n days remaining (30 days or fewer), Only n days left (7 days or fewer) or Deadline passed.

Switch the language

1. Click Settings in the navigation (area Reporting).
2. In the card Language click 🇬🇧 English or 🇩🇪 Deutsch. The interface switches immediately.

• The choice applies per browser (it is stored in the browser, not in the user account) and is also used by the “RoI Record” issue panel.
• The default is English. App error messages also appear in the chosen language; exception: the results of the GLEIF check are always in German (see Validation).
• Issues created from the app (epic, finding issues) use the language that was active when they were created; automatically created epics are in English.

Configure the basic settings

Procedure

1. Click Settings.
2. Enter the values in the cards (table above).
3. Click Save. Expected result: green banner “Settings saved.”. The settings apply to all users of the installation (not only to you).

The button Create annual-report epic now is described in Jira workflow: annual-report epic, finding issues and the “RoI Record” issue panel.

Load demo data (for a trial run)

1. Click Settings and scroll to the card Demo & test.
2. Click Load demo data. While loading, the button reads “Loading…”.
3. Expected result: green banner “Demo data loaded: 60 records created, 0 updated. Check the cockpit and the validation center.”. Loading again shows “0 records created, 60 updated”.
4. Open the Cockpit: 10 ICT service providers, 8 contracts, 6 functions, validation 3 errors, 1 warning (deliberate gaps in the demo data).

• Description in the app: “Loads the fictitious payment institution "Nordpay" as a sample register: 10 ICT providers, 8 contracts, 6 functions, supply chains (4th party) and assessments — including some deliberate gaps so validation and the Jira workflow can be demonstrated. LEIs are synthetic (valid check digits, not registered with GLEIF). Loading again updates the data (upsert).”
• The demo LEIs are synthetic: valid check digits, not registered with GLEIF – the GLEIF check reports this accordingly.
• Demo data and real data share the same register. They can only be removed one by one (Delete per record) or altogether with Delete all register data. Therefore do not load demo data into a register that already contains real data.

Delete all register data

1. Click Settings, scroll to the card Demo & test and click Delete all register data (red button).
2. The browser asks: “Really delete ALL register data? This affects all 15 templates and cannot be undone.” – confirm with OK (or cancel).
3. Expected result: green banner “All register data deleted.”. The records of all 15 templates are deleted. Settings, export history and Jira issues that were already created are not deleted.

Next steps

• Create, edit and delete records (maintaining the register)
• The 15 EBA templates at a glance
• Import an EBA Excel register
• Validation and data quality: consistency checks, EBA rules, GLEIF LEI check