Weights are not explained well enough
Problem
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". With the introduction of ~"Portfolio Management" weights will become more important.
We are currently not doing a good job of explaining what weights are. Especially as they will/can be of value to both devs/team leads/upper management.
Proposal
Introduce a way similar to "time tracking" that explains what weights are and how they are intended to be used.