Saved views for repository issues - public preview and adjustable row heights #200164
Replies: 284 comments 177 replies
|
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 
|
|
G |
|
crazy |
This comment was marked as off-topic.
This comment was marked as off-topic.
|
Works good on ios 16, just getting an ugly white line below. Please remove |
|
I am new to github and doing the best I can to learn how it works. I came from gitlab with a very mature product; and this is significantly better, but different and there is a learning curve. Any help or corrections are appreciated. Brandon SNTL |
|
It would be nice to have an option to hide this sidebar. |
This comment was marked as low quality.
This comment was marked as low quality.
|
There's a collapse button, which helps, but doesn't completely hide it. |
|
How about: github.com##[aria-label="Issues sidebar navigation"][aria-label="Issues sidebar navigation"] { display: none !important } |
This comment was marked as low quality.
This comment was marked as low quality.
|
I want the same little "Expand file tree" icon that you get when looking at a file in the repo. I don't want ANY space taken up by the side bar at all when not in use. Specifically There is utility in the custom views. I don't see any point in this otherwise, it's just a more intrusive version of the filters we already have. The custom views would be useful for my previous manager at work, but I don't really see anyone else I know using them. This has GOT to have a fully-hide option for the rest of us. |
|
There is no way to disable this feature preview in the "Feature Preview" setting dialog. |
|
Hola soy nuevo x aquí, se pone bien?? |
|
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. |
|
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. |
|
Even better: make it possible to see the view as a tab alongside 'Issues', 'Pull requests' saving yet another click |
|
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 :) |
This comment was marked as spam.
This comment was marked as spam.
|
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 |
|
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 |
|
Hello! Thanks for the report. We got a fix out for this. If you're still running into the issue, let us know! |
This comment was marked as low quality.
This comment was marked as low quality.
|
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. |
This comment was marked as low quality.
This comment was marked as low quality.
|
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". |
|
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. |
|
I personally find the Milestones button less prominent than it was before. |
|
This is not a minor nitpick, this is driving me insane and I hate that there is no way to get rid of this annoying sidebar. I might have used it, but now I just get mad every time I see it making the page look bad in "collapsed" mode. NO COLLAPSE! YES HIDE! |
|
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. |
|
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 :) |
|
If you don’t mind the tooltip1 being off-screen: github.com##section > div:has(> [aria-label="Issues sidebar navigation"]) { flex-direction: row-reverse !important; }section > div:has(> [aria-label="Issues sidebar navigation"]) {
flex-direction: row-reverse !important;
}Footnotes
|
|
win7 64位系统下，软件启动不了 |
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
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! |
|
Ability to set one view as the default view for issues for that repo would make this an awesome addition! |
|
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. |
|
HOW DO YOU DISABLE THIS EVIL THING COMPLETELY? |
|
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. |
|
I hate it so much |
|
it'd be nice if the sidebar were collapsible globally so I don't have to re-collapse it on every repo. |
|
Thank you for the feedback! We're going to be resolving this soon |
|
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! |
|
@CON3JITO please explain |
|
@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 |
|
No. HIDABLE globally, not Collapsible. |
|
Love the new views. Is it possible to have a dynamic filter criterion (like, milestone:latest for the most recently created or milestone:due)? |
|
EDIT: This is on Firefox 150, macOS 15.7.5 clipped_480.mov |
|
Thank you we are actively investigating this! |
|
The "report issues" link to here on the sidebar and the active responses from the author are very convenient and appreciated! |
|
Appreciate it! |
|
This should be the standard for all new features, and ideally for the entire site. It's a pain to hunt down the appropriate feedback thread for everything! |
|
HALLO |
|
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 |
|
This has been fixed! |
|
HALLO |
|
|
The labels disappeared: 
For me, the most important information is on issues (after the title). |
|
Just noticed the button to switch to the old view on the right. It's not obvious how to get back to the old view to see the labels. If this is a compact view, maybe color icon boxes with the first letter instead of labels. |
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as spam.
This comment was marked as low quality.
This comment was marked as low quality.
This comment was marked as off-topic.
This comment was marked as off-topic.
|
In the issues list, the links to display closed / open issue are now missing. They were very handy; now I need to type "closed" in the search field as a workaround. Or is there another new way to quickly display closed / open issues? |
This comment was marked as spam.
This comment was marked as spam.
|
With all that space, I think it would be nice if we could dock saved views in the sidebar. Thats all. This is super cool! |
|
The sidebar has filters:
Please add "Involves me", which adds filter That is very useful when one cannot remember the subject/content of an issue (it shows all your issues). |
|
The 'Bulk update is pending' popup is stuck. It won't complete, cannot be cancelled, and won't let me dismiss or hide it. This is blocking my screen and halting my work. 
|
|
I'd like to be able to save views on the Pull Request page sidebar as well. I can create views for PRs with different filters but I have to go to the Issues page to access them. |
|
Suggested issue title: Fix runtime errors and invalid configuration in README examples Copy the following into a GitHub issue: ## Description
I reviewed the README examples at commit 36985472d1c19a28809ede7442239279a67c1317 and found several runtime errors and configuration problems.
## Findings
1. **S3 event matching skips real events** — lines 228–233
S3 sends event names such as `ObjectCreated:Put`, without the `s3:` prefix. JavaScript switch statements also do not interpret `*` as a wildcard.
Suggested fix: use `eventName.startsWith('ObjectCreated:')` and `eventName.startsWith('ObjectRemoved:')`.
2. **Logger references an out-of-scope variable** — lines 452–480
The logger references `context`, but that variable is only available inside the handler. The first logging call throws `ReferenceError: context is not defined`.
Suggested fix: pass the request ID into the logger or create the logger inside the handler.
3. **Incorrect DynamoDB SDK v3 method** — lines 397–404
`DynamoDBDocumentClient` does not expose a `.get()` method.
Suggested fix:
```javascript
const { GetCommand } = require('@aws-sdk/lib-dynamodb');
const result = await docClient.send(new GetCommand({
TableName: 'MyTable',
Key: { id: event.id }
}));
ValidationLocal Node.js checks reproduced these failures:
Configuration findings were checked against AWS documentation. No AWS deployment was performed. References
|
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
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.
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:
Share feedback, report issues, or suggest ideas in this discussion.
All reactions