Evolving GitHub Issues
github.blog
Evolving GitHub Issues
1–10 of 92 posts
Re: Evolving GitHub Issues
#2Noooooo! I’ve been hoping for years and years to eventually land on a team that uses GH issues so I can not hate our ticket tracker for once, but they’re gonna shit it up like ADO and Jira and Asana before that can happen. They’d already made it borderline too complicated, this will complete the transition from productivity to “legibility”.
Re: Evolving GitHub Issues
#3What about merging duplicates?
Re: Evolving GitHub Issues
#4[deleted]
Re: Evolving GitHub Issues
#5Was expecting a link to an outage report . . . pleasantly surprised as I'm currently on-boarding my team to Jira and it's important that every innovation in this space is over-engineered :)
Re: Evolving GitHub Issues
#6[deleted]
Re: Evolving GitHub Issues
#7If Issues could be restricted to repo maintainers (with everyone else using Discussions), it would make contributing to F/LOSS projects far easier because you could easily see what the team was "thinking" (PR lists aren't like that).
As it is, most Issues are polluted by random support requests, suggestions and open-ended chat which obscures the focus so much that sometimes I just can't tell what they need help with, so I don't bother offering.
I have no interest in the Jirafication of Issue though. None at all.
Re: Evolving GitHub Issues
#8> Earlier this year, we introduced the private beta of increased project item limits, expanding the capacity from 1,200 to 50,000 items in a project.
This reminds me why smaller companies can steal market share from larger companies. I can understand that at GitHub scale, it's probably difficult to support more that 1,200 items per project. The result? The entire ecosystem has these limits imposed on them. A smaller company could easily support 50,000 issues for a repository since they are hosting fewer repositories.
Re: Evolving GitHub Issues
#9Noooooo! I’ve been hoping for years and years to eventually land on a team that uses GH issues so I can not hate our ticket tracker for once, but they’re gonna shit it up like ADO and Jira and Asana before that can happen. They’d already made it borderline too complicated, this will complete the transition from productivity to “legibility”.
i have always admired GitHub's issues system for its simplicity.
s/have/had/
Re: Evolving GitHub Issues
#10I wish I could turn off Issues without archiving a repo