This metric measures when issue cards are created. By default, the issue cards needs to be created by someone on the team roster to show up on this metric.  By using ‘include disabled users’ flag you can pull in users that did not create the card. 

Why should I measure Issue Creation?

Watching what types of items your team is creating over time can help you understand the struggles of your team. 

If you're logging a high rate of bugs, this can mean you need a tighter QA process. However, if you're only creating features, you may have a high performing team. Watch for major shifts here, and try to identify the causes.

What metric should I use in Allstacks?

We recommend starting with the ‘Issue Creation’ metric.

Under: Metrics > Team Productivity > Issue Creation

...

How It's Generated

We capture all issues created across all connected tools that provide issue management and log those by issue types.

General Filters

Use these filters to narrow down the information you want to see. After making any updates, make sure you click ‘update’ to have the changes reflect on the chart below.

...

TIP: Make sure to apply the changes you made to General Filters by clicking ‘Update’.

Chart Settings

You can use chart settings to format how the chart displays your data.  This is powerful when it comes to creating data visualizations to support the story you’re trying to tell.

...

This filter option ignores team roster set up, including users that are disabled. This is to ensure you include cards where the card creator may not be the current assignee or someone on your team.

Commonly Asked Questions regarding Issue Creation:

Q: Issue Creation metric is missing data. I’m not seeing everything I’m expecting to see?

...