Korl Knowledge Base

Everything you ned to know to get the most out of Korl.

Key Concepts

Roadmap projects
Project attributes
Korl Artifacts

Configure Attribute Data Settings

Configure attribute data sources
Manage attributes in Korl
Sync attributes from Jira or Linear
Infer attributes from the project doc
Ask KorlAI to generate content

Import and Sync Data into Korl

Import & sync data into Korl
Sync data from Jira
Sync data from Linear
Sync data from Notion
Sync Data from Google Docs
Sync data from Confluence
Sync data from somewhere else

Korl Artifacts

An artifact is a piece of communication collateral created in Korl. Currently, Korl can auto-generate two different types of artifacts: presentations, and updates.

Presentations can be created at any time from the “Create presentation” button. The format and content will depend on the presentation template you choose. There are also many ways to configure and edit the presentation once you create it.

When you create a presentation, Korl grabs the latest data for each included roadmap project.

The presentation is then preserved as a “snapshot,” meaning its contents will not change unless a user explicitly updates or edits the presentation itself – even as the underlying project data evolves. This ensures the presentation can serve as a useful comparison point in the future.

💡 Tip: When you “duplicate” a presentation, Korl creates a copy but pulls in all the latest data. You can then add or remove projects from the “Included projects” menu in the duplicated presentation. Korl automatically summarizes key changes between the presentations.

Updates are well-formatted, text-based summaries that can be copy-pasted into places like Slack or an email. They provide a less formal alternative to a full presentation.

You can auto-generate an internal update any time from the lightning icon on the upper right corner of the Roadmap table. Korl uses the latest project data to produce a short summary of what’s recently released, coming soon, or currently being defined.

Korl also sends a weekly email with this internal status update, highlighting changes since the prior week. It goes to all Korl users on Monday mornings.

cancel
Search results
Sync attributes from Jira or Linear

Attributes already tracked in Jira or Linear can be synced to Korl so there is no need for double data entry.

This is often the case for structured attributes such as dates, stage, and priority.

To sync an attribute from Jira or Linear, go to Settings, Project attributes, and set the attribute’s data source to Jira or Linear. Then choose the relevant field that should be synced to Korl.

Once you add a Dev link to a particular Korl project, Korl syncs the relevant data from the epic, project, or issue identified by that Dev link.

When you make an edit in Jira or Linear, the changes are synced to Korl automatically.

When you edit a synced attribute from Korl, you have the choice to push that change back to Jira or Linear (so long as you have enabled read-write permissions). If you choose not to push the change back, sync will be broken, and the attribute’s source will change to Korl (but you can always re-sync at any time).

Attributes synced to Jira or Linear have the

Jira logo

Jira or

Linear app logo

Linear icons next to them.

🐶 How Korl uses Korl We sync the following attributes from Jira:

  • Owner
  • Design links
  • Priority
  • Project images
  • Eng start
  • Eng complete
  • Release.

We bring in our Eng Complete date from Jira as the default for Release, but we often break sync and add buffer directly from Korl (e.g. move Release to +2 weeks after Eng Complete)

Infer attributes from the project doc

KorlAI can also analyze any project document written in Google Docs, Notion, or Confluence to extract data and auto-generate content for Korl attributes.

This is particularly useful for long text attributes such as Internal summary or Critical user journey.

It also works well for attributes such as Themes, Goals, and Target personas.

💡 Tip: If you define expected values for Themes, Goals, and Target personas under Settings, KorlAI will analyze the project document and pick the most relevant value from the ones you provided. If you have not provided expected values, KorlAI will come up with values on its own.

Once you add a Project doc link to a particular Korl project, KorlAI analyzes the document to populate values for the attributes configured to sync from the project doc.

As the underlying document evolves, ask Korl to “re-analyze” at any time to update the project’s attributes based on the latest content in the document.

If you make an edit in Korl, sync will be broken, and the attribute’s source will change to Korl. But you can always “re-analyze” to re-sync the attribute at any time.

Attributes synced to KorlAI’s analysis of the project document have the document icon next to them.

🐶 How Korl uses Korl We sync the following attributes from our project documents:

  • Project name
  • Internal summary
  • Themes
  • Goals
  • Target personas
  • Critical user journey
Sync data from somewhere else

If your data is not in Jira, Linear, Notion, Google Docs, or Confluence, the best alternatives are:

  • If you have multiple projects to import, get them into a .csv file and then upload that .csv to Korl. Your .csv should have a row per project on your roadmap and column per project attribute. Korl will treat the first row as column headers, then create a new roadmap project for each subsequent row in the table. You’ll have the opportunity to map columns in your .csv to the relevant attribute in Korl, and you can also ask KorlAI to auto-generate additional content as long as you provide an Internal summary.
  • If you have project documents in another document editor, upload a copy of each document to Drive. Next, “Open with Google Docs” or “Save as Google Doc” for each one. Then follow the steps to add from Google Docs.
Sync data from Confluence

If you have project documents (e.g. PRDs, one-pagers, product briefs, etc.) that are written in Confluence Pages, you will add from project docs.

Korl will create a new roadmap project for each Confluence Page you add.

  1. Go into the Roadmap tab in Korl and “Add from project docs” (under the + button).
  2. Select “Confluence” (you will be prompted to authenticate if you haven’t yet).
  3. Provide the URLs to the Confluence pages for which you want to create Korl roadmap projects. Note that you can add up to 10 URLs at a time.
  4. Ensure that you see a green check icon next to each URL, indicating Korl can access the page. If you don’t see the green check, ensure that the account used to authenticate Confluence has access to that Confluence page.
  5. Korl will create a new roadmap project for each provided page. KorlAI will extract or auto-generate as much metadata about the project as possible.

Note: The underlying documents do not need to have any particular structure

Sync Data from Google Docs

If you have project documents (e.g. PRDs, one-pagers, product briefs, etc.) that are written in Google Docs, you will add from project docs.

Korl will create a new roadmap project for each Google Doc you add.

  1. Go into the Roadmap tab in Korl and “Add from project docs” (under the + button).
  2. Select “Google Docs” (you will be prompted to authenticate if it has been more than 30 minutes since you last authenticated your Google account in Korl).
  3. Select the Google Docs for which you want to create Korl roadmap projects. Note that you can select up to 10 documents at a time.
  4. Korl will create a new roadmap project for each selected document. KorlAI will extract or auto-generate as much metadata about the project as possible

Note: The underlying documents do not need to have any particular structure

Sync data from Notion

There are two ways to get data from Notion into Korl, depending on what Notion data you want to import.

To add a roadmap project that has a dedicated Notion page describing what the project is, you will add from project docs.

  1. Go into the Roadmap tab in Korl and “Add from project docs” (under the + button).
  2. Select “Notion” (you will be prompted to authenticate Notion if you haven’t yet).
  3. Select the Notion pages for which you want to create Korl roadmap projects. Note that you can select up to 10 pages at a time.
  4. Korl will create a new roadmap project for each selected page. KorlAI will extract or auto-generate as much metadata about the project as possible

Note: The underlying documents do not need to have any particular structure

To bring in a number of projects from a Notion database (table), you will need to export that table to .csv and then import that .csv into Korl.

  1. Go to the Notion database (table) that has the projects you want to bring into Korl.
  2. Apply any desired filters.
  3. Click the 3-dot in the far upper right corner of the page (not the one located next to the table), then select “Export”
  1. Confirm the export format (“Markdown & CSV”), then start the export.
  2. Go into the Roadmap tab in Korl and “Add from .csv file” (under the + button).
  3. Follow the steps to upload the file and map the columns in your .csv to the relevant Korl attributes

For projects that have an associated Notion page describing the feature in more detail, add the Notion as the “Project doc link” so that KorlAI can analyze it and sync any additional data. You can either:

  • Include the URL in your .csv and be sure to map that column to the “Project doc link” attribute in Korl.
  • Link the relevant Notion page after finishing the upload (by going to the project and selecting to “Add project doc link,” which enables you to select any page from Notion)
Sync data from Linear

To get data from Linear into Korl, start by authenticating Linear (under Settings, then Integrations). If you have access to more than one Linear workspace, ensure that you select the desired workspace from the upper left corner when authorizing the integration with Korl.

Next, go to Settings, then Project Attributes to configure the Korl attributes that you want to sync from Linear. For each attribute that should sync from Linear, set the data source to Linear and then specify the Linear field to sync.

💡 Tip: You’ll be able to configure different fields for Linear projects versus issues (since Linear supports different fields for each). If you set Linear as the data source and don’t have a mapped field for either projects or issues, Korl will attempt to sync the field you’ve defined for the other type. If that field doesn’t exist (e.g. issues can have attachments in Linear, but projects cannot), Korl will simply note that the synced field doesn’t exist for the Dev link provided.

Now you are ready to import issues or projects from Linear.

If you want to import Linear issues, the best way to do this is to export a saved view from Linear to a .csv, then upload that .csv to Korl.

  1. In Linear, create a “Saved view” of the issues you want to import into Korl.
  2. From the view’s 3-dot menu, select “Export issues as CSV…”
  1. Open the CSV in Excel or Google Sheets.
  2. Add a column called “Dev link” that uses the concatenate function to add the unique URL for your Linear workspace (e.g. “linear.app/workspace/issue/”) with the “ID” for the issue to import.
  1. Download the Google Sheet as a .csv file.
  2. Go into the Roadmap tab in Korl and “Add from .csv file”  (under the + button).
  3. Follow the steps to upload the file and map columns in your .csv to the relevant Korl attributes. Ensure that you map the “Dev link” attribute in Korl to the “Dev link” column you just created in the Google Sheet that has the actual URL to the relevant Linear issue.

Once you import the .csv, Korl will not only create a roadmap item for each row in the .csv file, but it will also automatically sync data from Linear for the Korl attributes you configured to source from Linear.If you want to import Linear projects, you will have to add each project’s URL directly as the Dev link for a project in Korl. This is because when exporting projects, Linear does not include the project ID, which means you cannot easily derive the URL from the exported data.You can either export Linear projects, upload them as a .csv, and then add the Linear URL as the Dev link for each Korl project. Or you can simply add projects manually in Korl and then add the Linear project link, and all attributes configured to source from Linear will get synced.

💡 Tip: The fastest way to add Dev links for multiple items in Korl is from the Roadmap table, which supports inline editing (as well as hiding and showing columns for a more focused view).

Sync data from Jira

To get data from Jira into Korl, start by authenticating Jira (under Settings, then Integrations).

Next, go to Settings, then Project Attributes to configure the Korl attributes that you want to sync from Jira. For each attribute that should sync from Jira, set the data source to Jira and then specify the Jira field to sync.

Now you are ready to import issues from Jira (which could be epics, stories, tasks, etc.). The best way to do this is to export the issues from Jira to a .csv, then upload that .csv to Korl.

  1. In Jira, start a search and filter to the issues you want to import into Korl
  2. Open that filtered list in Google Sheets.
  1. Once in Google Sheets, remove any extra images or rows so the top row is column headers, and each row after that is a Jira issue that you want to import into Korl as a roadmap project.
  2. Add a column called “Dev link” that uses the concatenate function to add the unique URL for your Jira site (e.g. “https://company.atlassian.net/browse/”) with the “Key” for the issue to import.
  3. Download the Google Sheet as a .csv file.
  4. Go into the Roadmap tab in Korl and “Add from .csv file” (under the + button)
  5. Follow the steps to upload the file and map columns in your .csv to the relevant Korl attributes. Ensure that you map the “Dev link” attribute in Korl to the “Dev link” column you just created in the Google Sheet that has the actual URL to the relevant Jira issue.

Once you import the .csv, Korl will not only create a roadmap item for each row in the .csv file, but it will also automatically sync data from Jira for the Korl attributes you configured to source from Jira.🔜 Coming soon, you will be able to select the Jira issues you want to import right from Korl, without the need for .csv upload.

Import & sync data into Korl

There are three main ways to import roadmap projects into Korl: add from project docs, add from a .csv file, or add manually.

When adding from a project doc, you select one or more documents, each of which should describe a single project on your roadmap. KorlAI will analyze the documents, then create and populate a new roadmap project for each one. The underlying document does not need to have any particular structure.

When adding from a .csv file, you upload a single .csv file where each row is a project on your roadmap, and each column is one of the project attributes. Korl will treat the first row as column headers, then create a new roadmap project for each subsequent row in the table. You’ll have the opportunity to map columns in your .csv to the relevant attribute in Korl, and you can also ask KorlAI to auto-generate additional content as long as you provide an Internal summary.

When adding manually, you provide the data directly into Korl. Depending on your project attribute settings, additional data may be synced (as you add a Dev or Project doc link) or auto-generated by KorlAI (as you add an Internal summary).

Depending on where your roadmap data lives today, you may want to use a combination of these mechanisms to import your data into Korl.

Ask KorlAI to generate content

Finally, you can ask KorlAI to auto-draft External positioning content based on the internally-facing information already added to Korl.

This option is only available for External name, External description, and Customer impact.

When one of these attributes is synced to KorlAI, it gets auto-generated and auto-updated any time the project’s Internal summary changes.

If you make a manual edit to the KorlAI-generated content, sync will be broken, and the attribute’s source will change to Korl (but you can always re-sync at any time).

Attributes synced to KorlAI have the

KorlAI icon

KorlAI icon next to them.

🐶 How Korl uses Korl We ask KorlAI to auto-draft the following attributes:

  • External name
  • External description
  • Customer impact
Project attributes

Each roadmap project in Korl has attributes that track key pieces of information about the project. These attributes focus on information that is important when communicating to internal or external stakeholders. They are organized into several categories:

Project Overview
Project name The internally-facing name for the project
Internal summary A 1-3 sentence internally-facing description of what the project delivers
Owner The person most directly responsible for the project’s delivery (usually a PM)
Team The development team building the item
Dev link The URL for the epic, project, or issue where development status is tracked
Treated as a “Synced source” if other attributes are configured to sync from Jira or Linear
Project doc link The URL for a document (e.g. PRD, product brief, 1-pager) describing the project
Treated as a “Synced source” if other attributes are configured to sync from the project doc
Design links The URL(s) for files that detail project designs
Priority How important the project is to deliver
Choose from: P0, P1, P2, Backlog
Themes The strategic focus area(s) to which the project aligns
Values are configurable
Goals The business objective(s) to which the project aligns
Values are configurable
Target personas The user persona(s) or role(s) the project is intended to benefit most
Values are configurable
Project images Visual assets that help explain the item
.jpg, .png, .jpeg, .webp, .gif
Critical user journey The in-product steps a user takes to address the core need this project targets
Release Status
Stage
Choose from: Not Started, Defining, Developing, Validating, Released
Eng start The date when the project’s development is expected to begin or began
Eng complete The date when the project’s development is expected to complete or completed
Release The quarter, month, or exact date when the project is expected to or did release to end users
Status The confidence level that the project will release to end users on the Release date
Choose from: Released, On track, At risk, Off track, In backlog
Status update Comments about how the project is progressing
External Positioning
External visibility Whether the project can be shared with external stakeholders, such as customers
Choose from: Okay to share, Requires NDA, Do not share
External name The externally-facing name for the project
External description A 1-3 sentence externally-facing description of what the project delivers
Customer impact A 1-3 sentence externally-facing summary of how the project benefits end users
Shareable timeframe Whether the Release date can be shared externally, and if so, at what granularity
Choose from: None, Release Quarter, Release Month
Shareable media Visual assets added to Project images that are tagged as “Externally shareable”

Each attribute can be managed directly in Korl or synced from other sources such as Jira, Linear, or a project document in Drive, Notion, or Confluence.

You can configure attribute data sources by going to Settings, then Project Attributes.

Manage attributes in Korl

For attributes that aren’t already maintained in your dev tracking system or inferable from your product documents, it’s best to set the data source to Korl and add or edit them directly in Korl.

This is often the case for attributes that you historically managed in either a spreadsheet or presentation slides themselves.

Attributes managed in Korl have a

Korl logo indicates the source of data is Korl

Korl icon next to them.

🐶 How Korl uses Korl We manage the following attributes directly in Korl:

  • Dev link
  • Project doc link
  • Status
  • Status update
  • External visibility
  • Shareable timeframe
  • Shareable media
Configure attribute data sources

An attribute’s data source determines where and how the data for that attribute is generated.

You can manage each attribute’s data source by going to Settings, then Project Attributes, then clicking the “Edit attribute” button for the attribute you want to configure.

Korl is intentional about allowing customers to configure the data source on a per-attribute level. This is because we recognize every team has different established patterns for what is getting tracked where, and we know it’s critical to avoid duplicate data entry across systems.

💡 Tip When you configure a Korl attribute to sync from a source outside of Korl, you still always have the option to edit the value directly from Korl. In the case of Jira or Linear, you also have the option to push those edits back to Jira or Linear to keep everything synced.

Roadmap projects

In Korl, a project is a feature or improvement on your roadmap for which it is worth communicating to stakeholders about what it is and how it’s tracking.

It frequently maps to an epic in Jira or a project in Linear, but it can map to any issue type or notable bug fix depending on how your team tracks work.

Some projects will be for internal stakeholders only, while others will be okay to share with external audiences such as customers. The key is that a project is big enough that it warrants tracking and communicating about outside of the development team who owns the project.

Projects are listed in the Roadmap table, and each project has a detail page where users can view and manage key information about the project (i.e. the project attributes).

When you generate an artifact in Korl, such as a presentation or product update, Korl pulls in the most current data about the projects included in that artifact.

Korl Artifacts

An artifact is a piece of communication collateral created in Korl. Currently, Korl can auto-generate two different types of artifacts: presentations, and updates.

Presentations can be created at any time from the “Create presentation” button. The format and content will depend on the presentation template you choose. There are also many ways to configure and edit the presentation once you create it.

When you create a presentation, Korl grabs the latest data for each included roadmap project.

The presentation is then preserved as a “snapshot,” meaning its contents will not change unless a user explicitly updates or edits the presentation itself – even as the underlying project data evolves. This ensures the presentation can serve as a useful comparison point in the future.

💡 Tip: When you “duplicate” a presentation, Korl creates a copy but pulls in all the latest data. You can then add or remove projects from the “Included projects” menu in the duplicated presentation. Korl automatically summarizes key changes between the presentations.

Updates are well-formatted, text-based summaries that can be copy-pasted into places like Slack or an email. They provide a less formal alternative to a full presentation.

You can auto-generate an internal update any time from the lightning icon on the upper right corner of the Roadmap table. Korl uses the latest project data to produce a short summary of what’s recently released, coming soon, or currently being defined.

Korl also sends a weekly email with this internal status update, highlighting changes since the prior week. It goes to all Korl users on Monday mornings.

No results found.
Try different keyword
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.