Plan on where bug reports and feature requests go

[Jonas-Sander]

Should we e.g. put bug reports into issues and feature requests into discussions?

Can you create a shortcut from the issue creation dialog into the discussions? ("Create issue" --> "Feature Request" --> Forwarded to discussions tab)

What templates should we have in "issues"?

What other things than feature requests and bug reports do we have that might go into issues or discussions?

[Jonas-Sander]

@nilsreichardt

Should we e.g. put bug reports into issues and feature requests into discussions?

That was our plan so far right?

[Jonas-Sander]

Altough I guess there wont be only bug reports in isssues.

For example if there are requests for a new feature (e.g. adding/managing your grades) we might first add for a general discussion into the "discussions" tab.

If we have an actionable plan to implement something regarding this feature we then might create focused issues for PRs / implementation discussions.

[Jonas-Sander]

Also will we have other stuff (marketing, ideas for distributing sharezone, idk) here? As issues? As discussions?

E.g. I also created #33 (informing users that we open-source our app, which is not strictly code related).
Should we add this in the issues here as well? What about things that should be private? (e.g. things we want to surprise the community with)

[nilsreichardt]

Should we e.g. put bug reports into issues and feature requests into discussions?

No, our plan was a bit different. You explained it in this comment correct: #29 (comment)

[Jonas-Sander]

Currently we're just using issues with feature request for feature request where we're not decided on if we're gonna implement them or not and issues with enhancement label for features that we decided on to implement in the future.