I see that you just registered on Tildes yesterday—please make sure that you're not only using the site as a way to promote your own site/projects. It's fine to post your own projects...
I see that you just registered on Tildes yesterday—please make sure that you're not only using the site as a way to promote your own site/projects. It's fine to post your own projects occasionally, but it shouldn't be the main (or only) reason you're interacting with the community here.
In most software projects, issues are being opened much more often than they are closed. All the more so for popular projects. And whenever the rate of opening issues is higher than the rate of...
In most software projects, issues are being opened much more often than they are closed. All the more so for popular projects. And whenever the rate of opening issues is higher than the rate of closing issues, the number of issues in the issue tracker grows without limit.
Which is to ask, however nice this app is, are you attacking a problem that most projects have? The limiting factor in gathering lots of feedback is managing it all and figuring out what to do about it.
All fair points. This tool solved a particular issue we had. Whenever we asked our non-technical staff to test a new feature that was in alpha, they sometimes found some issues and reported them...
All fair points. This tool solved a particular issue we had. Whenever we asked our non-technical staff to test a new feature that was in alpha, they sometimes found some issues and reported them using spreadsheets, one row per each issue, or even plain text files. So I made this tool to make things easier for them, and also us: they no longer have to start a new spreadsheet/text file and add issues row by row, save it and share it with the rest, and we no longer have to grab those spreadsheets and convert them into issues.
GitHub issues are fantastic to track new features or bugs, who is assigned, categorize them, adding to projects and so on. At the same time, they’re also quite slow to create and creating a bunch...
GitHub issues are fantastic to track new features or bugs, who is assigned, categorize them, adding to projects and so on. At the same time, they’re also quite slow to create and creating a bunch of them consumes too much time.
One of the pain points I see with GitHub issues at work is that they’re cumbersome to create, particularly for those that are not developers or designers, like managers or testers, that want to report a bug without going through the process of creating them on GitHub.
Since I was tired of the slow process, I created this free open source app to to make GitHub issues faster using plain text.
I see that you just registered on Tildes yesterday—please make sure that you're not only using the site as a way to promote your own site/projects. It's fine to post your own projects occasionally, but it shouldn't be the main (or only) reason you're interacting with the community here.
Understood Deimos! 👍
In most software projects, issues are being opened much more often than they are closed. All the more so for popular projects. And whenever the rate of opening issues is higher than the rate of closing issues, the number of issues in the issue tracker grows without limit.
Which is to ask, however nice this app is, are you attacking a problem that most projects have? The limiting factor in gathering lots of feedback is managing it all and figuring out what to do about it.
All fair points. This tool solved a particular issue we had. Whenever we asked our non-technical staff to test a new feature that was in alpha, they sometimes found some issues and reported them using spreadsheets, one row per each issue, or even plain text files. So I made this tool to make things easier for them, and also us: they no longer have to start a new spreadsheet/text file and add issues row by row, save it and share it with the rest, and we no longer have to grab those spreadsheets and convert them into issues.
Fair enough! It might be best to lead with that explanation? QA done at work is often different from gathering issues from random Internet users.
GitHub issues are fantastic to track new features or bugs, who is assigned, categorize them, adding to projects and so on. At the same time, they’re also quite slow to create and creating a bunch of them consumes too much time.
One of the pain points I see with GitHub issues at work is that they’re cumbersome to create, particularly for those that are not developers or designers, like managers or testers, that want to report a bug without going through the process of creating them on GitHub.
Since I was tired of the slow process, I created this free open source app to to make GitHub issues faster using plain text.