Im not sure where to ask for it, I hope its correct forum.
I want to know what is happening with the issue I did report 1,5 month ago (14.04.20).
Is it possible it was not checked yet? When I search issue tracker, there are issues with numbers like 1243277 and mine is 1237490 (assuming they are ordered), so was mine ignored? Cannot be reproduced? if so, then why it’s still open? Also I want to add that this is bug in 2019.3, so I see no reason why it would be low priority as this is not old version of unity.
Could someone explain what to do? Shall I wait or report it again?
When you report a software bug, when it gets fixed has pretty much nothing to do with when the issue was filed, but instead other factors.
Here’s what affects if/when a bug gets addressed
How serious is the issue to affected users, and is there a workaround?
An issue blocking using Unity with no work around is of course a higher priority than a trivial inconvenience you can easily work around
How many users are affected by this issue?
An issue affecting lots of users is going to be higher priority than an issue only a handful will ever see
Are any high revenue accounts affected by this issue?
Sometimes money talks, since even a trivial bug is likely to get a quick fix when a million dollar account threatens to cancel their subscriptions over it
Is the bug report clearly written and easy to understand?
Don’t expect much movement even on a serious issue if they can’t even understand what problem you are reporting
Is the issue reproducible using only the steps provided in the bug report?
If they can’t reproduce the issue it is almost impossible for them to fix the issue, so if you didn’t provide clear steps to reproduce the issue then you either hope QA figures out those steps or don’t expect a fix any time soon
Is this issue mooted by planned future feature development?
PM’s and the dev team will see a fix to a feature that is already planned to be replaced as a big waste of time, and will not want to fix the issue unless they feel they have to
Are there development resources available to address the issue?
If no devs who specialize in that feature are available, then the fix is less likely to come, since they would have to either pull someone off something that is already important, or train someone up on the feature just to address the issue
For example an issue which affects the majority of users, in which there is no workaround, was clearly reported, is reproducible by QA, and fixes a feature which is not already planned to be replaced, is very likely to get addressed almost immediately. Say for example all audio stopped working if there were more than 3 audio sources in the scene. That would affect most Unity users, a workaround of limiting your scene to 2 audio sources is not that practical, and they aren’t likely developing an entirely new audio system any time soon. So they would probably jump on that bug quickly.
An issue though which affects only a handful of users, no revenue impacting accounts, has a simple workaround, is difficult to reproduce because the bug report isn’t clear how to do so, and affects a feature which the dev team is already expecting to deprecate soon anyway, is very likely to never get addressed. Say for example you found an issue with the built in renderer’s deferred rendering path where at or above 240 FPS with HDR off you get a weird flicker effect with shadows when you have more than 30 point lights in close proximity. Well that probably is never going to get fixed, because it probably doesn’t affect many projects due to how specific the issue is, and the built in renderer is already planned to be going away sometime in the future.
Every other issue is going to be somewhere in between those two extremes, and will be addressed (if at all) based on where it lands. Not much to do with when the issue was filed.
May 14th of 2020 is just two weeks, not 1.5 months.
It happens to take more time to reply to certain bugs, depends on if they need to reach out to actual developers for answers or tests. If you don’t get an answer 1 month later then it worth to follow up though, it may fell through the cracks.
Yup, I understand there might be various reasons to postpone issue, but I am a bit surprised because it’s related to SerializeReference feature. I never reported any bug to unity before, so I don’t know what to expect and there is still no reply. If it’s normal to wait 2 months then it’s fine, but one and half month feel a bit long to get any response.
In this case I will maybe try again if I dont get any response for longer time.
, my bad.