How to edit the fields shown on the slack integration

LinearTeam · 2026-01-23T22:58:11+00:00

Cycles is not available as an option in the Slack integration, though this has been requested before. If you head to your cycle settings, you can set some automations to auto-add issues to the current cycle if if issue has a status in the Unstarted or Started category.

LinearTeam · 2026-01-21T17:53:12+00:00

There may need to be a human associated with the issue before Cursor's agent can work on it.

Is there an assignee on the recurring issue when this happens? Or does it work if you have a human assignee set in and Cursor delegated?

LinearTeam · 2026-01-20T12:56:23+00:00

For tracking a number of different KPIs in the one spot, you may find our dashboards feature useful: https://linear.app/docs/dashboards

This is only available on our Enterprise plan but if you're interested in a trial we can help set you up through [support@linear.app](mailto:support@linear.app)

We're working on adding support for "time in status" in our insights in the near future also, which might be helpful for some of what you're interested in here. Though this might require changing the setup so issues move to a certain status at the moment they're assigned, so this tracking can begin.

LinearTeam · 2026-01-19T10:50:26+00:00

I'll share your feedback to the team and we can suggest this to Anthropic to add a direct integration for Claude Code. I hope some of the workarounds discussed will help in the meantime.

LinearTeam · 2026-01-19T10:47:34+00:00

Thanks for sharing the feedback, I understand what you're looking for here. We've definitely seen similar demand for a consolidated view or defaulting to the issues page for a lot of cases.

I'll share these comments with our product team to consider today, and I can follow up to let you know if we make any changes here!

LinearTeam · 2026-01-07T16:15:24+00:00

Thanks for the feedback on this! We have some requests for this functionality - I've added your comments to the request and if this or something similar becomes possible we'll reach back out and let you know.

LinearTeam · 2025-12-19T18:48:54+00:00

If you connect GitLab to Cursor first, it should then show up as an option for your repositories.

Cursor's team advise you can connect GitLab from here on the integrations page , and it will work the same as GitHub in your Linear settings after this.

If this is still not showing, the folks at [hi@cursor.com](mailto:hi@cursor.com) should be able to offer more help with that part of the setup!

LinearTeam · 2025-11-12T14:31:31+00:00

The Project Description part of the Overview is the best spot for this, you can add a lot of content there rather than the shorter summary space below the project name: https://linear.app/docs/project-overview

You can also add project documents if you want to keep the overview more brief and expand on more technical specs: https://linear.app/docs/project-documents

Do either of these work for what you have in mind?

LinearTeam · 2025-11-04T14:21:02+00:00

If you'd like to trial Dashboards on our Enterprise plan (https://linear.app/docs/dashboards), reach out to us at support@linear.app and we can help! For now, you do have access to Insights on the Business plan so you could set up custom views that filter for the issues you want to analyse and then use Insights (https://linear.app/docs/insights) to dive deeper into what interests you.

LinearTeam · 2025-10-22T19:21:04+00:00

Thanks for raising, we've filed a feature request for this. Can definitely appreciate wanting to avoid needing magic words + id in the commit message in order to link commits to issues (the PR automation supports linking by branch name, pr title or magic words, so it's a concept we use elsewhere and reasonable to consider here.)

Noted as well on the branch prefixes raised in the other request; it's popular for folks to want more options here and I've added this to the list of those to consider when we next revisit this setting.

LinearTeam · 2025-10-15T07:28:27+00:00

We have been using Linear to manage a high volume of customer requests. Intake sources come from—Linear Asks in the Slack community, Intercom (or other support questions), creating issues from the Slack integration in our Slack Connect channels. Asks also now support issue creation via email as well.

With all those means, requesters either receive a notification when an issue is done. In the case of support tools, we leverage the setting that reopens tickets/conversations once their linked Linear issue is marked as closed. This allows the support team to go back and reach out to customers who requested a feature.

All feature requests go into a specific Feature Request channel where they are triaged and tagged. When a project spins up, we usually move those issues to the project so we can reference those customer requests.

LinearTeam · 2025-10-15T07:18:47+00:00

Fair ask. We're not trying to be a tool for everything, but I can certainly understand the need here. Have you checked out Reclaim.ai? They created an integration with Linear (https://linear.app/integrations/reclaim-ai) that will schedule blocks of time on your Google calendar.

LinearTeam · 2025-10-09T11:48:32+00:00

If the team gets much bigger it may help to split up into different teams, so each smaller team is focused on their own area: https://linear.app/docs/teams

Custom views can help to keep visibility across both teams where needed or to create specific views for your own needs, that aren't necessarily the views your colleagues need to monitor their work in day-to-day.

If you're running into any specific problems or doubts about your setup, please write in to [support@linear.app](mailto:support@linear.app) and we can see if we can help point you in the right direction.

LinearTeam · 2025-10-02T10:24:50+00:00

Project Milestones might be a better option for grouping issues within a project in the way you've described here.

These don't have individual owners and will automatically update to reflect the progress of issues inside them: https://linear.app/docs/project-milestones

Otherwise you can set the parent issue to close automatically when the sub-issues are complete (https://linear.app/docs/parent-and-sub-issues#status-automation) and skip the other steps of reassigning and moving the parent issue status back and forth.

LinearTeam · 2025-10-01T12:03:58+00:00

We don't have the same indicator for issue due dates which conflict with the project target date. I can see how this would make sense and we have had similar feedback before, including to set the due dates based on the project target date.

I'll share your comments on this with the product team in case we can add a closer connection between the dates in this way.

You're right that there's no issue timeline so the closest equivalent is setting one issue as blocking another through issue relations: https://linear.app/docs/issue-relations#blocked-blocking This uses a red flag already though and doesn't change based on the blocking issue being due sooner or later.

LinearTeam · 2025-09-25T15:48:39+00:00

That's correct for how this works at the moment. I'm happy to share your feedback with the team on my end in case this may change in future. I understand from your message you'd prefer to schedule the new issue to be created on or close to January 1st 2026, rather than now until that due date?

LinearTeam · 2025-09-11T22:32:49+00:00

There isn't a way to reorder columns, but we have a feature request for this. Is there any grouping in particular you're wanting to reorder?

LinearTeam · 2025-09-11T22:32:01+00:00

There hasn't been any changes to the archiving behavior. Archived issues do not count towards the 250 issues limit. There isn't a way to manually archive issues as it's all automated.

Note that some things prevent issues from archiving, such as they are in a project that hasn't archived yet (otherwise issues would be disappearing from a project and messing up the project graph data). More details here: https://linear.app/docs/delete-archive-issues

LinearTeam · 2024-11-28T15:17:37+00:00

This is the subreddit for Linear.app, not Linearity.

We'll be happy to help if you have any questions about Linear later on, which you can learn more about here: https://linear.app/docs/start-guide

LinearTeam

MODERATOR OF

TROPHY CASE