Update Bug Reports narrative to include user feedback/suggestions #1537

New issue

Closed

opened 2018-06-01 19:40:40 +02:00 by tzarebczan · 9 comments

tzarebczan commented

2018-06-01 19:40:40 +02:00

(Migrated from github.com)

The Issue

Updating the Bug Report functionality to include a feedback/suggestions narrative will allow users to submit recommendations/feedback through the app.

System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

## The Issue Updating the Bug Report functionality to include a feedback/suggestions narrative will allow users to submit recommendations/feedback through the app. ## System Configuration   - LBRY Daemon version: - LBRY App version: - LBRY Installation ID: - Operating system: ## Anything Else  ## Screenshots

Bentley912 commented

2018-06-05 13:58:38 +02:00

(Migrated from github.com)

Hey. Id like to take a stab at this.

I have a few questions. Am i adding a new function in the lbry-redux code and also making some changes to the /'/report' component? If so, I cloned the lbry-redux repo and did not find the Lbry.report_bug() in that code. Where is it in the code ?

To clarify: right now, the app calls Lbry.reportBug({message}) on submit. Is it necessary to be able to seperate the bug reports from the feature requests? If so, I am having trouble finding the Lbry.report_bug() function. It would be necessary for me to create a new function in the Lbry-redux code, something like request_feature(), but did a search and could not find the report_bug code.

Hey. Id like to take a stab at this. I have a few questions. Am i adding a new function in the lbry-redux code and also making some changes to the /'/report' component? If so, I cloned the lbry-redux repo and did not find the `Lbry.report_bug()` in that code. Where is it in the code ? To clarify: right now, the app calls Lbry.reportBug({message}) on submit. Is it necessary to be able to seperate the bug reports from the feature requests? If so, I am having trouble finding the Lbry.report_bug() function. It would be necessary for me to create a new function in the Lbry-redux code, something like request_feature(), but did a search and could not find the report_bug code.

tzarebczan commented

2018-06-05 15:01:42 +02:00

(Migrated from github.com)

@Bentley912 we plan to eventually replace the Lbry.report_bug call (this is actually in the lbrynet-daemon, not in redux) so it's okay to reuse the same form/call for this request at the moment. So it's mainly just wording that needs to be adjusted in a few places.

Thanks for taking a shot at this!

kauffj commented

2018-06-05 15:35:44 +02:00

(Migrated from github.com)

@tzarebczan if we're going to work on this I'd really like to kill lbry.report_bug as it shouldn't exist.

Do we want these to go straight into the help desk?

@tzarebczan if we're going to work on this I'd really like to kill `lbry.report_bug` as it shouldn't exist. Do we want these to go straight into the help desk?

tzarebczan commented

2018-06-05 15:39:09 +02:00

(Migrated from github.com)

@kauffj we discussed using the helpscout api in the ticket here: https://github.com/lbryio/lbry-app/issues/1078

But regardless of how it's sent, I think these changes are separate.

@kauffj we discussed using the helpscout api in the ticket here: https://github.com/lbryio/lbry-app/issues/1078 But regardless of how it's sent, I think these changes are separate.

Bentley912 commented

2018-06-05 16:08:53 +02:00

(Migrated from github.com)

Ok. So, for now, I'll just change the language up a bit. When we get all that straightened out, Ill implement the helpscout from the API. Cool?

kauffj commented

2018-06-05 16:36:54 +02:00

(Migrated from github.com)

Sounds good, thanks and welcome @Bentley912!

🎉 1

Bentley912 commented

2018-06-05 16:57:15 +02:00

(Migrated from github.com)