Updates

April 15: Scoping, Macro Trends & More πŸ“ˆπŸ“Š

Kan Yilmaz
June 24, 2020

April 15: Scoping, Macro Trends & More πŸ“ˆπŸ“Š

We've been hard at work improving our Dashboard's usability to help you not only identify trends but understand what may have caused certain issues to appear.

Before we get into that, a quick note...

‍

πŸ™ Sorry for the latest push πŸ™

  • This morning at 1:30 AM Pacific yesterday, we launched an update to our Macro Trends dashboards which caused discrepancies in Cycle Time and Throughput for some users. This was resolved at 11:34 PM Pacific time. They were caused by timezones handling issues which resulted in lower Throughput and higher Cycle Time for ~25% of our users.
  • We've fixed the issue and will be addressing the root causes over the next few days. We are sincerely sorry for problems we may have caused for your team during this time.

‍

πŸ”Ž Better Scoping πŸ”Ž

Want to see trends for a specific team, project or member? What about how you did this sprint? Well the wait is over.

We've just launched flexible scoping so you can explore every combination of repositories, teams and members to find the trends you're looking for. You can also see how the past 2 weeks compares to your average!

‍

‍

πŸ‘€ Enhanced Discovery πŸ‘€

You probably have a few weeks where you wonder..

"Why was Throughput so high?"

"Cycle Time was excellent that week. What were we working on again?"

Our new Macro Trends pages allow you to click on any date range straight from the graph! Explore what happened during your good/bad weeks to understand what impacts your teams performance.

‍

‍

‍

πŸ“‰ Macro Trend Analysis πŸ“‰

Sometimes it's tough to figure out how your team is doing this month compared to their average. We added a few indicators to help with that. Go to any Macro Trend page and select the date range you care about. You'll be able to see how you did during that time against your 6 month average.

‍

‍

‍

⚠️ Metrics Update: Throughput ⚠️

Some users felt that our Throughput calculation wasn't capturing "Work Completed" as accurately as we could. We agreed. Since then we've made an adjustment to how we're calculating your Throughput.

Old Throughput:

Throughput == PRs Closed + PRs Merged

New Throughtput:

Throughput == PRs Merged

‍

‍

‍

πŸ“° Product Updates Page πŸ“°

We're always hard at work improving Haystack based on your feedback. We felt that users should know what we're up to so we created a public Product Updates Page so you can follow along with progress! Check in here if you want to see any new features or fixes we've added.

‍

πŸ•· Bug Fixes πŸ•·

  • Migrated high compute macro trends calculations to server-side for faster rendering
  • Fixed timezone handling bug that caused discrepancies in Macro Trends metrics
  • Fixed "Weekly Email" scheduler for more consistent delivery times

‍

πŸ’‘Improvements πŸ’‘

  • Add Pull Request "state" to the Contributor Timeline. Β Hover over any Pull Request to see if it's open/merged/closed.
  • Added "Created At" and "Completed At" to Pull Request Table
  • Added unit tests for core metrics to improve metrics stability

‍

⏰ In Case you missed it ⏰

  • 🚨Private Beta Closed - We closed our Private Beta on April 7th. Onward and upward!
  • βš™οΈRegex support - If you'd like to ignore certain Pull Requests from your metrics like "WIP" or "dependabot", send an email to support@usehaystack.io and we can add Regex Filters to remove these pesky Pull Requests

‍

Kan Yilmaz
CTO & Co-Founder of Haystack

Our latest news

Discover our latest articles, feature releases, and more!

Ready to get started?

Start Free Trial