Request access to new GitHub issues features

[targos]

Refs: https://github.blog/changelog/2024-10-01-evolving-github-issues-public-preview/

I'd like to add the nodejs org to the waitlist. I think sub-issues and issue types will be very useful to us.

[RedYetiDev]

Here's a TL;DR:

1. Issue Types: https://github.com/orgs/community/discussions/139933 - Instead of labeling issues as “Feature Request” or “Bug” (which we don’t have), GitHub will support a classification of issue types, alongside the traditional labels.

2. Sub Issues: https://github.com/orgs/community/discussions/139932 - Currently, we use tracking issues to manage different long-term tasks, however GitHub is introducing sub-issues, a way to open an issue that is a part of another issue.

[richardlau]

I think sub-issues and issue types will be very useful to us.

Personally, I'm looking forward to:

• On long issues, selecting ‘load more’ will now fetch 150 events instead of 50.

🙂

[mcollina]

I've heard that it fails to load repositories with more than 1000 open issues :(.

[targos]

@mcollina Is there a public discussion about this? I wouldn't like block on rumors.

[mcollina]

No I don't atm :(

[targos]

The microsoft/typescript repo has more than 5k issues open and is enrolled in the feature: https://github.com/microsoft/TypeScript/issues?q=sort%3Aupdated-desc+is%3Aissue+is%3Aopen

[legendecas]

Given with the precedent on microsoft/typescript repo with more than 5k issues, any concerns remaining with moving ahead on this?

[RedYetiDev]

IMO we should, before moving forward, decide what "Types" to add (if any), just so we are all aware.

[targos]

Here are the default issue types:

[ovflowd]

Here are the default issue types:

I feel we should have some based on the core labels we have? Not sure Task and Enhancement make sense. Bug, Feautre, Docs, Tooling, etc make sense for me.