Jixee is well suited for the situation we are in. Most of the development is distributed over geographical location. So to itemize the tasks and to provide systematic tracking and stages Jixee is very well suited. Jixee is well suited if the automating the different stages in the development like tasks creation, updations, etc, especially cross-platform with a lot of ways for continuous interactions.
[Sentry] is honestly an amazing product. It allows us to detect errors in real time complete with stack traces and any extra accompanying information the developer wants to provide in the alert. With the alerting into Slack it has allowed us to quickly triage and tag in people who need eyes on a specific issue. It would be really useful in any Saas product environment.
Jixee interfaces with current developer services to construct custom processes, as well as providing real-time notifications through web, email, or OSX desktop.
We actually ended up using both because New Relic is a more robust overall IT infrastructure monitoring product. However, sentry is more developer oriented on the backend and more client friendly on the front end as far as showing results and the dashboard etc. It can provide product level insights that New Relic does not.
Companies have problems executing certain activities, that must be constantly monitored so that they can be performed. This is why the purchase of this program is so necessary, to save the company all the resources that are wasted activities that are not fulfilled in the established times.
We could be calm after buying this software because we knew that the tasks that had more problems and in which more resources were spent, could be closely monitored.
Error tracking is a must in any modern dynamic website or app. By looking into the error notifications I'm able to fix errors before anyone even has a chance to complain about them!
Surprisingly, many website issues aren't showing up in Sentry, because they don't trigger exceptions. I'm interested in seeing if I can use Sentry to catch manually-triggered exceptions for "undesirable states" that my website can find itself in. Of course, that means I have to figure out how to have my client code recognize that it's in an undesirable state...