This bug will most likely be fixed with the branch upgrade UI of 2.2.6 (the code to indicate "needs upgrading" already exists, but is not available in the UI just yet)
This bug will most likely be fixed with the branch upgrade UI of 2.2.6 (the code to indicate "needs upgrading" already exists, but is not available in the UI just yet)