Jellyfish

What do you like best about the product?

It gives great visibility into team performance without feeling like micromanagement.
The dashboards are clean, easy to understand, and actually useful for decision-making.
I appreciate how it integrates smoothly with existing developer tools.
It helps identify bottlenecks early and improves planning accuracy.
Overall, Jellyfish makes engineering insights actionable and transparent.

What do you dislike about the product?

Jellyfish can feel complex to navigate, especially for new users.
Some reports and metrics lack flexibility and customization.
Integration setup can be time-consuming and not always intuitive.

What problems is the product solving and how is that benefiting you?

Jellyfish helps make engineering work more visible and easier to understand.
It connects data from different tools and puts everything in one place.
This makes it easier to track progress without constantly asking teams for updates.
It helps identify bottlenecks early before they turn into bigger problems.
Planning becomes more realistic because decisions are based on real data.
It improves alignment between engineering and leadership.
Teams can focus more on actual work instead of manual reporting.
It saves time by automating metrics and insights.
It brings clarity to priorities and delivery timelines.
Overall, it helps me make better, data-driven decisions with less effort.

What do you like best about the product?

I like using Jellyfish for tracking my tickets, PR reviews, PR merged metrics, and productivity metrics. I enjoy the ticket tracking feature. I also enjoy seeing my AI usage metrics, as it allows me to track how well I've used it. I can see how fast I solved my tickets using AI metrics.

What do you dislike about the product?

Even if I update the Jira ticket as closed, it takes quite some time to update in Jellyfish. Improving near real-time synchronization helps make task movement more accurate.

What problems is the product solving and how is that benefiting you?

I use Jellyfish for tracking my tickets, PR reviews, and productivity metrics. It solves ticket tracking, productivity metrics, and sprint review problems, helping me see how fast I solve tickets using AI metrics.

What do you like best about the product?

It gives a clear view of where the team’s time and effort are going, which makes planning easier.

I like how simple it is to understand insights without digging through complicated reports.

What do you dislike about the product?

Some of the data takes time to update, so the insights aren’t always real-time.

A few parts of the interface feel a bit complex at first and need time to get used to.

What problems is the product solving and how is that benefiting you?

It helps bring all engineering work into one place, so it’s easier to understand what the team is focusing on.

It gives clearer visibility into priorities and effort, which helps with planning and explaining work to stakeholders.

What do you like best about the product?

Jellyfish has strengthened our product organization’s ability to operate with data-driven decision-making. We can clearly see how our development and engineering work aligns to our investments and roadmaps to create better proactive tradeoffs and validation on what we should pursue.

What do you dislike about the product?

Would love to see more capabilities for product-led companies and the product leader’s perspective

What problems is the product solving and how is that benefiting you?

Predictable and reliable delivery rhythm, forecasting ability, identify misalignment between planned and actual work, validation of investments.

What do you like best about the product?

I appreciate how Jellyfish effortlessly captures and automates data signals, translating engineering activity into meaningful insights. This is particularly useful for my role as an Engineering Manager at Paylocity, as it provides visibility into productivity, project allocation, and areas needing improvement. The connection of data across Jira and GitHub offers a clear picture of where our team’s time and effort are focused, making the dashboards intuitive for tracking progress, balancing priorities, and spotting trends. This functionality eliminates the hassle of manually gathering data from various sources. I value how the dashboards facilitate more data-driven and transparent conversations with leadership. The automation of real engineering signals into meaningful metrics, rather than relying on manual reporting, gives me a real-time view of work progress and blockages, which in turn connects day-to-day engineering activities with strategic outcomes—something that would've been difficult to achieve otherwise. Another aspect I really like is the smooth setup process for integrating Jira and GitHub, with effective onboarding support from the Jellyfish team, ensuring quick start of generating insightful dashboards and metrics.

What do you dislike about the product?

I find that Jellyfish heavily relies on clean data from Jira and GitHub to generate accurate insights. If the data hygiene isn't consistent, the metrics can become misleading, making it difficult to trace where discrepancies originate or why certain metrics appear incorrect. Troubleshooting these issues is time-consuming, and Jellyfish lacks built-in tools to assist with identifying data gaps, suggesting corrections, or guiding teams towards better data configuration. Having additional flexibility to adjust or reclassify signals would make the insights more reliable and actionable, enhancing the platform’s overall effectiveness.

What problems is the product solving and how is that benefiting you?

I use Jellyfish to capture data signals for meaningful metrics, providing our team clarity on productivity and project allocation. Its integration with Jira and GitHub offers real-time views and facilitates data-driven decisions, saving time. However, reliance on data hygiene can skew insights without additional data validation tools.