Jellyfish

What do you like best about the product?

I really like the interface and how easy it is to navigate through the data. If you have your hierarchy set up and use Jira effectively, the integration lets you move up and down through the different levels of your organization and see how data from smaller units rolls up into the larger picture.

What do you dislike about the product?

There was a bit of a learning curve at first as I got used to the navigation, but once I understood where to find the information I needed, I could use favorites, bookmarks, and stars to quickly access the information I rely on regularly.

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

Jellyfish provides visibility into our information in a way we couldn’t get anywhere else. In particular, it shows where developers are actually spending their time, not just where they plan to spend it. The signals Jellyfish captures give us a clearer view of reality than our other planning tools. It also enables capitalization tracking without forcing us to rely on time tracking across our work.

What do you like best about the product?

The DevFinOps capabilities and DORA metrics have changed the way we operate as an engineering organization.

What do you dislike about the product?

I wish there was more in the way of ‘engaging’ users, driving them to the platform.

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

Labor capitalization, DORA metrics, AI Impact, synthesizing Jira, Gitlab, and Cursor data.

What do you like best about the product?

I like that Jellyfish provides clear visibility into my work, eliminating the need for manual tracking. The simple dashboards make it easy to understand performance trends quickly. It's incredibly useful for identifying delays in testing or review cycles, which helps me improve consistency and maintain accountability. The setup was straightforward, with smooth integration of tools like Jira and Git, and it was easy to start using. Switching to Jellyfish from more manual tracking methods made performance tracking more structured and data-driven. I appreciate how it gives me a clear view of my work and contributions while using it alongside other tools like Git, Jira, and CI/CD pipelines.

What do you dislike about the product?

The AI insights could be more detailed and tailored to QA needs, like providing insights on test coverage gaps, identifying flaky tests, and recurring defect patterns. It would also be beneficial if the AI could suggest clear actions on where to improve tests or highlight potential risks in upcoming releases.

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

I use Jellyfish to track my QA performance with clear dashboards, helping me quickly identify delays in testing cycles. It improves consistency and accountability by providing visibility into my time usage and contributions.

What do you like best about the product?

You can look at Team Pulse, Team Summary and Individual statistics during Retrospective for what went well, didn't go well.

What do you dislike about the product?

AI Impact was not integrated successfully with Amazon Q.

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

The biggest advantage is categorizing where the time is being spent by the developers, i.e. we have decided categories for each epic and defect.

What do you like best about the product?

Jellyfish is very easy to use and has a lot of documentation, which is great. I love the look and feel of the service. I appreciate the ability to assign team priorities and see how a single individual is doing. The Daily Team Digest to Slack is vital for monitoring across teams, and the Team Summary Dashboard offers an excellent snapshot of team performance and an insight into sprint trends. The initial setup, especially with the ingestion of the Jira team structure, was very smooth and handled changes well.

What do you dislike about the product?

- Sprints: We use t-shirt sizes and time estimation instead of story points, and there isn't currently an option to handle that. - Daily Team Digest: The list of stale Jira tasks operates on the last update date, but because we are doing sprints, the oldest anything gets is 14 days before the sprint changes. Those tickets are still in the same status but their last changed date has been refreshed. Something in the same status for 100 days may only show as 7 days on the report. If the section of the digest is about being stuck in a status, we should be able to configure what date it operates on.

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

Jellyfish compiles data from different locations into one platform, helping me monitor my team's progress and manage priorities more effectively. The Daily Team Digest and Team Summary Dashboard features are especially useful for overseeing team activity and researching sprint trends.

What do you like best about the product?

I like using Jellyfish because the UI is intuitive and easy to use. There are detailed metrics, and I can use date or sprint filters and drill into graphs, which is really helpful. The Teams view and Metrics by Outcome feature, along with Custom Groups, give me a unified view across our teams. Utilizing DevEx surveys quarterly provides insights into areas for improvement. All these parts give me a better understanding of my team and the work we do, helping me identify bottlenecks and provide hard data for supporting any decisions. The integration with Jira and GitHub works really well, giving insights into Jira tickets, sprints, planning, work allocation, and the cycle time for each ticket. For GitHub, it provides insights into PRs, comments, contributions, and how long they take.

What do you dislike about the product?

The filters start to load reports as soon as I change them, but sometimes I need to adjust multiple filters, and there is an unnecessary loading that slows down me getting to the final report I want. I would appreciate having an option to pause loading of the reports until I unpause it. So I can adjust filters and selections as I want.

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

I use Jellyfish to monitor my team's metrics, track PRs, Jira cycle time, work distribution, and predictability. It identifies bottlenecks and provides data for decisions. Integrating with Jira and GitHub offers insights into sprints, planning, and PR progress.

What do you like best about the product?

I like Jellyfish because it provides one place to go for combining data from Jira and Github, offering good metrics. The metrics display is easy to use, and I appreciate seeing comparisons with other teams and companies.

What do you dislike about the product?

Some graphs are affected by outliers. Would be nice to either remove them or be able to change the scale of the graph.

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

I use Jellyfish to watch velocity metrics for teams, with Jira and Github data in one place, offering good and easy-to-use metrics.

What do you like best about the product?

I really like how Jellyfish continues to engage with customers even after onboarding and consistently makes improvements to the application without causing any friction. Over the almost two years we've been using Jellyfish, they've added multiple features that I find useful and didn't have before. They're proactive from a product standpoint, gathering feedback for driving these implementations. Compared to other vendors, Jellyfish has excelled in maintaining this continuous improvement motion. I also appreciate the ease of onboarding, with a status page guiding me step-by-step through the initial setup. Jellyfish automates tasks that were previously manual, like pulling together actionable metrics and dashboarding for AI usage, thereby simplifying my workflow. The incorporation of an AI chat feature and a custom query mechanism really helps me overcome dashboarding limitations, allowing me to easily get the metrics I need.

What do you dislike about the product?

I find custom dashboarding challenging, though they're moving in that direction. Sometimes I need to engage support to fix data pulls from GitHub and Jira, but they resolve those quickly.

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

I use Jellyfish to identify engineering bottlenecks, measure productivity, track DORA metrics, and conduct career development conversations. It automates data collection from Github, Jira, and AI tools, replacing our hard-to-maintain custom solution.

What do you like best about the product?

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

What do you dislike about the product?

Sometimes the metrics aren't completely the same as internal metrics or teams want to customize and it is not possible. Load times are sometimes long and nightly refreshes aren't as useful as real time updates.

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

Getting efficiency metrics for teams so they can focus on targeted improvements, showing AI adoption metrics for new AI tools and Capdev reporting insights can be faster and more accurate

What do you like best about the product?

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.

What do you dislike about the product?

While the dashboards provide strong visibility, they can sometimes feel a bit complex or dense when trying to drill down quickly into QA-specific insights. More customisable or role-focused views would make it easier to surface what's most relevant without extra filtering.

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

I use Jellyfish to connect QA work with engineering priorities, identify pipeline bottlenecks, and track AI usage. It consolidates reports on testing efforts, aligning them with development progress, making it easier to spot issues like delays.