# How to create a sub-issue in Linear on Mac: button, command menu and shortcut

> Learn how to create a sub-issue in Linear on Mac using the + Add sub-issues button, the command menu or ⌘⇧O. Steps, shortcuts and fixes.

URL: https://www.lazur.app/how-to/create-a-sub-issue-in-linear
Updated: 2026-11-08

To create a sub-issue in Linear on Mac, open the parent issue and click + Add sub-issues below the description, then type the new title and save. You can also press ⌘⇧O from the parent, or press ⌘K and search for Create sub-issue in the command menu.

## Quick answer

- Open the parent issue, then click + Add sub-issues below the description.
- Press ⌘⇧O from the parent to open the sub-issue editor with the keyboard.
- Press ⌘⇧Enter to save and keep the same labels or assignee for the next one.
- Team, priority and project carry over. Labels do not.

Applies to: Linear desktop app for macOS, Apple silicon and Intel Macs. Time: 3 min. Difficulty: Easy.

## What you need

- Linear desktop app for macOS on an Apple silicon or Intel Mac
- Access to the team that owns the parent issue
- An existing parent issue, or its title and details ready to create one
- The latest desktop app build, since sub-issue fixes shipped in August and September 2026

## How to Create a sub-issue in Linear on Mac in Linear on a Mac

1. **Open the parent issue.** In the Linear desktop app, open the issue that will hold the new work. Click its title from your list or board. The parent is the issue that the sub-issues belong to, so open the right one before you go on. Tip: Start from the issue, not from a blank create form. The create-issue modal also works, as covered above.
2. **Open the sub-issue editor with the button.** (Parent issue > + Add sub-issues) Scroll to the area below the issue description. Click + Add sub-issues. The sub-issue editor opens with an empty title field. Tip: The button sits below the description, as Linear's docs describe.
3. **Or open the editor with the shortcut.** Shortcut: ⌘⇧O. While the parent issue is open, press ⌘⇧O. The same sub-issue editor opens without a mouse click. Tip: If ⌘⇧O opens something other than the editor, update the desktop app first.
4. **Or use the command menu.** (Command menu > Create sub-issue) Shortcut: ⌘K. Press ⌘K to open the command menu. Type Create sub-issue and choose it from the results. Linear uses the same editor for this route. Tip: To make several at once, choose Create multiple issues from the same menu.
5. **Type the title and details.** Type a short title, such as Reproduce crash on Safari. Add a description if the work needs context. Use the fields in the editor to change priority, assignee or labels when the sub-issue differs from its parent. Tip: Start titles with a verb. Lists read faster when each line says what to do.
6. **Save and keep going.** Shortcut: ⌘⇧Enter. Press ⌘⇧Enter to save. The editor reopens for the next sub-issue, and it keeps the same labels or assignee. Repeat this for each item in the batch. Tip: Use ⌘⇧Enter only for items that share the same labels or owner.
7. **Close the editor.** Shortcut: Esc. When the batch is done, press Esc. The sub-issue editor closes.
8. **Check the parent and the new sub-issues.** Look at the parent issue and confirm each new sub-issue is listed. Open one sub-issue to check the team, priority, project and cycle it inherited. Tip: Fix anything wrong on the sub-issue itself, one field at a time.

Linear's help docs give one set of sub-issue steps for both the Mac desktop app and the web app. The button, the command menu and the keyboard shortcut work the same way in either one. This page walks through those steps, then covers what a sub-issue inherits, the mistakes that cost people time, and what to check after you save.

![Person at a laptop planning tasks before they create a sub-issue in Linear on Mac](https://images.lazur.app/content-images/howto/create-a-sub-issue-in-linear/how-to-create-a-sub-issue-in-1-c8eb4b.jpg)

## Four ways to make a sub-issue in Linear on Mac

You have four ways to start a sub-issue. Most people use the button the first time, then switch to the shortcut once it feels natural. The other two options help when the work already exists as text in a comment or a checklist.

- Button: open the parent issue and click + Add sub-issues below the description.
- Shortcut: press ⌘⇧O while you view the parent to open the sub-issue editor.
- Command menu: press ⌘K, search for Create sub-issue, and choose it.
- Text: turn a checklist item or a comment into a sub-issue without retyping it.

## What a sub-issue inherits from its parent

A sub-issue copies some fields from its parent. That saves typing. It can also surprise you if you never look at the result. Team, priority and project carry over automatically. The cycle carries over when the new sub-issue is created in an active status. Labels never carry over. Assignee carries over only under certain conditions, so set it by hand when it matters.

| Field | Carries over? | What to check |
| --- | --- | --- |
| Team | Yes | Confirm it matches the parent's team |
| Priority | Yes | Change it if this piece is less urgent |
| Project | Yes | Confirm the project before you save |
| Cycle | Yes, if the status is active | Check it if your team plans in cycles |
| Labels | No | Add them by hand, or keep them with ⌘⇧Enter |
| Assignee | Only under certain conditions | Set it yourself if someone must own it |

_Inheritance for new sub-issues, based on Linear's sub-issue docs._

Labels are the field people miss most. Say the parent has a bug label. Your first sub-issue starts with no label, so add it in the editor before you save. Then press ⌘⇧Enter. The editor reopens with the label already set, which saves you from adding it again for each item in the batch.

## Create several sub-issues at once

When you already have a list of work, skip the one-at-a-time loop. Paste the list of titles into the sub-issue editor, and each line becomes its own sub-issue. You can also choose Create multiple issues from the command menu. This works well for a set of similar tasks, such as regression checks for one release.

## Turn a checklist or comment into sub-issues

Use this when the work already sits in the parent's description. Highlight a bulleted, numbered or checklist, then press ⌘⇧O. You can also choose Create sub-issue(s) from selection in the formatting toolbar. For a comment, hover over it, open the three-dot menu, and choose new sub-issue from comment. Select the comment text and press ⌘⇧O if you prefer the keyboard.

## Use a template for repeat work

Repeat work benefits from templates. In the sub-issue editor, click the templates icon and pick one. From the parent issue, open the command menu and choose Create new sub-issue from template. Templates keep titles and checklists the same across the team, so a release checklist looks the same each time.

## Add sub-issues from the create-issue modal

The shortcut also works from the create-issue modal. Linear's changelog from October 13, 2022 describes this behavior. You can add sub-issues before you save the parent, which saves a second trip. Full-screen issue creation uses the V key, and the same shortcut works there without saving the parent first.

## Why the shortcut opened the wrong screen

For a time, ⇧⌘O opened sub-issue creation when you expected the pull request preview. Linear's changelog for September 3, 2026 lists a fix for that clash. If the PR preview still does not open for you, check that the desktop app is current, then try again.

Shortcuts also depend on where you run Linear. The docs say the desktop app has less risk of clashing with browser-based presets or custom shortcuts. If ⌘⇧O does nothing in a browser tab, a browser setting or extension may be taking those keys. The desktop app is the simpler path if that happens.

## Sub-issues or a checklist?

Use a sub-issue when the work needs its own owner, status or priority. Use a checklist when the items are small and one person handles them all. You do not have to decide perfectly at the start. Highlight a checklist later and press ⌘⇧O to promote an item into a sub-issue.

## How deep can sub-issues nest?

The official sub-issue page does not state a nesting depth limit. It also gives no version notes for this feature. Do not build a process that depends on a specific depth. Test the case in your own workspace before you set a rule for your team. The pricing page mentions levels for sub-teams, which is a different feature.

## Duplicate a parent with its sub-issues

To duplicate a parent with its sub-issues, open the parent's three-dot menu and choose Duplicate. Turn on Include sub-issues before you confirm. Leave it off and you get the parent alone. This helps with repeat projects, such as a monthly release checklist. Check the copied titles and owners, since they may need updating for the new cycle.

## Sub-issues from MCP tools and Linear Agent

Sub-issues can also come from Linear's MCP tools or Linear Agent. Linear's changelog from October 22, 2026 says those sub-issues keep their parent's project when eligible. If your team uses these tools, still check the project field. Eligibility depends on the case, so a quick look saves a fix later.

## Mistakes people make with sub-issues

- Creating under the wrong parent. Look at which issue is open before you type a title.
- Expecting labels to come along. They never do, so add them each time or keep them with ⌘⇧Enter.
- Pressing Esc too early. You close the editor and have to reopen it to continue the batch.
- Skipping the project check. An inherited project can put the work in the wrong place.
- Turning every bullet into a sub-issue. Keep sub-issues for work that needs its own owner or status.

![Team reviewing a project board to decide which work needs a sub-issue in Linear on Mac](https://images.lazur.app/content-images/howto/create-a-sub-issue-in-linear/how-to-create-a-sub-issue-in-2-43c4c2.jpg)

## A worked example: a login bug with three sub-issues

Say your parent is called Fix login timeout on Safari. It has a bug label, high priority and the Auth project. You want three sub-issues: Reproduce on Safari, Patch token refresh, and Add regression test. Open the parent, press ⌘⇧O, and type the first title. Add the bug label, then press ⌘⇧Enter. The label stays for the next title, Patch token refresh. Type the third title, press ⌘⇧Enter again, then press Esc.

Team, priority and project come across to all three with no extra work. The label reaches all three because you kept it with ⌘⇧Enter. When you finish, read the parent once more. Confirm that the three sub-issues sit under it, each with the right team and project.

## Desktop app or web app for sub-issues

The steps match on the web app. Linear's docs say nearly all desktop functionality is available on the web in most browsers, and they recommend the desktop clients for the best experience. Pick the Mac app if you use Linear all day, since shortcuts clash less there. Pick the browser when you cannot install software on a work machine.

## Next steps after the sub-issues exist

After the sub-issues exist, give each one an owner and a status. If your team uses cycles, check each one's cycle field too. Linear's changelog from August 13, 2026 lists a fix for drag-and-drop of sub-issues in views sorted by status, title or due date. To set up the statuses your sub-issues move through, read [how to set up a workflow in Linear on Mac](https://www.lazur.app/how-to/set-up-a-workflow-in-linear). If you do not have a parent yet, start with [how to create an issue in Linear on Mac](https://www.lazur.app/how-to/create-an-issue-in-linear).

## Shortcuts

- Open the sub-issue editor from a parent issue: ⌘⇧O
- Open the command menu: ⌘K
- Save and keep labels or assignee for the next sub-issue: ⌘⇧Enter
- Close the sub-issue editor: Esc
- Create a sub-issue from selected checklist text: ⌘⇧O
- Full-screen issue creation, no parent save needed: V

## If it does not work

- **⌘⇧O opens sub-issue creation when I wanted the PR preview** Linear's September 3, 2026 changelog lists a fix for this clash. Update the desktop app, then try again. If the PR preview still does not open, report it to Linear with the steps you used.
- **I cannot find the + Add sub-issues button** Open the parent issue itself. The button sits below the description. If it is still missing, press ⌘K and search for Create sub-issue, which Linear's docs list as a command menu option.
- **My label is missing on the sub-issue** Labels are never inherited. Add the label in the editor, or save with ⌘⇧Enter so the label carries to the next sub-issue in the same batch.
- **The assignee was not set on the sub-issue** Assignee inherits only under certain conditions. Set it in the editor for each sub-issue that needs an owner.
- **Drag-and-drop of sub-issues fails in a sorted view** Linear's August 13, 2026 changelog lists a fix for drag-and-drop in views sorted by status, title or due date. Update the app. If the problem stays, report it with the name of the view.
- **⌘⇧O does nothing in a browser tab** A browser setting or extension can take the same keys. Linear's docs say the desktop app has less risk of this clash. Use the Mac app, or change the browser shortcut that conflicts.

## With Lazur

Lazur is a voice assistant for the Mac that lives in the notch. Hold ⌥ ⌘ and ask; it sees your screen, answers out loud, points at buttons and walks you through apps. Hold fn to dictate. Free for 3 days, then $18/month: https://www.lazur.app/download

- “Where's the + Add sub-issues button?”: Lazur circles the + Add sub-issues button below the description and labels it. You click it, and the sub-issue editor opens. Lazur does not click for you. (Points at it)

## FAQ

### Is the sub-issue shortcut the same on Mac and Windows?

Linear's docs list Cmd/Ctrl+Shift+O. On a Mac that is ⌘⇧O, Command, Shift and O. On Windows you use Ctrl, Shift and O. The rest of the steps are the same.

### Do the steps differ in the Linear web app?

No. Linear's sub-issue docs give one set of steps for the Mac desktop app and the web app. The shortcut behavior can differ because browsers use some of the same keys.

### Do labels carry over to a sub-issue?

No. Labels are never inherited from the parent. Add them in the editor, or save with ⌘⇧Enter so the next sub-issue in the batch keeps them.

### Can I create sub-issues from a checklist?

Yes. Highlight a bulleted, numbered or checklist in the parent's description and press ⌘⇧O. You can also choose Create sub-issue(s) from selection in the formatting toolbar.

### How many levels of sub-issues can I create?

Linear's official sub-issue docs do not state a nesting depth limit. Test the case in your workspace before you set a rule for your team.

### Does duplicating a parent copy its sub-issues?

Only if you turn on Include sub-issues. Open the parent's three-dot menu, choose Duplicate, then turn on that option before you confirm.

### Do I need a paid plan to create sub-issues?

The sub-issue docs do not mention plan limits. The pricing page lists the Free plan at $0 with a 250 issues limit, so check your plan before a large import.

### What if a sub-issue has the wrong team?

Team is inherited when the sub-issue is created. Open the sub-issue and check or change the team there.

## Sources

1. [Parent and sub-issues - Linear Docs](https://linear.app/docs/parent-and-sub-issues), Linear, checked 2026-11-09
2. [Faster sub-issue creation - Linear Changelog](https://linear.app/changelog/2022-10-13-faster-sub-issue-creation), Linear, checked 2026-11-09
3. [Priority inbox - Linear Changelog](https://linear.app/changelog/2026-09-03-priority-inbox), Linear, checked 2026-11-09
4. [Team initiatives - Linear Changelog](https://linear.app/changelog/2026-08-13-team-initiatives), Linear, checked 2026-11-09
5. [Linear Changelog](https://linear.app/changelog), Linear, checked 2026-11-09
6. [Get the app - Linear Docs](https://linear.app/docs/get-the-app), Linear, checked 2026-11-09
7. [Download Linear](https://linear.app/download), Linear, checked 2026-11-09
8. [Linear Pricing](https://linear.app/pricing), Linear, checked 2026-11-09