Issues: Index, Create and Show Page Updates Public Preview

[github-staff]

GitHub Issues is evolving! 🥳

Feedback wanted

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

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

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

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

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

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

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

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

[ndren]

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

Before, font weight 600:

After, font weight 500:

[Siedlerchr]

firefox on mac os

[PatchMixolydic]

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

[david-crespo]

Same in FF on Mac and Chrome on Mac.

[LiamGallagher737]

Same on Firefox on Linux

[markerikson]

ditto, Firefox for Windows

[samlh]

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

[sunnyi101]

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

[jcready]

[sunnyi101]

@samlh @jcready how often does this happen?

[samlh]

It was reproducing around once every 5 issues I looked at - however, I was unable to reproduce today, which is a good sign.

[InAnYan]

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

[azenMatt]

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

[gameboycjp]

The search bar matching the background color is the biggest one for me.

[sunnyi101]

@gameboycjp curious about your feedback, do you feel the search bar isn't highlighted enough in the new UI?

[gameboycjp]

@sunnyi101 Yeah. Maybe my eyes are bad, but it looks like the inside of the search box is the same color as the background.

[markerikson]

Yeah, this input box definitely needs a different background color:

[InAnYan]

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

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

[kbdharun]

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

New edits UI:

Old edits UI:

---

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

[peterloveland]

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

[bohdan-shulha]

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

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

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

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

[sunnyi101]

Thank you for the feedback!

[egorikftp]

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

the same layout on mobile looks correct:

[Lamparter]

What's broken on mobile?

[peterloveland]

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

[egorikftp]

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

[egorikftp]

I find out that the reason of this issue is this plugin 🙁

https://chromewebstore.google.com/detail/github-emoji/ecldoejhjmekemajgjjalfgkhgmfjgcl

[giordano]

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

[azenMatt]

Good spot - we will add this back

[giordano]

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

[boehs]

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

[azenMatt]

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

[jasperroel]

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

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

[nebkat]

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

[azenMatt]

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

[jasperroel]

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

That would be definitely be nice!

[xlenstra]

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

[sunnyi101]

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

[nakoyasha]

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

[azenMatt]

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

[nakoyasha]

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

[xlenstra]

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

[azenMatt]

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

[azenMatt]

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

[nakoyasha]

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

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

[sunnyi101]

Thank you for the feedback!

[zopsicle]

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

[azenMatt]

Good spot - we will get that fixed

[DavidVentura]

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

[azenMatt]

Thanks for sharing @DavidVentura - we will take a look

[evi-liu]

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

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

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

[DavidVentura]

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

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

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

[oliviertassinari]

When importing images, the size is no longer set correctly, e.g.

Import in GitHub discussion: ✅

Import in new GitHub issues: ❌

[sunnyi101]

@oliviertassinari let me check on that!
Yes, I am part of Github :). You should see the 'Staff' tag beside my name

[sunnyi101]

@oliviertassinari could you check now and let me know!

[jieyouxu]

FYI @sunnyi101 for me it does not show the badge on your profile's hover card or full profile page.

[oliviertassinari]

@sunnyi101 Thanks, this is now disabled. We will try to enable it back once we see most of the bugs that we care about are fixed 👍

[alondahari]

@oliviertassinari could you elaborate on the issue you saw above, about the image size? I can't see the image you attached. A link to the discussion / issue would also be helpful. Thanks!

[htekdev]

The main one i would really like to see fixed is the when a linked pull request is merged it closes the issue if the title of the pr follows some criteria. Most cases pull requests are just 1 part of the solution or if there are multiple pull requests in multiple repos or if after pull request being merged confirmation is required before closing the issue.

Having the issue linked is nice since from the issue we can create a branch in a repo then start working on something automatically linking pull request to issue... but the closing of issue is the main issue.

[sunnyi101]

@htekdev Thank you for the feedback! We will look into this. In the meantime, you could add sub-issues to the main issue and link the PRs to those sub-issues. When the PR is merged, it will only close the sub-issue and not the main issue. Let us know if that helps

[rugk]

UX: It's bad search shortcuts have been removed

I totally miss the "quick select" options that were there before. You could click on a dropdown on the left and choose "issues opened by you" (or similar). Literally, this is mostly the only option I have used the search bar there for. Like 80% of the time I likely want to (re-)find an open issue by my to check it's state, check for replies etc. (And yeah I cannot filter per repo in the notifications like that.) or e.g. to add new information I have found/debugged etc., when I don't know the title or so.
Long after that, "issues involving you" probably follow, for similar reasons. There no shortcut was there, but I would like it.

It was very convenient and easy (two clicks -> dropdown & clicking on the button). For the same process I now need to:

1. Click into the search bar.
2. Enter "a" at least. (Also note you need to know this.)
3. Click on "author:" (or write it I guess)
4. Click on "Me":
   

These are 3 clicks and one keypress at minimum to achieve the same repeating thing that previously was just two clicks away. I don't like this at all.
After all advanced search fine, but I mostly don't use or need any "advanced" features, I mostly just use plain old simple filtering and these should be as simple as before.

---

Copied from https://github.com/orgs/community/discussions/139934#discussioncomment-10851373 as probably more people notice it here.

[jcready]

Please use full width of the page on mobile. In general it feels like the density of the data has dropped.

New:

Old:

[cynecx]

Please don't omit the issue author on mobile view:

[giordano]

Why the issue number, in the issue page, is a clickable link...to the same page? Can the link be removed, please? It makes copying the issue number needlessly complicated, as you need to be careful not to click on the self-link.

[jieyouxu]

New issue description diffs are really hard to read/follow:

Old-style description diff (of a PR description):

• Diff background colors have good contrast with text color.
• Semantically meaningful line-wise diffs.

New issue description diff:

• The contrast is too low, making it really hard to read the actual text.
• Word-wise diffs.

[OrbisK]

Markdown Alerts are broken with the "new modal version":

Before: https://github.com/OrbisK/ui/issues/new/choose

Now: https://github.com/nuxt/ui/issues

[oliviertassinari]

Duplicate of the reported above, no?

[OrbisK]

yes. duplicate of https://github.com/orgs/community/discussions/139935#discussioncomment-10837858

[mykaul]

This seems to have broken the wide github chrome plugin (https://chromewebstore.google.com/detail/wide-github/kaalofacklcidaampbokdplbklpeldpj ) .
I honestly don't understand why GH doesn't use the full screen space available in wide monitors (am I the only one not working on a laptop only screen?), but it's worth mentioning.
There's an issue on the plugin's repo as well.

[Lamparter]

Isn't it already as wide as it can in the new folder structure view?

Maybe I don't have a wide enough monitor to reproduce

[Josh65-2201]

Please make the saved replies prompt bigger, Right now it feels so cramped and often scrolling can miss replies in the list

[Josh65-2201]

Labels cut off even when there lots of space to show the full text

[Lamparter]

Ooh that's annoying

[philfreo]

I wish I could "convert" a Label to a Type.

Right now I have to:

• Head to a URL like https://github.com/ORG/REPO/issues?q=is%3Aissue%20state%3Aopen%20label%3Afeature%20-type%3AFeature%20 on each repo
• Bulk assign hundreds of issues to the Type in batches of 25 from that page (can't do All at once)
• Delete the label
• Hope that any GitHub Project board views don't break / have to remake those project views with Type in the query for each of those

[Lamparter]

I'm sure someone's already written a script to do this 😅

[Lamparter]

Meanwhile I'd just bulk select and rename. I'm sure GitHub will come up with a solution for this soon.

[0x5bfa]

When you select one from this flyout and the item has spaces inside, the search query is messed up (fig. 1 and 2).
This is not the case when you click the one from one of issues added to this type (fig. 3 and 4).

Fig 1	Fig 2	Fig 3	Fig 4

[ThiloteE]

When linking a pull-request to an issue, then the link to the pull-request in the issue now looks very bland.

Before:

After:

The bright green (for open) and red (for closed) colour at the right side of the screen was something that gave a very unique charm to Issues. The colours and the symbol were explained by "open" and "closed". Now we have a symbol and have to teach new users of github what it means or follow the link to find out, which is a second step. Also, it was very easy to discern pull-requests in the middle of comments and wall of text and with the bright and large box, users would immediately be drawn to it and intuitively know that it is something important. Maybe also, because the font size was slightly larger. With the new UI, a linked PR is less prominent.

Note:

https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue.

Example:

• ✅ Fix #xyz links pull-request to issue. Merging the PR will close the Issue.
• ✅ Fix https://github.com/JabRef/jabref/issues/xyz links pull-request to issue. Merging the PR will close the Issue.
• ✅ Fix https://github.com/Koppor/jabref/issues/xyz links pull-request to issue. Merging the PR will close the Issue.
• ❌ Fix [#xyz](https://github.com/JabRef/jabref/issues/xyz) links pull-request to issue. Merging the PR will NOT close the Issue.

[misode]

Changing a milestone is now listed on two lines, whereas before it would be collaped to one line.

Expected:

Misode changed the milestone from Release 4.2.0 to Release 4.3.0 on Jul 9

Observed: