GitHub Issues Reviews

My key use case for GitHub Issues covers all the projects, including version control as well as issue tracking and discussions.

I use the labeling feature in GitHub Issues. Regarding task prioritization, I think integration with code repositories in GitHub Issues is easy to manage. In my opinion, the ability to assign issues to specific team members is a good function, and I think it simplifies collaboration. I utilize the Insights tab in GitHub Issues, and I can provide feedback about that option.

Based on my experience, GitHub Issues provides main benefits, such as saving time, saving money, and streamlining processes for me and my company.

The only issues I see as potential areas of improvement for GitHub Issues are that I would appreciate seeing some additional functions that can simplify my work.

I have been working with GitHub Issues for more than five years.

I believe we're talking about GitHub Enterprise, and for stability, I would rate the product a solid 10.

I would rate scalability from one to ten based on my experience as a solid rating.

I would provide feedback on technical support from GitHub, which operates through forum support. I would rate this aspect a 3.

Neutral

If I compare GitHub Issues with Jira, GitHub Issues is the better solution for me. For GitHub pricing in the Enterprise version, I would rate it as a 10.

The initial setup for GitHub Issues is simpler than Jira.

If I compare GitHub Issues with Jira, GitHub Issues is the better solution for me, and for GitHub pricing in the Enterprise version, I would rate it as a 10.

I can definitely recommend GitHub Issues to other users. I would rate this product a 10.

I've recently created an issue for a project I'm working on. We use it to categorize the issue with specific tags, assign it to particular users, track its status, and set its priority. This allows for better organization and ensures that tasks are appropriately tagged and assigned to the responsible individuals.

It enables mapping issues to specific team members, making it a valuable feature. The user-friendly nature of this functionality enhances the overall experience.

The challenge lies in the initial setup and the difficulty of adding new Issues.

I have been working with it for a few months.

It is stable, and I haven't encountered any issues.

In terms of scalability, we can include as many Issues as needed without encountering any apparent limits. Based on my observations from various open-source projects, even those with hundreds or thousands of Issues, there don't seem to be significant problems. There are around twenty to twenty-five members in the prototype.

The initial setup wasn't straightforward. I had to search for instructions on how to configure it.

It doesn't necessarily have to be deployed; instead, it is essentially assigned to an individual. We can create and assign a person to it, along with adding a suitable title. Maintenance is generally unnecessary, and the status doesn't need regular checking. Instead, the individual who oversees the issues, typically the leader, ensures completion by periodically verifying the assigned tasks.

It is an open source. There are no extra charges associated with it.

Overall, I would rate it eight out of ten.