Closing Bugs without a solution in tracker

So people are reporting bugs and they get closed without a real solution / proper comment to why it is getting closed.
And before you start flaming about we do it all for free, yeah we report the bugs for free aswell and want to improve the for free experience for everyone here.

some examples:

https://tracker.playphoenix.online/issues/0d9d3495-f3c3-4aa7-8c99-7e4c79b01dae (closed without addressing issue)
https://tracker.playphoenix.online/issues/97d97735-e70f-43e7-9926-4a83c6910e22 (set to resolved, but still being an issue)
https://tracker.playphoenix.online/issues/81159a3f-09e9-4e27-b546-25ef3014caa9 (closed without comment)

Just don't see why to report bugs when they are not fixed anyways?

Sun 11 Aug 2019 9:33 AM by

gruenesschaf

mze wrote: ↑
Sun 11 Aug 2019 9:05 AM
So people are reporting bugs and they get closed without a real solution / proper comment to why it is getting closed.
And before you start flaming about we do it all for free, yeah we report the bugs for free aswell and want to improve the for free experience for everyone here.

some examples:

https://tracker.playphoenix.online/issues/0d9d3495-f3c3-4aa7-8c99-7e4c79b01dae (closed without addressing issue)
https://tracker.playphoenix.online/issues/97d97735-e70f-43e7-9926-4a83c6910e22 (set to resolved, but still being an issue)
https://tracker.playphoenix.online/issues/81159a3f-09e9-4e27-b546-25ef3014caa9 (closed without comment)

Just don't see why to report bugs when they are not fixed anyways?

1 was closed as it's not a bug, when a mob starts to cast it will complete even if the target goes out of los, out of range or into normal stealth. Your comment mentions vanish, that is something entirely different there casts should be cancelled, open an issue for the pets where that is still the case. Necro, bd minions and other pets are sufficiently different that one can have the buggy behavior whereas the others don't and vice versa.

2 was assumed to be resolved due to a change that forced the target to clear, it's possible that this is either the same bug still or something else. Report it again if it's still an issue

3 was closed as it's not a bug, however, it's likely that it'll be changed anyways

Sun 11 Aug 2019 11:15 AM by jelzinga_EU

I understand that sometimes it is difficult to understand what's going on on the player's end and what is happening inside the dev his mind when he closes a report, however the latter could be resolved by explaining why a report is closed.

For example, if you take the third report as an example, if you consider it not a bug but do want to change it (perhaps) in the future, you could simply state it "not a bug currently = feature, perhaps a future change" and then set it to a status not closed but to a "For future version".

Assuming it is not only a bug-tracker but also a feature-request issue-database...

Sun 11 Aug 2019 11:30 AM by

gruenesschaf

jelzinga_EU wrote: ↑
Sun 11 Aug 2019 11:15 AM
Assuming it is not only a bug-tracker but also a feature-request issue-database...

That's kind of the thing. It's basically meant as bug tracker only, however, we weren't really consistent there and some things that actually are change requests are still in there and now with our request to put the reskin stuff in there as an issue it's probably fair to say: it depends :p

The main reason we don't want to have feature requests in there is that many ideas might seem like good ideas, however, they really aren't. For that reason there is the suggestion forum. Anything that receives no feedback or pretty much only negative feedback probably isn't that great an idea and as such would just pollute the backlog making it harder to find bug reports.