GitHub Community
Evolving GitHub Issues - Public Preview #148713
Replies: 139 comments 392 replies
-
|
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.
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)
Original issue template for the screenshots: https://github.com/quarto-dev/quarto-cli/blob/main/.github/ISSUE_TEMPLATE/bug_report.yml |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for reporting this. We can reproduce the issue, and are currently looking into it. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @mcanouil, we've rolled out the fix for this. Please let us know if you still encounter any issue. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, it works! |
Beta Was this translation helpful? Give feedback.
-
|
@mcanouil Just wanted to update you that we have addressed one of your feedback items related to the display of the Issue Template. Now, you will see the chosen template in the Issue Creator and even have the option to change it while creating the issue, in case you change your mind. Please let me know if it works as expected :) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks, that's great. 
|
Beta Was this translation helpful? Give feedback.
-
|
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:
Expected (old GitHub Issues UI)Example link: Correct scroll position, highlighted "provide sample image(s)" text:
Actual (new GitHub Issues UI)Example link: Incorrect scroll position, no highlighted text:
Also, copying the comment on my discussion thread by @MasterInQuestion:
|
Beta Was this translation helpful? Give feedback.
-
|
@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! |
Beta Was this translation helpful? Give feedback.
-
|
good feedback! |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
good feedback |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Oh nice. Thank you! We'll give it a try. |
Beta Was this translation helpful? Give feedback.
-
|
@boazreicher This feature has now regressed with the new "modal". It now always shows a modal even if there's only one issue template. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting @MichaReiser, we'll take another look at this. |
Beta Was this translation helpful? Give feedback.
-
|
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;)
|
Beta Was this translation helpful? Give feedback.
-
|
@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. |
Beta Was this translation helpful? Give feedback.
-
|
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!
Great job with those major features, hat tip! |
Beta Was this translation helpful? Give feedback.
-
|
good feedback! |
Beta Was this translation helpful? Give feedback.
-
|
What specific improvements does the user suggest for better clarity in announcements or feedback threads? |
Beta Was this translation helpful? Give feedback.
-
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…) |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
"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
|
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
cc @akenneth in case the above got lost in the noise, this flow is still totally broken. Thanks for your efforts & triaging! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Thanks @MasterInQuestion, glad it's fixed! |
Beta Was this translation helpful? Give feedback.
-
|
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 commentsNew: 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 timelineThis 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
Shown issue: pypa/pip#13165 |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Are there any additional pieces of information you believe should be included in the timeline or sticky header to make the interface more useful? |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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.) |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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! |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
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:
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the feedback @janbrasna! We are aware of this issue and I’ve logged your feedback against it. |
Beta Was this translation helpful? Give feedback.
This comment was marked as off-topic.
This comment was marked as off-topic.
-
|
Hello, And "we" are many and do not need to be moulded: |
Beta Was this translation helpful? Give feedback.
-
|
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. 🙏🏼 |
Beta Was this translation helpful? Give feedback.
-
|
THANK YOU - It works now!!! |
Beta Was this translation helpful? Give feedback.
-
Issues list flashes after loadingWhen loading the issue list or changing pages the list of issues flashes momentarily shortly after loading. See the following video: output.mp4I'm using a vertical 2560x1440 display with Firefox 134.0.1 on Windows 11. |
Beta Was this translation helpful? Give feedback.
-
|
Another minor issue that this video shows is the page title changes many times on a page load going through:
With the last being the one it settles on, and the useful one. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
@jfrost-mo This should now be fixed, could you verify? thanks again for bringing this to our attention! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
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 |
Beta Was this translation helpful? Give feedback.
-
|
@jfrost-mo Thanks for the report, I added it to our backlog and we'll take a look at that 💯 |
Beta Was this translation helpful? Give feedback.
-
|
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). |
Beta Was this translation helpful? Give feedback.
-
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. |
Beta Was this translation helpful? Give feedback.
-
|
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: |
Beta Was this translation helpful? Give feedback.
-
|
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.
My CPU/GPU is an 11th Gen Intel(R) Core(TM) i5-1145G7 |
Beta Was this translation helpful? Give feedback.
-
|
Relevent HTML: Compared with a working bar editing an existing image, this one is missing the |
Beta Was this translation helpful? Give feedback.
-
|
thank you for the additional info @jfrost-mo - passed this on to the team investigating this. |
Beta Was this translation helpful? Give feedback.
-
|
This appears to be fixed today. I've tested in Firefox and Edge, after various page refreshes, and with and without a template. |
Beta Was this translation helpful? Give feedback.
-
|
Could sub-issues inherit from the parent labels by default? |
Beta Was this translation helpful? Give feedback.
-
|
@mcanouil thanks for the suggestion! Would you mind sharing an example of how you would use this? |
Beta Was this translation helpful? Give feedback.
-
|
For example, in some repositories my client has a workflow based on labels: priority, difficulty, type (bug, enhancement, etc.), component (codebase, analysis, etc.). 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. |
Beta Was this translation helpful? Give feedback.
-
|
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? |
Beta Was this translation helpful? Give feedback.
-
|
Mostly labels. To summarise in a concise way:
|
Beta Was this translation helpful? Give feedback.
-
|
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)
|
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
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. |
Beta Was this translation helpful? Give feedback.
-
|
Looks like some issues are hidden with default filters on this preview. |
Beta Was this translation helpful? Give feedback.
-
|
@PLTytus thanks for reporting! should be fixed now ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
It is good now. Thanks for quick fix. |
Beta Was this translation helpful? Give feedback.
-
|
My $0.02: I don't like the new very minimal UI. The rich text box etc. looked nicer. Maybe I'm too old and grumpy with change bit yeah. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for your feedback! Has the new UI affected the system’s usability for you in any way? |
Beta Was this translation helpful? Give feedback.
-
|
Not too keen on the new issue creation experience. The creation window is too small. We use templates for different issues, and when I select a template and make the creation window full-screen, the template reverts to the default, so I have to choose the template again. It now takes 5 clicks to accomplish what I used to be able to do in 2. |
Beta Was this translation helpful? Give feedback.
-
|
Hi @pva-dspinner, thanks for reporting! This does look like unintended behavior (template selected should persist). |
Beta Was this translation helpful? Give feedback.
-
|
I'm happy to say that we have now fixed the issue where going from modal to full-screen was not retaining the progress. Now the transition should be seamless. |
Beta Was this translation helpful? Give feedback.
-
|
We have some problems with this new issue experience. Our issue template includes a drop down with a list of plugins (100+). The first problem is that with this new modal view it is not possible to scroll down. So it is impossible to select later items of the list. The second problem is that if you switch to the fullscreen view it switches back to an empty template instead of keeping the same template as in the modal. The third issue was already present before this issue changes were made. It is not possible to pass a value to a Drop down with a link. |
Beta Was this translation helpful? Give feedback.
-
|
That makes sense. I will log this as a feature request, as I can see how it could be useful to other users as well. If you have any screenshots illustrating the types of data you would prefill and are comfortable sharing them publicly, that would be great. |
Beta Was this translation helpful? Give feedback.
-
|
I'm sorry but I don't really have anything to show as this is only a plan that hasn't been implemented yet. So an example link would be And also a way for drop downs which is not yet supported. For example a |
Beta Was this translation helpful? Give feedback.
-
|
I'm happy to say that we have now fixed the issue where going from modal to full-screen was not retaining the progress. Now the transition should be seamless. |
Beta Was this translation helpful? Give feedback.
-
|
I just checked and it does indeed retain the state if it is based on a template. However if you write something into a blank issue the state is lost again. |
Beta Was this translation helpful? Give feedback.
-
|
@CD-Z this has now been fixed for the blank issues as well. Let me know if it all works as expected now. |
Beta Was this translation helpful? Give feedback.
-
|
I really don't like the new modal bug report (flow is new issue -> select template -> now a small modal) and feel like this is a significant UI/UX regression over the previous issue reporting design where after selecting an issue template it opens in its own proper issue page. I find it very important that design first-and-foremost needs to be functional! I'll list my pain points with this design in the following:
UPD: someone kindly pointed out to me there is a "fullscreen" button in the top-right corner of the modal dialogue menu bar.
Can we please just not have this secondary modal dialogue thing, and just use the proper fullscreen issue creation page? My apologies if this sounds like a rant (it kinda is), because I find it very frustrating to use (whereas I had no significant complaints for the old issue creation page). UPD 2: someone else also kindly pointed out to me that the fullscreen button doesn't keep the contents of the textfield of the modal dialogue if you have already written something and just deletes all your content. |
Beta Was this translation helpful? Give feedback.
-
|
@labudis If the GH team really wants this dialog, please add a setting that users can toggle under their profile to always skip the dialog. I encountered issues with the modal where accidentally hitting ESC or clicking off wiped everything, which isn't fun 😅 |
Beta Was this translation helpful? Give feedback.
-
|
I'm happy to say that we have now fixed the issue where going from modal to full-screen was not retaining the progress. Now the transition should be seamless. |
Beta Was this translation helpful? Give feedback.
-
@labudis I can confirm for me at least the transition preserves (1) the issue template type and (2) the already-entered content for said template, so thanks to the team for fixing that. However, can there please be a setting that just disables the secondary modal dialogue and always use the full-screen page? I never want to use the tiny modal dialogue with a bunch of other issues distracting in the background, and it's actively penalizing me trying to write a proper bug report with good context and reproduction steps. |
Beta Was this translation helpful? Give feedback.
-
|
This has now been fixed for blank issues as well. Thank you for your patience. I also take your feedback on board regarding showing the modal vs full page. It will undoubtedly inform how we develop this product further. |
Beta Was this translation helpful? Give feedback.
-
|
+1 on the feedback here. It's unclear to me what is gained by having the small modal dialog. Users are never going to be copying from the background of that page, so this only serves to restrict the amount they can see on screen. Furthermore, the presence of nested vertical scrollbars (as seen in the screenshot above) is a strong indication of a problematic UX. (Granted, it's not always avoidable, but it absolutely is here as demonstrated by the previous full-page design.) |
Beta Was this translation helpful? Give feedback.
-
|
Not sure if related to the new GitHub Issues, but it seems for issues and comments created by GoogleCodeExporter GitHub is not working properly:
Not sure if other (bot) accounts are affected as well. See https://github.com/orgs/community/discussions/150115. Would be great if someone could take a look at this. |
Beta Was this translation helpful? Give feedback.
-
|
Thank you for raising this - our team will investigate. |
Beta Was this translation helpful? Give feedback.
-
|
The UI allows clicking on "Ghost" users to add them to the filtering, but filtering by ghost users doesn't work. To be fair, filtering by ghost users wasn't possible before either, but hopefully it can be added as part of the new issues filtering? Clicking on this: Leads to this: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks - logged this for our team to look into! |
Beta Was this translation helpful? Give feedback.
-
|
Feedback: There was a change associated with this that changed the default action when you 'add new item' in a Github Project.
Old Behavior: Type content. Hit enter. It creates a new card in the selected column. Some folks use Projects as their way of tracking work they have done/need to do. Issues are not necessary for those folks and this is unnecessary UX annoyance.
In short: Please add some settings so users aren't just dragged towards features they don't & won't use. It's just shoddy product work. |
Beta Was this translation helpful? Give feedback.
-
|
When creating a checklist in one issue, I still want the tasks to be displayed like in the old behaviour. The new behaviour removes this task thing for check list items. If anything an issue should be complete when both sub-issues and checklist items are completed. |
Beta Was this translation helpful? Give feedback.
-
|
I'm curious about this one. Which use cases are you using checklists instead of sub-issues to denote roll-up work? |
Beta Was this translation helpful? Give feedback.
-
|
@evi-liu We have templates for different types of work, that mostly include checklist trailers, that ack something's achieved — not a thing that would make sense as a sub issue. Think: ### One line summary
### Description
### Success criteria
- [ ] Consumption lowered
- [ ] No hard feelings
- [ ] Profit!or some ops may use: ### Signed off by
- [ ] Clown dept.
- [ ] Balloon ops
- [ ] Pepperoni resourcesthat all benefit from %% completion percentage shown in issue overview/list or summary header. |
Beta Was this translation helpful? Give feedback.
-
|
New Issue Experience not shows the action status of commits. It would be better if adding it back. Disabled preview
Enabled preview
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks - I logged your feedback for the team! |
Beta Was this translation helpful? Give feedback.
-
|
Seems like the new UI doesn't respect the issue_template config. In our case blank issues should be disabled and only links to external issue tracker are provided instead. With the new design enabled, users can open blank issues without anything stopping them, links to external resources never show up as they were before |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @gribnoysup - we are aware of this issue and are working on a fix. |
Beta Was this translation helpful? Give feedback.
-
|
Hello all, I reported this bug via Support, they confirmed they can reproduce it, and said to report it here instead. Description My repositories have a single issue template configured which previously showed up in the description field of a new issue automatically: https://github.com/DavidAnson/markdownlint/blob/main/.github/issue_template.md Documentation for this feature is here: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/manually-creating-a-single-issue-template-for-your-repository The behavior should be (used to be) that opening an issue in this repository did not prompt for a template and automatically inserted the content of the template into the description of the new issue. (The template above is a large HTML comment to guide people to the right repository.) However, in the Preview Issue experience I've been opted into, the description field of a new issue is blank. Reproduction Steps
OR
Fault Type Permanent - Occurring repeatably |
Beta Was this translation helpful? Give feedback.
-
|
@DavidAnson we've announced in a recent changelog that the old Issue_template.md files are being deprecated in the Public Preview.
|
Beta Was this translation helpful? Give feedback.
-
|
@labudis You're way ahead of schedule, then. :) That gives the date March 30 (twice) yet we're only in February and it's already broken for existing scenarios. Folks who were opted into this feature without our knowledge didn't even know we'd need to be reading release notes to find out about stuff like this. For whatever it's worth, I suggest that it would be helpful to proactively communicate breaking changes to the community - as well as GitHub's support team. Thank you for following up here, I'll start updating my repos for the new behavior. |
Beta Was this translation helpful? Give feedback.
-
DescriptionHey, I'm facing what appears to be a massive problem 😱 with task-lists to sub-issues migration. I get the following error on numerous task-lists, when migrating to sub-issues:
I've been using task-list VERY HEAVILY in order to organize issues across multiple projects (some open source, some private) and sometimes multiple orgs. This error clearly shows that that sub-issues is still not in complete parity with task-lists, and therefore I'd very much appreciate addressing this issue before the migration's deadline 🙏🏻 🙏🏻 🙏🏻 |
Beta Was this translation helpful? Give feedback.
-
|
We are looking into supporting cross-org sub-issues! |
Beta Was this translation helpful? Give feedback.
-
Great news! Anything I can do to help? |
Beta Was this translation helpful? Give feedback.
-
|
It has been mentioned before, but as I explained previously, the discussion format with most content hidden from the UI makes it extremely hard to find the right thread to append to, so I'm posting separately: After submitting a new issue, it takes dozens of seconds (or multiple refreshes) to update the issue counter in the menubar: This shows the counters do not match. Never seen it in the og experience, however that one felt less "AJAXy" and IIRC refreshed the form action target page completely, so the count mismatch didn't appear in that flow? |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for flagging - we did some work in this area but looks like the issue regressed. Reported to the team. |
Beta Was this translation helpful? Give feedback.
-
|
It looks like issue counters for archived repositories do not work, some examples of counters completely wrong or missing: (shows 0/0 for thousands of issues being there…) (this one shows at least "1" in the nav bar, however the issue page shows then 0/0 when there are both open and closed… in an archived repo; no matter if archived, the counts should still work, right?) |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for reporting this @janbrasna - I logged for our team to investigate. |
Beta Was this translation helpful? Give feedback.
-
|
@labudis "ETA for project support in Markdown issue templates?" Currently only supported in yml as shown in docs Check the image also
|
Beta Was this translation helpful? Give feedback.
and others
-
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 milestones, labels and /issues dashboard pages have not yet been migrated.
Please leave your feedback below on what is working well, any bugs you encounter, and what else you'd like to see!
🛠️ Things we fixed
We're listening to your feedback and working hard to address the highest priority issues. Below is a list of bug fixes and enhancements that we rolled out since we launched the Public Preview.
🛠 Bug fixes:
✨ Features & Enhancements:
Beta Was this translation helpful? Give feedback.
All reactions