Default Priority isn't honored

[claytonsource]

With the introduction of Priority schemes, I would have expected some means of editing the default scheme to choose the default priority.  Even though the screen shows that a specific priority is default, the edit screen for all issue types shows the first priority as preselected from the list.

The only workaround I've found is to create a new scheme with the default priority as the top priority.  It doesn't appear to matter whether the default property is set to the desired priority or none.  It always preselects whatever the top priority happens to be.  

After creating the new scheme, I have to manually add every project (all 300+ of them) to the new scheme.  

I know there is a dark feature that is suppose to turn on editing of the default scheme, but this appears to have no impact on our environment.  The edit button never appears for the default scheme.

I'm hoping that this has been fixed in future releases of Jira Server; though no mention of any changes appear in the release notes.

Has anyone else found a work-around?

References: 

Enable default scheme editing via dark feature - https://jira.atlassian.com/browse/JRASERVER-66660

Our priority order is:

Highest, High, Medium, Low, Lowest, Unassigned (With Unassigned showing as default on the scheme page.

With the workout and manually changing the scheme for every project in our environment, the priority order is:

Unassigned, Highest, High, Medium, Low, Lowest (With No default selected since the behavior appears to be to default to the first priority in the list.)

Update: Our current version is 7.13.8.  Couldn't change it on the ticket once submitted.