In developer-speak it would be refered to as a Class C bug. To oversimplify:
Class A bugs are major problems, frequently involving either crashes, or _major_ gameplay problems. The really extreme ones in this category are refered to as "show stoppers."
Class B bugs are usually fairly serious problems, major graphical glitches, things that don't behave as they should, etc. These are distinct from Class A bugs in that they don't actually stop play, the game doesn't crash, or there are some annoying gameplay/graphic issues but you can continue on playing.
Class C bugs are minor things. There's a flicker when you switch from one screen to another, if you enter and exit the menu ten times the cursor changes color, or mispellings in the text.
The problem being described here is definitely a C bug. The programmers were probably walking into the office in the morning, and seeing a stack of ten or twenty A bugs, fifty or so B bugs, and quite likely 100 or more C bugs. Which do you think they're going to start on? (And this is _every_ day, fix two A bugs and a dozen B bugs today, and QA will have found just as many new ones for the next day)
Occasionally the head programmer or someone probably sorted through the bugs and assigned any class C bugs that would have been trivially easy to fix, but i don't think that rearanging a fair portion of the economics screen to fit that bit of information in would be judged very cost effective. Better to spend the time fixing one of the A class bugs.