Sub-issues should inherit Project settings from parent issue

[fritz-trawa]

Select Topic Area

Question

Feature Area

Issues

Body

If I have an-issue assigned to project X and team Y, and I create a sub-issue from it, it should automatically be set to project X and team Y. It's very time-consuming to have to reset them all by hand

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[fritz-trawa]

Anyone?

[brendanshanahan]

Would like to see this as well

[mmannion]

Agreed. This is the predominant use case in our workflow, and would save my team clicks.

Additionally, it would be more consistent with existing behavior when working in Task Board. For example, if I click Add item at the bottom of a status column to create a new issue, that issue is automatically added to the board's project and, in turn, displays on the board immediately.

When creating a subissue, however, the default project is No projects. Consequently, newly-created subissues aren't visible in the current task board, unless the creator remembers to choose the relevant project (or assigns the project subsequently).

[vegahar]

My team would also like this feature as well. Adding sub-issues and timeline view has been a productivity booster for us. Totally agree with @mmannion and @fritz-trawa on how time consuming it is to add the current project and/or for us the sprint

[mrinmayray]

Hi @fritz-trawa,

Thanks for raising this — your use case makes a lot of sense.

You're right: currently, when you create a sub-issue (using "Convert to issue" or through task lists), it doesn't automatically inherit the parent issue's project or team assignments, which can be tedious when managing larger workflows.

🛠 Current Behavior:
Sub-issues are treated as standalone issues once created.

They do not inherit project, team, assignee, or milestone settings from the parent issue by default.

✅ Workarounds:
Until GitHub provides native inheritance, here are a few possible workarounds:

Use automation rules (via GitHub Projects) to automatically assign issues based on labels or creators.

Create sub-issues using a script or GitHub Action that copies metadata from the parent.

Use issue templates with prefilled metadata, if that fits your workflow.

💡 Feature Suggestion:
This would be a great candidate for a built-in setting, such as:

“Automatically inherit Project, Assignee, and Team from parent issue when creating sub-issues.”

If you haven’t already, consider opening a feature request in the GitHub feedback repo so the product team can track demand for it.

Let me know if you'd like help setting up a workaround using GitHub Actions or automation rules!

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[natalia-bearden]

Having a native GH inheritance of the parent ticket's properties, configurable via the settings, would help our team as well. Thanks for bringing this up 🙏

[github-actions[bot]]

🕒 Discussion Activity Reminder 🕒

This Discussion has been labeled as dormant by an automated system for having no activity in the last 60 days. Please consider one the following actions:

1️⃣ Close as Out of Date: If the topic is no longer relevant, close the Discussion as out of date at the bottom of the page.

2️⃣ Provide More Information: Share additional details or context — or let the community know if you've found a solution on your own.

3️⃣ Mark a Reply as Answer: If your question has been answered by a reply, mark the most helpful reply as the solution.

Note: This dormant notification will only apply to Discussions with the Question label. To learn more, see our recent announcement.

Thank you for helping bring this Discussion to a resolution! 💬

[natalia-bearden]

Is there a better place to file a feature request like this, so it has a chance to get added to the GH devs' list of Issues to (hopefully!) address?