Jellyfish Reviews

My main use case for Jellyfish is that it has helped us save several hours of work each month for leaders. It incorporates detailed metrics that give us an idea about how the scrums can be improved and boost team performance.

A specific example of how Jellyfish helped my team save hours or improve scrums is that it gives us a holistic picture of data collected from various systems, regardless of the tech stack teams use. It is superior to other vendor products available in terms of customization, offering organization when necessary.

Jellyfish can collect data from various development teams and provide analysis without intervention.

Jellyfish has positively impacted our organization as it helps us grow our team efficiency at work. The documentation is excellent to start working with the product.

It helped my team grow efficiency through its easy setup, which takes time to learn, but is overall easy to use once you get the hang of it.

In my opinion, the best features Jellyfish offers are data collection, its lightweight nature, and the wonderful Jellyfish team.

When I mention data collection, Jellyfish stands out in that it can collect data from various development teams and provide analysis without intervention, helping us to make data-driven decisions easily. It is very lightweight, easy to configure, and provides accurate intelligent predictions. The Jellyfish team is wonderful, knowledgeable, and practical in resolving our queries on time.

Jellyfish provides a very excellent and intuitive user interface that helps to understand where time is being spent across our organization and is integratable with other platforms and software we use daily.

To improve Jellyfish, I suggest adding the view on the return on investment, making it easy to identify waste within our processes. It is a great way to see engineering overall results and measure.

Sometimes understanding the metrics is not simple. I also believe they should keep improving the user interface.

The individual developer metrics are not very useful and make the interface feel cluttered, which is an improvement that Jellyfish needs.

I have been using Jellyfish for five years.

Jellyfish is stable and has been reliable for our organization.

Jellyfish's scalability is good, as it handles our growth effectively.

The customer support is very responsive and proactive, and I have had good experiences with their support team.

I previously used Jira software, GitHub, and GitHub.

My experience with pricing, setup cost, and licensing is that everything was excellent, straightforward, and the cost is very cost-effective compared to other alternatives.

I have seen a return on investment as it is easy to set up and a great tool. It is a great tool because it is easy to identify waste within our process.

Before choosing Jellyfish, I evaluated other options such as Miro.

My advice to others looking into using Jellyfish is that I really recommend using it. If this is something your company is looking for, definitely give it a try. The Jellyfish team is also very responsive and supportive while updating, changing, or modifying required data. Having metrics from different tools in one place is very useful, especially when you have several engineering teams. I would rate this product a 9 overall.

In my work, I mostly use Jellyfish to provide clear visibility into my work, eliminating the need for manual tracking. The simple dashboard has been able to make it easy for me to understand performance trends quickly. It is incredibly useful because it helps me identify delays in testing or review cycles, which helps me improve consistency and also maintain accountability. The setup was straightforward with smooth integration of tools such as Jira and GitHub, and it was easy to start using. Switching to Jellyfish from more manual tracking methods made the performance tracking more structured. I appreciate the contribution while using it alongside other tools such as GitHub, Jira, and CI/CD pipelines.

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

Jellyfish has positively impacted my organization by helping us gain visibility into our information in a way we could not 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, which eliminates the guesswork.

The best features Jellyfish offers include clear visibility, integration capabilities, and its intuitive interface.

Regarding integration and the intuitive interface, I love the ability to integrate data from tools such as Jira and GitHub, where it simplifies tracking and productivity and project allocation. The intuitive interface and the actionable insights help my team to identify bottlenecks and improve performance, and it also makes it very easy to use, even for non-technical users.

I love the visibility which Jellyfish provides, and I also love the dashboards, where they make it easy to identify delivery risk and understand where teams are spending their time and discuss trade-offs without manually consolidating information from multiple sources.

The biggest issue I have with Jellyfish is how it attributes work done by engineers as AI-assisted work. It is really making a guess based on whether there are AI signals the day that they do appear, which is not really a great determination in my opinion.

The dashboard provides strong visibility, but it can sometimes feel a bit complex or dense when trying to drill down quickly into QA-specific insights. More customizable or role-focused views would make it easier to surface what is most relevant without extra filtering.

I have been using Jellyfish for two years.

I did previously use a different solution, as I switched from LinearB because I needed a great platform that is very easy to use and also cost-effective, and a tool that is very easy to use for both the engineering and also the data team.

I have seen a return on investment with Jellyfish, as prior to it, I manually tracked my developers' time spent on epics each month. This included calculating the cost associated with each epic and determining what was capitalizable versus non-capitalizable. Jellyfish automatically calculates the cost for me by interfacing with Jira, computing the FTEs for each epic. This has saved me a lot of time, saved me at minimum a day during my close processes.

My experience with pricing, setup cost, and licensing for Jellyfish is manageable and quite fair.

Jellyfish has been very helpful, especially before I had to go to disparate systems. I had to go to disparate systems such as Jira, GitHub, and LinearB to get data to understand my engineering team's performance. Now I can go to Jellyfish to have those data and metrics aggregated under the platform to understand the team's and organization's performance.

Regarding Jellyfish's AI capabilities, I think its governance and security are handled in an accurate and very secure manner, as the AI insights built within the product take the heavy lifting of evaluating data of the user. I find the accuracy and reliability of output to be very accurate and reliable always.

I would rate Jellyfish ten out of ten.