Automate/Suggest initial weight assignment
Weights are an indication of how much work a certain issue will be. They can be seen as the equivalent of "story points" for ~"Portfolio Management".
Weight is currently used as a way for both project/team leads and developers themselves to correctly predict how much work an issue will require.
With the introduction of ~"Portfolio Management" weights will receive a third function. They will communicate to upper management how much work/resources a group of issues/an epic is going to require.
However as this layer of information requires that weights should be set for each individual issue, in order to get to an end result/combined figure, we need a way to automatise this.
This solution would essentially try to remove a layer of complexity or user input from receiving work estimation on epics. As a side effect this may help weighting on individual issues as well.
- Word usage
- Label assignment
- Related issues
We give a prediction of weight to an issue, which shows up whenever an issue has no weight assigned.
This is going to be an difficult issue based on fuzzy input, but with potential big return
Possible iteration/alternative idea's:
We can create a voting mechanism positioned at the bottom of the issue which asks user about what they think how much work this issue will take. The prediction is then corrected with that, showing the amount of votes for validity