[Meta] Where is the best place to report non-support issues? (UX feedback, bugs, etc). What about a public issue tracker?

I ask because I imagine having all of the feedback and little bugs mixed in with tech support could be a real issue, but I can't seem to find an alternative forum section for them. Where should I place them?

Would the dev team ever consider a public issue tracker ala ArmA's use of their 'DevHeaven' platform? (https://dev.withsix.com/projects/cis) There were so many little bugs that the community could enter directly into the tracker - it enabled a level of interaction and a volume of input that I think would otherwise be difficult, and allowed the community to see if people agreed / the devs noticed.

(Hell, I logged some issues/suggestions that made it in to the final game and remain there to this day - better covering fire / bounding overwatch for infantry, and more consistent landing orientation for helicopters. These would've been lost in a forum, but are definite 'improvements' albeit rather small).

This would also make it possible to log lots of individual, independent issues - on a forum I imagine it'd be encouraged to submit multiple bugs in one post, but I may well discover them as I go, requiring lots of edits to the original post and making it all hard to track.

It's just a thought - I want to submit quite a volume of UX, UI, and tech feedback over time, but don't have any real way to do it.

30,010 views 10 replies
Reply #1 Top

Right, that's a little disappointing. A dedicated way to leave lots of feedback, with version info, hardware, etc, would be awesome. 

And yep, I imagine it would be gated by login details rather than being totally public, if it was to ever happen :)

Reply #2 Top

I don't understand - I'm responding to your criticism of the idea by saying that in that hypothetical, it would be founders only. 

Reply #3 Top

Right now posting to the Founders forum is the best way to do it. It's private and available only to Founder's purchasers.

Reply #4 Top

Quoting The_Gear, reply 6

Right now posting to the Founders forum is the best way to do it. It's private and available only to Founder's purchasers.

Makes sense, although it's not really a good platform to drill down into individual bugs, repro steps, any necessary attached files, etc. I'm currently sitting on a few pages of bugs and individual bits of UI/UX feedback that I've written down, but I'd hardly dump that into a single thread. I can't imagine keeping track of all of them and their conversations that way, especially with edits!

I PMed Frogboy about this issue - just hoping it didn't get squshed under whatever crazy volume of messages he must receive on here! :)

EDIT: It sounds like I'm holding bug reports hostage, but it's more that I can't find a way to reliably input this information, and that can be frustrating. 

Reply #5 Top

As it's still early, the forum posting will work for now. After we get a bit further contacting support/forum posting will be the best option. Support so we can gather your data and compile it with any other data we have. Since things can change rapidly this early, keep an eye on your list for things if they change/fix/get removed.

+1 Loading…
Reply #6 Top

Quoting The_Gear, reply 8

As it's still early, the forum posting will work for now. After we get a bit further contacting support/forum posting will be the best option. Support so we can gather your data and compile it with any other data we have. Since things can change rapidly this early, keep an eye on your list for things if they change/fix/get removed.

Yepp, that makes sense. Some of the points are UX/UI feedback rather than bugs, however, so they might not be addressed in the same way that those bugs would. It's not my place to speculate on the UX iteration process currently in place, though - I am but a fresh pair of eyes with some appreciation for such feedback when on the other end :)

Reply #7 Top

Quoting HateDread, reply 9


Quoting The_Gear,

As it's still early, the forum posting will work for now. After we get a bit further contacting support/forum posting will be the best option. Support so we can gather your data and compile it with any other data we have. Since things can change rapidly this early, keep an eye on your list for things if they change/fix/get removed.



Yepp, that makes sense. Some of the points are UX/UI feedback rather than bugs, however, so they might not be addressed in the same way that those bugs would. It's not my place to speculate on the UX iteration process currently in place, though - I am but a fresh pair of eyes with some appreciation for such feedback when on the other end :)

:thumbsup:  Excellent! We appreciate it here and I'd be happy to check things out when you post.