Hierarchy view in GitHub Projects [Public Preview] #184225
Replies: 32 comments 46 replies
-
|
Thanks for this feature!! I am very happy about it. I do have two points of feedback:
Thanks in advance. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the helpful feedback! We’re actively exploring both the ability to filter out closed sub-issues and preserving the expand/collapse state. These are improvements we’re hoping to deliver in the coming weeks :). |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
با تشکر و احترام از شما دوست گرامی حتما اعمال می نمایم |
Beta Was this translation helpful? Give feedback.
-
|
This is a MUST feature!! |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
How to get "Epic" Issue Type, as shown in the video?? |
Beta Was this translation helpful? Give feedback.
-
|
nvm. Found it: https://github.com/organizations/[organization]/settings/issue-types |
Beta Was this translation helpful? Give feedback.
-
|
This is fantastic, really useful for us! But why is this being worked on, when a very related, needed, highly demanded, and obviously missing feature has been left untouched since Dec 2021? Sort by "last updated", "created" |
Beta Was this translation helpful? Give feedback.
-
|
Indeed, absolutely crazy to see that while the "created" sorting isn't available yet... What a basic yet essential feature. |
Beta Was this translation helpful? Give feedback.
-
|
This is coming next 😄 |
Beta Was this translation helpful? Give feedback.
-
|
Wait, really? |
Beta Was this translation helpful? Give feedback.
-
|
Got it |
Beta Was this translation helpful? Give feedback.
-
|
This is great, really useful! Would love to see this enabled in Roadmap view as well! |
Beta Was this translation helpful? Give feedback.
-
|
Does this only work when you create and filter by something like 
|
Beta Was this translation helpful? Give feedback.
-
|
For those using the |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu I'm setting up a new project board using no:parent-issue and it lets me get just what I want to see. One small annoyance is I'm trying to order a backlog and the sub-issues within the parent issue based on priority/dependency manually. I can drag and re-order the top level, but to re-order the issues within a parent I have to open a second view focused on just issues with that parent. It would be nice if the drag handles let me order sub-issues as well in the one view. edit: I just saw that the Coming Soon section mentions exactly what I was requesting 🤦 |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu the no:parent-issue filter, or the -no:parent-issue does not resolve the original post issue.
The option of using no:parent-issue does not really work if you have multiple levels of nesting. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks all for the feedback on this! We are currently working on de-duplicating the items by default. Stay tuned 👀 |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
It means GitHub Projects now supports viewing issue hierarchies (parent–child relationships) directly in table view, making it easier to manage complex work breakdowns and see progress without switching views. |
Beta Was this translation helpful? Give feedback.
-
|
This is fantastic and was sorely needed. Please add this functionality to roadmap pages as well, it is desperately needed to make roadmaps viable because without hierarchical sorting it is impossible to make an effective roadmap. |
Beta Was this translation helpful? Give feedback.
-
|
Only realised today that roadmap hierarchy wasn't included when table view hierarchy was released. Is there a workaround for the roadmap to force a heirarchy-like layout? |
Beta Was this translation helpful? Give feedback.
-
|
Great to see this |
Beta Was this translation helpful? Give feedback.
-
|
Just to echo the above comments, this is so greatly appreciated as a new feature, the only gripe I've seen is the duplicate issue problem. Whilst the filter approach works somewhat, it's not reliable as we often have valid tasks that are isolated in nature, and therefore do not have a parent issue. Using the filter approach means we also lose these items when wanting the hierarchy view. |
Beta Was this translation helpful? Give feedback.
-
|
Duly noted. We are currently working to solve the duplicate issue problem. Stay tuned! |
Beta Was this translation helpful? Give feedback.
-
|
What is the in-process |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu An additional issue I have found is that if you are relying on a filter to remove the duplicate items in hierarchy view, then you can't drag and drop child items into an order. You can only drag top level items that have an issue number. IMO the end goal here is to have a tree of items which you can drag and drop into an order. (Assuming there is no sort applied.) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback! Solving the duplicate items and supporting drag and drop are both coming very soon :) |
Beta Was this translation helpful? Give feedback.
-
|
Drap Drop wont trigger it is not done outmoded |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Thanks for creating hierarchies, a wish is the possibility to save that all should expanded or collapsed. Now it is set to collapsed and it is needed to expand one by one. |
Beta Was this translation helpful? Give feedback.
-
|
It would be so cool to have the same thing for board layout, where parent issue would encapsulate their related child issues, rather than having child issues flattened next to parent. It's kind of hard for us to organize work when having a lot of issues with parent-child relationships. |
Beta Was this translation helpful? Give feedback.
-
|
Available |
Beta Was this translation helpful? Give feedback.
-
|
Briefly describe what you're missing |
Beta Was this translation helpful? Give feedback.
-
|
I was unsure what this button did before I came to this issue. It would be great if there was an informative or something else that described what the switch does. I don't have subissues so all it does is add more whitespace. |
Beta Was this translation helpful? Give feedback.
-
|
What else can you add up to what was said? |
Beta Was this translation helpful? Give feedback.
-
|
The update after clicking on an issue, then creating a list of sub-issues then closing the modal (to go back to the hierarchical view) seems somewhat long. I haven't timed it, but trying to drive issue creation from this screen (i.e. creating a large batch of hierarchical issues in one sitting) gets a bit annoying. Nevertheless, this is a great feature to keep improving! |
Beta Was this translation helpful? Give feedback.
-
|
I did find a workaround: If you keep two tabs open and switch between them, then the update seems to be triggered faster. |
Beta Was this translation helpful? Give feedback.
-
|
Another thing that would be super useful: The ability to export (either an image or PDF) of the entire table view, not just the viewport. And I don't mean a CSV, but the actual graphical view, as is. This hierarchical view is very useful for discussing and planning work order (irrespective of time), so it would be useful to be able to show it to other ppl without having to resort to screenshots. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
We've now shipped the following improvements to hierarchy view 🚀 :
We would love to hear any feedback you have as you try out these new features! |
Beta Was this translation helpful? Give feedback.
-
|
We actually liked having the duplicate issues 😅and were puzzled as to why a number of our issues were no longer showing up. Tasks are assigned at the child level, but there's also an overall owner at the parent level - now, to get at the children, we have to go looking for the parent issue under whoever has it assigned. Unassigned children used to show up at the bottom of the board in one big section (all children of all parents) so people could easily find all issues that were ready to be picked up. I've dropped hierarchy view from our board for now so the issues show back up again - is there something I can add to the query to ensure they all show up? |
Beta Was this translation helpful? Give feedback.
-
|
The changes have broken everything... I have epics that belong in themes. I have an epic view and now when hierarchy mode is on, many of the epics disappear. I thought this was a weird bug, but now I'm wondering whether it's the de-duping that's causing this (because multiple epics can appear in a theme). So completely unusable for me now for this view. :-( |
Beta Was this translation helpful? Give feedback.
-
|
OK... I can see what's going on now. I was using I have now removed the parent label and all is well again :-) |
Beta Was this translation helpful? Give feedback.
-
|
Same for us, could you please make that a setting? |
Beta Was this translation helpful? Give feedback.
-
|
this change has completely broken our milestone views so that now only tickets without parents will show in the board. De-duplication is likely the culprit but we actually wanted that since we have Feature tickets, Epic tickets, etc where the EPICs will be in the milestones but features won't. because of the change, now these epic tickets won't show because they have a parent ticket. We don't want to remove the parent relationships but do want to ensure the sub tickets (EPICs) continue to show. Please make this a setting or option as its made the view unusable right now with the recent change. |
Beta Was this translation helpful? Give feedback.
-
|
I came here to learn and help and so much occurred. I would like to have some guidance this time in addition to the learning I have done on GitHub and other platforms |
Beta Was this translation helpful? Give feedback.
-
|
What is your best interests here? |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
Feature request please for an option to show "duplicate" items as main-level line items - children which have parents that are also showing up in the view. We were using hierarchy view until those items were removed from the view by default - we're now no longer using hierarchy view. |
Beta Was this translation helpful? Give feedback.
-
|
I also hope that "duplicate" items are allowed as an option. It is actually quite useful and im no longer using Hierarchy view since this was removed. |
Beta Was this translation helpful? Give feedback.
-
|
This might just be a bug, but I wish exports would include sub-issues. Today, with hierarchy on, the view will include sub-issues even whether or not they match the filter, which is actually great (if this ever changes, please at least make it an option!). But when I export the view, sub-issues aren't included, not even when they do match the view filter. Ideally, the tsv export would include all sub-issues in the view (i.e., given the current filter behavior, even the ones not matching the filter). It should be a faithful(ish) representation of what I see in the view so that I can manage those same items in other ways as well. |
Beta Was this translation helpful? Give feedback.
-
|
ما الذي تريدني أن أعدله؟
…On Tue, Mar 17, 2026, 9:42 PM Asdf مراد ***@***.***> wrote:
ضبط
—
Reply to this email directly, view it on GitHub
<#184225 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BRITTME23DRTHWFRX46HZJD4RG2CNAVCNFSM6AAAAACRTDH3V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMJYGM3TQMQ>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
The 'hierarchy view' is present in the 'Board' layout, but should be present in the 'Roadmap' layout as well to ease planning view and decision making. |
Beta Was this translation helpful? Give feedback.
-
|
please add back the ability to see "duplicate" items. This was a breaking change from prior versions and there is no option to choose whether you want the old or new behavior (show or hide). |
Beta Was this translation helpful? Give feedback.
-
|
Seconding the ask for "duplicate" items. The main, unexpanded listing should be able to include any items that match the filter query. |
Beta Was this translation helpful? Give feedback.
-
|
Will do.
If you are working with me
…On Fri, Mar 27, 2026, 9:47 PM Marc Manza ***@***.***> wrote:
please add back the ability to see "duplicate" items. This was a breaking
change from prior versions and there is no option to choose whether you
want the old or new behavior (show or hide).
—
Reply to this email directly, view it on GitHub
<#184225?email_source=notifications&email_token=BRITTMFL77CG7VAWXSM5G5T4S3SHPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRTGQ4TSNZZUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16349979>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BRITTMERG4ET7ZXDSB23B534S3SHPAVCNFSM6AAAAACRTDH3V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMMZUHE4TOOI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Here’s a clean, original reply you can post: This is a really useful addition, especially for teams managing complex work structures. One thing I noticed while testing hierarchy view is that it greatly improves visibility, but it also introduces some workflow challenges depending on how Projects are structured:
💡 SuggestionIt would be really helpful if GitHub added:
Overall though, this is a strong step forward for planning and breaking down work more clearly. Just needs a bit more control for real-world project workflows. If you want, I can also make you a shorter 2–3 line reply version for quick commenting 👍 |
Beta Was this translation helpful? Give feedback.
-
|
Something changed recently. I don't know if it's the deduplication or if the hierarchy view interacts poorly with the "slice by" feature we're also using. We want to show a hierarchy and slice by issue type. The issue types forms a hierarchy. This is how the "slice by" column look like with hierarchy view turned off: 
And with hierarchy view turned on: 
They used to show the same data. The hierarchy goes as follows: Project -> Epic -> Feature -> Story. The issues are connected as sub-issues. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, its annoying, but logic. Your Epic -> Feature -> Story are children of Project, so if you enable hierarchy, it only shows the types that are the topmost hierarchical items. In your example, you still have 5 Story and 3 No Type issues that aren't children of any other type and this is why they show up in the sliced list. |
Beta Was this translation helpful? Give feedback.
-
|
Is it due to deduplication? Because it initially worked the way I want it to work. |
Beta Was this translation helpful? Give feedback.
-
|
We can't filter out items that have a certain state. We usually use This works in a normal view, but when we enable a nested hierarchical view, the closed issues reappear. They are still shown. Only those that are the topmost items are filtered out, I assume. But since most issues are nested and thus inside an Epic, which we rarely close, we would also like Done and Closed items to be filtered out when they are in a nested view. Can this be fixed? 
|
Beta Was this translation helpful? Give feedback.
-
|
How did you add the icons for each issue type? Is there a way to get them automatically, or it is just an icon in in title of each issue? |
Beta Was this translation helpful? Give feedback.
-
Its just an icon I add to each issue. It is however possible to automate this with Actions. I read it somewhere, but as I'm the PO of the product and already have to type lots of issues titels and their info, I don't mind doing the extra work of adding the icon. You just type Here is a screenshot of the icons I find useful for their specific project issue / filter. Feel free to use them in your own projects. Screenshot is for Windows 11 users. Icons are different on Windows 10 
-- |
Beta Was this translation helpful? Give feedback.
-
|
It's slightly inconvenient in that one needs to select the type (for proper filtering) and add the icon, but it's not a huge issue. I guess issue templates could help, at least for creating new items. |
Beta Was this translation helpful? Give feedback.
-
|
it also looks like archived child issues are shown in the hierarchy view. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, it works!
…On Tue, Apr 21, 2026, 3:58 PM Jacob Carlborg ***@***.***> wrote:
Is it due to deduplication? Because it initially worked the way I want it
to work.
—
Reply to this email directly, view it on GitHub
<#184225?email_source=notifications&email_token=BRITTMCAWAZVR2U4ALJ5PAD4W6EBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGU3DOMBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16656701>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BRITTMGJJRF2LPHZ6FMVZQT4W6EBDAVCNFSM6AAAAACRTDH3V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRVGY3TAMI>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
|
Do you want my personal assistance?
On Thu, Apr 23, 2026, 8:53 AM Scott Ellison CSA ***@***.***>
wrote:
… Yes, it works!
On Tue, Apr 21, 2026, 3:58 PM Jacob Carlborg ***@***.***>
wrote:
> Is it due to deduplication? Because it initially worked the way I want it
> to work.
>
> —
> Reply to this email directly, view it on GitHub
> <#184225?email_source=notifications&email_token=BRITTMCAWAZVR2U4ALJ5PAD4W6EBDA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNRWGU3DOMBRUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-16656701>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/BRITTMGJJRF2LPHZ6FMVZQT4W6EBDAVCNFSM6AAAAACRTDH3V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMNRVGY3TAMI>
> .
> You are receiving this because you commented.Message ID:
> ***@***.***
> com>
>
|
Beta Was this translation helpful? Give feedback.
-
|
🤔 so you want me to say the whole thing here?
…On Fri, May 8, 2026, 7:16 PM Eduardo Kalinowski ***@***.***> wrote:
How did you add the icons for each issue type? Is there a way to get them
automatically, or it is just an icon in in title of each issue?
—
Reply to this email directly, view it on GitHub
<#184225 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BRITTMGSQG7KC46L6DZW3AD4ZYP6JAVCNFSM6AAAAACRTDH3V6VHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTMOBVGU3TSOI>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hierarchy view for GitHub Projects is now available in public preview. You can now view your full issue hierarchy directly in project table views, giving you clear visibility into complex work breakdowns without losing context or switching views.
🔗 What is hierarchy view?
Hierarchy view lets you see the full nesting of sub-issues directly in GitHub Projects.
hierarchy_view.mp4
With hierarchy view enabled, you can:
Getting started
To enable hierarchy view, open the View menu and turn on Show hierarchy.
Coming soon
We’re continuing to invest in hierarchy view. Next up:
Beta Was this translation helpful? Give feedback.
All reactions