Multiple term membership price field option ignores terms in back-office

Create a price set with a radio button price field. Include a 2 term option for the General membership (screenshots attached).

When you use this price set in front-end contribution page, if the user selects the 2 term option the membership end date is correctly set to 4 years ahead. If you use it to create a membership in the backend - the '2' term property is ignored and the membership end date is only 2 years ahead.

I think this "might" be a RECENT regression as I'm pretty sure I tested this use case a week or so ago.