We’ve launched an update that allows you to choose which teams should have their members counted as developers for the Total Contributor Count metric. This lets you count exactly the right people and avoids skewing metrics that use your contributor count due to the inclusion of non-developer users.
This update is available for Github, Gitlab and Bitbucket connections today. Please reach out to your Treno contact if you would like any assistance making configuration changes to your connections.
]]>We’ve launched an update that allows you to choose which teams should have their members counted as developers for the Total Contributor Count metric. This lets you count exactly the right people and avoids skewing metrics that use your contributor count due to the inclusion of non-developer users.
This update is available for Github, Gitlab and Bitbucket connections today. Please reach out to your Treno contact if you would like any assistance making configuration changes to your connections.
]]>Deployments are now better associated with the teams and projects that caused a deploy to happen. This is done by making smarter use of already available relationships and mappings to create associations for deployments.
It is now possible to classify data from your integrations as a Bug, Tech Debt, or Innovation based on its tags or custom fields values. This gives Treno even more flexibility to model the world exactly as your company sees it.
]]>Deployments are now better associated with the teams and projects that caused a deploy to happen. This is done by making smarter use of already available relationships and mappings to create associations for deployments.
It is now possible to classify data from your integrations as a Bug, Tech Debt, or Innovation based on its tags or custom fields values. This gives Treno even more flexibility to model the world exactly as your company sees it.
]]>And while you’re setting up those Dashboards, you might be interested to try Treno’s new Tag support for metrics. Now you can slice metrics to view and track the subset of events that relate to a particular Tag on the original item, such as an issue in Jira or a Pull Request in Github. If you use the same Tags across all your delivery tools, Treno can follow these concepts across your entire development process.
]]>And while you’re setting up those Dashboards, you might be interested to try Treno’s new Tag support for metrics. Now you can slice metrics to view and track the subset of events that relate to a particular Tag on the original item, such as an issue in Jira or a Pull Request in Github. If you use the same Tags across all your delivery tools, Treno can follow these concepts across your entire development process.
]]>