The following is a comprehensive guide for using Groomba.
A Groomba team contains your team's estimation participants and settings for how you want to estimate issues.
In team settings, you can configure:There are two commonly used fields in Jira for estimation: Story Points and Story point estimate, case sensitive.
This is a legacy field, but you may work with Jira projects that use it. By default it is available for Story and Epic issue types in classic projects. You can edit your settings to make it available for all issue types, even in next-gen projects.
This is a default field (locked) in Jira. You cannot delete this custom field. This is the default when you enable the Backlog and Estimation features in a next-gen project.
You can select any Jira issue to estimate, as long as you have access to that issue in Jira. The selected issues will start polling in your team channel with the settings configured in /groomba settings
Note that you can use /groomba ISSUE-1 to bypass any backlog settings you set up in your team settings. This means, for example, you can poll Bug type issues even if you have Bug type issues explicitly disabled in your Backlog Settings.
There are several possible results of a poll.
This is the best result -- your story has been assigned a point value in Jira that is based on an average of your team's votes.
This adds an impediment in Jira -- the issue will not be polled automatically again until that flag is removed in Jira. The common meaning of a flag is that not all information is available to estimate.
This is "We shouldn't do this poll right now". Currently, this pushes your issue to the back of a virtual queue containing the first ~100 of your backlog issues.
This transitions your issue to "Done" or an equivalent resolution in Jira.
After the poll has concluded, there are several options to follow up on the results.
You can also poll for a Jira issue again by typing /groomba ISSUE-1
If your Jira backlog has unrefined issues, estimate polls for those issues will arrive as messages. Just click the buttons to vote. Defer means “let’s punt” or “let’s not estimate right now”. An issue is automatically deferred if no one votes on it. If an issue is deferred, it will be surveyed again sometime later. Flag means “flag this issue in Jira”. If an issue is flagged, it won’t come up again until someone removes the flag in Jira.
These are settings are optional because you can choose not to automatically poll issues from a backlog. You can do this by setting your max backlog polling issue amount to zero (see Turning off auto-polling section.)
If you'd like to automatically poll from a specific set of Jira issues, you can pick any Jira filter that
contains the JQL you want for your backlog. For example,
description IS NOT EMPTY AND created >= startOfYear()
is a JQL statement that finds all issues
with a description and was also created this year.
Reminders are messages sent individually to users from the bot. In order to reduce the amount of notifications, we wait a certain amount of time to allow your team a chance to vote and to group polls together in a single message. Note that reminders will not be sent during your working hours configured in Scheduling Settings section.
Smart default remindersWith advanced averaging settings, you can choose how Groomba your averages votes. There are several factors you can change to give more conservative or less conservative estimates. Note that you are always free to re-estimate an issue after the polling concludes.
Smart default remindersThere is also a convenient method to Test your configuration with example point values.
When you create a team, Groomba picks smart defaults when your team will be polled, but scheduling settings allow you to customize this.
You can achieve this by first opening your team settings and then changing the selector for Maximum issues open from auto-polling backlog amount to zero.
You can get in touch with us easily with /groomba feedback or by emailing hello@groomba.ai
We are currently adding more ways to view and manage your teams, but right now the best solution is to run the command /groomba org
We deeply appreciate your support to keep the lights on and to keep offering innovative ways to save
developer time.
You can create or cancel your subscription by following the Stripe portal link. We will
also
perform manual changes on your account if you contact us via /groomba feedback or emailing
hello@groomba.ai