search

mysteriumnetwork / node

Mysterium Network Node - official implementation of distributed VPN network (dVPN) protocol
https://mysterium.network
GNU General Public License v3.0
1.1k stars 314 forks source link

Some ideas on how to improve our current "report log" solution (issue reports) #4382

Open isaackielma opened 2 years ago

isaackielma commented 2 years ago

Is your feature request related to a problem? Please describe. Currently we have bug reporting feature on Desktop app (help tab) , Android app (help tab), and Node UI (lower left corner of page "bug symbol"). All of these reports have a general text box for a general description and email. When these bugs get reported they all end up in the same private repo called 'node-user-reports' https://github.com/mysteriumnetwork/node-user-reports.

Because they are not very detailed in information about issues and all bundled up together, it becomes quite time consuming to organize them all and redirect the into node, mysterium-vpn-desktop and mysterium-vpn-mobile issues on our public repos.

Below I have a few suggestions that may help this bug reporting process become more efficient.

Describe the solution you'd like

  1. If these bugs required more details before being submitted this would help issues being solved more quickly without having to ask so many questions in between. Maybe having a template like we do here on node issues would encourage our providers/users provide us with more detailed bug reports. example:

Describe the bug A clear and concise description of what the bug is. To Reproduce Steps to reproduce the behavior:

  1. Go to '...'

  2. Click on '....'

  3. Scroll down to '....'

  4. See error Expected behavior A clear and concise description of what you expected to happen. Screenshots If applicable, add screenshots to help explain your problem. Environment (please complete the following information):

    • Node version: [e.g. 0.19.1]
    • OS: [e.g. raspbian buster, debian 10]
    • Desktop app version (if applicable): [e.g. 2.0.4]
    • Docker (if applicable): specify docker version and image tag Additional context Add any other context about the problem here. Describe alternatives you've considered A clear and concise description of any alternative solutions or features you've considered. Additional context Add any other context or screenshots about the feature request here.

  5. Redirecting these bugs straight to their respective public repositories (maybe not public but separate repositories). If once these bugs are submitted on UI or in app, if they could appear directly on public repos. example: Provider has a bug on client app android version. He/she goes to submit bug and report lands on mysterium-vpn-mobile (public or private).

  6. I understand this may potentially clog the public repos with issues. Therefore we could maybe create private repos for that and support could filter through them more easily? Just by having logs easily attached to the issues is a huge time saver. But having all of these issues bundled up on same repo can get confusing

Anyways these are just some ideas, but if they are too complicated to implement no problems at all!

ZygintasBudrys commented 1 year ago

Ask @isaackielma if still relevant