Explanation of "Won't Fix" for bug reports?

Unity Engine
1

I got a response to a bug last night (1175627) that kind of puzzled me. The response was:

My impression of “Won’t Fix” is that this is a dead-end for issues, with no expectation that the issue will ever be worked, because Unity doesn’t believe it’s important enough to work on. But the response referred to “nearest future”, with more pressing issues “at the moment”.

So I’m curious if this is a dead issue, never to be looked at again? “Won’t Fix” implies dead forever to me, but the language of the issues implies that it could be looked at the in future. If so, is there a different status for this kind of issue to not give the impression that it will never be worked?

2

It might mean it is thrown to the bottom of the backlog instead of simply closed. But even closed bugs can be reopened and fixed if a dev or QA team member has it in for this bug and won’t shut up about it.

Working in QA, I’ve unilaterally reopened closed bugs several times and made my case for why the priority was wrong and it really needs fixing. Sometimes I’ve won in that, sometimes it gets closed again.

2 Likes
3

It more or less means, wait a couple of months and resubmit the bug if you still care about it and try to make your case.

Edit: Also often times it might mean “we plan to re-write the whole feature sometime in the future, so there is no point in wasting time trying to fix the old codebase”

2 Likes
4

I’m not sure that sufficiently explains why some bugs remain in this state for years. E.g. https://issuetracker.unity3d.com/issues/ui-elements-position-changes-after-entering-and-exiting-play-mode

5

In that specific case, I have this theory that Unity people start hiding when they hear the words “Editor GUI”.

2 Likes
6

The editor’s GUI has had a significant amount of work behind the scenes since 5.x. File a new bug report if it is still an issue.

7

It is. Thanks for the feedback guys, I’ll submit a new bug report.