Jellyfish Reviews & Product Details

As I have used Jellyfish more, I have found its biggest value is not just the visibility it provides, but how it supports better planning and leadership conversations. It brings engineering delivery, team allocation, capacity, and investment priorities into one place by connecting data from tools such as Jira and GitHub.

The dashboards make it easier to identify delivery risks, understand where teams are spending their time, and discuss trade-offs without manually consolidating information from multiple sources. It is especially useful for creating a shared view between engineering, product, PMO, and leadership teams. Review collected by and hosted on G2.com.

The initial setup and learning curve could still be improved. Configuring teams, investment categories, and metrics may require support from experienced users or the PMO team.

More guided onboarding, clearer explanations of how metrics are calculated, and easier report customization would help users become productive more quickly. It would also be useful to have more flexibility when tailoring dashboards and reports for different audiences. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

The AI insights built within the product takes the heavy lifting of evaluating the data off of the user. The UI is fairly straightforward with pleasing visuals throughout the product. Pulling data from our disparate systems and present a full picture across our engineering organization in one place is a big win. When I do have to deal with the support team, they have been prompt and helpful in resolving my issues. Review collected by and hosted on G2.com.

The biggest issue I have with Jellyfish is how it attributes work done by engineers as AI assisted work. It's really making a guess based on if there are AI signals the day that they do a PR which isn't really a great determination in my opinion. Not having the ability to designate static teams has also been a problem when we have teams that are support teams who's work spans multiple JIRA projects. Review collected by and hosted on G2.com.

The effort-based allocation model is the standout. Jellyfish translates raw development activity into an FTE-equivalent split across investment categories (Growth, KTLO, Support) based on actual effort signals rather than ticket counts — which is critical, because counting issues badly misrepresents real work. This is what made my monthly CEO and board reporting credible: leadership could trust an "X FTE went to Growth this month" figure because it reflected effort, not just Jira volume. The mapping of investment categories to our own strategy taxonomy and the month-over-month trend views also let me show direction over time with minimal manual assembly, and the delivery and AI-assisted PR metrics fed our AI-adoption reporting well. Review collected by and hosted on G2.com.

The biggest frustration is the newer AI impact reports: there's no way to export the underlying data to CSV. The reports render fine in the UI, but if you need the numbers for your own analysis — cohort breakdowns, month-over-month trends, feeding an executive deck — you're stuck. You can look at the data but you can't take it with you, so getting it into a usable format means manual extraction rather than a simple download. For a metrics platform whose whole value is helping you report, locking the data inside the dashboard defeats the purpose.

On top of that, I've seen the per-tool detail figures and their aggregate rollups diverge by around 10 percentage points, which is a real problem when the aggregate is the number going in front of the board. Both issues are workable, but they add reconciliation and extraction steps to what should be a clean pull. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

Jellyfish took a complicated, manual process we had for capitalizing software development costs and made it a breeze for us in Accounting. Our old process of using timecards & tracking epics was very burdensome, taking atleast a full day of close to compile. With Jellyfish, at the click of a button I have all the data I need to book our monthly entry. The documentation Jellyfish provide has also been extremely helpful to communicate with our auditors on our processes and how everything works. Review collected by and hosted on G2.com.

None - Jellyfish has been amazing. I really have nothing bad to say. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

- 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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.

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. Review collected by and hosted on G2.com.