Skip to main content
If your team was already tracking issues in Linear before connecting NOCK, you do not have to start from scratch. The import feature lets you pull a snapshot of existing issues from your selected Linear team into NOCK, creating corresponding tickets so your history is visible alongside new feedback. Importing is an on-demand action — you trigger it manually whenever you need it, rather than an automatic background sync of all historical data.

​
What gets imported

When you run an import, NOCK copies the following fields from each Linear issue into a new NOCK ticket:
Attachments, comments, and Linear-specific fields such as cycle assignments or estimates are not imported. Only the core issue content listed above is brought across.

​
How to trigger an import

1

Confirm your team selection

The import pulls issues from the Linear team currently selected in Settings → Integrations → Linear. Before starting, confirm this is the correct team. If you need to change it, see Choose a Team & Project.
2

Open the import screen

Go to Settings → Integrations → Linear, then scroll down to the Import section and click Import issues from Linear.
3

Review the preview

NOCK will show you a count of the issues it found in the selected team. Review this number to confirm you are importing from the right place.
4

Confirm the import

Click Confirm import to begin. NOCK will create a ticket for each issue it fetches. Depending on the number of issues, this may take a few seconds.
5

Review your imported tickets

Once the import completes, your new tickets will appear in the NOCK ticket list. Each ticket will include a link back to its original Linear issue.

​
Import behaviour and limitations

Import is on-demand, not continuous. Running the import creates a snapshot of your Linear issues at that moment in time. Issues created in Linear after the import is complete will not appear in NOCK automatically — only new tickets submitted through NOCK will generate new Linear issues going forward.
Running the import a second time may create duplicate tickets if the same issues are fetched again. Check your existing tickets before importing a second time. If you need to refresh data for a specific issue, edit the ticket directly in NOCK.
If the import returns fewer issues than you expected, or returns nothing at all, see the Troubleshooting page. Common causes include API key permission gaps and selecting a team with no existing issues.