Export/Import

Export OKRs

Exporting your OKRs in OKR for Jira is a straightforward process, and you have two options: using our API or creating a .csv export. This guide focuses on the .csv export method.

CSV export

1. In OKR for Jira, navigate to the OKR Overview table options menu.

   Open

   

2. Locate the Export button and click on it.

   Open

   

3. Choose your export options:

   • All OKRs: If you have filters applied, only those OKRs will be exported. To get everything, check "Export all columns."

   • Column headers: These are the labels at the top of each column. You can skip them if you prefer.

   • File name: Change the suggested name ("export.csv") to something you'll remember.

   • By default, two top options are already selected: displaying the visual hierarchy of the OKRs (which means that each new level will have a larger indent) and the hierarchy column (containing a list of numbered levels by which you can easily filter the list in a spreadsheet). The first two exported columns with hierarchy will look like this.

4. Click Export .csv file. The download should start automatically.

To open the file, use any spreadsheet program like Excel, Google Sheets, or Numbers.

Import OKRs

The OKR import feature allows you to quickly transfer your OKRs into OKR for Jira Cloud by using a CSV file.

Preparing the CSV file

To ensure a successful import, your CSV file must adhere to the following structure. Here's an example of a valid CSV file:

Required fields:

• Order: A unique numerical identifier for each OKR. Top-level objectives typically start with whole numbers (for example, 1, 2), while Key results or Sub-objectives use decimal numbers (e.g., 1.1, 1.2) to indicate their relationship to the Objective. This information is always required.

• Type: Specify whether the row represents an Objective or a Key result (case-sensitive). This information is required.

• Period: The timeframe for the OKR – it has to match an existing period in OKR for Jira.

• Owner: The Jira username or email address of the OKR owner.

• Status: The current status of the OKR. It’s not case-sensitive. It has to match an existing OKR status.

• Summary: A brief description of the OKR.

Optional fields:

• Expected Start/End Date: The start/end date of the OKR (format: DD/MM/YYYY). They are not required. If they are not present, they will be set based on the period.

• Start/Current/Target Value: The initial/current/desired end value for the Key result. These values are required for the KR.

• Description: A detailed explanation of the OKR.

• OKR type: The type of OKR (for example, Personal, Team, or Organizational).

• Teams: A multi-value field to indicate which teams are involved with this OKR.

• Labels: A multi-value field to assign labels to OKRs for easy categorization.

• Weight: Represents the OKR’s significance.

Before you import

• Ensure your CSV file is under 10 MB and saved in the .csv format.

• You must have the Create OKRs permission to import OKRs.

• UTF-8 encoding is supported, but avoid using UTF-8 with BOM (Byte Order Mark). This specific encoding can cause import errors.

You can execute one import per user at a time. Multiple simultaneous imports are possible for the tenant.

Steps

1. In OKR for Jira, navigate to the OKR Overview table options menu.

2. Locate the Import button and click on it.

3. Click Select file.

4. Select a CSV file.

5. Click Confirm.

Once the upload is successful, click Finish import to close the dialog. You can monitor the import status on the left-hand side of the screen.

You’ll receive an email about the status of your import:

Troubleshooting errors

If there is at least one error, the import won't be successful and no OKRs will be added. You might encounter a screen similar to this:

In any case, please carefully review your CSV file. Common reasons for errors include:

• Duplicate Order numbers: Key Results should not have the same order number as an Objective.

• Incorrect Type: Ensure entries are either Objective or Key result (case-sensitive).

  Period mismatch: Check that the "Period" in your CSV matches an existing period name in OKR for Jira.

• Invalid Owner: Use a valid Jira username or email address.

• Symbols in Summary: You may encounter issues with UTF-8 encoding with BOM. While English text works well, inputting alphabetic symbols may lead to failures.

• Missing Expected Start/End Date – If the Period fails, these might fail, too. Otherwise, they shouldn't cause any problems.

• Missing values in Key Result columns: Key Results require values for Start Value, Current Value, and Target Value.