Jellyfish Reviews & Product Details

Its extensive integration capabilities allow it to pull data from Jira, GitHub, Slack, and other company channels, creating a holistic overview of engineering resource utilization. This information can then be connected back to company-wide initiatives, providing valuable insights.

Helps PM identifies bottleneck in the delivery across PM and engineering team.

Its very intuitive and easy to use Review collected by and hosted on G2.com.

What I find challenging about this is that, for it to be truly effective, it relies heavily on integration with other tools like Jira or GitHub. Additionally, its usefulness depends on people consistently following established processes. Without this, much of the dashboard in Jellyfish can end up being ineffective and inconclusive, which poses a significant challenge.

From tool perspective it has limited customisation option, so you have to changes your process to accommodate that. Its visual feel a bit outdated and there can be better filters Review collected by and hosted on G2.com.

Jellyfish gives unmatched visibility into how our engineering team’s time is spent across product development, tech debt, and unplanned work. It helps connect engineering effort directly to business priorities — something that was always difficult to quantify before. I especially like the Investment Allocation and Delivery Insights dashboards, which make it easy to communicate engineering impact to leadership in a clear, data-driven way. Review collected by and hosted on G2.com.

While Jellyfish provides powerful insights, the initial setup and data model configuration can be a bit complex — especially when integrating multiple Jira projects or custom workflows. Some of the reports take longer to load when dealing with large repositories, and custom dashboard flexibility could be improved. However, once everything is configured properly, the value it delivers easily outweighs the setup effort. Review collected by and hosted on G2.com.

What I find most compelling about Jellyfish is its ability to seamlessly integrate Git and Jira data into a coherent and easily understandable format. This amalgamation of data not only simplifies the complexities but also translates into actionable insights, allowing for a more informed decision-making process.

The straightforward setup of Jellyfish, coupled with an array of built-in features and opinions, distinguishes it from many alternatives. This user-friendly approach aligns with Jellyfish's philosophy, making it a practical choice for teams aiming to streamline their processes without unnecessary complications.

In essence, what I appreciate most about Jellyfish is its ability to turn complex data into actionable insights while maintaining a user-friendly interface and a commitment to continuous improvement. Review collected by and hosted on G2.com.

While Jellyfish has proven to be a valuable tool, there are a couple of aspects that could be improved upon.

Firstly, the customization and configuration process in Jellyfish is not as self-service as desired. The platform's opinionated nature, while promoting standardization across teams, comes at the cost of flexibility. This trade-off might not align with every organization's philosophy, as some may prefer a more customizable approach.

In summary, while Jellyfish excels in many areas, improvements in customization options and a more streamlined self-service configuration process would contribute to an even more seamless user experience. Review collected by and hosted on G2.com.

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

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

First, it's an easy and relatively intuitive tool to get acquainted with. I feel like a kid in a candy store exploring the different lenses through which I can view our work. It has made me very curious about the way in which we do work. As we become stronger with Jellyfish, we're able to ask better questions and experiment with our options, and we're able to see what comes of it very quickly! Second, the support has been outstanding. Andrey has been utterly patient as I pepper him with questions, and has consistently guided me to the answers I need. Third, Jellyfish University has been very helpful, especially the lessons that help with diagnostics. It's an excellent, effective resource and makes me feel like the Jellyfish team is invested in our success (which is very refreshing)! Review collected by and hosted on G2.com.

First, dislike is too strong a word. There's nothing I dislike - at least not yet!

The learning curve is real but again, the tool is intuitive and once you get a toe hold in even one aspect, additional understanding comes quickly if you put in the effort. (Isn't that just the nature of operations, though?) I'd also like to see roll-up reports to the executive level, and I'd like additional, diagnostics-oriented JF University training. For teams that have no history in observing how they work, it's a real necessity to help them understand that this is intended to be used by them (or their leaders, anyway) as an aid, and as a way to align, and yes, protect, their team. Our greatest challenge hasn't been learning the tool, but gaining traction internally. I would also like a report that shows who's logged in and who hasn't. Maybe that exists at the administrator level, but I suspect some of those complaining the loudest haven't spent much time in it.

I would also REALLY like to see more robust planning options to give teams better long-term insight into how realistic their plans are, especially with regard to pulling in dependencies. Review collected by and hosted on G2.com.

It is great to see an overview of the impact I'm having across projects. It helps project velocity for other projects and keep check on consistency. The UI is quite clear and easy to use to review relevant stats. I like that it integrates seamlessly with Jira which we use as our project management tool. While the data is valuable, I'm not frequently checking the dashboard as it does not affect my day-to-day work, but it definitely helps plan for new projects and recap our velocity of past projects. Review collected by and hosted on G2.com.

One stat that I find confusing/counter productive is the notion that all work (git commits) should be able to be attributed to a work item (jira ticket). I understand that this is needed from a reporting perspective, but in the real world it it often creates significant overhead for small changes to require creating a jira ticket just to "track the work". It would be awesome if somehow work without a jira ticket could be associated to a project by looking at the context/content of the work. Review collected by and hosted on G2.com.

I really like being able to check team metrics such as velocity and cycle time, which helps me identify trends early and adapt quickly. Jellyfish gives our team a clear, data-driven view of engineering investments and progress. It makes it much easier to align engineering work with company priorities and to communicate impact with leadership. I also appreciate the intuitive dashboards, which make complex development analytics easy to understand, and the Jira integration that saves time on manual reporting. Review collected by and hosted on G2.com.

While Jellyfish is powerful, there can be a learning curve at the beginning, especially when setting up integrations and customizing views. Some of the reports could offer more flexibility in filtering or drilling down into details. That said, the support team is responsive and actively improves the product based on feedback. Review collected by and hosted on G2.com.

Love the visibility the tool provides and how easy it is to use!!! We are able to look at each team more objectively. Each team has the same metrics, with some variance based on the way the teams work (scum, scrumban, kanban, etc) . I love that the tool keeps improving at a pretty rapid pace, and they are so welcoming of ideas and feedback to make Jellyfish even better! The support team is super helpful, and communicates well as they work to resolve issues. Review collected by and hosted on G2.com.

Sometimes the teams don't like the visibility.... Also, managers have a lot on their plate and may not be leveraging the tool as effectively as they can so I wonder if we are getting as much value as we could be (but that is on us, not JF). Review collected by and hosted on G2.com.

What I value most about Jellyfish is the impact it generates through its data. Recently, we conducted a general review of what it has meant to have this tool in our organization, and we reached a conclusion: "As Jellyfish grows, so do we." This phrase sums up the growth that has been brought to us by being able to understand the industry through the information Jellyfish provides us.

Today, we find great value in understanding how our investment is distributed, what the health of our teams is, and how to approach 1:1 conversations with our engineers by relying on frameworks like SPACE. All of this allows us to make higher-level decisions, guiding the organization towards measurable goals, always with the well-being of our collaborators at the center. Review collected by and hosted on G2.com.

As an opportunity for improvement, it would be valuable to have more options to build custom reports and to apply filters to metrics based on the configured work categories. Review collected by and hosted on G2.com.

Jellyfish offers excellent visibility into engineering operations by providing clear metrics around resource allocation, delivery performance, and team alignment with strategic initiatives. Its integrations with tools like Jira and GitHub make it easy to pull in data without any manual effort. The visual dashboards are intuitive and help stakeholders understand engineering productivity in a language that makes sense to both technical and non-technical teams. It’s especially useful for engineering leaders aiming to improve planning, track investments, and justify priorities across business units. Review collected by and hosted on G2.com.

While the platform is powerful, there’s a learning curve involved especially during the initial setup and dashboard configuration. Some customization options can feel limited unless you’re working closely with their support team. Additionally, depending on how your team structures Jira projects, data hygiene and tagging become crucial, which might require some internal process changes. That said, once set up correctly, the value becomes apparent. Review collected by and hosted on G2.com.