The UI, down to the content and styling of menus, looks a lot like Linear. I'm chuffed to see the best parts being borrowed, but it looks like they've made sub-tasks/issues too simple, as they aren't first-class issues, but mere checkboxes with short descriptions.
New GitHub Issues Beta
121–130 of 223 posts
Re: New GitHub Issues Beta
#122What ever happened to Fogbugz?
Still around, https://fogbugz.com/ but owned by somebody other than Fog Creek.
Re: New GitHub Issues Beta
#123This doesn't seem to have the one feature I want most, which is the ability to track the status of projects and milestones that span multiple repositories. Anyone know if this is there and they didn't mention it, or is on the roadmap?
Yes, this is one of the main scenarios we are enabling in the Fall. Project tables and custom fields are already cross-repo enabled in the beta.
Mariorod! As a company currently using GitHub issues, is there any way to jump onto the beta program quicker?
Re: New GitHub Issues Beta
#124Earlier quoted context omitted.
> Jira seems so universally hated that it feels like any competition that ticks a few basic needs could start hurting them. I regularly meet with tech companies in the 2~10 person dev team range and easily 70%+ still use Jira. These co's have the choice of choosing Jira (i.e. it isn't being jammed down on them by a corporate overlord) yet there's still hate? I don't get it. I'm beginning to think the Jira hate is sim…
I use Jira with 300+ users for both software and non software projects. I don't love it for either but I don't hate it enough to move. Any tool that offered 1:1 feature parity and a full migration, would only need something as simple as slightly cheaper or faster for me to move. IMO the administration is a pain even for simple things. I've also been on Jira for at least 4 years now and the development is just sad...…
I am relatively new to this, completed one year at my job a while back. But I find Jira isn’t that bad. My teams have used Kanban boards to track stuff and I find it quite helpful. Sure, I forget to update my tickets every once in a while but it is a good tool IMO. So can you explain what you meant when you said the new UI isn’t better?
Re: New GitHub Issues Beta
#125I don't use GitHub Issues [much] because I was under the impression that issues are not themselves stored as a git repo, but rather they are some kind of proprietary database GitHub maintains. Thus they create lockin for GitHub. Am I wrong about this?
Why are you using Github if not for their social features?
Github's social/discovery features are too strong - it makes it difficult to justify keeping OS projects on GitLab even if the feature set is better for maintainers
Re: New GitHub Issues Beta
#126Github should first fix that it displays "issues" of a repository instead of useful info when exploring https://github.com/explore Why would I want to see issues of a repo I have no clue about? I am there just to discover a new repo.
It does not only show issues, but also other content. What would you consider useful information?
Re: New GitHub Issues Beta
#127I am longing for the day they deprecate Azure Devops and merge it into GitHub Enterprise. This is the only way I’ll ever get the ability to work with GitHub in my company, which has a much superior UI/UX imo.
Azure DevOps is quite a bit more advanced than GitHub. Is there a feature that GitHub has that is missing from Azure DevOps?
UX is very subjective and while DevOps is not perfect, I don't find it straight up horrible. It has way more features that need a place in the UI. Plus it's lightning fast compared to JIRA.
Re: New GitHub Issues Beta
#128I don't use GitHub Issues [much] because I was under the impression that issues are not themselves stored as a git repo, but rather they are some kind of proprietary database GitHub maintains. Thus they create lockin for GitHub. Am I wrong about this?
Why are you using Github if not for their social features?
I can't tell if you're joking, but if not I use it because it's a reliable, free git server.
Re: New GitHub Issues Beta
#129It floors me that they haven't addressed the underlying architecture issues that made Issues unusable: Issues are only for a single repo. Business users don't (and shouldn't) know what repo to add an Issue to. This is why we moved away from Issues and none of these new visualizations make the product usable until they deliver multi-repo issues.
GitHub issues should not be used by non-technical contributors though (imo)
Re: New GitHub Issues Beta
#130Earlier quoted context omitted.
Maybe Github Issues is not supposed to work as a support ticketing system? You are allowed to move issues between repos, so in theory you could create a dummy repo where users can add issues, and then those issues can be moved to their appropriate repo.
What if I want to define a new feature that has both backend and frontend tasks, and have separate repos for the FE and BE? Which repo do we create the issue in?
You'd group the repos together in an organizational project and open the issue there.
https://docs.github.com/en/issues/organizing-your-work-with-...