Post

@github such a great idea about adding Different Fields to GitHub Issues, it will definitely help in my Open Source Project!!
English

This is going to be such a game changer for project management workflow. I always find myself clicking through dozens of individual issues just to figure out the basic details like priority or estimated effort, which can be honestly super tedious when you're trying to triage a massive backlog. Having that metadata visible right at a glance on the list view makes it so much easier to organize sprint tasks and get a clear picture of the project status without having to jump back and forth between screens constantly.
English

@github Can't wait for PMs to abuse Issue Fields to mark everything 'Effort: 5m, Priority: P0'. 🤷
English

@github Finally. No more parsing raw markdown text just to find out a bug's priority. 🛠️
English

@github Typed issue fields for everyone is overdue. Priority and effort as real data beats another free-text dump
English

@github Finally. No more parsing raw markdown strings just to find the issue priority. 🛠️
English

@github haven't used git or github properly yet but this looks like a genuinely useful feature for when I get there
English

@github Finally. Tired of abusing labels for things Jira solved a decade ago. 🛠️
English

@github priority: high, effort: low, dates: never - finally a feature that matches my workflow
English









