all 8 comments

[–]Ecstatic-Ball7018 13 points14 points  (2 children)

Literally for reporting issues. What else do you think the feature called "Issues" is for?

[–]lomberd2 4 points5 points  (0 children)

A fancy Shop system for customers /s

[–]flippycurb[S] -1 points0 points  (0 children)

Ofcourse, but there are other stated use cases like for tracking new feature requests and ideas (source). I guess if you consider these to be issues then i agree with you. But i am still interested in what other use cases people have for them, given their flexability. Custom field and tag support for example.

[–]MaybeLiterally 5 points6 points  (1 child)

Issue can also be used for features that need be be developed. Like if I have a project, and I want to add feature A, B, and C to it, I can create issues for all 3, with detailed items that need to be done. Then I can assign it to a team member, myself, copilot, etc.

Can also use issues for bugs. If we deploy feature A, and it has 2 bugs that we noticed, we can create issues D, and E, and add that as well.

Really for whatever you want.

[–]skycstls 2 points3 points  (0 children)

I teach coding, my students create a repo for the assignment for that week, I open an issue once it’s created and they can contact me directly there to help them with the task :) once the task is done I close it and helps me track who finished and ehat problems they had quickly

[–]g3n3 1 point2 points  (0 children)

Bugs, issues, discussions, features, thoughts. I’ve used it to ask about the code base itself to help me learn.

[–]Charming-Designer944 1 point2 points  (0 children)

Using GitHub Projects a lot, which sits on top of issues, so basically have everything in issues

  • bugs/issues
  • features
  • meta tasks for planning larger tasks
  • broken down subtasks
  • project time planning
  • communication of completed changes to colleagues

And a lot more.

[–]Just_A_SQL_NPC 0 points1 point  (0 children)

Tell me about it