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!

[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!

[kanahamppari]

good feedback

[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

[labudis]

@MichaReiser thanks for your feedback! The legacy issue template workflow has been superseded by the new issue templates about 4-5 years ago. The support for the legacy issue templates has been removed with the New issues experience and currently there is no plan to bring that back.

However, I understand the value of not having to pick a template when creating an issue, and have logged your feedback as a feature request. For completeness, are there any other benefits of the legacy issue template that you're missing?

In the meantime, I'd recommend setting up your repository with the new issue template.

[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

[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!

[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.

[ohiosveryown]

Some time ago, there was this feature to "expand all" hidden posts along the timeline on especially long issues/PRs

This is something that exists in issues, but PR's does still have the pagination / progressive load more interaction (unless I'm misunderstanding).

I definitely hear the comments that it would be a more pleasant experience to be able to filter out some of the noise, and overall to just be able to navigate a longer issue more easily. I'll relay the feedback.

[ichard26]

I know it's better form to leave a reaction (ironic, yes), but this is important to me:

I definitely hear the comments that it would be a more pleasant experience to be able to filter out some of the noise, and overall to just be able to navigate a longer issue more easily. I'll relay the feedback.

Thank you! ❤️

[janbrasna]

@ohiosveryown Thanks Matthew, appreciate it. For demonstration purposes consider e.g. this issue/announcement as an example: actions/runner-images#10636 — it's linked to from gazillion of projects, and trying to find a comment from maintainer/staff somewhere in the middle of the timeline is a pain:

[MasterInQuestion]

    Partly, as the desperate move to workaround the desperation:
    https://github.com/orgs/community/discussions/39463
    .
    This is the 3rd thread for the same topic...
    https://github.com/orgs/community/discussions/139935
    https://github.com/orgs/community/discussions/132506

    But the new paged design is not just easy.
    Several aspects (concerning the actual implementation) must be carefully considered before deployment:
    Lest causing irrevocable havoc. (permalink interoperability)

    I have conceived the basic idea roughly.
    And shall further discuss in the dedicated thread.

    ----

    "timeline spam"
    This seems to specifically only matter for Issues reference events?
    (other event types don't seem to cause alike trouble, generally)

    Probably the multiple reference events consecutive shall be default collapsed?
    Proposal:
    Display at max 3 consecutive reference events (between other events, comments) only.
    For > 3: Display 2, last entry as "Show ${Count} more references".
    Needless to collapse if it's the last event. (i.e. no other events, comments following)
[ ^
    Maybe its display also needs to have paged view?
    As it's possible to have several hundreds thousands references between... ]

[willpower232]

permalink interoperability

the "reference in new issue" link does not work with this editor for some reason, have to disable this feature preview to make it appear in the issue content 🙃

[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

[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.

[alexus37]

Hi @jfrost-mo,
thank you for reaching out and bringing this issue to our attention. We are aware of the problem, and I’ve noted your feedback regarding it. 🙏

[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

[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.

[MetRonnie]

I also get this on Windows 11 with Edge 131.0.2903.146

[labudis]

Thanks @MetRonnie, might be related to the OS, logged this bug for our team to investigate.

[MasterInQuestion]

    For alike issues, remember to rule out the possibility of client-side extensions' interference.
    (most typically, uBlock Origin alike)

    Side note:
    OS typically won't matter to such extent.
    (mostly the browser, or user extension)

[jfrost-mo]

I'm on Firefox on Windows 11 with uBlock Origin and Zotaro Connect as extension. It is instead rendering full width on my similarly configured Firefox on RHEL 9.

[MasterInQuestion]

    Both Firefox at the same version?
    Reproducible without extensions interference?
    (try in Private Browsing to rule out caching issues too)


    I noted alike issue on:
    https://github.com/MetOffice/CSET/issues/new
    .
    Seems the input box has bad preset width.
    (that requires JavaScript to later overwrite to proper width..?)

    And combined with alike script failure...
    https://github.com/orgs/community/discussions/148713#discussioncomment-11864127

[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.

[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.

[Mishasama]

After closing issue, before refreshing the page, the button for reopen is not available and it will show no permission.

[labudis]

Thanks for flagging this @Mishasama but I was not able to replicate it on my environment. Could you please share a few more details about your OS, Browser and the types of permissions you have in the repo? Many thanks.

[Mishasama]

OS, Browser and the types of permissions you have in the repo

Win 10 21H2
Edge 131.0.2903.146
Permission: Guest (No roles)

[thestelz]

One thing that I have noticed is with Assignees suggested only lists yourself for issues that have already been created, but list a lot more on new issues.

Before:

After:

[labudis]

@thestelz thanks for reporting. I was able to replicate this so will log as a bug for our team to troubleshoot.

[Kyleberth]

On the old version: If you copied bullet points and text from the issue and pasted on another platform (say zendesk or docs) that formatting would follow

On the new version: If you copy formatted text, it pastes to another platform without the formatting, and unusual amounts of spaces. Awkwardly.

Example: copied this text:

Pasted into Zendesk like this:

Previously the paste would look like this:

[ohiosveryown]

Thanks for reporting this. I'll file this one for the team.

[MasterInQuestion]

    The behavior of copying post-rendered texts alike, remains mostly undeterministic whatsoever.
    (different browsers, environments may have different (and much incompatible) handling)

[uncenter]

I don't see a way to quickly remove labels from an issue in the sidebar without going into a submenu anymore.

Previously:

Now:

I really liked the convenience of the former.

[alexus37]

Thanks for reaching out! 🚀 It looks like this functionality is provided by the extension refined-github, so it isn't part of the core GitHub experience. However, your feedback is still incredibly valuable, and I will log it as a feature request so we can prioritize it.

[RayDeeUx]

Will the "Filters" dropdown be carried over to the new Issues design?

Using repository hannibal002/SkyHanni as an example:

Original:

Preview:

[labudis]

@RayDeeUx Thanks for your feedback. Our plan is to redesign the filter experience and introduce saved filters in the sidebar. We've briefly previewed this new experience in December but due to user feedback we decided to pull it back as we make it better. Watch this space!

[janbrasna]

Adding here ^^ The only filters I use basically dozen+ times a day are some of the pre-set in the "Filters:" dropdown in the og experience. I have zero interest in typing them manually gajillion times a day now. (Currently I can still access them from the PR filter dropdown as a workaround)

[expertsleepers]

Issue creation is broken (in Safari on Sonoma, at least).

Click "New Issue". On the next page, you can't type in the subject field where it says "create new issue". It's like the keyboard focus is somewhere else, even if you click in the box.

[alondahari]

Hi @expertsleepers, sorry you're blocked by this. Could you please share more information about the issue you're experiencing?
Which organization / repository you are trying to open an issue in? is it happening in multiple repositories? could you share a video / screen shot? Thank you!

[expertsleepers]

I just realised what is actually happening is simply a matter of focus - the focus is on non-editable text, instead of on the subject line. See recording:

Screen.Recording.2025-01-17.at.09.16.32.mov

This is in my own private repo.

[alondahari]

@expertsleepers thanks again for the report and the recording, super helpful! We are aware of this issue and I'll add your report 🙏🏼

[Timmmy-nlb]

Issue creation is broken - With click of "new issue" it shows only a empty fame below the menu.

If you deactivate the "New Issue Experience" preview, the issue overview is displayed again.
The problem is that the error only occurs if you are NOT a member of the organization.
If you are a member, everything looks fine.

[Timmmy-nlb]

With click on menu "issues" I see a empty frame:

If I deactivate the feature:

after this I see it "normal":

[Timmmy-nlb]

If I'am a member of this Org - the problem does not occur.

[alondahari]

@Timmmy-nlb thanks for the added context! I found the error you hit, we'll take a look at that asap 🙏🏼

[alondahari]

Did you say it's only happening once you click on the "New issue" button, or when you initially navigate to the Issues tab?

[Timmmy-nlb]

Sorry, my misstake.
If you click on "issue" in the menu - not "new issue", because you don't see it at this moment.

[dirtyhenry]

Congrats on the feature!

Checkboxes in a main issue body could be more responsive in the new UI. It seems much slower than before. 🙏

Narrated.2025-01-17.12.19.mp4

[antoniomatheus]

Also, the task counter has been removed from the interface :(

[alexus37]

Thank you both for reporting this. I'll file this one for the team. 🙏

[egor83]

@antoniomatheus I also miss the task counter, and created an issue about it: #149409. You might want to upvote it for better visibility.

[tonytamavm]

is the preview available on github enterprise server local install?

[alexus37]

Hello @tonytamavm, thank you for your inquiry. The preview feature is currently unavailable on GitHub Enterprise Server local installations; however, we are actively working to make it accessible for local setups.

[KaelWD]

Can you get rid of this dropdown? Just having three close buttons like refined github used to do barely takes up any more space.

Sort by reactions being a submenu is annoying too, what do you guys have against making frequently used options visible without extra clicks?

[alexus37]

Thanks for the feedback 🥇 I will forward it to our designers :)

[mishaturnbull]

Hi there -- I like 95% of this feature, including sub-issues, but I seem to be missing issue label colors in some places:

If I disable this feature and refresh the page:

Under the preview, the label colors do show up if I go to the filter-by-label drop-down. However, I see the same issue if I click on an issue (the colors don't show up).

I thought at first this may have been from the colorblind theme preview (which I don't remember enabling, but was), so I turned that off to be sure; but it had no effect.

Thanks!!

[0xWDG]

I have 2 big issues with it.

1. I cannot assign multiple people from the issue list.
2. I need to constantly reload the page if I want to edit a issue.

[ogoffart]

We would like to request a way to de-emphasize the "blank" issue template in the new issue interface.

Blank issues can be helpful for team members who know how to add labels, but we'd prefer that users select one of our bug or feature request templates. These templates automatically set the appropriate labels, helping maintain consistency.

Before:

In the previous interface, the "Blank Issue" was a small link, and most users didn't notice it. Only those familiar with the process were using it.

Now

Now, the "Blank Issue" is prominently displayed in the middle, and we’ve already had users selecting it instead of the proper templates.

---

Is there a way to configure the order of the issue templates or customize the label/description for the "Blank Issue" to make it less prominent?
Or is it possible to limit the "Blank Issue" option to collaborators only?

And by the way, can we set the "Issue Type" from within the issue template?

For reference, our repository is https://github.com/slint-ui/slint

Thank you

[distantnative]

Projects still shows up in the sidebar, while the feature is disabled for the whole org an no projects are available.

We would expect that UI part do be hidden in this case, not cluttering up the UI more without any use (since the actual feature is disabled).

[zkrising]

This change is giving me massive issues with load times and navigation state not working. Sometimes now, the back button to go off the "new issue" page does nothing. Frequently the search bar does nothing. It changes the URL but nothing actually changes.

Clicking on individual issues or PRs sometimes loads forever. The only reliable way I've found to open issues and PRs at the moment is to right click->open in new tab. There is something seriously broken with how your rewrite deals with page navigation -- I am using vanilla firefox and I have never had any issues like this before. I assume this is related to this preview.

[zkrising]

Here's a video of the kind of issues I'm getting: https://streamable.com/tnot90

This renders the entire PR and Issues view completely unusable.

[zkrising]

Console is full of "Too many calls to Location or History APIs within a short timeframe.", so it's likely that. Maybe some sort of debouncing you're doing doesn't work in firefox or something. Either way it's pretty frustrating to have such a major part of github break on firefox!

[Noobyguy775]

Same thing here, also on firefox, I also noticed that the progress bar on the top is just infinitely scaling sometimes, if that's helpful.

I just accidentally reloaded this page, and had to navigate back to here from the main discussions page. And I had to click on the link to go to this discussion 3 times 🔨

[Noobyguy775]

It looks like this will only happen when there's data in the url. Removing ?q=is:issue state:open allows me to open anything