Weighing efforts

a special set of labels 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 contributions 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 weighing efforts is generally unnecessary weighing efforts as described in this page is not necessary in the general case, as it will only marginally alter the reports in our experience, the volume of contributions and the tendency for any particular team to have homogeneous practices makes the approximation perfectly acceptable for decision making one scenario where this feature proves useful is when your team has uneven contributions with few large "product roadmap" contributions and many "technical work" contributions adding an effort label on the larger contributions will increase their relative importance and ensure that the accounted work surfaces unbiased in dashboards effort weight and task estimation while the effort label may ressemble the estimation that can be set on tasks in several ticketing systems, they serve different purpose estimation is an evaluation of the load prior to the work being realized, and used for planning purpose efforts labels are an observation of the load following the work being realized, and used for reporting purpose for this reason, the effort label is never be set automatically by echoes, which works with the assumption that which contribution took longer cannot be determined reliably values label meaning xs the effort required for this change was 5 times smaller than our average change (default value) s the effort required for this change was 2 times smaller than our average change m the effort required for this change is roughly average l the effort required for this change was 2 times greater than our average change xl the effort required for this change was 5 times greater than our average change note the default value is xs for pull requests because we observed that the most numerous pull requests also are the smallest ones indeed, we observed that the distribution of actually weighed pull requests is uneven so that the typical pull request is small when a few large pull requests weight a lot on the average toggling effort labels general case the effort labels are 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) jira 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