Issues: Index, Create and Show Page Updates Public Preview

[github-staff]

GitHub Issues is evolving! 🥳

Feedback wanted

Thank you for participating in the issues public preview for sub-issues, issue types and advanced search.

• Sub-issues Public Preview #139932
• Issue Types Public Preview #139933
• Advanced Search for Issues Public Preview #139934
• Increased Project Item Limits Public Preview #139936

This new functionality is built on top of a UI rewrite of issues, which we would love your feedback on!

The aim of this rewrite was to clear up technical debt, allowing us to move faster in bringing new functionality to issues. With this in mind our goal has been parity with the existing experience. It should feel very familiar with only a few minor cosmetic tweaks.

The experiences that have been included so far in these updates are:

• The repository issues index
• The main issue body
• The issue creation experience

The milestones, labels and /issues dashboard pages have not yet been migrated.

Please leave your feedback below on what is working well, any bugs you encounter, and what else you’d like to see!

[ndren]

Why is the font weight on /issues lower now? It makes the text a lot more difficult to read.

Before, font weight 600:

After, font weight 500:

[lumaxis]

@ndren Would you mind sharing your OS and browser? This is not intended behavior and we'd like to get it fixed 🙏🏼

[Siedlerchr]

firefox on mac os

[PatchMixolydic]

Previously reported in the old thread (via Firefox on Linux).

[david-crespo]

Same in FF on Mac and Chrome on Mac.

[LiamGallagher737]

Same on Firefox on Linux

[samlh]

On mobile, when I use the browser back button to return from an issue to the issues list, the issues list will intermittently (but annoyingly regularly) fail to load for me. Reloading the page woks around the issue. Otherwise, the new issues list is ok.

[sunnyi101]

Thank you for the feedback! We will look into this.

[InAnYan]

I don't like that overall UI has less contrast than before. I'm really used to that contrast and now for me everything is a little bit too light or invisible.

[azenMatt]

Would you be able to share a screenshot and highlight the areas that are problematic for you here so we can take a look?

[InAnYan]

The other thing I don't like is the "title bars":

Previously most of the space was for avatar and username. Now it become much smaller and more space is captured by this blueish background

[kbdharun]

Agreed, also edits are shown in the far right making it difficult to identify them.

New edits UI:

Old edits UI:

---

While the new UI aligns with the edits identification in the GitHub discussions UI here, I think it is better in both places to make the comment/thread better identifiable that it was edited.

[peterloveland]

Thank you both for the feedback! We are currently working on some fixes for these 👍

[bohdan-shulha]

Omg, this is so much a long-awaited feature for me.

I maintain an open-source (actually, fair source) project and I have multiple repositories for different services (server & agent software).

I am used to creating all tickets on the primary repo (server) and then, if there is work to be done for an agent, I create an issue in the agent's repo with a single line: "Relates to ####".

Now I can create sub-issues for another repo in my "epics" and better see the actual progress!

[sunnyi101]

Thank you for the feedback!

[egorikftp]

UI looks broken on desktop (https://github.com/ComposeGears/Valkyrie/issues):

the same layout on mobile looks correct:

[Lamparter]

What's broken on mobile?

[peterloveland]

Thanks so much for the feedback! 🙌 @egorikftp Would you be able to share the OS and browser from your desktop screenshot? We can see some unintended alignment/spacing

[egorikftp]

@peterloveland
macOS 15 and Google Chrome (Version 128.0.6613.138 (Official Build) (arm64))

[giordano]

With the "classic" interface, in the issues index page, when sorting issues by last updated you'd see both the time when the issue was opened and last updated. With the new interface you see only the time when the issue was last updated. I'd prefer to retain the information of when the issue was first reported.

[azenMatt]

Good spot - we will add this back

[giordano]

Thanks for looking into this! A related missing feature when sorting by last updated is the indication of the user who reported the ticket, you need to open the issue to see the name. Hopefully if you bring back the time information you'll bring back also the username bit 🙂

[boehs]

I miss the "progress circle" on the issue list, and I want to encourage checkboxes to continue to contribute to said circle

[azenMatt]

Thanks for the feedback - we are looking into how we manage this with both sub-issues and checkboxes at the moment and will make sure to take this into account

[jasperroel]

The "Sub-issues" appear by default in the /issues view. Since Sub-issues (or Tasks, the way we want to use them) are not relevant in the main issues list, is there a way to exclude them by default?

For example, the default filter for Issues is is:issue state:open, where it would be nice if we can customize this to be something like is:issue state:open -type:Task

[nebkat]

Would be great if sub-issues had a checkbox for whether to show them in the main list or not. I like the idea of subdividing larger issues but I feel like I'm forced into repeating the title of the parent issue because it only makes sense in that context, at which point it's just polluting the main issues list.

[azenMatt]

'Saved views' (with a customisable default) is somewhere we would like to go in the future which could help here?

[jasperroel]

'Saved views' (with a customisable default) is somewhere we would like to go in the future which could help here?

That would be definitely be nice!

[xlenstra]

On /issues, due to the 'give feedback' notification, there currently is a bit of margin between the menu bar and the issue list, which really throws me off. It feels like there should be something there

[nakoyasha]

Having to wait for all issues to load before you can switch between open and closed tabs is so annoying, I get that this is probably a very minor nitpick but it'd be nice if the delay wasn't there at all.

[azenMatt]

Thanks for the feedback @nakoyasha - how are you finding the loading in general? The performance of the /issues page is still something we are working on

[nakoyasha]

Aside from that, I think it's okay (haven't tested it with a ton of issues yet so can't really say)

[xlenstra]

On /issues, I dislike that currently both the comments and assigned person always show up, even if there are no comments and no one is assigned. It feels like it just clutters the screen, and especially for comments it makes it more difficult to find the issues/PRs that actually have comments on them

[azenMatt]

Thanks for the feedback here @xlenstra - this was also a hot topic for us internally 😄 it seems to have fans on both sides so we will continue collecting more thoughts here before we change anything

[azenMatt]

Additional comment in this discussion here: https://github.com/orgs/community/discussions/139935#discussioncomment-10822165

[nakoyasha]

It would be nice if pin, transfer, lock and delete were in this menu:

and not at the bottom of the issue, hidden away by a scroll:

[zopsicle]

Left clicking on a pull request in the issues list opens it in a new tab. It should only do this when middle clicking, not when left clicking. This does not happen when left clicking on an issue, only on a pull request.

[azenMatt]

Good spot - we will get that fixed

[DavidVentura]

The Add existing issue dropdown does not show/complete all issues. There are many issues matching the query in my repo, but after adding a few to the issue, the rest are not selectable:

[azenMatt]

Thanks for sharing @DavidVentura - we will take a look

[evi-liu]

Hi @DavidVentura, thanks for sharing this feedback! Couple of follow-up questions:

• Are there other issues you're looking for in that repo that include upgrade in the title or is it in the body of the issue?
• Are the issues you're searching for open or closed issues?
• Are the issues you're searching for already added as sub-issues to another issue?

This will help us inform how to improve the search functionality!

[DavidVentura]

• Upgrade is in the title, and yes there are more issues
• Open
• No

Initially the dropdown contained ~10 items (out of 21), and as I started picking them, each item got removed from the list, but a new item did not take its place; so the dropdown shrunk item by item until it was empty.

Typing #issuenumber on the dropdown does show the issue, containing upgrade in the title

[arcanis]

More of a feature request than a feedback on the current beta, we'd reaaally appreciate if we could have status checks on GitHub Issues (not just PRs). This would let us validate that issues have proper repros without having to add a giant list of comments added by annoying bots.

[azenMatt]

you are thinking in terms of 'does this issue have replication steps yes/no' rather than 'do the replication steps actually work'?

[Lamparter]

I've noticed quoted text isn't collapsing anymore:

Previously, this would have collapsed into a smaller scrollable area, for better viewing.

Do you understand what I mean? 😅

[CeruleanDerpo]

The removal of the "clear filters" button makes usability worse

[azenMatt]

We have an 'x' to clear here:

Does that help at all?

[jclulow]

Put the "Filters v" dropdown on the issue search back? Also, for the love of god, stop changing everything.

[boehs]

Also, for the love of god, stop changing everything.

Either you or somebody in your organization opted into this beta. While like most betas it is flawed, in my opinion what it represents is quite a positive change. Issues have needed attention for a while.

[azenMatt]

Thanks for the feedback on the filter, we are collecting feedback on that as it was not heavily used so we wanted to explore a more minimalist version along with the auto complete.

[david-crespo]

Issue create

Removing the inner box on the textarea and the spacing on the left edge of the screen is a clear UX downgrade. Also the spacing between the submit buttons and the text area is obviously too large.

After

Before

[azenMatt]

Thanks for the feedback - we will take a look

[Su5eD]

Seems like the new issue UI is not aware of blocked accounts. When trying to add a reaction to an issue created by a person that has me blocked, I can access the emoji selector, but upon picking a reaction and closing the selector, it only appears briefly on the issue before being removed.

[xieyuh430]

謝謝

[christopherpross]

Hello,
I am a blind user, and I navigate GitHub using NVDA as my screen reader along with Firefox as my browser. I've noticed some improvements in the accessibility of the new issues list view, which I want to highlight:
• I can now navigate through the list of issues using the arrow keys, which makes it much faster for me to go through them. I can also press Enter to open an issue, and this functionality works smoothly.
However, there are a few areas where the experience could be enhanced:
1.
The new issue view does not appear consistently across all repositories for me. Is this intended, or do I need to adjust any settings to enable this view universally?
2.
While navigating an issue, certain information is read aloud that may not always be relevant or clear. Here is an example of what is currently read out from the aria-label:
• "AI Integration Microservice: Status: Open. Add author TheMorpheus407 to current search query. More information available below."
• "Add author TheMorpheus407 to current search query." This appears to be an actionable item, but as a screen reader user, I am unsure how to trigger this action or if it's even possible for me. Additionally, since this is the author of the issue, I believe it should be presented separately as informational content rather than part of the main navigation flow.
• Essential details like labels, number of comments, and creation date are missing from the list item name. These details are accessible when navigating via headings, but it would be helpful if they were included in the list item itself to provide a more comprehensive summary.
3.
"More information available below." This message could be optimized by allowing screen reader users to customize which information is included in the list view. Perhaps an option could be added to GitHub settings to choose which details are announced. Alternatively, keyboard shortcuts could trigger a live region that provides more details when needed.
Thank you for considering these suggestions! I appreciate the ongoing efforts to improve accessibility and hope this feedback helps in making GitHub even more inclusive.
Best regards,
Christopher

[kbdharun]

Hi, nice to have accessibility feedback from a screenreader user and kudos to you for trying it out, I am not affiliated with GitHub, but regarding your first question, it isn't available across all repositories currently as this feature is in public preview and is currently opt-in for organization administrators to join the waitlist (and it isn't available for repositories hosted under normal users).

[azenMatt]

Thanks for sharing @christopherpross

as @kbdharun pointed out the reason for point 1 is because only orgs in the beta will have the new version.

I'm glad the new navigation is smoother for you, that was exactly the outcome we were looking for 😄 let me work with the team on points 2 and 3 so see what we can improve here.

[simonklee]

It's no longer possible to select/batch update more than 25 issues.

[azenMatt]

I could be missing something 😅 but the old experience also only supports 25

[porzana]

There used to be a "customize" button at the top right of this section, which allowed you to only subscribe to open/close. It seems that it has been removed. That's pretty unfortunate, I used this feature often to be notified about bugfixes/feature requests being implemented without having my inbox spammed.

If the old dialog is too complicated / requires too many clicks, maybe taking inspiration from Refined Github would make sense:

[azenMatt]

Thanks @porzana - we are working on adding this back in

[sa-kei728]

When creating a new sub-issue, the settings at the bottom are getting cut off.
It would be great if I could scroll.

[azenMatt]

We are taking a look at this now

[lucacasonato]

Hey - we just enabled this in the @denoland org. However, we are now unable to see all of our issues in the denoland/deno repo, because we have more than 1000 issues 😆

It seems even with the default filter (so no filter), you can only view the first 40 pages of results:

https://github.com/denoland/deno/issues?page=40

If you don't think this is reasonably fixable within a day or two, please opt us out of the preview again until this is fixed. Thanks!

[lucacasonato]

Thanks @azenMatt - can you let me know when this limit is lifted, and we can try again?

The sorting from the end thing doesn't work if you have more than 2000 issues

[lucacasonato]

@azenMatt It seems that the limit still exists for me, even if I do not see issue types anymore. The org still seems to be opted into some of the experiments - just in particular not the issue types one anymore. Can you take a look?

[azenMatt]

I can confirm that the account is no longer in the feature flag - it might just need more time to update. The flag is on an org by org basis so if you have other orgs they might have also opted in

[lucacasonato]

Hey Matt - I am still seeing this behaviour: https://github.com/denoland/deno/issues?page=40

[lucacasonato]

Sorry to ping again, but we are still seeing this a day later:

[nick-kang]

When creating an issue, it'd be a nice UX improvement if I can click tab from the Title directly to the description textarea. Right now, clicking tab from the Title, takes me to the Write nav item.

[Su5eD]

Markdown admonitions seem broken in issue form template.

See here for an example.

[LeoColomb]

I second that.

Before	After

[typed-sigterm]

Maybe it's better to place the search button to the left, like the search bar on the top of the page.