Nov 2: πŸ«‚ Detailed Settings for Team Members, Commit Without Pull Request, Risk Trends πŸ«‚

Julian Colina
November 2, 2021
  • toc-h2
  • toc-h3
  • toc-h4
  • toc-active

πŸ“’ EngProd Guide πŸ“’

One of the key advantages of using Haystack is that we have the economies of scale to know what works best across the industry. We leverage these insights to help build our product and to help you, our customers, build elite engineering teams.

The EngProd Guide contains our independent research and analysis into what works for building elite engineering teams. We have now begun to open-source the material in this guide, allowing you to access these carefully curated insights on proven strategies for how the best engineering teams operate. This guide complements the material already in our blog and product help centre.

You can access this guide by visiting engprod.guide in your web browser. Reach out to us if there's any material you'd like to see in this guide which we haven't already made available.

πŸ«‚ Detailed Settings for Team Members πŸ«‚

Engineers sometimes move from one team to another. It is therefore important to be able to attribute work (i.e. Pull Requests) to the team they were working on at that particular time.

We've updated our teams page to contain Joined At and Left At fields allowing you to set your teams more accurately, giving you much more actionable insights.

For more information you can read our article on precise calculation of team members.

⚠️ New Risk: Commit Without Pull Request ⚠️


The biggest risks are sometimes the most hidden ones. Commits pushed directly to the master branch, without a pull request, risks of lower quality.

Now Haystack allows you to visualise and drill-in to this risk. You can check Risks page to see if there is any hidden code being pushed without a second eye reviewing it.

πŸ“ˆ Risk Trends πŸ“ˆ


It's not about raw numbers, it's about being better than before, it's about trends.

We've added trend graphs for your teams risks. Trends for the following risks are added:

  • Commit without pull requests
  • Large pull request
  • High cycle time
  • Merge without review
  • Too many cooks
  • Too many discussions

You can access risks trends from Metric Hall page.

πŸ’‘ Improvements πŸ’‘

  • Added branch and label filters
  • When using Git Tag deployments, regardless of the person being in a team or not, it'll show in deployment pages
  • Free users notifications now require minimum Startup plan
  • Slack app permissions reduced

πŸ•· Bug Fixes πŸ•·

  • Fixed bug where auto-sync on repositories would not remove repository
  • Fixed bug where updating a team would duplicate team members
  • Fixed bug where deployments would not show if the member was not in a team causing confusion

⏰  In case you missed it  ⏰

  • πŸš€ New Backend, Faster Dashboard πŸš€ - We wanted to support users by iterating faster while maintaining fast query speeds. With this refactor, Haystack will be more reliable and iterate at a much faster pace.
  • πŸ›  Drilldown Deployments πŸ›  - We have added support to drilldown into Deployments and Hotfix Deployments.
  • πŸ— Improving Change Failure Calculation πŸ— - Failure rate calculation is now more accurate.
  • πŸ”„ Auto Repository Sync πŸ”„ - We added an 'Auto Sync' feature to automatically sync your Github Repositories into Haystack.
  • πŸ”„ Auto Team Sync πŸ”„ - We added an 'Auto Sync' feature to automatically sync your GitHub Teams into Haystack so you can use Github Teams as your 'source of truth'.
  • πŸ“° Product Page - Keep up to date with feature releases here!


About the author

Julian Colina
CEO & Cofounder of Haystack.

Our latest news

Discover our latest articles, feature releases, and more!

Ready to get started?

Start Free Trial