[Feature Request] Spend limit display misleading when set mid-cycle with pre-existing member accruals

Bug Description
Feature request: over-limit spend display looks alarming when a per-member spend limit is created mid-cycle.

In the org admin spend management page, setting a per-member spend limit after that member has already accrued spend this month produces a misleading display. The member's existing MTD spend is shown against the new limit with no context.

Example: a member had $28.56 MTD spend, an admin then set a $1 limit, and the row now effectively reads as ~2856% of the limit.

I understand the limit itself works correctly and only gates future usage, so this is probably not a huge issue. But honestly it was pretty scary to look at: I was shocked for a moment when it showed a member at over 3000% of their allowed limit, and my first thought was that the limit had failed or someone was massively overcharged. Maybe some kind of note about the spend predating the limit, or counting it differently, could have avoided that panic, but you folks would know best what fits here. Just flagging it as something worth a look when you get the chance. Thanks!

Environment Info

• Platform: darwin
• Terminal: tmux
• Version: 2.1.175
• Feedback ID: fc99603c-f6e3-4cc1-82d4-8fc3249e7c1b

Errors

[]