Tag mapping rules now match your tags case-insensitively,
Custom field mapping rules now correctly match array values, such as Components in Jira,
And as usual, a variety of performance and security fixes.
Tag mapping rules now match your tags case-insensitively,
Custom field mapping rules now correctly match array values, such as Components in Jira,
And as usual, a variety of performance and security fixes.
This update is available for all accounts today. Please reach out to your Treno contact for more information.
]]>This update is available for all accounts today. Please reach out to your Treno contact for more information.
]]>We’ve launched an update to add support for integrations with self-hosted and on-premise development tools. Our engineers will work with your IT and InfoSec teams to get your Treno workspace up and running in no time.
This update is available for all supported integrations today.
]]>We’ve launched an update to add support for integrations with self-hosted and on-premise development tools. Our engineers will work with your IT and InfoSec teams to get your Treno workspace up and running in no time.
This update is available for all supported integrations today.
]]>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.
]]>If you were wondering why your Cycle Time or Coding Duration metrics weren’t looking quite right, you weren’t alone. A bug relating to how the commit timelines used by these metrics was constructed had issues with squashed commit merges. But never fear, we’ve squashed that bug so you can continue to squash your commits.
The Team Members metric now reports the maximum count for period-over-period comparison instead of the average count. The maximum more accurately describes what this metric is measuring.
No, you’re not imagining things: the Review Outcome metrics really are gone. We’ve renamed them to Review Feedback to better describe what they’re measuring: the number of rounds of feedback left by individual reviewers on your Pull Requests.
We’ve also made a bunch of smaller improvements to the interface that you may notice here and there.
As always, if you run into any problems, please let us know!
]]>If you were wondering why your Cycle Time or Coding Duration metrics weren’t looking quite right, you weren’t alone. A bug relating to how the commit timelines used by these metrics was constructed had issues with squashed commit merges. But never fear, we’ve squashed that bug so you can continue to squash your commits.
The Team Members metric now reports the maximum count for period-over-period comparison instead of the average count. The maximum more accurately describes what this metric is measuring.
No, you’re not imagining things: the Review Outcome metrics really are gone. We’ve renamed them to Review Feedback to better describe what they’re measuring: the number of rounds of feedback left by individual reviewers on your Pull Requests.
We’ve also made a bunch of smaller improvements to the interface that you may notice here and there.
As always, if you run into any problems, please let us know!
]]>