Jellyfish
JellyfishExternal reviews
425 reviews
from
External reviews are not included in the AWS star rating for the product.
Seamless Jira Integration, Powerful Progress Tracking
What do you like best about the product?
I find Jellyfish very helpful for tracking progress on a weekly, monthly, and quarterly basis. It gives me a clear picture of my work contributions over time. The integration with Jira is fantastic, as it makes it easy to see what I'm working on and how my efforts are distributed across different areas, including tracking the AI impact within the team. I also appreciate the Individual Summary option in Jellyfish, which provides a clear, consolidated view of my work, making it easy to understand my contribution, progress, and impact over time. Additionally, the initial setup of Jellyfish was easy, smooth, and straightforward.
What do you dislike about the product?
I feel one area that could be improved is tracking AI power users over time. Currently, I am only able to see the most recent data, but it would be very helpful to have visibility into AI power users on a weekly, monthly, or quarterly basis.
What problems is the product solving and how is that benefiting you?
I use Jellyfish to track my work and overall progress. It helps me with weekly reporting, understanding Jira tickets I've worked on, and tracking AI impact. The Jira integration gives great visibility into open issues, PR changes, and commits.
Visually Appealing But With KPI Challenges
What do you like best about the product?
I like using Jellyfish because it offers convenient tracking of my teams regarding the work accomplished and delivery KPIs. I particularly appreciate that it gathers all the necessary information in one place and integrates well with Jira and GitHub. Also, I find its interface easy to use and its graphics very beautiful. The 1:1 discussion section is relevant because it provides ideas on questions to ask employees during their meetings.
What do you dislike about the product?
The KPIs with the sprints really don't work well. We have bi-weekly sprints and the numbers are not reproducible. This causes a breakdown of trust with the managers. Also, the initial setup requires an adaptation of the processes, which has led many teams to have to change their Jira workflow.
What problems is the product solving and how is that benefiting you?
I use Jellyfish to track my teams' work and obtain delivery KPIs. It centralizes information, creating a link between Jira and GitHub.
Fantastic UI, Needs Holiday-Adjusted Metrics
What do you like best about the product?
I like that Jellyfish has a really cool UI. In my profile, it shows everything related to AI Impact and Jira ticket details like how much time I have a ticket assigned to, and the number of pending tickets. It has a section related to Jira called 'Open assigned issues' which shows the ticket assigned to me and for how long. Additionally, it integrates with GitHub so I can easily track the PR raised and the number of comments on PR. The initial setup was also pretty easy.
What do you dislike about the product?
I have an issue with how it calculates power users for AI apps during public holidays. It doesn't account for public holidays, so if it's a holiday and we don't use the AI app, the overall percentage goes down regardless of it being a holiday.
What problems is the product solving and how is that benefiting you?
I use Jellyfish to spot which users aren't efficiently using their company licenses. Its cool UI and integration with Jira and GitHub help me track assigned tickets, PRs, and comments easily.
Streamlined Project Planning with Intuitive UI
What do you like best about the product?
I like the simplicity in Jellyfish's UI and the intuitive features, such as tracking the weekly items I've completed. The Activity page is particularly helpful because it consolidates all the activities I've been working on in a single sprint in one place, so I don't have to search through multiple pages and reports. Also, once I got accustomed to the tool and its features, it became very helpful.
What do you dislike about the product?
I noticed a little bit of friction initially to get the details about Jellyfish.
What problems is the product solving and how is that benefiting you?
Jellyfish helps identify sprint commitments and achievements, providing all activities in one place without navigating multiple pages, thanks to its simple UI and intuitive features.
Actionable Engineering Insights with Seamless Integration
What do you like best about the product?
It gives great visibility into team performance without feeling like micromanagement.
The dashboards are clean, easy to understand, and actually useful for decision-making.
I appreciate how it integrates smoothly with existing developer tools.
It helps identify bottlenecks early and improves planning accuracy.
Overall, Jellyfish makes engineering insights actionable and transparent.
The dashboards are clean, easy to understand, and actually useful for decision-making.
I appreciate how it integrates smoothly with existing developer tools.
It helps identify bottlenecks early and improves planning accuracy.
Overall, Jellyfish makes engineering insights actionable and transparent.
What do you dislike about the product?
Jellyfish can feel complex to navigate, especially for new users.
Some reports and metrics lack flexibility and customization.
Integration setup can be time-consuming and not always intuitive.
Some reports and metrics lack flexibility and customization.
Integration setup can be time-consuming and not always intuitive.
What problems is the product solving and how is that benefiting you?
Jellyfish helps make engineering work more visible and easier to understand.
It connects data from different tools and puts everything in one place.
This makes it easier to track progress without constantly asking teams for updates.
It helps identify bottlenecks early before they turn into bigger problems.
Planning becomes more realistic because decisions are based on real data.
It improves alignment between engineering and leadership.
Teams can focus more on actual work instead of manual reporting.
It saves time by automating metrics and insights.
It brings clarity to priorities and delivery timelines.
Overall, it helps me make better, data-driven decisions with less effort.
It connects data from different tools and puts everything in one place.
This makes it easier to track progress without constantly asking teams for updates.
It helps identify bottlenecks early before they turn into bigger problems.
Planning becomes more realistic because decisions are based on real data.
It improves alignment between engineering and leadership.
Teams can focus more on actual work instead of manual reporting.
It saves time by automating metrics and insights.
It brings clarity to priorities and delivery timelines.
Overall, it helps me make better, data-driven decisions with less effort.
Efficient Ticket Tracking with Room for Improvement
What do you like best about the product?
I like using Jellyfish for tracking my tickets, PR reviews, PR merged metrics, and productivity metrics. I enjoy the ticket tracking feature. I also enjoy seeing my AI usage metrics, as it allows me to track how well I've used it. I can see how fast I solved my tickets using AI metrics.
What do you dislike about the product?
Even if I update the Jira ticket as closed, it takes quite some time to update in Jellyfish. Improving near real-time synchronization helps make task movement more accurate.
What problems is the product solving and how is that benefiting you?
I use Jellyfish for tracking my tickets, PR reviews, and productivity metrics. It solves ticket tracking, productivity metrics, and sprint review problems, helping me see how fast I solve tickets using AI metrics.
Effortless Insights Make Team Planning a Breeze
What do you like best about the product?
It gives a clear view of where the team’s time and effort are going, which makes planning easier.
I like how simple it is to understand insights without digging through complicated reports.
I like how simple it is to understand insights without digging through complicated reports.
What do you dislike about the product?
Some of the data takes time to update, so the insights aren’t always real-time.
A few parts of the interface feel a bit complex at first and need time to get used to.
A few parts of the interface feel a bit complex at first and need time to get used to.
What problems is the product solving and how is that benefiting you?
It helps bring all engineering work into one place, so it’s easier to understand what the team is focusing on.
It gives clearer visibility into priorities and effort, which helps with planning and explaining work to stakeholders.
It gives clearer visibility into priorities and effort, which helps with planning and explaining work to stakeholders.
Elevating how we manage our product portfolio
What do you like best about the product?
Jellyfish has strengthened our product organization’s ability to operate with data-driven decision-making. We can clearly see how our development and engineering work aligns to our investments and roadmaps to create better proactive tradeoffs and validation on what we should pursue.
What do you dislike about the product?
Would love to see more capabilities for product-led companies and the product leader’s perspective
What problems is the product solving and how is that benefiting you?
Predictable and reliable delivery rhythm, forecasting ability, identify misalignment between planned and actual work, validation of investments.
Efficient Data Insights, Needs Stronger Data Hygiene Tools
What do you like best about the product?
I appreciate how Jellyfish effortlessly captures and automates data signals, translating engineering activity into meaningful insights. This is particularly useful for my role as an Engineering Manager at Paylocity, as it provides visibility into productivity, project allocation, and areas needing improvement. The connection of data across Jira and GitHub offers a clear picture of where our team’s time and effort are focused, making the dashboards intuitive for tracking progress, balancing priorities, and spotting trends. This functionality eliminates the hassle of manually gathering data from various sources. I value how the dashboards facilitate more data-driven and transparent conversations with leadership. The automation of real engineering signals into meaningful metrics, rather than relying on manual reporting, gives me a real-time view of work progress and blockages, which in turn connects day-to-day engineering activities with strategic outcomes—something that would've been difficult to achieve otherwise. Another aspect I really like is the smooth setup process for integrating Jira and GitHub, with effective onboarding support from the Jellyfish team, ensuring quick start of generating insightful dashboards and metrics.
What do you dislike about the product?
I find that Jellyfish heavily relies on clean data from Jira and GitHub to generate accurate insights. If the data hygiene isn't consistent, the metrics can become misleading, making it difficult to trace where discrepancies originate or why certain metrics appear incorrect. Troubleshooting these issues is time-consuming, and Jellyfish lacks built-in tools to assist with identifying data gaps, suggesting corrections, or guiding teams towards better data configuration. Having additional flexibility to adjust or reclassify signals would make the insights more reliable and actionable, enhancing the platform’s overall effectiveness.
What problems is the product solving and how is that benefiting you?
I use Jellyfish to capture data signals for meaningful metrics, providing our team clarity on productivity and project allocation. Its integration with Jira and GitHub offers real-time views and facilitates data-driven decisions, saving time. However, reliance on data hygiene can skew insights without additional data validation tools.
Powerful Metrics and Planning, with a Learning Curve for New Users
What do you like best about the product?
Our team originally investigated Jellyfish for it's Software Capitalization capabilities, but found that it provides us with far more. We've been able to drastically reduce the amount of time our LT spends reviewing capitalization, and now have them using Jellyfish metrics (story point efficiency, velocity, cost and HC utilization) to better plan for future sprints and quarters. We're still working on getting our data to the point where we can wholly rely on Jellyfish for planning, but have seen material changes in where we spend our time and how we manage our teams and orgs.
What do you dislike about the product?
Jellyfish has lots of capability spread over many pages, and this means there's a bit of a learning curve for new leaders. Jellyfish is working on an AI assistant to help centralize collection of data, but it isn't ready quite yet. Once this is ready it will make our data easier to find and should allow us to ask questions that aren't on Jellyfish dashboards today.
What problems is the product solving and how is that benefiting you?
Jellyfish helps us in two ways-
1) We use it to accumulate Software Capitalization information. This allows us to amortize innovation spend in the current year which is useful for growing companies
2) We use it to provide us with Engineering metrics. We're able to see how much we're spending on new builds, how much time is going to maintenance work, and where we may need to support an individual or team. This helps us in real time as we encounter blockers in our projects and also helps us to plan for the future.
Jellyfish is including AI utilization metrics in their software but hasn't yet built it out for the provider we use. Once available we'll use it to understand how effective our org is at using AI tools.
1) We use it to accumulate Software Capitalization information. This allows us to amortize innovation spend in the current year which is useful for growing companies
2) We use it to provide us with Engineering metrics. We're able to see how much we're spending on new builds, how much time is going to maintenance work, and where we may need to support an individual or team. This helps us in real time as we encounter blockers in our projects and also helps us to plan for the future.
Jellyfish is including AI utilization metrics in their software but hasn't yet built it out for the provider we use. Once available we'll use it to understand how effective our org is at using AI tools.
showing 31 - 40