Push prioritization data to GitLab Issues
This is part of the prioritization pilot #1563 (closed)
Problem To Solve
If the prioritization data is confined to only Sisense, there is less of a chance that PMs will check it regularly. We need to push the prioritization data back into GitLab issues so that PMs can sort lists and boards by priority ranking.
Tasks
-
Determine labeling system that maps Cost of Delay / Duration into some finite amount of ranges that can be mapped to a scoped label set and automatically applied/updated on a given issue.
Edited by Gabe Weaver