Saved views for repository issues - public preview and adjustable row heights

[sunnyi101]

savedview.mp4

If you manage issues in a busy repo, you know how much time goes into re-applying the same filters every day. You filter down to unassigned bugs, work through them, then rebuild the same filter tomorrow. Multiply that across a team and everyone is recreating the same searches over and over.

Saved views for repository issues are now available in public preview. Set up a filtered view once, save it, and everyone on the repo can use it. No extra tooling, no workflow changes. We've also added adjustable row heights in Projects so you can fit more information into your tables.

How it works

Anyone with triage access or above can create shared views like Unassigned bugs, Needs triage, or Customer-reported issues. Set them up once, and the whole team gets the same view.

• Saved views live in the new Issues sidebar, alongside quick links like Assigned to me, Created by me, Mentioned, and Recent activity
• The sidebar gives GitHub Projects a new home, so it's easier to move from Issues into your planning views
• You can save up to 25 views per repository, so teams can cover the searches they run most
• Milestones and Labels are now easier to reach from the same sidebar

The goal is simple: stop rebuilding the same searches, and give your team one shared place to find the issues that matter.

📐 Adjustable row heights in Projects

rowheighths.mp4

You can now set the row height in Projects table layouts. Open the view options, pick the row height option, and choose between Single, Medium, Tall, or Extra Tall.

Taller rows give cells more room for longer titles, labels, and extra fields without truncation. The setting only affects the table layout, and you can save it as part of a view so it sticks for everyone.

💬 Feedback

We're actively iterating on this and your input directly shapes what comes next. We'd love to hear:

1. Are saved views easy to set up and share across your team?
2. Does the new sidebar make it easier to find the issues and projects that matter most?
3. Do the row height options give you the right amount of space in your tables?

Share feedback, report issues, or suggest ideas in this discussion.

[Josh65-2201]

No Issue view is working for me, they always fail to load but not when using the normal issues page with the same search terms

[ARKITEKTENXxREAL]

I use the "Issue" function in github as a hybrid between SoMe and a place to share more than txt. In the beginningen I thought that was the main reason of ISSUES at Github. Lowkey Think of a conding version of IG. 30 sec video upload, many pictures, you can code the txt and so on....

[HtetSec-0ps]

Hello. I am THAN HTET, a member of GDP. I apologize to everyone for the lack of replies. I have had a lot of difficulties learning due to personal issues and not being proficient in using such advanced technologies. So I will do my best to do my best research and provide advice and replies daily. Thank you all.

[bytaesu]

It would be nice to have an option to hide this sidebar.

[adamkdean]

I would love to be able to hide it entirely @sunnyi101 rather than just collapse it. Please stop fixing things that aren't broken

[Vangelis66]

@arp242 wrote:

If you're using Stylus or some such:

div[class^="CollapsibleSidebar-module"] { display:none !important; }

Since a few hours ago, this userstyle no longer works as intended 😞 ; it now only hides the footer of the sidebar (where the Feedback, Preview and Collapse sidebar buttons reside), not the whole sidebar 😢 ; it would appear that now the footer has got "a life" of its own, separate from the main issues sidebar; would you be so kind as to offer a fix?
In the meantime, I've gone back to using uBO to hide it...

Thanks in advance 😄 ...

[arp242]

@arp242 wrote:

If you're using Stylus or some such:

div[class^="CollapsibleSidebar-module"] { display:none !important; }

Since a few hours ago, this userstyle no longer works as intended 😞 ; it now only hides the footer of the sidebar (where the Feedback, Preview and Collapse sidebar buttons reside), not the whole sidebar 😢 ; it would appear that now the footer has got "a life" of its own, separate from the main issues sidebar; would you be so kind as to offer a fix? In the meantime, I've gone back to using uBO to hide it...

Thanks in advance 😄 ...

Tag was changed to aside instead of div:

aside[class^="CollapsibleSidebar-module"] { display:none !important; }

[Vangelis66]

Thanks a ton! 🫶 Sanity restored...

[romgerman]

There is no way to disable this feature preview in the "Feature Preview" setting dialog.

[msfredb7]

Minor feedback: I'd like to see my views directly in the sidebar to save 1 click. The goal of views is to save clicks, but having to click twice might result in me being to lazy to use them.

NB: The views I'm creating are nothing crazy big.

[ta-hoshino]

I agree with this opinion as well.

If I were to add one suggestion, it would be to allow users to choose which views appear in the sidebar. The reason is that always displaying views that are not used frequently but are needed occasionally can make the sidebar feel cluttered.

[nikitabobko]

Even better: make it possible to see the view as a tab alongside 'Issues', 'Pull requests' saving yet another click

[gwennlbh]

yeah, sth like this!

maybe with a collapse/expand arrow on the Views tab, so that theres room to do this on not only the Views tab, but also Projects and Milestones (only showing open projects/milestones)

and heck why not even do this for labels, although theres usually too much labels for that to be useful

or instead of a collapse/expand arrow, make it so that views/projects/miletones are pinnable to the sidebar, so you can chose what shows up directly in the sidebar :)

[AThousandShips]

The sidebar keeps popping out to full size before collapsing each time the page reloads which makes it very disruptive, it also takes up excessive space on small screens, I think this should be something you can disable

[AThousandShips]

Also the folding of the side bar is not remembered across multiple tabs, which makes it very impractical when navigating the website, for example opening just closed issues or filtering by a specific tag

[CON3JITO]

Hello! Thanks for the report. We got a fix out for this. If you're still running into the issue, let us know!

[v-coder247]

Hi @AWilly0897, thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

[CST1229]

Extremely minor nitpick: I don't like how the sidebar pushes away the rest of the issues page, making the page off-center, even when collapsed. It's just mildly annoying to me. Not sure how this should be fixed, or if it even should be 'fixed'. (One of: option to hide the sidebar entirely, center the page when collapsed, center the page always, or don't change anything)

Though I DO like how it finally gives a rather discoverable-ish way to get to the milestones page, instead of "edit the URL to add /milestones".

[glen-84]

Not minor in my opinion, and something that so many UIs get wrong.

Just have the sidebar float, so that it doesn't affect the positioning of the main content (reduce the main content width if necessary).

I find it very awkward like this.

[DNin01]

I personally find the Milestones button less prominent than it was before.

[srnyx]

I think moving the sidebar to the right side and then keeping the main content (issues list/etc.) still centered would look a lot better. (and decreasing the width of the main content of course to accomodate the sidebar)

It would feel too squished if the sidebar was on the left and the main content was still centered. But with the sidebar on the right, the issue titles/metadata is no longer near the sidebar, creating a natural separation, rather than a forced one.

This of course impacts the expected "sidebar on the left" design. But, I do think it makes some sense to have it on the right, as individual issue pages have their sidebars (assignees, labels, projects, etc.) on the right too.

[gwennlbh]

the thing is, designs dont do "sidebar on the left", it's more about content hierarchy: you put the more general stuff at the start of the reading order (so left in LTR languages) and go more detailed as you continue on the inline (horizontal) axis

so here the sidebar is more general than the content to its right since its what appears when you click something on the sidebar

but on issue pages, the right-hand sidebar has metadata about the issue, so more specific than the issue title/description

thats why its like this :)

[ebndev]

Hi @Neustradamus,

Please note, contacting any member of GitHub Staff via unsolicited mentions or pings is strongly discouraged and may be considered a violation of our prohibition against harassment. Please review our Code of Conduct for more information.

The team is actively monitoring this thread however not every comment may get a reply, and feedback left in this discussion should only be for this specific topic. I've gone ahead and added a "Product Feedback" label to your other discussions.

Let's work together to keep GitHub Community a place where people feel safe to participate by being respectful of them and their time.

Thanks for understanding!

[opwise-Jeff]

Ability to set one view as the default view for issues for that repo would make this an awesome addition!

[thorntonryan]

Absolutely! To elaborate one potential use case, I want the "public" facing issue list to contain user visible "bugs" or other "feature requests". That way users can see what problems have been reported and what capabilities have been requested. To achieve this I'd like to set my filters by issue type and exclude uninteresting (from an end user's vantage) issues from the default views.

I really want to "hide" task level issues that are more related to project planning, task decomposition, etc. work. Our non-technical audience doesn't really care if, internally, we update to "LibFoo v1.2.3.4". It may be necessary to fix their bug, but it's really just "noise" from their vantage. Dedicated views will help us keep this internal/public distinction... but it would be helpful to have control over the "public" facing / default view most users will see first.

[michael-conrad]

HOW DO YOU DISABLE THIS EVIL THING COMPLETELY?

[mccolljr]

Seconded. I have a specific workflow that I use. I am all for creating new features for people that use them, but if you don't give me a way to opt out I am going to leave Github. This is like the third or fourth "mandatory" change. I don't use github in this way. With the way you're pushing AI features, I know that it would be a few minutes with Copilot to implement a settings-driven toggle for this.

[connorshea]

it'd be nice if the sidebar were collapsible globally so I don't have to re-collapse it on every repo.

[sunnyi101]

Thank you for the feedback! We're going to be resolving this soon

[CON3JITO]

Hi! Just wanted to follow up and let you know we got a fix out for this. If you're still running into the issue, let us know!

[ivanperez-keera]

@CON3JITO please explain

[inuyasha82]

@CON3JITO please make a fix also to let user hide it everywhere. I don 'use that feature at all, and is taking screen space. I don't want to collapse a bar that I don't use, i want to have a nice toggle: Enable this feature: Yes/ No

[bomeejung]

Love the new views. Is it possible to have a dynamic filter criterion (like, milestone:latest for the most recently created or milestone:due)?
The link to Projects doesn't add anything IMHO.

[Hamham6]

EDIT: This is on Firefox 150, macOS 15.7.5
If the display is wide enough that the sidebar doesn't automatically collapse, but not wide enough that it gets placed properly next to the issues, then this illegible overlapping off the sidebar and the issues happens. In addition, the sidebar gets pushed way up if you scroll up, so there is just the sidebar and blank space with nothing there.

clipped_480.mov

[sunnyi101]

Thank you we are actively investigating this!

[Hamham6]

The "report issues" link to here on the sidebar and the active responses from the author are very convenient and appreciated!

[sunnyi101]

Appreciate it!

[ArthurKun21]

Please make it remember if I collapsed it or not, so that whenever I go to another repo's issue it would remember it and I don't have to toggle it again

[ARKITEKTENXxREAL]

W Kairos Timeline 29. juli 2026 kl. 17:47 skrev vhf2jghn76-sys ***@***.***>:  W — Reply to this email directly, view it on GitHub<#200164?email_source=notifications&email_token=BT2JGECJRBX4RFILIZEGSYL5HIMBNA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZYGI4TKOJXUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17829597>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BT2JGEDUMEDFTTDHJ2DGZIL5HIMBNAVCNFSNUABIKJSXA33TNF2G64TZHMZTAMJVG4ZTGNBUHNCGS43DOVZXG2LPNY5TCMBTGIYDOMRYUF3AE>. You are receiving this because you commented.Message ID: ***@***.***>

[HtetSec-0ps]

The current local time in my country is 0230 am. I haven't slept since last night. I've been studying GitHub and learning how to use it. I don't have a computer to use like the tech teams. This is my first time working with such advanced technologies, so I'm reading carefully to make sure I don't make any mistakes. So I apologize for the late reply.

Thank you all.

Have a good night.

[vuckob01]

Hello,
today I try to configure clevo-control-center n my computer. I must say almost everything is working on my computer. DMI is: Product Name: NS5x_NS7xAU , Board: NS5x_NS7xAU, BIOS: 1.07.13. OS is Linux Zorin, 18.1, with Kernel 7. Working functions are: ✅ kernel module
✅ DCHU API v9
✅ fan control
✅ RGB keyboard
✅ Clevo Control Center GUI
✅EC settings reading
Not working: battery saver, which can be read, but not write.

[v-ember]

Hi @vuckob01, thanks for being a part of the GitHub Community!

In our Community Code of Conduct, we ask that members contribute in a positive and constructive way. This type of post is considered "off topic" as GitHub Community Discussions focuses primarily on topics related to GitHub itself or collaboration on project development and ideas. Any repeat and future violations may result in a temporary or indefinite block from the Community.

We appreciate your understanding.

[v-ember]

Hi @iamkarlkm, thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

We’ll be hiding this post for now, but please feel encouraged to create a new discussion in English if you still need support.

[v-ember]

Hi @88866888, thanks for participating!

Unfortunately, we don’t currently have moderators for languages other than English. Until that changes, we need to ask that everyone use English here in the GitHub Community when posting to ensure discussions are adhering to our Code of Conduct.

[aa-kyg]

Who deliberately decided that rapidly recognizable visual symbols were unnecessary in a heavily used technical interface? Please restore them.

[HtetSec-0ps]

I am sorry. I do everything my use only gmail. Cause I really person. So I don't have much another accounts

[RoarGronmo]

Could you please add a prefix on the field tags, so we can see what type of field it is:

[abimaelmar27-design]

GEACUAASN

[tobysu111-art]

LX -> Documentation and project structure
L0 -> Requirements and Objectives
L1 -> Architecture and implementation
L2 -> Validation of the codebase
DS -> Descoped Feature, Descoped Analysis

[tobysu111-art]

LX -> 文件和專案結構
L0 -> 要求和目標
L1 -> 架構與實現
L2 -> 程式碼庫驗證
DS -> 去範圍特徵,去範圍分析

[prevleakgroup]

done, adopting