I completely understand why you see this as a 30-min fix, and therefore they should just knock it out.
That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed.
The question becomes this: at what point is fixing this issue more valuable to the company than any other issue the same dev could work on?
And the answer is possibly "never", depending on what high-impact bugs, features, or technical debt they have on their priority list.
That's not how they would likely see it. If their devs are 100% utilized (which I'm sure they are), then fixing any issue -- even a 30-min one -- is going to mean that a different issue is delayed.
The question becomes this: at what point is fixing this issue more valuable to the company than any other issue the same dev could work on?
And the answer is possibly "never", depending on what high-impact bugs, features, or technical debt they have on their priority list.