This section lets you fine-tune how task data is interpreted and displayed in your workspace. By customizing these rules, you can ensure that only relevant issues are considered, and your metrics accurately reflect your team’s workflow.

Exclude Tasks

The "Exclude Tasks" setting lets you filter out specific tasks from your metrics based on type or keyword.

Configuration Options:

• Ignore Type:
  • Issue Type: Select specific issue types (e.g., Bug, Task, Feature) to exclude from metrics.
• Keyword: Use keywords to exclude tasks. For instance, if tasks contain [DO NOT SCAN] in the title, enter the keyword to ignore such tasks.

How to Use:

1. Choose the ignore type (Issue Type or Keyword).
2. If using keywords, enter the phrase you want DevStats to ignore. Example: [DO NOT SCAN]

Exclude Subtasks

The “Exclude Subtasks” setting allows you to automatically remove all sub-issues (subtasks) from report metrics.

When this option is enabled, DevStats will ignore any issue classified as a subtask, ensuring that your metrics reflect only parent-level work items.

Configuration Option: Exclude Subtasks (Toggle):

• On: All subtasks are automatically excluded from metrics.
• Off: Subtasks are included and counted normally.

No additional configuration is required.

How to Use:

1. Enable the Exclude Subtasks toggle.
2. Once activated, all subtasks will be ignored across report metrics.
3. Disable the toggle at any time to include subtasks again.

Example:

• A parent issue with multiple subtasks will count as one item only in metrics.
• Subtasks such as implementation details, checklists, or supporting work will not affect throughput, cycle time, or other calculations when the toggle is enabled.

Custom Assignee Field

The "Custom Assignee Field" setting allows you to specify a custom field from Jira that represents the assignee of tasks in your workflow. By providing the field ID of the custom assignee field, DevStats can accurately map and manage task assignments in alignment with your team's workflow.

Why use custom fields?

This feature is particularly useful if your Jira instance uses a custom field to track task ownership, rather than the default assignee field. Configuring this ensures DevStats processes your data correctly, leading to accurate metrics and insights.

Configuration:

1. Locate the Field ID in Jira

• Go to your Jira project settings.
• Find the custom field used for task assignees.
• Note the ID associated with this custom field (e.g., 1042).

2. Enter the Field ID in DevStats

• Navigate to the Custom Assignee Field section in the Advanced Settings.
• Enter the custom field ID into the input box provided. Example: 1042

3. Save Your Changes

• Click the Save button to apply the custom field ID.
• DevStats will now use this field to map assignees in your tasks.

Notes and Tips

• Ensure Accuracy: The field ID must exactly match the one configured in your Jira project settings.
• Default Field Use: If you do not use a custom field, this step is not necessary, and DevStats will rely on the default assignee field in Jira.
• Validation: Double-check the field ID before saving to avoid errors in task mapping.

Configuring this setting ensures that DevStats can fully adapt to your Jira workflow and provide meaningful insights into task ownership and team performance.

Done Column

The Done Column setting lets you specify the appropriate column or status of your project management tool to define when a task should be considered "done."

Why configure a done column?

Different projects may use different names for the column that indicates task completion (e.g., Done, Closed, Completed). This setting ensures DevStats interprets the correct status across all your projects, providing accurate completion metrics.

Note:This setting only works when a project management tool is used as the data source (e.g., Jira or Linear).

Configuration

1. Open Project Configuration

• Navigate to the project you want to configure.
• Click on the project settings to open the configuration panel.

2. Select the Done Column

• Use the dropdown to choose the column/status that should be considered as "done".
• Example: Done, Closed.

3. Save Your Changes

• Click Save to apply your configuration.
• DevStats will now recognize tasks moved to this column as completed.