A new era for the timeline
Milestones on the timeline
A new timeline design layers in details to give a more accurate overview of project progress.
Milestones will now appear on project bars as long as they have a target or completion date. Represented by diamonds, milestones indicate status and can be hovered over or clicked on to show details. Milestones near each other collapse into a set, like on a map app.
You can change a milestone's target date from the timeline view by dragging it to a new date. Select individual milestones to move them, or if they appear together, hold shift to drag all milestones to a new date. Dragging a project to change its start and target date will move the milestones along with it, but you can hold Cmd/Ctrl to keep milestones in place. Right-click on the project to add a new milestone.
A new chronology bar makes it easier to navigate the roadmap and understand where you are in time. When you move your mouse, a cursor line will appear to indicate the exact date. You can now also choose to display week numbers instead of dates.
You can now display team cycles on the timeline, too, which appear below the chronology bar.
And we've added a few more settings to make working with the timeline easier:
- A display option to show the project list, which can be hidden with Shift [ to get more space
- Shortcuts to leap to Today or change the zoom to Year, Quarter, or Month
- Offscreen project indicators that show the dates of the project and can be dragged to reorder
- A display option to hide prediction bars to reduce clutter and take cleaner screenshots for status reports
Create issues via email
Create issues via email
Bring your email-based workflows into Linear by turning emails into issues.
- Quickly create bug reports and feature requests from customer emails
- Forward reports to general emails like security@ to specific Linear teams
- Automatically turn email notifications from service providers into issues
Set up a unique intake email for your team so that any emails sent or forwarded to that address will go to Triage or your team's default workflow status. You can also create unique intake emails for individual templates to automate the issue creation process further and apply specific fields. Learn more and generate intake emails from team or template settings.
AI-generated issue titles in Slack
When you create Linear issues using the Slack integration or with Asks, we now pre-populate the title with AI-generated summaries to save you one step in the issue creation process.
Linear Mobile (Private Beta)
Linear Mobile is now in private beta for iOS and Android. Pre-order to join the waitlist: https://linear.app/mobile.
Google Calendar integration
Sync your status in Linear with out-of-office events from Google Calendar. If someone tries to assign an issue to you or mentions you in a comment when you are OOO, they'll see that you are unavailable and for how long.
/shrug
Typing :)
will now convert to 🙂 and :joy:
to 😂 automatically. Type /shrug
to get the universal ¯\_(ツ)_/¯
.
Project update comments
Project update comments
You can now comment on project updates to discuss changes and ask follow up questions. Comments sync bi-directionally across Linear and Slack, so everyone can chime in on one thread — even teammates who don't have a Linear account.
You can now also:
- Subscribe to receive updates from specific projects
- Copy project updates as markdown for easy sharing
- Disable progress report metrics on individual updates
Tables
A long-standing feature request, Linear now support tables in issue descriptions, documents, and comments. Add a table using the /table
command.
Branch-specific workflow automations
Set custom workflow automations based on particular target branches with our GitHub and GitLab integrations. For example, you can set up your workflow so that when a PR is merged to…
- staging -> the issue status will change to In QA
- main -> the issue status will change to Deployed
You can also override a default rule in a particular branch with no action if desired, so that issues linked to a change in that branch will not change status. Branch rules can also be specified using regex (e.g., ^fea/.*
can set automations for all of your feature branches). Update your configuration in your team's Workflow settings.
- @-mentioned issues include the title as well as the ID
- See version history and revert to previous content in documents
- Codeblocks now have a Copy action button
- Linear's Figma plugin is available from the Figma for VS Code extension
Project timeframes
Project timeframes
Use broad date ranges as project start and target dates instead of specific ones. This lets you plan project timelines at your current level of certainty, such as next month, quarter, or year, when they more accurately reflect product timelines.
- Plan ahead by selecting more flexible target dates
- Filter your view to just the timeframe that matters (e.g. Q2 projects)
- See roadmaps in different time resolutions (e.g. group by month)
- Communicate launch timelines to colleagues
Customize cycle dates
You can now customize cycle start and end dates to coincide with planning meetings and match the rhythm of your team.
- Choose the exact start date when activating cycles
- Edit the start or end date of individual cycles to work around holidays
- Navigate between individual cycle pages with
Opt
/Alt
+J
/K
- Issues completed during cooldowns are now attributed to the previous cycle
Integration improvements
- [Asks] When an Ask is created from a top-level Slack message (using 🎫 or the overflow menu action), we now automatically import all threaded messages under it to the synced Linear comment
- [Slack] When an issue is created from a top-level message in Slack, we now automatically import all threaded messages under it to the synced Linear comment
- [Front] You can now create and link Linear issues from internal discussion threads
New filters & ordering
- Filter projects by Last project update = Never
- Sort projects by Status. Active projects are prioritized over unstarted, completed, or canceled ones
New keyboard shortcuts & command menu actions
- Ctrl Shift I to focus issue description input
- Type
v + space
in the command menu to quickly search for custom views - The command line now removes accents from an input string (e.g. Mela would return both Mélanie and Melanie)
New settings
- Disable spellcheck in text fields in My Account > Preferences
- Opt out of immediate email notifications when you are assigned an urgent issue or an issue breaches its SLA
Jira Sync
Jira Sync
We’ve upgraded our existing integration with Jira to support two-way syncing and added support for more fields including synced comment threads. If you work with colleagues who use Jira, or need to keep a Jira project updated while working on issues in Linear, Jira Sync makes this seamless and efficient.
Enable Jira Sync to link Jira projects to Linear teams. Any issues created in the linked Jira project will appear in Linear and vice versa. Updates to an issue title, description, assignee, status, label(s), and priority will sync immediately across both applications. Use the synced comment thread in Linear to see and reply to comments posted in Jira.
To start syncing issues from your Jira project, set up the integration in settings. Existing Jira Link users can follow these instructions to enable bi-directional syncing. The integration syncs newly created issues only; to import existing Jira issues into a Linear team, use our migration assistant.
GitHub Issues Sync
GitHub Issues Sync
We’ve heard your feedback that you would like to manage issues for open source projects in Linear. With GitHub Issues Sync, your OSS issues can now be synced bidirectionally between GitHub and Linear. This lets you triage and discuss your community requests in the same place as all of your other work.
- Issues in linked GitHub repositories will show up in Linear.
- Title, description, status, labels, assignee, and comments on the GitHub issue will sync across both applications.
- Reply to GitHub issue comments from Linear via the synced thread or have separate, private discussions in the issue with your teammates.
To start ingesting issues from your OSS repository, set up the integration in GitHub Integration settings.
Integrations gallery
You can now browse and search for all integrations, including those made by third parties, in the new integrations gallery in workspace settings. Individual integrations settings pages have been updated to include screenshots, a detailed description, and configuration instructions.
- Fixed an issue preventing renaming favorite folders on touch devices
- Converting between different list types now also works for nested lists
- Fixed a bug where contextual menus would not scroll correctly when using up and down arrow keys
- We now show your next Triage responsibility shift when using PagerDuty
- Fixed a bug in project views where the "Show empty groups" options would not work as intended
- Blocking and blocked issue relations now have a new icon that better indicates whether they are blocked or blocking
- You will now receive a Slack notification for the synced Slack thread that is created in your messages with the Linear Asks app when you create a private ask through Linear Asks app home
- You can now select up to 10 templates to use when creating an issue using the Slack integration. This has been increased from the previous limit of 5.
- Fixed incorrect workflows assigned to a team that prevented issue creation from custom views
- Search shortcuts in the command menu now have an icon to better indicate that you're searching against a partial set of entities
- Fixed search not showing archived documents
- If cycle automation settings are enabled, issues that are started or completed during a cycle cooldown period will now be assigned to the next cycle if they are not currently in any cycle
- Fixed a problem with connecting project updates to a project channel
- Fixed a problem with filter menu misplaced when the sidebar is collapsed
- Added label, assignee, and project milestone suggestions to the Triage accept dialog
- Linking a GitHub PR now works correctly with multiple connected GitHub organizations
- You can now change the start and end date of individual cycles
- Changed the max width of project documents
- Fixed a broken "View authorized applications" link in OAuth-related email
- [Webhooks] Added support for issue and project update reactions
- [API] Added ability to filter comments by corresponding project update and document content
- [API] Fixed a problem that would cause errors when fetching the added or removed labels of an issue using its history field when the referenced label had been deleted
Inline comments
We’ve made several editor improvements that make it easier to collaborate on work directly in Linear.
Inline comments
You can now create comments on project documents. Select any text and press the comment button that appears or use the shortcut Cmd Option M.
- Notifications go to the document creator and anyone mentioned
- Reply to the comment or resolve it with a single click
- Access the full comment history from the header
Collaborative editing
All documents and issue descriptions in Linear can now be edited by multiple people at the same time. You’ll see input cursors whenever someone else is editing or viewing the text. All changes are instantly saved and synced to everyone else in realtime.
Slash commands
Type / into the editor to see a list of actions you can perform, including creating lists or headings and uploading files. This is available when writing issue descriptions, comments, documents, and project updates.
- We now show more comment replies without collapsing them under the fold
- Resolving the root comment of a thread will now collapse the entire thread
- Improved rounding up for relative dates. Dates within a 2-week range will be shown as days, e.g., "12 days ago."
- Documents and links in a project are now ordered by the date of their creation, with newly created items positioned at the top
- Status changes triggered by git automations will no longer reset an issue's sort order
- When a user is assigned as a project lead or a project member, they are automatically subscribed to receiving project update notifications about the project
- Split view is now supported on smaller tablet-sized screens
- You can now create date-based custom view subscriptions
- Added the ability to de-select select items by clicking on the X button in a quick action selection row
- You can now select a specific template to use as the default template for a channel when auto-creating an Ask in that channel
- You can now refresh the list of projects available through Jira Link
- Teams are now soft deleted and can be restored within 7 days after deletion
- We now surface any errors connecting to your PagerDuty schedule directly on the triage screen
- Changed the 'rename issue' shortcut to Shift R and the 'reply to comment' shortcut to R
- [API] Webhook issue payloads now include the issue
identifier
- Fixed sub-issue assignees when copying the parent issue
- Fixed a problem with hex color changes not saving when editing a project icon
- Fixed a bug where Insights were showing the wrong total number of issues when filtered by parent issue
- Fixed an issue where clicking Escape to go back to a list view would sometimes cause the loss of your position in the list
- Fixed the placement of the macOS Text Replacement dropdown on desktop
- Fixed an issue where Front "conversation" links could not be added to issues
- Suspended users are no longer shown in the "Open user..." action
- Fixed a crash when entering a large number in time fields
- Connecting project updates Slack notifications for a project now notifies the correct Slack channel of the new connection
- Fixed saving additional filters in custom views
- Fixed a bug that would not maintain sub-issue order when duplicating an issue
- Fixed a bug that would not copy the default team state when making a copy of a team
- Fixed a bug where pressing Escape twice would not blur the editor after pasting a link
New Git automation: Ready for merge
New Git automation: Ready for merge
You can now add issue status automations for pull requests that have passed checks and are ready to be merged. This new workflow step is available for both GitHub and GitLab and can be configured in your team’s Workflow settings.
Linear will capture both approvals and passing checks/pipelines according to your repository’s branch protection rules. For example, if you require two approvals and specific checks to pass, Linear will update the issue status only when those conditions are met.
The new status automation can be combined with a View Subscription to subscribe to all new issues that are marked as ready for merge which can be helpful for QA workflows. It also allows you to differentiate between issues in code review versus issues that have been approved.
Improved authentication controls
We shipped significantly improved controls to manage your authentication sessions. The new Security & Access settings page lists all authenticated desktop application and browser sessions with security information such as location, IP address, and last seen status. This makes it easier than ever to audit access to your account. You'll also find a list of all OAuth integrations you have granted access to.
To enable this level of granularity we completely reworked how Linear handles sessions behind the scenes. As a result, we now also allow better control over session length so you won't get logged out by surprise.
- We now provide a more informative status update in the synced Slack thread when an issue is marked as a duplicate of another issue
- We will now default to choosing the next available instance of an hour when generating reminder date options for 12 hour clocks, rather than defaulting to the same time tomorrow
- We now display a team selector when using a project template URL for a template which doesn't specify a team
- Fixed scrolling in issue lists on Google Pixel devices
- Fixed incorrect milestones and roadmaps assigned when applying multiple project templates
- When using
Copy issue title(s)
command, issue identifiers are also included in the issue titles - It is now possible to subscribe to DPA updates in https://linear.app/settings/account/notifications
- Improved keyboard navigation when nav sidebar is collapsed
- Fixed a problem with large images not fitting within the viewport on the project update notification page.
- We now add the 🚨 emoji to the Slack message if an Ask created from that message is marked as urgent
- Fixed using
Cmd/Ctrl
Tab
andCmd/Ctrl
Shift
Tab
to change tabs on desktop even while writing descriptions or comments - Added link and filter button to the subscription notification badge
- Fixed an issue where users couldn't create Asks issues for private teams they were not members of
- Added action for uploading files and images to the slash menu
- Enabled file upload keyboard shortcut (
Cmd/Ctrl
Shift
+U
) even when editor is focused - We will now send a message to the Slack thread when an Asks issue has moved out of triage
- Ensured spacing between issue history entries is consistent
- Fixed scenario where desktop and web notifications would sometimes not be sent.
- Fixed some overflows and text styling on Project Update settings page.
- Markdown formatting will be properly preserved when using a template with placeholders for Asks
- Fixed triage responsibility PagerDuty mapping
- Fixed a bug that would prevent linking a merge request for a project in a subgroup.
- We now indicate if you need to manually add a bot to a Slack channel in the Asks settings page in Linear
Resolve comments
Resolve comments
You can now resolve comments in threads to keep discussions focused and decisions clear.
Resolve the first comment to collapse all replies. Choose specific comments to hide all replies except that one so that you can highlight key details or decisions made. Resolve comments from the ···
menu, by right-clicking on any comment, or by submitting your current reply with ⌘ ⌥ Enter.
Asks improvements
We’ve added two new features to Linear Asks based on your feedback:
- Auto-create Asks by mentioning the
@Linear Asks
bot - Mark Asks as urgent from Slack to signal they need a fast response
Linear Asks
Introducing Linear Asks
Let everyone in your Slack workspace turn their requests into Linear issues — even if they don’t have a Linear account. Found a bug? Have a question? Just create an Ask to send your request to the relevant Linear team. Eliminate cluttered channels and reduce context switching.
- Streamline intake with workflows, templates, and automations
- See realtime updates in Slack and get notified when your Ask is complete
- Receive requests in Linear in a shared team inbox
- Apply SLAs to time-sensitive requests
Asks is available on the Plus plan and can be enabled in settings. Try Asks and other Plus features for 30 days with a free trial.