Skip to content
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

Prepare issue and response templates for user issues #5120

Closed
Tracked by #3096
upbqdn opened this issue Sep 8, 2022 · 3 comments · Fixed by #6858
Closed
Tracked by #3096

Prepare issue and response templates for user issues #5120

upbqdn opened this issue Sep 8, 2022 · 3 comments · Fixed by #6858
Labels
A-docs Area: Documentation C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage

Comments

@upbqdn
Copy link
Member

upbqdn commented Sep 8, 2022

Motivation

Zebra is going to have its first release candidates and active users. We should prepare issue templates to make bug reporting unified and easy for people outside the ZF team.

We might also want to have some suggested responses to tell users when they report issues.

Related issue: #5121.

@upbqdn upbqdn added C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage A-docs Area: Documentation P-Low ❄️ labels Sep 8, 2022
@teor2345 teor2345 changed the title Prepare issue templates for reporting user issues Prepare issue and response templates for user issues Sep 8, 2022
@mpguerra
Copy link
Contributor

Aside from the response template, what is the difference between this a our existing bug report template? Have we decided how we are going to ask users to report issues? e.g is it just going to be by creating a new issue in github?

@upbqdn
Copy link
Member Author

upbqdn commented Sep 15, 2022

what is the difference between this a our existing bug report template?

The way I see it is that bug reports are related to the source code, and issue reports are related to usability. I think we could just edit the existing bug report if such a distinction is unnecessary.

Have we decided how we are going to ask users to report issues? e.g is it just going to be by creating a new issue in github?

This should be addressed in #5121.

@teor2345
Copy link
Contributor

what is the difference between this a our existing bug report template?

The way I see it is that bug reports are related to the source code, and issue reports are related to usability. I think we could just edit the existing bug report if such a distinction is unnecessary.

I think it would be ok to make the bug report template into a "user bug report" template.

We're not using it as developers, because we have usually:

  • already diagnosed the bug, or
  • we've seen it on our supported infrastructure in CI.

@mpguerra mpguerra moved this to 🆕 New in Zebra Sep 22, 2022
@mpguerra mpguerra added this to Zebra Sep 22, 2022
@mergify mergify bot closed this as completed in #6858 Jun 8, 2023
@github-project-automation github-project-automation bot moved this from 🆕 New to ✅ Done in Zebra Jun 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: Documentation C-enhancement Category: This is an improvement S-needs-triage Status: A bug report needs triage
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants