Added a boolean flag to enable "one message, one thread" mode

[nzhuk]

This boolean flag disables sending of the token parameter, which forces the backend to create a new thread for each new feedback message.

It's especially useful for use cases where HockeyApp feedback is used by beta testers to report issues and bugs found in the app. Current "single-thread, multiple messages" mode is quite problematic since it makes it hard to track status of various issues being reported by testers.

This feature has been also requested in HockeyApp support forum, e.g.

• https://support.hockeyapp.net/discussions/problems/28975-single-feedback-thread
• https://support.hockeyapp.net/discussions/problems/55916-how-am-i-supposed-to-start-a-new-feedback-after-another

ping @anlinde

[msftclas]

Hi @nzhuk, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution! In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

[msftclas]

@nzhuk, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

[lumaxis]

Thanks for the contribution @nzhuk! We'll need some time to discuss this and see if we can merge this change like this. Some problems I see right now:

• We are aiming to achieve more platform parity in the future. So if we merge this here, we would need to support this in all of our SDKs. Android, tvOS, Mac, various flavors of Windows, Unity, Xamarin, etc. We don't make such a commitment lightly so this will need careful consideration.
• I also see some practical concerns: How does this work if a developer replies through the web interface to a certain feedback thread? Will this be shown to the user? Is this really useful without a user interface to navigate the different threads from the client side?

Thanks for your patience as we think about this!

[nzhuk]

Thanks for considering this, @lumaxis !

I could elaborate my use case a bit. We're using HockeyApp feedback feature in our testing builds. It works like this:

• User performs a special gesture, which opens the feedback view
• User can write problem description and tap "Send". Screenshot and all important logs are attached and sent to HockeyApp

Currently we don't provide any interface for the user to actually see any active discussion threads - this feature is used just for posting issues. Since we also know each user's email address, any further discussion between developer and issue reporter can be had via other channels (e-mail, Slack, Skype etc).

The major problem with current SDK is that if same user reports several issues, they all end up under the same feedback thread in HockeyApp web site, under the same title. This makes it impossible to use feedback thread states (Open, Waiting, Resolved, Closed etc) to track the status of each reported issue, since now status applies to all issues in that single thread.

[nzhuk]

Closing due to inactivity.