Copyright © Trenohttps://validator.w3.org/feed/docs/rss2.htmlTreno Product Updateswww.treno.iohttps://www.treno.io/?utm_source=noticeable&utm_campaign=treno&utm_content=other&utm_id=K6f39qd01FaXwDzouVdH.HqjciPyYJgAZ5TK4D0bi&utm_medium=newspageenFri, 09 Sep 2022 08:59:04 GMThttps://noticeable.io[email protected] (Treno)[email protected] (Noticeable Team)https://storage.noticeable.io/projects/K6f39qd01FaXwDzouVdH/newspages/HqjciPyYJgAZ5TK4D0bi/01h55ta3gsa63vktkx4tnmqzvm-header-logo.pngTreno Product Updateshttps://www.treno.io/?utm_source=noticeable&utm_campaign=treno&utm_content=other&utm_id=K6f39qd01FaXwDzouVdH.HqjciPyYJgAZ5TK4D0bi&utm_medium=newspagehttps://storage.noticeable.io/projects/K6f39qd01FaXwDzouVdH/newspages/HqjciPyYJgAZ5TK4D0bi/01h55ta3gsa63vktkx4tnmqzvm-header-logo.png#058efcicuUIM7gQQNw8agKoS0IWed, 07 Sep 2022 08:58:00 GMT[email protected] (Brian Wolter)This Week in Bugfixeshttps://treno.noticeable.news/publications/this-week-in-bugfixesWe’re always working to improve Treno for your team. Here’s a few of the bugs we’ve crushed this week:

  • 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.

]]>
We’re always working to improve Treno for your team. Here’s a few of the bugs we’ve crushed this week:

  • 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.

]]>
Bugfix
suAih1qAwUAxhN578ugPMon, 29 Aug 2022 08:40:00 GMT[email protected] (Brian Wolter)Treno Observationshttps://treno.noticeable.news/publications/treno-observationsTreno can now automatically analyze your team’s data and identify performance issues, anomalies, and trends that may need investigation—and push these observations right to your team’s Slack as soon as they’re discovered! This is a major step forward for engineering performance observability and we can’t wait for you to start seeing what Treno’s automated, proactive analysis can reveal.

This update is available for all accounts today. Please reach out to your Treno contact for more information.

]]>
Treno can now automatically analyze your team’s data and identify performance issues, anomalies, and trends that may need investigation—and push these observations right to your team’s Slack as soon as they’re discovered! This is a major step forward for engineering performance observability and we can’t wait for you to start seeing what Treno’s automated, proactive analysis can reveal.

This update is available for all accounts today. Please reach out to your Treno contact for more information.

]]>
New
aAaz4M22dxQFy3QgFM8TWed, 17 Aug 2022 09:52:00 GMT[email protected] (Brian Wolter)Self-hosted and On-prem Integration Supporthttps://treno.noticeable.news/publications/self-hosted-and-on-prem-integration-supportIf your team self-hosts some or all of your development tools—like Jira, Github or Gitlab—we’ve got great news for you: Treno now supports your setup!

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.

]]>
If your team self-hosts some or all of your development tools—like Jira, Github or Gitlab—we’ve got great news for you: Treno now supports your setup!

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.

]]>
New
1cg5LegTvmtmIXV93dXrWed, 10 Aug 2022 09:25:00 GMT[email protected] (Brian Wolter)Improved Developer Contributor Countshttps://treno.noticeable.news/publications/improved-developer-contributor-countsIt turns out that some of you have a lot more non-developer accounts in Github than we imagined! We can certainly see why–Github is a great product that can facilitate all kinds of workflows. But it also meant we needed to reconsider how we count your developers.

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.

]]>
It turns out that some of you have a lot more non-developer accounts in Github than we imagined! We can certainly see why–Github is a great product that can facilitate all kinds of workflows. But it also meant we needed to reconsider how we count your developers.

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.

]]>
Improvement
vuGVxWbWCPmgHxt60ZbMWed, 03 Aug 2022 10:57:00 GMT[email protected] (Brian Wolter)Improved Support for Integrationshttps://treno.noticeable.news/publications/improved-support-for-integrationsIt’s no secret that development processes vary considerably from team to team. So we’re always working to improve Treno’s ability to capture and model the unique ways that your company does things. Today we’re releasing a few of these updates to our integrations:

Improved Deployments Mapping for Teams and Projects

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.

New Support for Classifying Data by Tags or Custom Fields

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.

]]>
It’s no secret that development processes vary considerably from team to team. So we’re always working to improve Treno’s ability to capture and model the unique ways that your company does things. Today we’re releasing a few of these updates to our integrations:

Improved Deployments Mapping for Teams and Projects

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.

New Support for Classifying Data by Tags or Custom Fields

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.

]]>
Improvement
uxvmRUBpfZ5LiBtRa3hXSat, 29 May 2021 16:54:00 GMT[email protected] (Brian Wolter)Custom Dashboards & Tagshttps://treno.noticeable.news/publications/custom-dashboards-and-tagsTired of looking at that wall of one hundred metrics searching for the five you care about? So were we. That’s why we added Treno’s new Dashboard functionality. Now you can navigate to the Dashboard tab within any Project, Team, or your entire Workspace to easily see the metrics you care most about.

Slice Metrics by Tag

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.

]]>
Tired of looking at that wall of one hundred metrics searching for the five you care about? So were we. That’s why we added Treno’s new Dashboard functionality. Now you can navigate to the Dashboard tab within any Project, Team, or your entire Workspace to easily see the metrics you care most about.

Slice Metrics by Tag

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.

]]>
NewImprovement
TL1VDPiOuFLVhJQC0gMuWed, 12 May 2021 23:21:10 GMT[email protected] (Brian Wolter)This Week in Bugfixeshttps://treno.noticeable.news/publications/this-week-in-bugfixes-2021-05-12What better way to break in our new product update page than with a bunch of bugfixes? We couldn’t think of one, so here they are:

  • 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!

]]>
What better way to break in our new product update page than with a bunch of bugfixes? We couldn’t think of one, so here they are:

  • 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!

]]>
Bugfix