Jellyfish
JellyfishReviews from AWS customer
0 AWS reviews
-
5 star0
-
4 star0
-
3 star0
-
2 star0
-
1 star0
External reviews
404 reviews
from
External reviews are not included in the AWS star rating for the product.
Visibility into Engineering Work and Priorities
What do you like best about the product?
Jellyfish gives engineering leaders visibility into where time is being spent. It helps break down work across projects, KTLO, and initiatives so teams can see alignment with priorities. The reporting makes it easier to have data-driven conversations about tradeoffs and capacity.
The biggest upside is clarity. Jellyfish takes data that’s usually scattered across git, tickets, and spreadsheets and brings it into one place. This reduces guesswork and helps managers and executives align on what teams are working on and how it connects to strategy. It also helps track trends over time, like cycle time or allocation shifts, which makes planning and retrospectives more grounded.
The biggest upside is clarity. Jellyfish takes data that’s usually scattered across git, tickets, and spreadsheets and brings it into one place. This reduces guesswork and helps managers and executives align on what teams are working on and how it connects to strategy. It also helps track trends over time, like cycle time or allocation shifts, which makes planning and retrospectives more grounded.
What do you dislike about the product?
What do you dislike about Jellyfish?
The tool can feel rigid. The categorization of work is powerful but depends on tagging and setup, which creates extra overhead. Some managers worry about metrics being misused against individuals rather than used for organizational insight. The interface can also be overwhelming at first, and not all dashboards are intuitive without training.
The tool can feel rigid. The categorization of work is powerful but depends on tagging and setup, which creates extra overhead. Some managers worry about metrics being misused against individuals rather than used for organizational insight. The interface can also be overwhelming at first, and not all dashboards are intuitive without training.
What problems is the product solving and how is that benefiting you?
Jellyfish solves the problem of visibility in engineering work. Before, it was difficult to understand how much time was going into projects, KTLO, and unplanned work. Now we can see how work maps to company priorities and track trends like cycle time and allocation shifts. This helps with planning, resourcing, and having grounded conversations with executives about tradeoffs. It reduces guesswork, builds trust in data, and makes it easier to align engineering with product and business goals.
Empowers Engineering Leadership with First-Class Support
What do you like best about the product?
I find Jellyfish incredibly powerful for understanding engineering workflows and facilitating improvements. Its visualisations and out-of-the-box data exposure empower my engineering managers to elevate their analysis and understanding of their team's flow. The scenario planner is highly valuable in aligning estimates with capacity, aiding productive capacity planning discussions, and, most crucially, understanding when something will be done. Furthermore, the insight derived from using Life Cycle Explorer to identify bottlenecks and enhance team interactions is invaluable. The first-class support from the Jellyfish team, including quick assistance from individuals like Andrey, also significantly enhances my experience.
What do you dislike about the product?
I find some parts of the user interface not intuitive enough, which could be improved for better user experience. Additionally, while the scenario planning feature is useful, incorporating more embedded tools like milestones and projections would enhance its functionality (Little's Law in particular). The insights provided could also be more actionable by offering suggestions on how to improve areas of friction and better training for users to understand concepts, such as estimates and their role in agility and the SDLC.
What problems is the product solving and how is that benefiting you?
I use Jellyfish to understand and improve team planning, delivery, and investment, empower engineering managers, tackle stream-level bottlenecks, identify communication issues, and enhance team collaboration.
Practical tool for engineering insights, though data quality depends on integrations
What do you like best about the product?
As an Engineering Manager at Paylocity, I love how Jellyfish captures and automates data signals to translate them into meaningful engineering metrics. It gives our team visibility into productivity, project allocation, and areas to improve, all in a user-friendly experience. The dashboards make it easy to spot trends and drive better decisions without having to manually piece together data from multiple sources.
What do you dislike about the product?
The biggest challenge is its heavy reliance on GitHub and Jira hygiene to generate accurate insights. If the underlying data isn’t clean, the metrics can become misleading, and it’s not always clear why the numbers are off. Troubleshooting incorrect data takes time, and I wish there were built-in tools to help Engineering Managers quickly pinpoint issues or adjust signals for more reliable insights. A stronger layer of data validation or guidance would make the platform much more powerful.
What problems is the product solving and how is that benefiting you?
Jellyfish helps us bridge the gap between engineering work and business priorities by turning raw signals from GitHub and Jira into meaningful metrics. It gives visibility into how engineering time is spent, how projects are progressing, and where bottlenecks exist. This has improved our ability to plan, prioritize, and have data-driven conversations with leadership. As an Engineering Manager, I can use Jellyfish to guide team growth, identify trends early, and ensure alignment with company goals.
Easy to Use Reporting for Capitalization
What do you like best about the product?
As an accounting user of the system, the ease and simplicity of generating reporting that can be used to support our software capitalization calculations saved us many hours of manual work over our old process.
What do you dislike about the product?
The visibility into HOW Jellyfish determines the allocation of FTE time isn't great, and can be confusing for auditors and new users of the system.
What problems is the product solving and how is that benefiting you?
Jellyfish solved our problem of needing to manually calculate capitalizable work time.
Useful if used appropriately
What do you like best about the product?
* summary metrics
* integration of Jira + Confluence + GitHub data
* integration of Jira + Confluence + GitHub data
What do you dislike about the product?
* can easily be used in superficial and short-sighted ways to equate developer output with developer impact
What problems is the product solving and how is that benefiting you?
Personally it is not solving a problem for me but I appreciate that the metrics are transparent to engineers
Streamlined and Insightful for Teams
What do you like best about the product?
I really like how Jellyfish makes complex project tracking feel simple. The dashboards are clear, and it’s easy to see where priorities and resources are aligned. It helps connect strategy to execution without feeling overwhelming.
What do you dislike about the product?
The reporting can sometimes feel a little rigid if you want to customize things deeply. It’s great for high-level visibility, but drilling into very specific use cases occasionally takes extra effort. I’d also love to see more integrations with other tools we use day-to-day.
What problems is the product solving and how is that benefiting you?
better view for team analytics
Jellyfish Review
What do you like best about the product?
I like the ability to see what has impacted a sprint and when one of my developers might have struggled to complete work during a spting.
What do you dislike about the product?
I wish data updated real time for thing like sprint metrics, and open pull requests
What problems is the product solving and how is that benefiting you?
We use jellyfish to analyze project health, sprint velocity, and performance of our engineering team
Best in business tool for engineering managers
What do you like best about the product?
The integration with Jira and our git repositories is seamless, bringing together and highlighting all the key data we need. The DevEx module, along with the ability to survey teams with extensive customization, has been particularly valuable. Slack alerts and team pulse features help keep everyone informed—even those without a Jellyfish login—by surfacing any tickets that are stuck. The daily digests provide insights into what is slowing the team down, enabling us to investigate issues and improve our processes. Allocation metrics reveal how much time is spent on bugs or specific components, which helps guide prioritization discussions and supports more accurate estimates. Additionally, the individual metrics and interaction data are useful for facilitating performance discussions with engineers.
What do you dislike about the product?
The permissioning and data privacy settings in Jellyfish are too rigid, making it difficult for my boss to grant granular access to non-managers. For instance, we are unable to provide our tech lead with a team-specific view without also exposing individual performance data for everyone, which is not ideal.
What problems is the product solving and how is that benefiting you?
Performance management, team prioritization and planning, identifying blockers and slow-downs.
Great tool for team tracking
What do you like best about the product?
I appreciate its team pulse feature, which helps in reviewing stuck pull requests and tickets.
What do you dislike about the product?
Jellyfish lacks integration with the Outlook calendar.
What problems is the product solving and how is that benefiting you?
I use this to track my time, which makes it easier for me to generate reports when needed. It helps in tracking bug to feature ratio to analyze where the issue lies, either with requirements or implementation.
infra work in jellyfish needs some work
What do you like best about the product?
I like the general overview that is given across the various jira projects. It allows me to dig into who might be overcommited and on what they are stuck working on.
What do you dislike about the product?
Since I manage multiple jira projects it would be nice to combine them into a singular overview.
Since one project is also jira service desk it would be helpful to have some ability to map tags to investments. otherwise it appears that service desk work doesn’t really map to anything.
Since one project is also jira service desk it would be helpful to have some ability to map tags to investments. otherwise it appears that service desk work doesn’t really map to anything.
What problems is the product solving and how is that benefiting you?
the ability to quickly and easily see team level metrics and then view how those metrics were contributed to by various team members.
showing 51 - 60