Now Available ✨ Close issue as a duplicate, REST API for sub-issues, and more!

[github-staff]

Following our "Evolving GitHub Issues" announcement we've continued to improve the experience based on your feedback, including closing an issue as a duplicate, a REST API for sub-issues, and expanding the limits for both sub-issues and issue types.

These new features are all available in public preview for you to try. To gain access for your organization, please sign up here. Check out the changelog announcement here.

🧹 Close an issue as a duplicate

You can now close an issue as a duplicate of another issue, making it easier to manage your issues and provide more clarity on why they were closed.

When closing an issue, select Close as duplicate from the dropdown to search for and select the duplicate issue. You'll then see an event in the timeline and note at the top making it clear why it was closed.

duplicate_video.mp4

⚙️ REST API support for sub-issues

You can now use the REST API to view, add, remove, and reprioritize sub-issues, making it easier to automate your use of sub-issues. Check out the documentation to learn more.

➕ Increased limits for sub-issues and issue types

You can now have up to 100 sub-issues per parent issue (up from 50), as well as up to 25 issue types in an organization (up from 10), making it easier to manage, classify, and break down work.

📱 Issue types on GitHub Mobile

You can now view, add, and update issue types on GitHub Mobile.

🔍 Improved filtering for sub-issues and issue types

You can use the has: and no: filters to search for sub-issues and issue types both from a project and the repository issues page, making it easier to find the exact set of issues you're looking for and make updates.

Example filters include:

• no:type to find all issues that do not yet have a type
• no:parent-issue to find all issues without a parent issue
• has:sub-issue to find all issues that have sub-issues

✨ Additional improvements

On top of the many bug fixes we've shipped, we've also introduced the following improvements:

• If the sub-issue is from a different repository than the parent issue, you will now see the repository name in the sub-issues list.
• In GitHub markdown, pasting in a project link will now show the project name as well as more project details on hover.
• Projects insights charts now use Highcharts, which is an industry standard library for charts, improving our accessibility of projects insights.
• You can now use the UpdateProjectV2Field GraphQL API mutation to directly update all single select field options in one API.

✍️ Tell us what you think!

Share your feedback by posting a comment below 👇

See how to use GitHub for project planning with GitHub Issues, check out what’s on the roadmap, and learn more in the documentation.

[BenjaminOmar]

First of all, i would like to say that our team LOVES the new GitHub project structure. There is one feature that would elevate it. As of my understanding, there is no way of doing advanced filtering (like shown above) inside of the project. This would be a great additidon, so we could have even greater KanBan board structures. The field i am talkin about is underlined here:

Would also be great to be able to separatly filter on the sliced properties as stated here:

Other than that, it works great!