urn:noticeable:projects:K6f39qd01FaXwDzouVdHwww.treno.io2022-09-09T08:59:04.844ZCopyright © TrenoNoticeablehttps://storage.noticeable.io/projects/K6f39qd01FaXwDzouVdH/newspages/HqjciPyYJgAZ5TK4D0bi/01h55ta3gsa63vktkx4tnmqzvm-header-logo.pnghttps://storage.noticeable.io/projects/K6f39qd01FaXwDzouVdH/newspages/HqjciPyYJgAZ5TK4D0bi/01h55ta3gsa63vktkx4tnmqzvm-header-logo.png#058efcurn:noticeable:publications:icuUIM7gQQNw8agKoS0I2022-09-07T08:58:00Z2022-09-09T08:59:04.844Z

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

<p>We’re always working to improve Treno for your team. Here’s a few of the bugs we’ve crushed this week:</p><ul><li><p>Tag mapping rules now match your tags case-insensitively,</p></li><li><p>Custom field mapping rules now correctly match array values, such as <em>Components</em> in Jira,</p></li><li><p>And as usual, a variety of performance and security fixes.</p></li></ul>Brian Wolter[email protected]urn:noticeable:publications:TL1VDPiOuFLVhJQC0gMu2021-05-12T23:21:10.120Z2021-05-12T23:44:45.168Z

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

<p>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:</p><ul><li><p>If you were wondering why your <strong>Cycle Time</strong> or <strong>Coding Duration</strong> 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 <strong>squashed commit merges</strong>. But never fear, we’ve squashed that bug so you can continue to squash your commits.</p></li><li><p>The <strong>Team Members</strong> 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.</p></li><li><p>No, you’re not imagining things: the <strong>Review Outcome</strong> metrics really are gone. We’ve renamed them to <strong>Review Feedback</strong> to better describe what they’re measuring: the number of rounds of feedback left by individual reviewers on your Pull Requests.</p></li><li><p>We’ve also made a bunch of smaller improvements to the interface that you may notice here and there.</p></li></ul><p>As always, if you run into any problems, please let us know!</p>Brian Wolter[email protected]