This is exactly what I think. Most managed projects do that, because when a project grows it gets a forum. Small projects can use issues for discussion.
IMO the goal should not to purge issues for the sake of purging issues, the goal should be that active issues are issues worth reading. If an issue is tagged a bug by a developer, it’s deemed to be worth the time to read it -until it is fixed by a code change (closed), or it’s reevaluated as not a bug (untagged), or it’s closed because other code changes have made the bug irrelevant (closed as obsolete).
One always can read and search closed issues, but by default it should be a waste of time.
either they have been asked questions, or they have deliberately ignored the issue template. I’d not hesitate as tagging an issue as needed user input in this case (except some very exceptional cases like this one: "duplicati" org on Docker Hub is going to go away · Issue #4906 · duplicati/duplicati · GitHub).
For standard ‘I’m asking for help’ issue, why asking another time what is the Duplicati version when it was already asked in the issue template ? They know that getting details right is necessary. The delay is because people are not always available and can be busy with their life. If they are very busy but still want to do a proper answer, they can post a comment saying so, it will avoid issue closing.
If I have gotten the github action right, they will be exempted as it should be (IMO of course). If a developer (or a triager) has deemed an issue an enhancement, it is interesting to read and should not be closed automatically. Removing the tag ‘user info needed’ is nice but not necessary.