Evolving GitHub Issues - 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.

To provide your feedback on other experiences released at the same time, please visit:

• Sub-issues Public Preview #148714
• Issue Types Public Preview #148715
• Advanced Search for Issues Public Preview #148716

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!

🛠️ Things we fixed

We're listening to your feedback and working hard to address the highest priority issues. Below is a list of bug fixes and enhancements that we rolled out since we launched the Public Preview.

🛠 Bug fixes:
• In certain repositories, running a search would navigate to the Issues page
• Some users couldn’t view the Issues Index
• Broken navigation for some users
• Focusing on the title input when creating an issue
• Closed (not merged) linked PRs showing as drafts in the development picker
• Pagination on the Issues Index causing elements to jump
• Ability to perform exact searches in Issues
• Some assignees not appearing in the assignee search
• Checklist indentation
• Emoji alignment

✨ Features & Enhancements:
• Automatically bypass template selection if there’s only one template and blank issues are disabled
• Create milestones directly from the milestone picker

[mcanouil]

Parsing of code blocks in issue templates within the new GitHub Issues is broken. (see the bottom of the screenshots)

Additionally, as you can see at the top, the name of the template and its description is no longer displayed in the preview of the new issues.

Preview	Current

Using extra backticks or indentation leads to different parsing issue in the preview. (None allows to get proper display as without the new GitHub Issues)

Extra backticks block

Indentation block

name: Bug report description: Report an error or unexpected behavior labels: [bug] body: - type: markdown attributes: value: | You can share a Quarto document using the following syntax: `````markdown ````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document using `format: html`. It is written in Markdown and contains embedded Python code. When you run the code, it will produce a message. ```{python} print("Hello, world!") ``` {#fig-placeholder} {{< lipsum 1 >}} A reference to @fig-placeholder. The end. ```` ````` - type: textarea attributes: label: Bug description description: Description of the bug. placeholder: Please describe the bug here.

name: Bug report description: Report an error or unexpected behavior labels: [bug] body: - type: markdown attributes: value: | You can share a Quarto document using the following syntax: ````qmd --- title: "Reproducible Quarto Document" format: html engine: jupyter --- This is a reproducible Quarto document using `format: html`. It is written in Markdown and contains embedded Python code. When you run the code, it will produce a message. ```{python} print("Hello, world!") ``` {#fig-placeholder} {{< lipsum 1 >}} A reference to @fig-placeholder. The end. ```` - type: textarea attributes: label: Bug description description: Description of the bug. placeholder: Please describe the bug here.

Original issue template for the screenshots: https://github.com/quarto-dev/quarto-cli/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml

[boazreicher]

Thank you for reporting this. We can reproduce the issue, and are currently looking into it.

[boazreicher]

Hi @mcanouil, we've rolled out the fix for this. Please let us know if you still encounter any issue.

[mcanouil]

Thanks, it works!

[karlhorky]

Copying my comment from discussion 139935 (cc @alondahari @labudis):

---

Linking to a text fragment does not work with the new GitHub Issues UI, reproduction steps:

1. Use a browser that supports linking to text fragments (eg. Google Chrome)
2. Visit a page with the new GitHub Issues UI (eg. Preflight Docker container with PostgreSQL database: opts.uid is NaN upleveled/preflight#588)
3. Select some text on the page, right click and select "Copy Link to Highlight" (see screenshot below)
4. Visit the example link
5. 💥 Observe that the page either scrolls to the wrong position and does not highlight the text

Expected (old GitHub Issues UI)

Example link:

https://github.com/lovell/sharp/issues/4247#:~:text=provide%20sample%20image(s)

Correct scroll position, highlighted "provide sample image(s)" text:

Actual (new GitHub Issues UI)

Example link:

https://github.com/upleveled/preflight/issues/588#:~:text=We%20need%20to%20investigate

Incorrect scroll position, no highlighted text:

---

Also, copying the comment on my discussion thread by @MasterInQuestion:

The janky anchor navigation is far more pervasive...
    github.com/orgs/community/discussions/139935#discussioncomment-11058053

[labudis]

@karlhorky thanks for flagging this again! We are aware of this issue but we are working through a large backlog of ideas and suggestions and this particular fix has not yet reached the top of the priority list. We do consider every piece of feedback that comes from the community so please keep highlighting anything that could be improved - it truly helps!

[jfredt]

good feedback!

[MichaReiser]

Copying my comment from the previous discussion

---

We're still using the legacy issue template workflow because we want only a single template with some pre-defined content in the description. We don't want users to have to select a template.

We noticed that the issue template no longer works after opting into the public beta. Now, I'm mainly curious to understand if this is intentional because the workflow is considered legacy or if you plan on bringing back support for legacy templates, and we can keep using it. Thank you

[MichaReiser]

Thanks. No, it's really just that the new issue template feels overkill for projects with exactly one template.

[ricard9dl]

Did you notice any significant changes in how the legacy templates work after opting into the public beta?

[jenniyuslauw]

good feedback

[boazreicher]

Hi @MichaReiser, we've rolled out a change so that now when creating a new issue, if the repo has blank issues disabled and exactly one template, it will bypass the template selection dialog and instead go directly to creating a new issue using that template.

[MichaReiser]

Oh nice. Thank you! We'll give it a try.

[janbrasna]

I'm not sure what is actually part of what "experience"/preview, as this discussions space doesn't really make it easy to navigate and understand how it all relates together, with announcements posted as "unanswered questions", and messaging from staff indistinguishable from any other content amidst emoji explosions in categories and labels looking like unicorn barf of color and shapes and other myspace-esque qualities that probably only make sense to folks under the legal drinking age… so sorry if I'm not posting in the right thread, but they all look quite alike, with some of the boilerplate text of announcements recycled, esp. wrt what's in scope and what not, that seems to be identical across the threads, so you've effectively lost me there;)

1. I've noticed there's some "preview" without any info, feedback link, or opt-out (incl. in settings):

• Issues showing "Preview" badge with no additional context taking up valuable space #149146

2. Not sure if the new editor UI is also part of this, can't find the same as above (missing preview info, opting out of the experience, and a link to feedback) to post under the announcement/feedback there, so made a new thread:

• Issue composing textarea feedback #149149

[labudis]

@janbrasna Thank you for sharing your feedback and I'm sorry to hear you did not find our communications clear. It's one of the largest public previews in recent GitHub history touching many parts of the Issues experience and whilst we strive our best to communicate clearly, there is always scope to do better and we take your comments on board.

Regarding the scope of the release, it impacts virtually every part of the Issues experience. We focused on improving the performance and usability of the new issues experience whilst keeping it as similar as possible to the classic Issues experience that our users know and love. In addition, we have added three completely new features: sub-issues, issue types and advanced search.

I will respond to the two specific pieces of feedback in their respective discussion threads.

[janbrasna]

Oh no worries Tadas, I'm just probably not wired to navigating the discussions space for feedback purposes;) and failed to find the appropriate threads instead of submitting new ones. Hopefully it's relevant to what you've been working on — thanks for taking a look, appreciate what you do here!

we have added three completely new features

Great job with those major features, hat tip!

[jenniyuslauw]

good feedback!

[gabrieldigger]

What specific improvements does the user suggest for better clarity in announcements or feedback threads?

[janbrasna]

What specific improvements does the user suggest for better clarity in announcements or feedback threads?

Funnily enough, it's e.g. hard to tell apart content from GH staff, compared to others once it gets a bit noisier like here — so if this inquiry comes from a Hubber I'd be happy to elaborate a bit more if you're interested, nonetheless I see no sign that this particular user is "staff" to begin with.

(E.g. I'd like to unsubscribe from all other notifications from other comment threads, and only get pings for the reply threads on comments I've participated; and/or only staff responses instead of getting pings throughout the day of everyone adding to the feedback etc. — but there's definitely more, happy to share a user's PoV from the experience of several years using the discussion space as a landing page for feedback from GH UX preview opt-ins…)

[dirkf]

The design whereby issues are listed in a single page is fundamentally useless for an issue with more than a few tens of posts. It should be possible to show an issue with a large number of posts in a multi-page scheme where it isn't necessary to expand elided posts.

[alondahari]

@willpower232 by "this editor" do you mean this discussion post? If so, that's correct that feature is only implemented in issues and pull requests.

[willpower232]

"this editor" refers to the feature preview, I was trying to reference a chunk of code in a new issue in a private repo whilst this feature preview was enabled for me and the big textbox was empty

[MichaelChirico]

I'm also experiencing this on a public repo -- "Reference in new issue" flow is totally broken.

Previously, "Reference in new issue" would pre-populate some fields, especially copying over a perma-link to the highlighted code. That was the core appeal of that feature, otherwise I would just "copy permalink" and click the "New issue" button myself.

[MichaelChirico]

cc @akenneth in case the above got lost in the noise, this flow is still totally broken. Thanks for your efforts & triaging!

[MasterInQuestion]

    "permalink" of "issues/new" is relinked to:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11990086

    The topic here is actually about something mostly irrelevant...

[ichard26]

First all, I want to say congratulations on the new features! I haven't had the time to play around with them as the preview has just rolled out for my repositories, but they do seem useful on a first glance. Sub-issues and issue categories are of course totally doable with crosslinking and labels, but giving them dedicated space in the UI is nicer. I'll follow up if I have further feedback once I've played around the new features.

Anyway, I'm sure I missed the relevant discussions on the old (and unwieldy) thread, but I want to bring up two issues (🥁) I have:

The sticky issue header no longer states the creation date or the number of comments

New:

Before:

While I appreciate that some people probably don't need this information, I find it invaluable having these two pieces of information always available to me. When I'm sorting through tens of issues at once, it can be easy to lose track of what exact issue I'm on. For example, if I'm looking at an older and more heavily commented issue, I'll probably prioritize fixing this issue over a newer issue with less activity. Of course, I can still find this information from other places, but I have to click or scroll away, when with the old UI, it was just right there!

Is it possible to readd this information to the header? If not (maybe it's used by the new features?), could we at least add a count of comments somewhere on the issue view?

Labels are overly aggressively truncated in the timeline

This seems to be a trend with all of the recent UI refreshes. I get that making an UI less busy is nice and all, but there is more than enough room to display the full type: feature request label without being truncated.

Shown issue: pypa/pip#13165

[ohiosveryown]

The sticky issue header no longer states the creation date or the number of comments

This is something we talked about quite a bit internally, the amount of information to surface in the sticky header. I could see how comments would be helpful when having multiple issues open. I'll file this and the label truncation to the team.

[MasterInQuestion]

    Related:
    https://github.com/orgs/community/discussions/139935#discussioncomment-11568166

[stosic]

Are there any additional pieces of information you believe should be included in the timeline or sticky header to make the interface more useful?

[MasterInQuestion]

    Outright copied from linked:
    “|2| The top banner is missing quite some issue details:
    E.g. "${Author} opened this issue ${Timestamp} · ? comments · Fixed by #?"
    Just compare without the Preview.”

    It's not about being more useful...
    It's strictly about being no less useful. (no regression)

[janbrasna]

One piece of a11y feedback I'd love to see sorted somehow rather soon(ish), as I'm not currently aware of a way to opt-out of the UI (as that's managed on repo owner side, or org/enterprise side?) is this aggressive flickering loading the numbers and search highlights:

Screen.Recording.2025-01-14.at.22.38.10.mov

(Safari 18, macOS 15)

For my health condition this is only extremely uncomfortable, but for some others this flicker can be actually even dangerous.

Could this please only display once loaded fully, and not "fly in" from random directions? (I'd honestly prefer the static values as the classic experience or PR view has upon loading in the first place.)

[ohiosveryown]

Accessibility Is definitely an area we value heavily, so I really appreciate your feedback here. I'll file this and relay it to the team.

[janbrasna]

Thanks! I inspected the recording frame by frame and noticed: the numbers fly in from above, or move up and down; their labels move up and down; also the pills changing size and position, and the labels moving from their default positions to accommodate for longer number values after they are loaded; also while numbers invisible the filter dropdown labels next to it move left and right. That's a lot of movement!

[MasterInQuestion]

    Abuse of animation, exemplar...
    Best-effort loading doesn't mean adding meaningless interims alike:
    That only adds jankiness and slows actual loading, pointlessly.

[janbrasna]

I'm not entirely sure if that is also part of the new timeline experience, but it landed with it for me so it seems relevant:

Viewing edit history for individual comments has some changes that make it somewhat harder to understand what's added, what's changed, what's removed in the text… I was struggling with the "diff" color-coding there, will try to collect some samples over time to demonstrate the tiny things… However for now the bigger issue is the actual diff logic seems to have changed too, resulting in unreadable outputs like this:

[akenneth]

Thanks for the feedback @janbrasna! We are aware of this issue and I’ve logged your feedback against it.

[MasterInQuestion]

    Obfusdiff...
    https://github.com/orgs/community/discussions/139935#discussioncomment-11640523

    Matters new Commits pages too.

[Timmmy-nlb]

Hello,
we, companies, still need the required option in the issue forms to be able to enforce reasonable processes.
This only works in public repos and not in private or internal repos.

And "we" are many and do not need to be moulded:
https://github.com/orgs/community/discussions/148495
https://github.com/orgs/community/discussions/63402#discussioncomment-6968642
https://github.com/orgs/community/discussions/51500
https://github.com/orgs/community/discussions/4264#discussioncomment-1262667
https://github.com/orgs/community/discussions/63470
https://github.com/orgs/community/discussions/4349
https://github.com/orgs/community/discussions/4378
https://github.com/orgs/community/discussions/43859
[...]

[alondahari]

Hi @Timmmy-nlb, thank you for your feedback. I hear you (plural) and feel your frustration over this issue. I logged your feedback on our existing issue and will clarify what's our next steps here. 🙏🏼

[jfrost-mo]

Issues list flashes after loading

When loading the issue list or changing pages the list of issues flashes momentarily shortly after loading. See the following video:

output.mp4

I'm using a vertical 2560x1440 display with Firefox 134.0.1 on Windows 11.

[jfrost-mo]

Another minor issue that this video shows is the page title changes many times on a page load going through:

• Repo Issues
• GitHub - Where software is built
• Issues - Organisation/Repo

With the last being the one it settles on, and the useful one.

[dirkf]

These are just side-effects of the client-side JS lazy-loading implementation which is always going to be flaky in the real world (say, not in the Gbit LAN many-core client dev/test environment). This is a critical piece of site functionality and enhancements should build on the existing functionality instead of replacing it.

[alondahari]

@jfrost-mo This should now be fixed, could you verify? thanks again for bringing this to our attention! ❤️

[jfrost-mo]

The flashing is fixed, thanks!

The upon initial loading of the Issues list, the page title just goes through "GitHub - Where software is built" before settling on "Issues - Organisation/MyRepo", and only then if you do a hard reload (Ctrl-F5). However when changing page on the issue list the page title however now settles on "Repo Issues", after going through "Issues - Organisation/MyRepo". See the below video demonstrating this:

output.mp4

[alondahari]

@jfrost-mo Thanks for the report, I added it to our backlog and we'll take a look at that 💯

[dirkf]

The 'close-as-duplicate' function is the only real positive of the rework for me. Its problem is that you have to guess which issue is the non-duplicate master issue. The potential duplicate-of list should prefer or identify issues where the issue has already had issues closed as duplicate-of it. And it should be re-implemented so as not to require JS (and then it would be fine just to type in the issue number).

[jfrost-mo]

Issue title box is tiny when composing new issue

The title box when composing a new issue is very small. This makes it hard to type issue titles of more than a few words. This runs counter to encouraging people to give descriptive issue titles.

[jfrost-mo]

Testing in Firefox after you asked it appeared to be fixed:

However when I went to edge to test there, and it was still small:

And going back to Firefox after a Ctrl-F5 it is small again:

[jfrost-mo]

I'm running Firefox 134.0.2 (64-bit) and Microsoft Edge for Business Version 132.0.2957.115 (Official build) (64-bit) on Windows 11.

	Windows versions
Edition	Windows 11 Enterprise
Version	23H2
Installed on	12/‎12/‎2024
OS build	22631.4751
Experience	Windows Feature Experience Pack 1000.22700.1055.0

My CPU/GPU is an 11th Gen Intel(R) Core(TM) i5-1145G7

[jfrost-mo]

Relevent HTML:

Compared with a working bar editing an existing image, this one is missing the InlineAutocomplete-module__fullWidth--X6eXo class.

[labudis]

thank you for the additional info @jfrost-mo - passed this on to the team investigating this.

[jfrost-mo]

This appears to be fixed today. I've tested in Firefox and Edge, after various page refreshes, and with and without a template.

[mcanouil]

Could sub-issues inherit from the parent labels by default?

[labudis]

@mcanouil thanks for the suggestion! Would you mind sharing an example of how you would use this?

[mcanouil]

For example, in some repositories my client has a workflow based on labels: priority, difficulty, type (bug, enhancement, etc.), component (codebase, analysis, etc.).
It's used to assign to GitHub projects amongst other things.
Each time a sub-issue is created, they need to go to each of them to add the exact same labels, some times with slight change for priority/difficulty.

To me, it makes sense to have an inheriting behaviour by default rather than having issues with no labels, milestones, projects even though they are created from one with.

Note: the issue was also there with the "item-issue" before the preview, so not really a new problem.

[ohiosveryown]

We've discussed inheriting meta data as we were building the feature, and it's something that's come up before. You mentioned labels, milestones, etc. Is that what you would expect? Or just solely labels?

[mcanouil]

Mostly labels.
Milestones make also sense to me in the sense that if you added the parent to a milestone, it likely means your sub-issues are also in that milestone, but I don't have strong expectations on milestones.

To summarise in a concise way:

Meta	Inherits
Labels	Yes
Type	Maybe
Milestones	Yes/Maybe
Project	Maybe
Assignees	No

[eishiya]

Looking forward to trying out the advanced search! I very rarely need it, but when I do, not having it hurt.

I don't like how accessing Most Reactions, Least Commented, Least Recently Updated, etc all take extra clicks now. Sure, the menu looks tidier now, but it's made browsing issues slower, without any new functionality that warrants the more complex interactions. The original menu was not large or overwhelming, it doesn't need to be shrunk. If it's being shrunk for phone users: cool, show that to phone users, not to people with proper screens :] I think even phone screens tend to be high-res enough now to fit the old menu quite comfortably, though.

(And it's inconsistent with the PRs list. Presumably that'd be fixed eventually, but really I'd rather see the old PR-style menu kept, as it's more convenient, with everything available with one click in the menu.)

(Edit: Whoops realised this is a Discussions thing probably not connected to the Issues rework, shows how often I use Discussions xP)
I think the background colour for replies on issues is too high-contrast, at least in the Dark Dimmed theme I'm using. Replies are important and easy to miss if not highlighted, but they don't need to grab my eyeballs out of my skull to be noticed xP Played around with just disabling that colour (so the default background colour shows through) and I think that looks plenty good, and if you want to highlight replies more than that, I think perhaps making the indent-line next to them higher contrast would be the way to go - it wouldn't hurt the contrast or readability like changing the background colour does, while still calling attention to replies.

I also noticed while editing this that sometimes the post input box collapses for a frame before reappearing sometimes. That never happened before.

[labudis]

Thank you for your feedback @eishiya! I'm glad you are enjoying the new advanced search!

We take your comments on board regarding the layout changes. There is always a tight balance between keeping things tidy and introducing additional steps to accessing functionality.

[eishiya]

Another usability gripe from me: When opening a link to a PR/commit from an issue via the "{user} closed this [...] in {PR}" text, it opens in a new tab, whereas before it opened in the same tab. Other links in posts in issues also open in the same tab. For consistency, and because it's much easier to force a same-tab link open in a new tab than to force a new-tab link to open in the same tab in most browsers, I think these and similar links should open in the same tab.

[PLTytus]

Looks like some issues are hidden with default filters on this preview.

[alondahari]

@PLTytus thanks for reporting! should be fixed now ❤️

[PLTytus]

It is good now. Thanks for quick fix.

[jay]

I noticed that the word commented is missing from the replies now, like "jay commented x hours ago". I did not realize that was intended because other words are not missing (like opened) and so I reported it as a bug (ticket 3187195). In my opinion without a break between the elements it looks spaced too close together. That is probably because the element that was removed in the preview had text that was defined as " commented " with a space before and after. If I add a padding-left:3px; to make up the space then I think it looks better. Here's a screenshot for comparison:

[labudis]

thanks for your feedback and attention to detail @jay - I will pass this on to the team.

[borbware]

Please, I ask you to bring this UI back for task lists. It's an integral part of my workflow, and it helps a lot that you can see from the issues page what's the progress with the tasks.

I read from a comment that you're planning to sunset task lists altogether (!), and I hope you could still reconsider that. Tasks are much faster to create than sub-issues (try to create 20 sub-issues with just a keyboard!), and serve a very different purpose. Creating new sub-issues pollute the issue tracker (and yes, sometimes you do want that), but tasks are contained in their issue. I have many issues with 50+ tasks in them, and using sub-issues in their stead just wouldn't be feasible.

Also, I wish you could change the spacing of tasks in a task list back - they take much more space now:

Thanks for your consideration!

[MasterInQuestion]

    "is the spacing between lines too much?"
https://github.com/orgs/community/discussions/139005#discussioncomment-11793510
    “https://github.com/MasterInQuestion/attach/raw/main/community/community/139005/10710215-Very-Spacious-Plus.webp
    https://github.com/orgs/community/discussions/139005#discussioncomment-11806370
    Spacey compactness. Entertaining indeed.”

[octatone]

@borbware checkbox lists are not going away. When you see mentions of task lists deprecation, we're specifically talking about the private beta tasks lists feature that was rolled out to some orgs. That feature is what sub issues is replacing, not simple markdown checkbox lists.

I've logged your feedback regarding the spacing and we're also looking at counts. Thanks again for your feedback :)

[dequejenn]

I also vote for the tasklists to stay. The UI of being able to type directly into the issue without doing an edit and then trying to scroll through and find where that checkbox was in the markdown code is a much better UX. I love tasklists because of how quick and easy it is to add and remove tasks

[borbware]

@octatone oh phew, happy to hear that! thanks for the answer!

[LokiMidgard]

@borbware checkbox lists are not going away. When you see mentions of task lists deprecation, we're specifically talking about the private beta tasks lists feature that was rolled out to some orgs. That feature is what sub issues is replacing, not simple markdown checkbox lists.

I've logged your feedback regarding the spacing and we're also looking at counts. Thanks again for your feedback :)

But at least the x of n view is gone, only referenced subissues will be shown in an x / n view at the top and in the issues overview. So checking some kind of progress for an issue needs now sub issues.

I like the sub issues, but for some tasks creating an sub issue for it is overkill. I would like to see an combination of the old task list and the sub issues. Combined or seperate would for me not matter (I think I would prefere combined).

[Y-T-G]

I don't like the bounce it does when loading the issues page. The elements load partially, then suddenly expand and change their position. This often leads me to click something that I didn't intend to click because it moved.

Screenrecorder-2025-01-31-12-52-10-445.mp4

[labudis]

@Y-T-G thank you for flagging this to our attention! We are working on some fixes in this area.

[MasterInQuestion]

    Sluggish JS loading aforementioned:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11854150
    https://github.com/orgs/community/discussions/148713#discussioncomment-11947983

[typed-sigterm]

I'm not sure if the bug #150407 caused by Markdown rendering change relates to this

[MasterInQuestion]

    Triaged:
    https://github.com/orgs/community/discussions/150407#discussioncomment-12036083
    .
    Abnormal checklist (TaskList) rendering for wrapped lines of the "..." button.
    Specific to the Issues Preview.

[labudis]

@typed-sigterm thanks for reporting! We are already working on a fix for this.

[labudis]

Should be fixed now!

[Xenius97]

[labudis]

@Xenius97 thanks for the comment, could you please elaborate what do you think is not working as expected?

[Xenius97]

@Xenius97 thanks for the comment, could you please elaborate what do you think is not working as expected?

Every item in the list is misaligned, I mean the checkbox.

[labudis]

@Xenius97 this should be fixed now!

[borbware]

Not sure if this is the right place for this feedback, but having this "x hidden items" UI somewhere in the middle of this page makes it very hard to notice that there are actually more comments than you can see at the moment.

(I thought my earlier message was deleted because I couldn't find it at first.)

...maybe show the UI in the bottom or top of the page, or both?

[shaedrich]

When I search something on the page with Ctrl + F and I can't find it, I need to use Ctrl + F to search for "hidden items" or "Load more…" and click "Load more…" as many times as necessary for the actual text in question to appear on the page, which indeed isn't that ideal 👍🏻

[MasterInQuestion]

    Dedicated thread:
    https://github.com/orgs/community/discussions/39463

    See also:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11864333

[labudis]

Thank you for raising this @shaedrich! This is something our team is investigating but as far as I'm aware is not a very straightforward fix.

[zolotokrylin]

Bug: closed PR is shown as a draft PR

In issue feed:

In PR view:

[MasterInQuestion]

    Probably duplicate:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11943595
    "Closed (not merged) linked PRs show as drafts."

[labudis]

@zolotokrylin thank you for your feedback and thanks @MasterInQuestion for linking the related thread! We are aware of this issue so I will make sure to add your feedback to it.

[unitycoder]

too much spacing everywhere, trying to make a issues list takes all the space,
as in:

• ..
• ...
• ..

[labudis]

Thank you for your feedback @unitycoder!

[legoktm]

When I visit https://github.com/freedomofpress/securedrop/issues, the milestone labels are truncated to the exact point where they aren't useful, as I can't tell if it's slated for the 2.12.0 or 2.13.0 release.

Is there any reason to truncate them so short in the first place? There's definitely enough space for it, and the length is already variable based on the username.

[MasterInQuestion]

    Exact duplicate:
    https://github.com/orgs/community/discussions/139935#discussioncomment-10895208
    https://github.com/MasterInQuestion/attach/raw/main/community/community/139935/Clipmiles.webp

[verdverm]

Can you for the love of god STOP CHANGING the UI constantly!

[verdverm]

The problem is constant change, and many of them degradations. Why do you feel the need to constantly tweak the UI? (I have my hunches)

Specific example: the feed was changed years ago in favor of making it like a stupid social media algorithm, it should have been rolled back immediately based on the immense feedback from people. To this day it remains hot garbage and useless

[MasterInQuestion]

https://github.com/orgs/community/discussions/139005#discussioncomment-10842885
    “The real problem is the breakage: not rewrite.
    Nobody could really complain if nothing went wrong:
    How massive the change might be.”

[verdverm]

@labudis another specific example of really poor UX is GitHub discussion, where you hide relevant comments on threads behind a link I have to click. Show the whole conversation in discussions. It's better UX and simpler code.

[MasterInQuestion]

    Duplicate:
    https://github.com/orgs/community/discussions/148713#discussioncomment-12036073

    Out-Of-Memory for really big threads would be another problem.

[verdverm]

If OOM is really an issue for Discussions, there are more serious problems at Microsoft GitHub than I realized

There are plenty of other sites that can load far more than a long threaded discussion would ever come close to

[delucis]

The comment text areas in the new issues view is spectacularly laggy for me (and on a very high end machine, could be even worse for older computers). I’m seeing INP of up to 400ms while typing which is not really useable — an interaction as basic as typing should not have delays longer than the 16ms required for 60 FPS as a rule.

I’ll also note some other annoyances such as a less good “Quote reply” functionality. Previously, selecting a part of a comment and then “Quote reply” from the three-dots menu would only populate the text selection as a quote in your reply. Now it always includes the full comment.

[labudis]

Thanks for your feedback @delucis! I've noted these issues for our team.

[LegalizeAdulthood]

New Issue Duplicates Previous New Issue

With the new experience, if I file multiple issues in a row, the first issue shows me an empty issue title, description, labels, etc.

However, when I file a subsequent issue, it copies all the information from the previous issue I filed.

If I disable the 'new experience' for issues, then each new issue starts blank as expected.

My repository has no issue templates defined.

[labudis]

Thank you for reporting this @LegalizeAdulthood - we are aware of this bug and are already working on a fix.

[MasterInQuestion]

    Related:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11898231
    https://github.com/orgs/community/discussions/148713#discussioncomment-11921034

[RSNFreud]

Hey,

I am still not getting issue type from the action issues.labeled - Can this please get looked into?

[rileybroughten]

We have it on our backlog to add the issue type to all payload events (see this comment for a similar note). I'll provide an update when this is provided and appreciate your patience on this!

[CyrilleB79]

Hello

I am a blind user and contributor to NVDA screen reader, a free, open source software hosted and developed on GitHub by NV Access and volunteers. For a bit of context, NVDA is one of the two main screen readers used on Windows.

I'd like to provide feedback related to accessibility on the new GitHub issue experience. With the new experience, there have been improvement, but also, unfortunately also some UX degradations.

Improvements

Improved page hierarchy

The hierarchy of headings provides a much easiest way to navigate both:

• in the issue list page: with H3 for individual issues in the list and H2 or H1 for other headings
• in a specific issue page:
  • with H2 for various sections of the page and H3 for each comment
  • more specifically, the fact that Description, Activity and "Add a comment" are H2 is very nice; before, everything was under H2 "Conversation".

Hidden comments

The fact that, in pages with many comments, "x remaining items" is also an H3 heading is very appreciated: it allows me not to miss any comment when jumping between comments.

Events

The fact that events are isolated in some way, i.e. in their own region, is also appreciated since it allows me to jump between events and also clearly indicates me the boundary between various types of content, i.e. comments and events.

Drawbacks

Though, there are drawbacks that would need to be fixed. As a general feedback, I'd say that the new UX is much too verbose when pages are read with the screen reader, which is less efficient and even challenging for blind people.
To give more specific details:

Browsing comments in an issue page,

With the old UX, I used to do as follow with NVDA in browse mode:

• Press H to jump to next heading (NVDA browse mode shortcut):
  NVDA says: "CyrilleB79 visited link commented on Feb 21, 2024 heading level 3"
• Press down arrow once:
  NVDA says the beginning of my comment, e.g.: "This is the text of my comment witch is quite long..."
• Press down arrow various times:
  NVDA reads the remaining content of my comment chunk by chunk

With the new UX, I do as follows (in browse mode):

• Press H to jump to next heading (NVDA browse mode shortcut):
  NVDA says: "CyrilleB79 commented on Feb 21, 2024 heading level 3"
• Press down arrow
  NVDA says: "visited link CyrilleB79"
• Press down arrow
  NVDA says: "link on Feb 21, 2024"
• Press down arrow
  NVDA says: "Collaborator"
• Press down arrow
  NVDA says: "menu button collapsed subMenu Comment actions for comment: "This is the text of my "
• Press down arrow
  NVDA says: "menu button collapsed submenu Comment witch is quite... (truncated)""
• Press down arrow
  NVDA says the beginning of my comment, i.e.:
  NVDA says the beginning of my comment, e.g.: "clickable This is the text of my comment witch is quite long..."
• Press down arrow various times:
  NVDA reads the remaining content of my comment chunk by chunk

We can see that:

• After having pressed H I need to press much more down arrow to finally reach the interesting part, i.e. the content of the comment
• In the new UX, I can hear a lot of ducplicated information before reaching the useful content, part of it is because some items that were before the heading are now after it. It makes sense from an organization point of view, but it's quite catastrophic regarding verbosity.
• The presence of the text of the comment in the button's name is specifically very confusing; it should be removed; buttons usually have a short name and we are used to look at their position / context to know to what they apply.

Verbosity of add/remove reaction button

The button to add/remove reaction is much more verbose:

• before NVDA reported: "button collapsed subMenu Add or remove reactions"
• now NVDA reports: "Reactions toolbar clickable menu button collapsed subMenu Add or remove reactions"

Verbosity of labels

Now when reading an issue in browse mode, not only the label is reported but also the explanation of this label. Usually we only need to know the label, not to hear the description each time. If you want to provide more information, I guess that there is a way to report that an item has a detailed description (that can be reported on demand by the screen reader), but I do not exactly know how it works...

Back button of browser

In the issues list, when I press Enter to open a specific issue and just realize that I have opened the wrong issue, pressing "back" in my browser used to position me at the same position in the previous page; now, the position in the previous page is lost.

Opening an issue in a new window

In the issue list, pressing shift+Enter to open an issue in a new browser window does not work anymore, i.e. the issue opens in the second browser windows as well as in the first one.

What's the point in putting it (or maybe them in the future?) in a toolbar?

Mentioning users

The menu appearing when @mentioning some people has also become much more verbose.

Conclusion

There is probably more feedback to provide but that seems to be a starting point with the things that seem more important to me.

Note that this has been discussed a bit here in NVDA's repository.

I'd also like to mention @SaschaCowley from NV Access to participate in this discussion.

[labudis]

Hi @CyrilleB79, thanks for your detailed feedback—it’s incredibly helpful. I’m glad to hear the improvements to page hierarchy, hidden comments, and event isolation have made navigation easier.

I apologize for the increased verbosity and navigation challenges. We’ve conducted an accessibility audit and are committed to addressing the highest severity issues, including those affecting screen reader efficiency.

Your insights help us prioritize fixes, and we appreciate your advocacy. We’ll share updates as we make progress.

[kuraga]

Good day!

New Issues UI has stopped to increase the Issues (5) count at the header-tab-titles, until you fully reload the page.

(Haven't checked on pull requests.)
There was no such issue on a pull request creating. But it's a subject to check.

Is it known? Thanks.

[labudis]

@kuraga thank you for your feedback! Could you please add additional context on which views you are seeing this on. Any screenshots would be super helpful as well! Thanks in advance.

[kuraga]

@labudis , thanks for the reply! Sure.

1. I'm creating an issue at https://github.com/lazyscribe/lazyscribe:
   
2. Submit the form.
3. Expected: Issues (8).
4. Actual: .
5. Press <F5>.
6. Actual: .

There was no such issue on a pull request creating. But it's a subject to check.

[labudis]

Many thanks for the repro steps! I've raised a bug for our team to investigate.

[kuraga]

Thanks!

Ping me when needed.

P.S. There are Discussions, too.