We’ve just dropped an improvement to the Health Checks capability: Rule Configuration!

What is it?

Prior to this release, the number of changes to due dates and sprints, as well as the in progress durations were hard coded and not able to be changed. While these were reasonable starting points, all teams work differently.

Not all rules have additional configuration. Look for the Configure Rule option for enabled rules.

The following rules can now be configured as below:

Due Date and Sprint Changes

You can now set the maximum number of changes allowed and whether to count changes to an earlier date / sprint. This works well for teams who look for opportunities to deliver sooner and adjust their tickets accordingly!

Otherwise, if this is not checked, this will count all due date / sprint changes that occurred while the sprint was in progress, except for where these are set for the first time.

Number of Times in Progress

This can be set to whatever number you like. Greater than zero.

Duration in progress

This is a behemoth one. You can now set a default maximum duration that applies to all issue types, as well as specific durations for each issue type configured on your Jira instance.

The general advice here is to:

• Set Bugs and Sub-tasks to 1-3 days
• Set Tasks and Stories to 7-10 days
• Set Epics from 4-6 weeks.

These are in line with the TicketCoach defaults but feel free to tweak to your heart’s content. That’s why we made this configurable!

Other changes

We also took the opportunity to address some feedback around selecting projects for inclusion. Prior, we only surfaced the Project key which is fine for uber power-user Jira neck-beards but not so much for normal humans.

Now you can search by, select and see the project names for projects when configuring TicketCoach.

How are we doing?

As usual, please provide feedback on how this improvement has helped you to get better value from TicketCoach or ideas for improving further!

Photo by Panagiotis Falcos