-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make issues more usable and manageable #13
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🤯 Wow ! So cool ! Please have a look at my comments.
Will issues be auto-labeled ? I guess the ones created with the template will get the 🐛 bug / 💡 feature label. How about using a workflow to tag new issues as triage
or adding them to a board ?
Also we could use automations to automatically change the state label of an issue when it is moved to a different column in a project ?
Anyway, thank you for taking the lead on this ! 💯
|
||
| Label groups | Labels | | ||
|--------------|-----------| | ||
| Type | ![documentation](https://img.shields.io/github/labels/graasp/graasp-feedback/📚%20documentation?style=flat-square) ![feature](https://img.shields.io/github/labels/graasp/graasp-feedback/💡%20feature?style=flat-square) ![bug](https://img.shields.io/github/labels/graasp/graasp-feedback/🐛%20bug?style=flat-square) | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about prefixing each label with the group it relates to ?
💡 feature
-> type: 💡 feature
I think it would give a bit ore context, when reading labels on an issue. Maybe that is not relevant for all, but I think especially for platform it would make sesn in order to distinguish them from other types of labels ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good from my end! Agree with @spaenleh's comments.
change wording in README and add doc section elaborate user bug report template
Hello, thanks for your comments. I believe this repo is part of a much larger system/workflow that we should put in place to efficiently gather user and external developer inputs. It calls for a general discussion around this. @spaenleh, I took your comments into account. If you have some time in the coming weeks, we could see how to automate more this repo. I don't have enough experience to do it efficiently. See #14 |
I updated the README, the labels and the issue templates with the hope that we can centralize the input from end users in this repo. This repository should be an intermediate between user feedback (oral, emails, or even directly here) and the issues of the relevant repository.
The README is very simple at the moment. Please, share you thoughts and suggestions on how to improve it. The same goes for the templates and the labels.