Some developers you have are awesome and take the time to understand the issue and then there are some who close the issue without discussing it with the original poster. For example, I don't understand why the issue: RSRP-286713 was marked as "Won't Fix" and CLOSED so quickly. The developer decided there is no problem and marked it as "Won't Fix" and CLOSED the issue. I know this is a bug because that is not how it worked in R#5.
(1) I really wish that since I am taking the time to write a YouTrack issue then the developer can give time to read the issue and think about it before saying "Won't Fix" and CLOSING it. He has to give me a good reason why he won't fix it and discuss it with me and if we both agree then the issue should be marked appropriately. It shouldn't be immediately marked as "Won't Fix" and CLOSED.
(2) I'll admit that if the developer has a good reason then he shouldn't fix it but in this case he doesn't have a good reason and in many other cases I have seen the same thing. I think a manager should review any MANUALLY USER SUBMITTED issues that aren't going to be fixed in the 6.1 update and make sure he agrees with the developer that this isn't a problem.
Otherwise, why am I bothering to write and report the issues to developers that don't really take the time to think about the issues I see?