### Summary

<!--
Please briefly describe what part of the code base needs to be refactored.
-->

### Improvements

<!--
Explain the benefits of refactoring this code.
See also https://about.gitlab.com/handbook/values/index.html#say-why-not-just-what
-->

### Risks

<!--
Please list features that can break because of this refactoring and how you
intend to solve that.
-->

### Involved components

<!--
List files or directories that will be changed by the refactoring.
-->

### Intended side effects (optional)

<!--
If the refactoring involves changes apart from the main improvements (such as
a better UI), list them here. It may be a good idea to create separate issues
and link them here.
-->

### Missing test coverage (optional)

<!--
If you are aware of tests that need to be written or adjusted apart from unit
tests for the changed components, please list them here.
-->

### Links / references (optional)

<!--
E.g. related issues and merge requests, external resources.
For relations to other issues in Gitlab, please use the standard Gitlab format
'group/project#issue_number' to allow easy automatic linking.
-->

### Issue Planning (for developers only)

<!-- Projected start date for handling this issue. -->

StartDate: 2020-04-01

<!-- Expected completion date for this issue. -->

DueDate: 2020-04-01

<!-- Issue impact, 1 (lowest) to 10 (highest). -->

/weight 1

<!-- Estimate of total time needed to solve this issue. -->

/estimate 2d 5m

<!-- Time already spent on this issue. -->

/spend 5m

<!-- Labels to add to this issue. Use ~"Short Term" for planning. -->

/label ~enhancement, ~"Long Term"
