RedSquirrel87
commented
4 years ago Original comment by Red Squirrel (Bitbucket: Red_Squirrel, GitHub: RedSquirrel87).
Well, it could be an idea for the future, yes, but frankly I see it like an useless complication for the bug tracking service. I mean, why to go through external scripts, bots, etc... when you just click on a link and write here directly? You don't even need to create an account to post here on Bitbucket xD
Also I see at least 2 other problematic things in a such implementation:
- Most of the bug reports made by users are always minimal, like "Kissmanga does not work anymore", an issue that maybe I cannot even reproduce by myself. There is therefore the need for interaction between me and the user to try to better understand the error and understand why it doesn't work for him and not for me, or just ask him for some additional details. The most of the users will never come here later and manually search for the report made automatically by the bot to check if there are answers or not, or its status.
- Duplicates: now the user when clicking on the link will come to the main page where he will be in front of the list of already open issues, so it is quite easy to notice if an issue has already been reported recently for that website. By reporting bugs from the program, you have no idea if someone else has already reported the same problem, so there is the risk of creating 4-5 different bug reports made by users and all concerning the same problem.
So yes, I understand that it can be an idea that simplifies the life for the user who reports a bug, but that surely unnecessarily complicates things for the issue reporting system by and large xD
Original report by Anonymous.
Hello.I've been using a few downloaders over time and I think yours is one of the best out there. But one thing that feels off, in my humble opinion, is the way bug reports are sent. For example, Hakuneko (another manga downloader) lets you send the reports without actually going to Github, because it allows the use to send them from the software itself. You can still open the issues on GitHub but most of the users just use the built in function. From what I can see, they use Google Forms and then they use a bot service to open the issue on GitHub. I looked around a bit and it seems like Zapier can do it with Bitbucket. This is Zapier: https://zapier.com/. With a free plan, it gives you 100 actions every month, if I remember well. Just add Google Forms and BitBucket and see what it can do. I think you can definitely add a Google Sheet window on the tool as well. I don't know if you've already considered it, but you know, a lot of people just want things to be the easiest possible. I'm sure way more people would report things if they didn't have to open the issue tracker on BitBucket.