Evolving GitHub Issues and Projects (GA) · community · Discussion #154148

#### 📈 Expanding project limits All your issues can also be laid out in a GitHub Project. We've listened to your feedback that you want space for more issues in your projects, so we've expanded the limits from 1,200 to a huge **50,000** items per project! 🎉 With today's general availability announcement, we'll be removing the opt-out option in the coming weeks. Moving forward, we'll also make increased limits your default mode. … #### beberlei May 7, 2025 - This is a real problem, even with projects, because you would don't always group by parent/child in projects, so there are enough views where you would end up with (to keep this example) a list of three or more tickets all named "UI" - - - - … ## GitHub Projects + GitHub Issues Automation Capabilities Automation between GitHub Projects and GitHub Issues feels half-baked. Webhooks make it difficult to fully automate issues/projects ourselves. For example, if I want to automatically update an issue’s label when it's moved from one project field (e.g., “Category”) to another, there’s no webhook available for GitHub Projects. The only workaround is to run scheduled jobs to keep everything in sync — but that’s expensive and inefficient. … ## GitHub Projects View with Mixed Issue Types and Static Project Fields Another challenge arises when using mixed issue types within a single project, each needing different project fields. For example, we might have a field like “Effort,” which only applies to Tasks, not Stories. Or an “Impact Area” field meant for Bugs, but not Features. Since all these issue types live in the same project (to maintain correlation and visibility), having static fields for everything becomes cumbersome and semantically unclear. … ### SeeringPhil May 23, 2025 - Hello there! Great work with the new issues/subissues and projects view 😄 There are some pain points when using those new features: … - Once devs fix those issues, they can then add the sub-issue ticket in QA project/backlog. That's how it used to work before too, but not anymore. We're concerned about it as we've setup an integration of QA project with our slack channel specifically for QA related alerts. So whenever a new sub-issue is added with main ticket, an alert is sent by default because the by default selected projects are both i.e. main project and QA project.