More precise regression tracking

[brson]

@FraGag

Perhaps the branch name could be part of the milestone's name? For example: 1.20 (nightly), 1.19 (beta), 1.18 (stable). Then the older versions have no branch name at all (e.g. 1.17). When a release moves to a different branch, the milestones are renamed to update the branch name; when the stable version is replaced, the previous stable version loses its branch name.

Even with that though, you can't know what channel the version was on at the time any given issue was closed, which is what determines whether a backport is needed. For example if I put my issue on "1.20 nightly", fix the issue, then rename to "1.20 beta", I don't need a backport; but if I put my issue on "1.20 nightly", rename it to "1.20 beta", fix the issue, then I do need a backport.