131–140 of 213 posts
A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.
But you’re completely right, GH search is truly bad
A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.
A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.
Earlier quoted context omitted.
It would be a tough sell for my org to triple our license spend on GHEC just so we can teach a bunch of folks new software.
A FOSS plugin to mimic Service Desk on top of Github issues would be great. You'd miss the infinite complexity of Jira workflow configuration, but that might be a good thing.
A GitHub feature I think would be really handy is suggesting duplicate issues when writing up a new issues. Many projects ask that you search for already reported tickets, but GitHub's current search isn't great if you aren't sure what you are looking for.
Agree! For fun, I had put together a GitHub bot for this purpose a while ago. It indexes all existing issues in a repo, creates embeddings and stores them in a vector DB. When a new issue is created, the bot comments with the 3 most similar, existing issues, from vector similarity. In theory, that empowers users to close their own issues without maintainer intervention, provided an existing & solved issue covers thei…
Earlier quoted context omitted.
Cynical answer: because having users writeup duplicate issues and then having maintainers close them is more engagement than warding off unnecessary toil. Gotta keep those metrics going up and to the right.
I suspect it's more to do with issue management isn't their core product so doesn't get the same attention an issue management system would give it.
This is also what is happening with GH issues.
Earlier quoted context omitted.
We tried (dev-centric org) but the non-technical users weren’t able to use it well / didn’t like it - so now we don’t have issue tracking at all for non technical stuff -.-
Oh my! That doesn't sound like a good place to be in. I hope y'all figure something out to get them onboard or migrate out.