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.

This article will go through how you can get accurate data for your team whilst engineers are moving from one team to another.

To configure precise calculations, go to the Teams page and click on the gear button for that specific team. You should see a page like the one below.

By default, each member will have Joined At and Left At fields as empty. This means all the pull requests of that member will be included inside the team. You can configure these fields by pressing the gear button.

If both Joined At and Left At fields are set, Haystack will only include pull requests that were opened between these dates when filtering by the team. Haystack will still show all pull requests when nothing is filtered (AKA organization view).

If Joined At the field is set but Left At is empty, Haystack will count only pull requests that were opened after Joined At date. Any future pull requests will be included in the teams' metrics.

If Left At the field is set but Joined At is empty, Haystack will count only pull requests that were opened before Left At date. Any future pull requests will not be included in the teams' metrics.

By using these settings, Haystack allows you have a more accurate team view.

If you require further assistance, contact [email protected] or chat with us through the chatbot. We have helped 100+ engineering leaders track this data, and would be happy to share our expertise.

For further information on configuring teams, check the following pages: