Getting easy metrics for team projects that is easily accessible for managers and engineers.

I use Jellyfish to understand how testing and engineering effort contribute to overall product delivery and business priorities. It helps me track where QA and automation work is going, identify bottlenecks in the development workflow, and solve the lack of visibility between testing work and broader engineering priorities. With Jellyfish, I can better connect testing activities to feature delivery, identify where delays are coming from in the pipeline, and understand how much effort is going into. I particularly like the visibility it brings across engineering teams and QA work in relation to business priorities, along with reports on demand and budget planning. The visibility and reporting feature is especially valuable, as I can see consolidated reports that show where testing efforts are concentrated, how they align with development progress, and where delays and bottlenecks occur. This makes it easier to pinpoint issues like slow handoffs between development and QA. After moving to Jellyfish, manual work has been reduced, and the process of collecting data from multiple tools has been drastically reduced.

I like the bird's eye view of signals that Jellyfish provides. The easy integration with APIs is a big plus for me, and I really appreciate the AI adoption in the platform. It saves me a lot of time compared to maintaining bespoke Excel files. The initial setup was very easy, with a presales engineer fully setting it up before the agreement was signed.