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