Team Versioning

Team Versioning provides the flexibility to view metrics based on how teams were structured during the selected time period, preserving historical accuracy.

By default, Hivel metrics reflect the current team configuration - meaning that past metric values are calculated based on today’s team structure, not how the team was structured historically.

---

🔍 Default Behavior (Without Team Versioning)

• Metrics are always calculated using the current list of authors in each team.

• If an author moves teams, their past contributions are still shown under their new team, not where they were when the work was done.

Example:

• Author A was in Team B from Jan to Feb.

• In March, Author A is moved to Team C.

• You view Team B metrics from Jan 15 – Feb 15: 👉 Without Team Versioning, Author A's contributions will not show under Team B (since they are now in Team C).

---

📦 Behavior With Team Versioning Enabled

With Team Versioning enabled, Hivel utilizes historical team structures to calculate metrics. This ensures each metric reflects which authors were part of a team at the time the work occurred.

Example:

• Author A is in Team B (Jan–Feb), then moved to Team C in March.

• You view metrics for:

  • Jan 15 – Feb 15: ✅ Author A's contributions appear in Team B metrics.

  • Mar 15 – Apr 15: ❌ Author A's contributions do not appear in Team B metrics, but are part of Team C instead.

---

Please Note: This feature is based solely on user movement across teams, rather than the actual teams themselves. If a team is removed from Hivel, all the associated versioning data will not be retained.

📌 Why Use Team Versioning?

We recommend using Team Versioning to:

• Analyze metrics accurately for historical team performance.

• Avoid misleading trends caused by team structure changes.

• Support performance reviews and retrospectives based on actual team dynamics at the time.

If you’re unsure whether Team Versioning is enabled or want to enable it, reach out to [e-mail].