Project and Issue-Type Setup
Before your team can create Objectives and Key Results, OKR Tracker needs to know which Jira project holds your OKRs and which issue types, fields, and link type to use. You run this setup once, from OKR Settings, in the Onboarding & Data section. It is admin-initiated and never runs automatically on install — you stay in control of every change made to your Jira configuration.

OKR Settings project and issue-type mapping
## Run the onboarding flow
Open OKR Settings (Jira Settings → Apps → OKR Settings) and go to Onboarding & Data. Work through the steps in order:
Pick the OKR project → choose the Jira project that will hold your Objectives and Key Results. Everything the app reads and writes is scoped to this project.
Confirm or create the issue types → the app checks for the Objective and Key Result issue types. If they already exist, it reuses them; if not, you can create them from here.
Confirm or create the custom fields → Quarter, Target/Current Value, Unit, Progress %, and Confidence Level. These hold the OKR attributes that drive the rollup and reports.
Confirm or create the "realizes" issue link type → this links a Key Result to the Objective it contributes to.

Onboarding creating Objective and Key Result types
## Why onboarding needs an extra scope
Creating issue types, custom fields, and the link type changes your Jira configuration, so this step uses the manage:jira-configuration scope. The app only exercises it during onboarding — never as part of day-to-day OKR work. See Data Handling and Permissions for a plain-language breakdown of every scope.
Idempotent and safe to re-run
Onboarding is idempotent: if a type, field, or link type already exists, the app detects it and reuses it instead of creating a duplicate. You can re-run the flow safely at any time — for example, after adding a missing custom field — without disturbing the parts that are already in place.
Until a project is set
Until you set the OKR project, Objective and Key Result creation is disabled. The hub still shows the dashboard, so you can explore the app, but the create actions stay locked until setup is complete.
Who can run this step depends on your app role — see Roles and Permissions. For first-time installation, start with Installation and Setup.