It's common for backlogs to build up with issues that become irrelevant or will never get addressed. We're introducing issue auto-closing to automate the trouble of manually clearing stale issues. Once enabled, issues will be auto-closed and marked canceled if they haven't been updated after a certain time period.
You can turn on Auto-close for your workspace by selecting Enable: Issue auto-closing from the command menu (Cmdk). You'll configure the time period and applied status under Settings > Team > Workflow.
#in the editor
We've made some big improvements to the filter command menu. When you open the filter menu (f) and select any of the content types you want to filter with, we now compute how many issues in your current view would match each value. This gives you a good overview of the number of issues that would be selected were you to apply that filter.
The filter command menu will now also hide any unmatched filter values under a sub-section.
Previously we would list all possible values regardless of whether they match any issues in the current view. For example, if you were looking at a project and wanted to filter against assignees, we would previously list all the users in your organization. Now the filter menu is much more useful and will display only the users that have assigned issues in the project.
The Search view and My Issues potentially display issues from multiple teams. Filters have great improvements across these pages, too. We now group issue statuses and labels across teams, so that if you search for a label called "Bug", we display issues from all teams that match the same label name. And you are now able to filter against all labels and issue statuses from all teams, instead of having to choose from labels and issue statuses of the last active team.
We're now proud owners of the linear.new domain which is an easy to remember way to create a new Linear issue. Just type it in any browser and we'll forward you to the new issue creation page as long as you're logged into your account.
By default, Linear generates two upcoming cycles if you have the feature enabled. This lets your team plan ahead by adding issues to future ones. If you're using relatively short cycles, you might want to increase the number of upcoming cycles available. Head over to your team settings to change how many upcoming cycles Linear creates. You can add up to 10 upcoming cycles.
Linear now has functionality to completely delete your workspace and all associated data. It's accessible to all workspace admins under the workspace settings page.
Project pages received a requested feature – completion graphs. These graphs show you the progress you're making towards completing the project.
You'll be able to see how your project scope has changed over time. The project completion graphs will also predict how long it will take to complete the project. The prediction is based on the velocity at which issues in the project are completed, where more recent weeks weigh more heavily than older weeks.
You can access them from the project details pane, which you can open from the toolbar or by pressing Command/Ctrli on the project page.
To make it easier to follow what has changed in Linear, we now show links to the latest changelog posts in the app sidebar. When there are new updates, the indicator will change color to Linear purple and you can quickly jump to the changelog post. You can also subscribe to changelog updates via email and Twitter.
We're excited to add a much requested feature which is both fun and useful: emoji reactions to comments. Now you don't need to send a comment to acknowledge a proposed solution, just select 👍 and the original comment author will be notified in their Inbox. The whole modern emoji set is available and anyone can join the party 🥳
✨ ProTip: To add emojis to issue descriptions, or to your own comments, just type
To make communicating shipped features or canceled bugs easier, we also added two new notifications: completed and canceled issues. Whenever an issue is moved to either status, subscribers are notified.
We're announcing Linear for general availability today. You can sign up yourself as can your team and there's no more need for an invite. We're also announcing pricing plans. Smaller teams can still use Linear for free without limits on users as long as your active issue count stays below 250.
Ps. We're looking for experienced TypeScript developers and product designers to join our team. Read more here.
We're excited to add support for GitLab. It lets you integrate Linear issues and merge requests with the same functionality as our existing GitHub integration:
You can connect Linear with GitLab.com or your self-hosted GitLab installation starting today.
Linear now has its own documentation site full of information on how to use the product better. We wanted to highlight the most common features and also expose less known ones in case you haven't found them yet. To step up your Linear knowledge, we list shortcuts and ProTips marked with ✨!
Linear's board views now have the ability to collapse rarely used columns. This might come in handy if your team mostly works out of a few columns and would like to hide less frequently used ones.
To hide a column, select "Hide" from the board column's menu. View or unhide hidden columns by scrolling to last column of the board (to the right). You can also drag issues into hidden columns.
We're adding support for multiple workspaces under one user account. This makes it easier to keep your personal tasks in a separate workspace from your company's workspace or to collaborate with multiple companies without logging in and out.
Teams that work with multiple clients can now create separate workspaces for each client so that their work and access to GitHub are separated.
To create a new workspace, select the option from the workspace navigator which is accessible by clicking the workspace name in your sidebar.
Linear has supported setting the issue status using keyboard shortcuts for a long time using Command/CtrlOption1-5. This worked fine for teams using the default statuses. However, if a team added more statuses to their workflow, the keyboard commands would only target the first status of each status type (e.g. Backlog).
Linear now has keyboard shortcuts for all statuses of the selected team and you can change the status of selected issues using Command/CtrlOption1-9. Additionally, the multi-select tray now detects if the team has multiple states for the "Move to Backlog" and "Move to Active" actions and will display a menu to let the user choose the state to move the issues to.
We've spent a considerable amount of time improving our backend infrastructure to support our ever-growing userbase. While this is an ongoing process, we've now completed a major refactor of the service infrastructure that considerably improves the reliability of our backend and lets us scale the application to a lot more users. Not everything went according to plan and we did have a few outages during these migrations for which we sincerely apologize.
Until now you could sign up for Linear using a GSuite account and invited users were able to log in using their Google account.
Today we are announcing email login with magic links, which enable you to sign up and log in using any email address. We also removed the limitation where you could only invite external collaborators if they had a @gmail.com account.
Logging in using email magic links is simple. Type in your email and we'll send you a link. When you click the link, you'll be taken to Linear and immediately logged in.
We've made a couple of improvements to our GitHub integration. We now correctly handle draft pull requests and there is a new workflow setting to configure drafts.
We've also made improvements to issue links that get posted to pull requests on GitHub. When you update the pull request and link new issues, the links are posted correctly.
We added support for GitHub draft pull requests in Linear. If you open a draft pull request, which is linked with an issue, it will show up as a draft in Linear. When the pull request is marked as ready for review, it will trigger automation in Linear and move the issue to the in progress status.
Links to the Linear issue in associated GitHub pull requests have also been improved. The pull request link can now be expanded to show the full description of the issues without leaving GitHub.
Users now have the option to subscribe to all team and project notifications. This should make it easier to triage new issues and manage the overall scope.
Issue data can now be exported in CSV format by workspace admins. You can schedule the export in Import/export settings and you'll be emailed the download link once the exported data is available.
Previously, the My Issues view would display currently active issues that have been assigned to you. By popular request, we improved the view to allow you to quickly display issues that are either Assigned to you, Created by you, or ones you've Subscribed to. Issues on your Backlog will now also be included in the listing.
User avatars will now show whether the user is currently online, away or offline. The profile page has been updated to show this information, too, and will additionally show the time they've last been online. You can also see this information in a popover when hovering on a user's avatar in the comments section of any issue.
We made subtle improvements to contrast and font size in light mode and the emails sent by Linear. The added contrast and slightly enlargened text size improves legibility especially for muted and faded text.
You can now resize the left and right sidebars by clicking and dragging on their edges. Useful for making the most of your preferred window size.
To make it easier to discover the ways to import issues into Linear from other systems, we added an Importers page in the the Workspace Settings. Linear currently supports importing issues from GitHub, Jira, Asana, and Pivotal Tracker.
title/identifierconfiguration option for Git branch names
A lot of Linear users have GitHub integration enabled and use our Copy git branch name action (Command/CtrlShift.) to copy the git branch name when starting to work on an issue. We've now added the ability to change the format of the branch name that will be copied. To change it, go to your Github integration settings.
We made several highly requested improvements to issue estimation. Each of the following new settings can be found under your team settings.
You can now choose how unestimated issues are counted towards estimate totals. Counting every unestimated issue as 1 point towards the estimate totals makes the most sense for most teams, and this remains the default.
Previously, your issues were either not estimated at all, or you had a positive estimate value. If you want to distinguish between unestimated issues, but still allow issues to not count towards the total estimate for a cycle or project, you can now enable zero point estimates.
All of our estimate scales have 5 values by design. Larger estimates usually mean that there is a lot of uncertainty about the complexity of an issue and breaking the issue up into smaller pieces is usually the best approach. However, if you want, you can now extend the scale and add two more values to the estimates.
We have added external links to projects. In addition to the project description, they can be used to link to external resources such as designs in Figma, project plans in Notion and so on.
To access project links, visit the project page and open the sidebar (Command/Ctrli).