Evolving GitHub Issues - Public Preview #148713

github-staff · 2025-01-08T10:21:07Z

github-staff
Jan 8, 2025

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:

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 · 2025-01-13T13:14:16Z

mcanouil
Jan 13, 2025

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!")
        ```
        
        ![An image]({{< placeholder 600 400 >}}){#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!")
            ```
            
            ![An image]({{< placeholder 600 400 >}}){#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

3 replies

boazreicher Jan 13, 2025

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

boazreicher Jan 15, 2025

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

mcanouil Jan 15, 2025

Thanks, it works!

karlhorky · 2025-01-14T10:24:47Z

karlhorky
Jan 14, 2025

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:

Use a browser that supports linking to text fragments (eg. Google Chrome)
Visit a page with the new GitHub Issues UI (eg. Preflight Docker container with PostgreSQL database: opts.uid is NaN upleveled/preflight#588)
Select some text on the page, right click and select "Copy Link to Highlight" (see screenshot below)
Visit the example link
💥 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

2 replies

labudis Jan 14, 2025
Maintainer

@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 Jan 17, 2025

good feedback!

MichaReiser · 2025-01-14T13:35:31Z

MichaReiser
Jan 14, 2025

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

6 replies

MichaReiser Jan 14, 2025

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

ricard9dl Jan 17, 2025

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

jenniyuslauw Jan 17, 2025

good feedback

boazreicher Jan 21, 2025

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 Jan 21, 2025

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

janbrasna · 2025-01-14T14:14:18Z

janbrasna
Jan 14, 2025

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;)

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

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

5 replies

labudis Jan 14, 2025
Maintainer

@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 Jan 14, 2025

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 Jan 19, 2025

good feedback!

gabrieldigger Jan 20, 2025

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

janbrasna Jan 20, 2025

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 · 2025-01-14T21:05:27Z

dirkf
Jan 14, 2025

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.

10 replies

MasterInQuestion Jan 17, 2025

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 Jan 17, 2025

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 Jan 21, 2025

@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 Jan 21, 2025

"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 Jan 21, 2025

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 · 2025-01-14T21:49:45Z

ichard26
Jan 14, 2025

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

4 replies

ohiosveryown Jan 14, 2025

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 Jan 17, 2025

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

stosic Jan 23, 2025

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 Jan 23, 2025

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 · 2025-01-14T22:03:32Z

janbrasna
Jan 14, 2025

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

3 replies

ohiosveryown Jan 14, 2025

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 Jan 14, 2025

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 Jan 17, 2025

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

janbrasna · 2025-01-15T10:54:04Z

janbrasna
Jan 15, 2025

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:

2 replies

akenneth Jan 15, 2025

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

MasterInQuestion Jan 17, 2025

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

Matters new Commits pages too.

Timmmy-nlb · 2025-01-15T14:33:51Z

Timmmy-nlb
Jan 15, 2025

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.

1 reply

alondahari Jan 15, 2025

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 · 2025-01-16T11:34:59Z

jfrost-mo
Jan 16, 2025

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.

6 replies

jfrost-mo Jan 16, 2025

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 Jan 16, 2025

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 Jan 16, 2025

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

jfrost-mo Jan 17, 2025

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 Jan 21, 2025

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

dirkf · 2025-01-16T11:58:48Z

dirkf
Jan 16, 2025

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

0 replies

jfrost-mo · 2025-01-16T11:59:47Z

jfrost-mo
Jan 16, 2025

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.

12 replies

jfrost-mo Jan 22, 2025

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 Jan 22, 2025

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 Jan 22, 2025

Relevent HTML:

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

labudis Jan 22, 2025
Maintainer

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

jfrost-mo Jan 23, 2025

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

mcanouil · 2025-01-16T12:39:25Z

mcanouil
Jan 16, 2025

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

4 replies

labudis Jan 16, 2025
Maintainer

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

mcanouil Jan 16, 2025

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 Jan 16, 2025

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 Jan 16, 2025

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 · 2025-01-16T13:07:15Z

eishiya
Jan 16, 2025

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

2 replies

labudis Jan 16, 2025
Maintainer

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 Jan 21, 2025

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 · 2025-01-16T14:33:45Z

PLTytus
Jan 16, 2025

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

2 replies

alondahari Jan 16, 2025

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

PLTytus Jan 16, 2025

It is good now. Thanks for quick fix.

beingminimal · 2025-01-24T15:52:39Z

beingminimal
Jan 24, 2025

@labudis
We need an ordering option like issue reordering in milestones in the org settings of issue types. This would allow us to reorder issue types, which is affecting all repos in the organization. Please consider adding this feature next week, as it is not a big task.

Screen.recording.2025-01-24.9.18.16.PM.webm

4 replies

labudis Jan 24, 2025
Maintainer

Thanks @beingminimal - we already have this on our board as a feature request and I've added your comments for team's visibility.

beingminimal Jan 24, 2025

@labudis any ETA?

labudis Jan 24, 2025
Maintainer

We're still working through a backlog of other higher priority items, so unfortunately I can't give you a definitive estimate. However, should this end up on our sprint board, I will let you know!

beingminimal Jan 24, 2025

ok thanks a lot for reply.

qodfathr · 2025-01-24T16:45:20Z

qodfathr
Jan 24, 2025

What's the plan for tasklists? I'm in total agreement that they are not the way to manage a hierarchy and sub-issues are far better, but having an editable list when in "view" mode to add/remove/reorder items within an issue is useful and convenient.

4 replies

evi-liu Jan 24, 2025
Maintainer

Hi @qodfathr, we’re planning to sunset tasklists and focus our investment on sub-issues as the primary hierarchy experience moving forward. To ensure a smooth transition, we’re introducing the ability to convert checklist items into sub-issues. This will maintain the flexibility of quickly creating items within issues while providing an easy way to elevate them into hierarchical sub-issues when needed.

qodfathr Jan 24, 2025

Understood and I 100% agree with that plan. My point was that, in an issue, it's nice to have a better list editor. For example, maintaining a checklist of acceptance critiera. Expressing AC as sub-issues feels like a very heavyweight solution for many projects.

Ignoring the tracks/tracked by capabilities of tasklists, using them to arrange lists of non-issue items has been, for us, a good experience which exceeds having to edit the issue wholesale, especially for quickly adding items to the list and reordering the list.

This comment was marked as off-topic.

Sign in to view

borbware Jan 29, 2025

nooo do not sunset tasklists, my whole workflow depends on them :(((

EDIT: apparently this is about a private beta feature, not markdown tasklists that I was worried about.

MasterInQuestion · 2025-01-24T21:43:38Z

MasterInQuestion
Jan 24, 2025

Empty search query ("q") behavior regression:
https://github.com/orgs/community/discussions/139935#discussioncomment-11013719
https://github.com/orgs/community/discussions/139935#discussioncomment-11587319
(unjustly shortcut to default search query now?)

Matters in particularly more, as now it seems the New Issues experience is coerced to everybody...
https://github.com/orgs/community/discussions/139935#discussioncomment-11599077
[ ^
I noted a "New Issues Experience" in "Feature preview dialog".
Currently seems not viable for logged-out access? (which is the generic view)
[ ^ Default on and associated to login cookie for customization..? ]

I suggest default disable the Preview for logged-out access.
Alike the Commits' (that disabled already).

https://github.com/orgs/community/discussions/139935#discussioncomment-10895208
“I don't think current half-broken beta can be made default:
Logged-out cannot opt-out.” ]

"why you want to opt out?"
Feels like overall regression, for one do not make use of any the added functionality.

https://github.com/orgs/community/discussions/148713#discussioncomment-11930743
“It's not about being more useful...
It's strictly about being no less useful. (no regression)”

1 reply

octatone Jan 28, 2025

Really appreciate your input about the q param handling! I’ve made sure the team is aware, and it’s now on our list to review.

rohlem · 2025-01-26T12:04:01Z

rohlem
Jan 26, 2025

For some reason while I have the "New Issues Experience" feature preview enabled, the set of newly-addable emojis is reduced from the previous 8 (still documented in the REST API) to just 5.

Example:

If a type of reaction is already there I can toggle it, but the selection when adding one seems arbitrarily limited.
Particularly I've started the habit of using ❤️ (:heart:) for quick "thank you" / "you're welcome" / appreciation, and would be bummed if I had to stop just because the web UI doesn't show the option anymore.

10 replies

rohlem Jan 28, 2025

@alondahari You are exactly right, some elements are hidden due to overflow!
Looking into this I found two things:

the relevant div with class Overlay_StyledOverlay-... containing the popup menu is assigned a CSS class kFfiTK with a rule overflow: hidden;. (Not sure if that class name is stable, or a random ID string that will regenerate differently on the next update?)
I'm not sure why that rule is there (I don't know much about UI design), but removing it makes the overflowing elements appear, which would seem like the better default in terms of accessibility.

I noticed that I can force this bug to appear by adding a CSS rule max-width: 100%; to that same Overlay_StyledOverlay-... div element. I don't know whether that hints at what you're saying about client-side calculations or not; "100%" forcing elements into overflow at least doesn't seem intuitive.

And then I noticed that such a max-width: 100%; rule is being added for me locally through a client-side CSS userstyle plugin I forgot I was even using... 🤦
So first of all I am sorry for not realizing this sooner and potentially wasting your time.
I understand that you might only have limited interest in supporting such obscure customization, so I completely understand if this immediately transforms this issue into a "wontfix".
Not hiding overflow still seems like it would be a better default to me. Maybe the 100% thing points at a miscalculation somewhere - or not, I'm no CSS expert.

Either way, thank you very much for your troubleshooting so far and helping me realize the local issue and fix!

rohlem Jan 28, 2025

For what it's worth, the max-width: 100%; width seems to come from the min-width: 192px; rule that is also attached to the same CSS class kFfiTK of the overlay's Overlay_StyledOverlay-... div element.
For me the properly-sized width is 318 pixels, so updating the rule to min-width: 318px; fixes the sizing behavior for me, even in different browser zooms and window sizes/ratios.
I don't know what the significance of 192px is though, why it was chosen, whether replacing it with 318px would be a viable solution, and how other clients react to this.

MasterInQuestion Jan 28, 2025

Essentially the same clipping spree:
https://github.com/orgs/community/discussions/139005#discussioncomment-10889895

octatone Jan 29, 2025

@rohlem can you confirm that the issue is fixed for you when you disable the custom style extension?

rohlem Jan 29, 2025

@octatone It is, however the root of the issue comes from min-width: 192px;.
To me it looks like that value is simply wrong. If you could increase that size to min-width: 318px; it would work perfectly as-is.
overflow: hidden; also seems like the wrong default to me. It's your call, but I don't see why that was chosen for this element.

NetSysFire · 2025-01-26T12:36:37Z

NetSysFire
Jan 26, 2025

Bug: It keeps appending spaces to my issue search queries. I already searched for "space" in this discussion, so I hope this is not a duplicate. This is the newest Firefox on Linux.

Steps to reproduce:

My search query is is:issue "12345"
Press enter.
Replace "12345" with anything else.
Press enter again.
Watch your browser URL bar closely, I see a %20 appended for each time you do the last two steps. You can also see the trailing whitespace by just selecting the field. I accumulated a lot of %20 in my search URL before noticing.

Unrelated thing: I hate how it hides the issue progress. When you put checklists inside issues, it used to display a little progress indicator on how many things were ticked off already. This is missing now and I do not like this at all.

1 reply

octatone Jan 28, 2025

Appreciate you bringing this up! It’s on the team’s radar now, and we’ll give it a closer look.

inferiorhumanorgans · 2025-01-26T14:57:58Z

inferiorhumanorgans
Jan 26, 2025

Make the bad man stop. I'm so, so tired of trying to engage with someone else's project only to find the Github team has stubbornly decided to enshittify ~~something~~ everything.

0 replies

nielsdos · 2025-01-26T18:33:25Z

nielsdos
Jan 26, 2025

Not showing the entire discussion upon loading an issue page, and having to click "load more" makes no sense to me. If I click on an issue I want to see the latest discussion that happened.

3 replies

TheGiraffe3 Jan 27, 2025

What issue are you seeing this with?
GitHub counts mentions by other pull requests/issues as part of the conversation, so if there have been lots of mentions the actual dialog may be hidden.

MasterInQuestion Jan 27, 2025

Essentially:
https://github.com/orgs/community/discussions/39463#discussioncomment-11293956

octatone Jan 28, 2025

We’re all ears for feature ideas—thank you! I’ve made sure the team is considering this one.

Arinono · 2025-01-27T11:31:55Z

Arinono
Jan 27, 2025

✅ Resolved

Previously we had the ability to manage the project fields from the issue itself, but not anymore (or I didn't find how yet)

Before	After

If this helps, this project/board is an organisation one (spanning multiple repositories) and issues are automatically added to it. Filtering issues in the list with this project as a filter works

10 replies

labudis Jan 27, 2025
Maintainer

Thank you all for the added context and sorry for the trouble, we identified the issue and are working on a fix. I'll keep you posted!

labudis Jan 27, 2025
Maintainer

@serge-rider @mzur @ajdubovoy @Arinono we've just pushed a fix for this. Could you please verify things are now working as normal on your end? Many thanks 🙏

ajdubovoy Jan 27, 2025

Yes, looks like it's back, thank you!

Arinono Jan 27, 2025

Looks all good! 👌

mzur Jan 27, 2025

Looks perfect. Thank you for the quick fix!

demaziej · 2025-01-28T14:56:24Z

demaziej
Jan 28, 2025

Bug : in the milestone view there is no checkbox and we can't select multiple PR at once (for example to change them to another milestone)

Also in the feature page the "feature" is labeled as for "issue" but not for milestone

3 replies

labudis Jan 28, 2025
Maintainer

@demaziej Thank you for your feedback! Would you be able to share a screenshot demonstrating the issue on the Milestone page?

Also, could you please expand on this comment here as I wasn't able to understand the underlying issue you are experiencing:

Also in the feature page the "feature" is labeled as for "issue" but not for milestone

Many thanks!

MasterInQuestion Jan 28, 2025

"Feature preview dialog" said "New Issues Experience".
But somehow affecting Milestones?

----

Thanks for explaining. But I don't use it...

labudis Jan 29, 2025
Maintainer

@MasterInQuestion Milestones is a feature that is part of the Issues scope here at GitHub.

nzwulfin · 2025-01-28T16:57:55Z

nzwulfin
Jan 28, 2025

With the new UI enabled, referencing a code block in an issue results in a blank issue instead of adding the link to the highlighted code block. Created a gif showing with the preview on and then disabled.

https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/creating-an-issue#creating-an-issue-from-code

2 replies

labudis Jan 28, 2025
Maintainer

Thanks for flagging this @nzwulfin. I will log an issue for our team to look into.

This comment was marked as off-topic.

Sign in to view

jay · 2025-01-28T19:03:00Z

jay
Jan 28, 2025

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:

1 reply

labudis Jan 28, 2025
Maintainer

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

borbware · 2025-01-30T20:04:57Z

borbware
Jan 30, 2025

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!

4 replies

MasterInQuestion Jan 30, 2025

"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 Jan 31, 2025

@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 Jan 31, 2025

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 Jan 31, 2025

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

Y-T-G · 2025-01-31T04:56:05Z

Y-T-G
Jan 31, 2025

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