The effort dimension can optionally be used to influence the weight of a work item, such as a GitHub pull request or GitLab merge request. Echoes considers all changes to be equally weighted by default, which may not always be true. For example, a change may have taken just 1 hour of effort, while another was the focus of an entire week. This is where effort labels come in handy: they allow you to simply express the effort that went into a change with basic t-shirt sizing.
The effort required for this change was 5 times smaller than our typical change.
The effort required for this change was 2 times smaller than our typical change.
The effort required for this change is roughly average (default value).
The effort required for this change was 2 times greater than our typical change.
The effort required for this change was 5 times greater than our typical change.
Contrary to the other dimensions, the effort dimension is currently not configurable, and cannot be set as primary.
The effort dimension is not published by default to avoid cluttering your product development tools with labels that may not be used. To enable them on your GitHub or GitLab instance:
- Go to your integration settings (requires administrative rights on your Echoes accounts).
- Configure the installation for which you want to remove effort labels.
- Toggle "Effort labels" for this installation and save your changes. The corresponding labels will automatically be created or deleted by Echoes at the destination (the duration of the operation may depend on the number of repositories impacted).
An "Echoes - Effort" custom field is always created in JIRA: it is up to the administrator of the JIRA instance to add this field to the issue templates of your choice.