4 ms·
The mongoid repository (https://github.com/mongodb/mongoid https://github.com/mongodb/mongoid) doesn't have issues turned on and instead points people to JIRA.
by andrew_ 5y ago
The mongoid repository (https://github.com/mongodb/mongoid https://github.com/mongodb/mongoid) doesn't have issues turned on and instead points people to JIRA. That's one way to avoid users reporting issues like this - I'd see JIRA and "nope" right out.
- ineedasername 5y agoIs JIRA that bad even for just logging an issue? Or do you nope out of the dependency?
- plorkyeran 5y agoAt the minimum it's another account you have to register. The more Jira-specific problem is that making drive-by issue reporting frictionless is an extremely low priority for Jira (or for the people who choose to use Jira), and there's often going to be a bunch of confusing steps required. It also just signals that they aren't really that interested in hearing from users. People who crave feedback and bug reports go to where the users are rather than making the users come to them. Even if they use Jira internally, they'll do things like monitor stack overflow and provide support on Github.
- house9-2 5y agoIt really is "that bad". JIRA is not made for humans.
- zionic 5y agoMy favorite example is Zendesk. They’re a customer support company with all their GitHub issues turned off, forcing you to use their support system. Of course, if you email them telling them they broke their library (for the 3rd time this year) and forget to email them on your account holder email they’ll respond that they only take requests from the designated email, and say goodbye. Even when you use the right email you’re still playing telephone between some poor support person and a dev. Absolute trash-tier company, I have a backlog item to completely scrap their SDK from my apps I just haven’t gotten around to it.