+1

I see "the oldest one" more like a guideline or preference than a hard rule. Sometimes there is another ticket with more or better information on the issue. It's a judgement call

The other technique I've used is to keep the additional issue open, but have the associated PR be purely a docs change. That was for https://bugs.python.org/issue30661, where changing the default behaviour in the tarfile module also changed the default behaviour in shutil. It doesn't apply for pure bug fixes though - only cases that call for a versionchanged entry in the documentation.

That would make the two possible resolutions be:

1. For multiple bug reports with a common underlying cause, choose the one that best reflects the underlying fault (often, but not always, the oldest one), mark the other issues as duplicates of that one, and then associate the PR and NEWS entry with the selected issue
2. If it seems appropriate to have more than one NEWS entry for multiple affected APIs, then some of the issues may be converted to documentation issues rather than being closed as duplicates