I am looking forward to project management without Jira!
GitHub introduces sub-issues, issue types and advanced search
121–130 of 213 posts
Re: GitHub introduces sub-issues, issue types and advanced search
#122I'm curious if there are folks here who work at for-profit orgs who use GitHub projects as their sole issue tracker for the entire org. How do you do it and what are the common pain points? Do you couple it with other issue trackers/project management tools like Jira? If so—why? I still feel GH Projects is solely aimed at OSS or dev-centric or dev-only orgs and doesn't cater to teams with non-devs, which is how I thi…
We ditched Jira to go all-in on GH. It's nice having the project management in the same place as where the actual work happens. It's not perfect, but it's better than GH + Jira. Probably the benefit I'm most happy with are that people are writing more, and in greater detail. I don't know why that is. For some reason, the GH experience just encourages writing, whereas the Jira experience seems hostile to it.
Nice job!
Re: GitHub introduces sub-issues, issue types and advanced search
#123Earlier quoted context omitted.
We ditched Jira to go all-in on GH. It's nice having the project management in the same place as where the actual work happens. It's not perfect, but it's better than GH + Jira. Probably the benefit I'm most happy with are that people are writing more, and in greater detail. I don't know why that is. For some reason, the GH experience just encourages writing, whereas the Jira experience seems hostile to it.
Interesting. Are you an all-dev org or did you also onboard non-devs into GH Projects? > the GH experience just encourages writing, whereas the Jira experience seems hostile to it. Huh, that's interesting to hear. I didn't personally find it harder to add detailed descriptions in Jira back when I used it couple of years back. Wonder if there's anything specific about the experience you can describe that makes you fee…
Roughly half the company are programmers, so we have non-devs working with GH Projects and collaborating on issues.
Colleagues who aren't developers have become more engaged in the process of writing bug reports or giving feedback on product development (or at least, the parts of it that concern them). Some of the non-programmers have admitted that they are surprised by how much they enjoy using GitHub.
Re: GitHub introduces sub-issues, issue types and advanced search
#124This seems... unneeded bloat? I guess there are some obsessive organizers out there, but a markdown checklist of steps - potentially with links to other tickets seems like all you need. If you're going to improve something improve code review! Let me comment on and suggest diffs to lines the author did not touch. Like half the time I am reviewing code it is "Hey, you refactored this but you missed a usage in this oth…
A lot of this will seem trivial if you haven't used Github for an organization's management of issues. This also lets you start off with a markdown checklist, and convert items to sub-issues.
See, but I do. For almost a decade, we have used it as-is for tickets and bug tracking, and it's never been a problem. I just don't see the use case for sub issues.
Re: GitHub introduces sub-issues, issue types and advanced search
#125Earlier quoted context omitted.
Interesting. Are you an all-dev org or did you also onboard non-devs into GH Projects? > the GH experience just encourages writing, whereas the Jira experience seems hostile to it. Huh, that's interesting to hear. I didn't personally find it harder to add detailed descriptions in Jira back when I used it couple of years back. Wonder if there's anything specific about the experience you can describe that makes you fee…
Roughly half the company are programmers, so we have non-devs working with GH Projects and collaborating on issues. Colleagues who aren't developers have become more engaged in the process of writing bug reports or giving feedback on product development (or at least, the parts of it that concern them). Some of the non-programmers have admitted that they are surprised by how much they enjoy using GitHub.
That's really nice to hear. I'm glad things worked out for your org.
GitHub marketing folks probably should reach out to you :)
Re: GitHub introduces sub-issues, issue types and advanced search
#126Great, a few more decades and it might become a usable bugtracker. What's next on the list? Maybe priority/severity or status/resolution? I helped on a quite large open source project for some time and loved working with Bugzilla. The announced switch to Github for that project was one reason I lost interest. I even prefer to work with a well administrated(!) Jira over Github issues.
Using Github issues as a manager of multiple teams using multiple repos in GitHub has so many gaps, I often wonder if I'm just doing it wrong. The multi-repo issues feature a few years back was a huge step forward but also is very incomplete, still. Multi-repo labels and milestones, for example, are an obvious missing feature.
Exactly this, they are so close!
Re: GitHub introduces sub-issues, issue types and advanced search
#127I'm curious if there are folks here who work at for-profit orgs who use GitHub projects as their sole issue tracker for the entire org. How do you do it and what are the common pain points? Do you couple it with other issue trackers/project management tools like Jira? If so—why? I still feel GH Projects is solely aimed at OSS or dev-centric or dev-only orgs and doesn't cater to teams with non-devs, which is how I thi…
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.
Re: GitHub introduces sub-issues, issue types and advanced search
#128I'm curious if there are folks here who work at for-profit orgs who use GitHub projects as their sole issue tracker for the entire org. How do you do it and what are the common pain points? Do you couple it with other issue trackers/project management tools like Jira? If so—why? I still feel GH Projects is solely aimed at OSS or dev-centric or dev-only orgs and doesn't cater to teams with non-devs, which is how I thi…
We were interested in Issues and Projects, but the number of people at an organization who need access to those but not to code or CI is pretty large. GitHub does not have a different license option for BA/CX/PM types. We ended up going with Jira for tasking, which was substantially cheaper.
I was sad about this because issues/projects had all the stuff I personally cared about, and there was no need to work to set up integrations. I think there was some anxiety by the PMO that it wasn't mature enough for what they wanted, but I don't remember any specifics. Probably something about reporting.
Re: GitHub introduces sub-issues, issue types and advanced search
#129I'm curious if there are folks here who work at for-profit orgs who use GitHub projects as their sole issue tracker for the entire org. How do you do it and what are the common pain points? Do you couple it with other issue trackers/project management tools like Jira? If so—why? I still feel GH Projects is solely aimed at OSS or dev-centric or dev-only orgs and doesn't cater to teams with non-devs, which is how I thi…
We were interested in Issues and Projects, but the number of people at an organization who need access to those but not to code or CI is pretty large. GitHub does not have a different license option for BA/CX/PM types. We ended up going with Jira for tasking, which was substantially cheaper. I was sad about this because issues/projects had all the stuff I personally cared about, and there was no need to work to set u…
That's how I feel as feel. It's costly given the things non-devs types won't need and it's not fleshed out enough to attract those types of folks to make the switch. GitHub is probably missing the boat tbh. Even the marketing page (https://github.com/features/issues) is targeted at developers.
Re: GitHub introduces sub-issues, issue types and advanced search
#130this happens after I've moved everything to height. downside is it was a lot of work. upside is height is amazing and I'm pleased with the choice. anyone else using it?
> anyone else using it?
We're looking for a new home, with Pivotal Tracker shutting down on April 30th (101 days left!). I had not heard of Height before.
On first glance, it looks like a genuinely modern project management service -- which is both interesting and unsettling.