Projects - Break down large issues into smaller ones

[demetrios]

Select Topic Area

Question

Feature Area

Projects

Body

The Docs on GitHub Projects clearly state in their Best Practices that you should break down large issues into smaller issues. But they don't state how?!?

I guess I'm expecting to easily build a hierarchy in my project where one project may have many "issues" (aka tasks). Each of those tasks then becomes a parent of list of sub "issues" (or tasks). I can't figure out how to do this?!?

I can reference an issue by the issue number but that is effectively just a markdown document (with comments) not a project hierarchy.

IMHO each Issue needs ability to link to a parent and/or a child. Issues can become their own "project" and vice versa. And shouldn't issues be contained within their parent not dropped en mass into a single directory?

I'm missing something. GitHubProjects is cumbersome the way I'm trying to use it. Can anyone help?!?

Guidelines

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

[seyLu]

Hi @demetrios

You can watch this vid from the Github official Youtube channel: Break issues into Actionable Tasks

Or the Github official docs: About tasklist

Summary:

• Large Issue
• Add tasks
• Convert task to issue

[demetrios]

Thank you for your help. The problem I'm having (maybe it's a bug) is when I create a task list in an issue. The items appear and I can reorder them with the handle on the left when I hover but there is never a circle with a dot in the middle (on the right) that I could click to turn that task item into an issue of its own.

1. To be clear the first issues were created as Draft Issues in a new Project.
2. I was able to convert those draft issues into regular Issues by clicking on the down arrow and "Convert to Issue".
3. Then I get a new Issue in which I create a task list.
4. None of those tasks can be turned into their own issue for further refinement/detail.

I'm missing something or GitHub Projects is unfortunately buggy.

[seyLu]

I don't think it is a bug but more so the github team hasn't implemented it yet.

You can view the docs for workarounds: Using projects and tasklists.

[gtjamesa]

Some of the docs you may be reading refer to the private beta of tasklists. The beta looks like it supports issue creation directly from the lists themselves

Tasklists are in private beta and subject to change. We have currently paused onboarding to the beta. Tasklists build upon the previous iteration of task lists.

[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! 💬

[peter-8640]

Lol, I read this thread after watching the nice youtube video, trying and failing to use task to generate issues, reading this ticket which is similar in content and frustration level: #69168
Anyway, 👍 for this feature.