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

[ricard9dl]

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

[jenniyuslauw]

good feedback

[kanahamppari]

What are the benefits of not having to pick a template when creating an issue?

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

[MasterInQuestion]

    Partly, as the desperate move to workaround the desperation: [1]
    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
[ [1]
    Potential workaround:
    https://github.com/orgs/community/discussions/148713#discussioncomment-11880911 ]

    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 🙃

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

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

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

[labudis]

@jfrost-mo I just wanted to check if you are still experiencing the issue with the title text area being very small?

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

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

[AceCoderLaura]

The "types" feature half-duplicate labels, in that they're a replacement for bug/feature labels but only on issues. I can't remove my bug/feature labels because they're still used for PRs. So this feature is pretty much useless and creates a SSOT problem.

[labudis]

Thanks for flagging your use case @AceCoderLaura. We do strive to drive consistency between Issues and PRs so I will make sure to pass this feedback on to the relevant team.

[zolotokrylin]

The evolution of this Github issue is not well thought through in the release.
IMHO, more concepts were introduced, making the product more complex and less coherent.

It would be better if the speed and reactivity of a page load were increased.

[MasterInQuestion]

    In my more extreme experiments somehow I don't even need labels...
    All can be just represented in title.
    https://forum.vivaldi.net/post/802910

[thewilkybarkid]

I like that the list of commits linked to an issue is more compact, but it no longer has the build status icon. We commit to main regularly and use the issue to group them and keep track of builds. We can still do the former, but the latter isn't possible.

[zolotokrylin]

Not having the status discourages me from using the new version as well.

[nordicjm]

Upon creating an issue, tried to assign it to 3 people that are members of the project, first was added fine, the other 2 (I searched up 3) did not appear in the list at all. After creating the issue, I was then able to find them in the list and add them to the issue

[labudis]

Thanks for raising this @nordicjm - raised a bug for our team to investigate.

[itkfm]

Avatars next to messages are no longer clickable.
Hovering them no longer shows an infobox pop-up.

Well, except for one – your own one next to the “Add a comment” box:

[boazreicher]

Hi @itkfm , thanks for reporting. We are aware of this issue, and are currently working to address it.

[zolotokrylin]

The original timeline feed is much better, especially for understanding how issues are interlinked. How the new feed is displayed makes it much harder to determine which interlinked issues are closed and which are open.

[labudis]

Thank you for your feedback @zolotokrylin - will make sure to pass this on to our team.

[Falke-Design]

My old ISSUE_TEMPLATE.md is not applied anymore. Is this a breaking change or a bug? If it is intended please notify in the docs about it too: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository

[labudis]

@Falke-Design Thanks for flagging this. The new issues experience does no longer support the old ISSUE_TEAMPLATE.md files and this feature will be fully deprecated when this functionality reaches General Availability later this year. We will be updating the documentation as well.

I wrote more about this in an earlier comment:
https://github.com/orgs/community/discussions/148713?sort=old#discussioncomment-11831926

[simon-abbott]

When gathering before-and-after screenshots for some other feedback I noticed that the "owner" badge on the issue isn't present in the new design. Is that intentional?

Old:

New:

---

EDIT: To be transparent I have not checked whether or not other badges (member, contributor, etc) have the same issue.
EDIT 2: Here is a link to the issue in the screenshot in case it helps: simon-abbott/testing#3

[alondahari]

@simon-abbott Thank you for the report, I logged your comment for the team 👍🏼

[TheDestroyerKSP]

Strange behavior I've noticed from subissue templates, not sure if it's intentional? It seems like after you use a template, the details entered will persist into the next time you use it.

I use a couple templates in the YAML format.

1. Create a subissue using the template, fill in the info and submit it
2. Make a new subissue using the same template, even on a separate issue.

It's a bit annoying to have a template and having to clear it each time to submit a new one?

Example behavior:
https://github.com/user-attachments/assets/22377881-4237-490b-88ae-55b2c43b90ab

Desired behavior: template should reset when creating a new subissue.

This persists in just regular issues too, not sure if intentional, a bug, or something I need to configure somewhere.

[alondahari]

@TheDestroyerKSP Thank you for bringing this up, we'll look into it!

[janbrasna]

Can't tell if that's related to the timeline preview, but was getting these yesterday and today:

[susanwere]

Hi @janbrasna , thanks for the feedback.

For the Timeline cannot be loaded error? Does this occur consistently on a specif issue? Could you also please share the reproduction steps? Thanks.

[borbware]

If there's a non-checkbox bullet point in a task list, you cannot reorder tasks any more by dragging them with the mouse.

Can be reordered:

• to do 1
• to do 2
• to do 3
• to do 4

Cannot be reordered:

• to do 1
• to do 2
• to do 3
• [skip] to do 4

(Hmm, maybe this page uses the old UI because here it still CAN be reordered....)

Anyway, I need this feature, because sometimes a task in the list is not relevant anymore, so I just write something else than "x" in the checkbox to leave a note that this was in the to do list but wasn't implemented. (Kind of like "closed as not planned" issue).

That gives me two feature ideas, actually...

1. it would be nice to be able to reorder normal bullet point lists as well
2. it would be nice to be able to right click a task in the task list to strike it through!

[shaedrich]

wouldn't it be better to write something like

- [ ] to do 1
- [ ] to do 2
- [ ] to do 3
- ~~[ ] to do 4~~

where the last entry would render with intermediate property set to true and greyed out or something similar?

[borbware]

Yeah, this looks good! (Additionally, i would like to have it in the UI as well so I wouldn't have to open the edit mode just for this.)

[susanwere]

Thank you for the feedback @borbware. Will pass this on to the team.

[borbware]

1. Number of tasks done (for example, 8/93 tasks) is no more visible in the issue header.

2. Also, for some reason, you can't see anymore all the issues an issue is tracked by:
   

[susanwere]

Thanks again for the feedback @borbware 🚀. Will pass this on to the team too.

[simon-abbott]

Just found a bug in the new issue editor. If you press enter in the middle of a list to add a new entry it starts to katamari the rest of the message.

github_input_bug.mov

[susanwere]

Thank you for the feedback @simon-abbott. Will pass this on to the team.

[molanostephane]

Hi,

The issue search on a repository has become irrelevant (feels like a regression), since when i type something it searches on the whole github issues(instead of issues of the repo) 😅 (see video)
Capture vidéo du 22-01-2025 17:43:36.webm

I use search in issues of a repo in order to find related issues or PR with keywords matching my term. If i have to add filters to properly search on the repo only it's adding extra steps to a single step action.

So i decided to disable t for now :)

[rileybroughten]

Thank you for raising this @molanostephane. If you could provide some more details so the team can look into this that would be great!

• Are you seeing issues returned that do not belong in the repository you are searching from (I couldn't tell whether that was the case from the attached video)? Searching from a repository issues list only returns issues from that repository, as adding a repo:<repo> search term does not impact results.
• As you have opted out of the experience, are you seeing different search results with the same filter compared to this new experience? If you could provide any screenshots or videos of before vs after, or links, that would be helpful so we can investigate any differences you may be seeing.

[dritchie-nsitech]

Hello,

I had a user report to me that whenever he submits a new issue using our templates and goes back to enter another issue, the text from the previous submission is being retained. This was not happening in the version prior to this preview. I had him revert back and he confirmed that it went back to working.

Before I realized we could turn off the preview, the only way to go back to it working properly was to open each 'new issue' in a new tab.
I was able to confirm that even if I cancelled out of an issue submission, if I left and returned later in the day, my text was still cached in that scenario as well.

I had reported this to GitHub support and they redirected me here.

Please, fix this problem before these previews become the 'live' version.

Thanks!

[labudis]

Thanks @dritchie-nsitech, we are aware of this issue and are prioritising a fix soon.

[edorphy]

I don't like that commits don't show the checkmark or x next to it in the new issue experience. I don't want to have to look at a commit to see it displayed there. There is significant value in 'at a glance'.