Yes, right now. It was deemed as not important enough (by me and others on the team) as the user base it affected never used the functionality that was broken for them anyway and the users who did use this functionality were not affected by the issue at all. Now we are doing some changes to our overall environment setup and suddenly this same bug is going to affect all users who currently rely on the functionality.