Guide
Using Linear Integration, you can import Linear data into Fibery.
This is done through a time-based synchronization process. This means that all the information synced periodically from Linear to Fibery.
Please, note, that this integration is one-way sync. So at the moment there is no way to push data from Fibery into Linear.
Setup
Create a Space.
Navigate to Space settings and click on the Integrate button.
Select the Linear box.
Authentication of your Linear account can be done through OAuth.
Allow the permission request.
Customize the Integration settings.
Databases
It is possible to decide which databases need to be synced to Fibery. However, these databases are tightly connected, so only deselect any of them if you understand the consequences.
Include archived entities
To sync archived projects, issues, and more, you can enable this setting in Linear.
Initiatives
It's possible to sync only selected initiatives, leaving it empty means syncing all Linear initiatives into Fibery.
Set up Fields and Databases.
The provided Slack fields by the integration can be mapped and configured to the Fibery integration database.
Click on the Sync now button on the bottom of the screen to start the sync process.
Use cases
1. Link Product Areas or User Stories to Linear Issues
Connect high-level product planning in Fibery with implementation tasks in Linear.
How it helps:
Maintain traceability between product requirements and development work.
Ensure alignment between product vision and technical implementation.
Easily reference detailed specifications from Linear issues within Fibery.
Key details:
Synchronization is one-way from Linear to Fibery.
Product managers can link product areas or user stories in Fibery directly to Linear tasks, giving the team a clear line of sight from planning to execution.
2. Track Development Progress
Monitor the status of Linear issues directly in Fibery.
How it helps:
Provides real-time visibility into development progress.
Simplifies reporting for stakeholders.
Helps identify bottlenecks or delays earlier.
Key details:
All Linear issue statuses are reflected in Fibery.
Teams can create dashboards, charts, and reports to visualize progress without switching tools.
You can also run Fibery Automations and AI on top of Linear data
3. How to link feedback to Linear data?
Here we are going to use Highlights
Setting Up Feedback Sources and Targets
Feedback can come from multiple databases in Fibery, such as:
Only select databases that actually contain feedback. For example, payments or employee databases usually aren’t relevant as sources.
Targets are the items in Fibery you want to link feedback to, such as:
Native Fibery databases
Linear issues
To configure targets for Linear:
Go to Settings → Highlights.
Define which database will be the source and which will be the target.
For Linear, select Issues as the target (or any other database, you want link feedback to)
Create the Highlight
Open a feedback item (e.g., a conversation).
If the database is set as a source, you’ll see a Create Highlight button.
Highlight the relevant text in the feedback and click Create Highlight.
Assign it to the target Linear issue.
You can find the relevant issue manually or with AI
Highlights allow you to attach specific feedback to an issue for tracking and prioritization.
Counting and prioritizing Feedback
You can create formulas to analyze feedback metrics:
Number of Requests:
Formula example: Highlights.Count
This counts how many times a feedback item has been highlighted.
Unique Requests:
Use Count unique if multiple feedback entries contain the same request.
Importance/Weighting:
You can also include additional fields to account for customer priority or severity - Highlights and Targets formulas
Using Multi-Column Layouts
This helps team members switch between development overview and feedback overview efficiently.
Setting Automations
Automations help monitor high-priority issues:
Trigger: Issue is updated.
Condition: Number of Requests = 5
Action: Notify relevant team members.
This ensures that frequently requested items are flagged and addressed promptly.
Summary
Sources: Feedback databases (conversations, chats, topics)
Targets: Linear issues
Highlights: Link specific feedback to a target
Formulas & Layouts: Analyze number of requests and customer importance + make it look good for teammates
Automations: Notify teams when requests exceed thresholds
Unsupported fields
Team database: Active cycle — We add the active cycle field to the cycle database in the linear template. The active cycle is calculated using the cycle timerange and the current date.
Initiative database: Description — this field is inaccessible through Linear API.
Comments — we have decided not to support this field to streamline our solution. Please let us know if it is important to you.
FAQ
Why are some Linear Projects not syncing with Fibery?
If you're noticing that some Projects from Linear aren't showing up in Fibery, but others are syncing just fine, here are a few things to check:
Check for Initiative Filters
If you’ve applied a filter to Linear Initiatives in your integration settings or synced databases, only Projects linked to visible Initiatives will be synced. Projects associated with filtered-out Initiatives will not appear in Fibery.
Reconnecting the Integration
Reconnecting the Linear integration (e.g., deleting and re-adding it) won’t resolve this issue if filters are still applied. Make sure to review and adjust filters on Initiatives, Projects, or related databases.
Still not syncing?
If filtering doesn’t seem to be the cause and the issue persists, reach out to our support team with: