using a second rank field on a board filter is incorrectly case sensitive, causing ranking to be disabled

Issue Summary

For environments that create a second global rank custom field (for example called 'Rank2'), it appears that there is a ranking check on the board that is incorrectly triggering a warning that in turn will prevent users from using that new rank field for drag and drop ranking on a board that is ordered by that rank field.

Steps to Reproduce

1. Create a new Global Rank Custom field (example name of Rank2)
2. Create a saved JQL filter for an existing JSW classic scrum project such that it tries to use this new field (example JQL of

   project=SCRUM order by rank2 ASC
   

   Note that this example refers to 'rank2' by lower case.)

1. Create a new board of type scrum, choose from saved JQL filter, pick filter saved previous
2. In the backlog of this new board, attempt to drag and drop the order of any issue in order to change it's rank2 value

Expected Results

Expect that rank2 value for that issue will be changed according to its relative position to other issues on the board

Actual Results

• Ranking does not happen to the 'rank2' field.
• Instead the end users sees this error message

  Ranking is disabled, as the Filter Query for this board is not ordered by ascending Rank. Please check your filter configuration.

• The filter the board is using should not be case sensitive for any JQL term being referred to here.
•  
• 
• 

Workaround

Changing the JQL saved filter from:

project=SCRUM order by rank2 ASC 

into:

project=SCRUM order by Rank2 ASC 

Then save that filter, and reload the board.  This will then allow you to rank issues using this new custom field rank value instead of the default rank value.