Keep feature requests open, until they are implemented or rejected, reopen if needed

[aisbergde]

Feature request often are closed as so called "duplicate of ...". Often this is right. But often the focus is a bit different. And then it happens, that the related issue will be closed, not solving the original closed feature request. Or we are forced to mix up different things in a discussion, just because the developer, who closed the original request, did not realize, that these are different issues.

Duplicates should be duplicates. Related and duplicates are not the same. Often something is closed as duplicate, what is just related.

If we search and find closed issues and ask to reopen them, then normally(?) this doesn't happen.

What we get: a closed feature request for a not implemented but still required feature. And nobody is willing to reopen. Frustrating.

I would ask to keep feature requests open, until they will be implemented or really rejected. And it would be great, if they would be reopened, if someone asks to reopen and the request to open is reasonable.

Some "maybe we will do it, but in a bit different way" is understandable. But until this different way is not implemented, the feature request exists. Just to close it, because someone has something different on his virtual road map, is not the best way, to collect feature ideas.
Closing or rejecting with a clear explaining is fine and helpful on the other hand.