Don't close all enhancement requests

[Kamik423]

• None of the other issue templates apply to this issue.

Multiple enhancement requests got closed without much discussion or justification. The rules also explicitly state that no duplicate issues should be created. I think this just frustrates people seeking the same enhancement and I think many people then also won't comment on said issue.

I think a wont-fix label and a justification would be more appropriate. Specifically I'd like to know why #12, #23 and #35 were just closed; I think there is some discussion to be had there. Additionally leaving them open and marking them as wont-fix makes it easier for other people to discover them. With them closed it will stifle any discussion around that issue; even if some conditions change to make it applicable again.

EDIT:

The treatment of #23 is particularly harsh, quite obviously did you not understand what the issue was actually about and closed it (twice!); you also did not engage when @cdraeger re-explained the quite valid point he had. This very much underlines the point I was making.

[alexcimander]

Hey @Kamik423, thank you for your feedback. First off you are right - the last months we where somewhat overwhelmed by the requests, ideas, critics and all other discussions going on. We learned from that and re-disscussed our Github-Ticket handling and we want to do better!

All topics you mentioned where brought to discussion and were not prioritized by the clients. We still have those tickets and todos in our backlog - so they are not forgotten. 🙏

I hope that you can understand that we are not able to share all details with you but please keep in mind: we hear you and we are trying our best to involve you and the whole community in the process of designing an app for everybody out there. Your feedback is always important and helps us to bring certain topics back to discussion. 👍

Thank you and all who are watching for participating. I will close this issue now (just joking).