> Is that the internal name Apple uses for bug reports?
Yes, but also all other types of progress tracking.
> why would Apple ignore radars like this?
The only Radars I've filed to other teams that actually got any traction are clear-cut bugs with a simple repro that don't require any UI/design changes to fix. Without a repro & sysdiagnose the engineers will likely never even read through the whole bug report before discarding it.
In general my view is that a lot of Apple engineers are stretched pretty thin and don't really have time to work on that kind of stuff with the pretty quick pace that a yearly OS release schedule imposes on them (supporting redesigns, new UIs, new hardware). If a bug is caught immediately it's considered a regression and there's a higher chance it'll get fixed, but issues that are around for >1 year without being flagged back to the engineers responsible are unlikely to ever be prioritized.
The most unlikely "bugs" to ever get fixed are design issues that aren't really considered bugs in the first place, like the FaceTime audio ducking issue I mentioned above. For reference, when you're on a FaceTime call the OS (both iOS and macOS) will heavily dampen all other audio to the point where it's pretty unintelligible even at 100% volume. There's no way to fix it because it's Working as Intended(TM) and the Apple designer knows what customers want more than you, the other engineers, or the customers themselves. It's been around for years and has had dozens of Radars filed internally and externally but no progress has been made.
Yes, but also all other types of progress tracking.
> why would Apple ignore radars like this?
The only Radars I've filed to other teams that actually got any traction are clear-cut bugs with a simple repro that don't require any UI/design changes to fix. Without a repro & sysdiagnose the engineers will likely never even read through the whole bug report before discarding it.
In general my view is that a lot of Apple engineers are stretched pretty thin and don't really have time to work on that kind of stuff with the pretty quick pace that a yearly OS release schedule imposes on them (supporting redesigns, new UIs, new hardware). If a bug is caught immediately it's considered a regression and there's a higher chance it'll get fixed, but issues that are around for >1 year without being flagged back to the engineers responsible are unlikely to ever be prioritized.
The most unlikely "bugs" to ever get fixed are design issues that aren't really considered bugs in the first place, like the FaceTime audio ducking issue I mentioned above. For reference, when you're on a FaceTime call the OS (both iOS and macOS) will heavily dampen all other audio to the point where it's pretty unintelligible even at 100% volume. There's no way to fix it because it's Working as Intended(TM) and the Apple designer knows what customers want more than you, the other engineers, or the customers themselves. It's been around for years and has had dozens of Radars filed internally and externally but no progress has been made.