feat: change discord link to feedback form

ONEARMY / community-platform

A platform to build useful communities that aim to tackle global problems

https://platform.onearmy.earth

MIT License

1.14k stars 386 forks source link

feat: change discord link to feedback form #3717

Closed benfurber closed 3 months ago

benfurber commented 3 months ago

PR Checklist

[x] - Commit messages are descriptive, it will be used in our Release Notes

PR Type

[x] New feature (non-breaking change which adds functionality)

Description

This changes the current button (that's on every page) that goes to discord to a quick feedback form using retool.

I think it's best to keep it super simple atm, see the quality of the feedback we get and improve from there.

Git Issues

Closes #3716

benfurber commented 3 months ago

@davehakkens The form can be editted here: https://onearmy.retool.com/forms/editor/Reporting/CP%20-%20Feedback%20Form

benfurber commented 3 months ago

Also. Un-hide the button on mobile/tablet - worth checking it looks ok so have added a preview to review.

github-actions[bot] commented 3 months ago

Visit the preview URL for this PR (updated for commit 8985714):

https://onearmy-next--pr3717-feat-3716-add-feedba-0xh5068f.web.app

_{(expires Fri, 02 Aug 2024 08:45:36 GMT)}

_{🔥 via Firebase Hosting GitHub Action 🌎}

_{Sign: 6d65e4f8fee2f6ab2da0c1c3b85b8797d66afa59}

cypress[bot] commented 3 months ago

2 failed tests on run #5910 ↗︎

Details:

feat: change discord link to feedback form
Project: onearmy-community-platform	Commit: `89857145ea`
Status: Failed	Duration: 08:03 💡
Started: Jul 2, 2024 2:29 PM	Ended: Jul 2, 2024 2:37 PM

howto/write.spec.ts • 1 failed test • ci-chrome

View Output Video

Test		Artifacts
[How To] > [Create a how-to] > [By Authenticated]		`Test Replay` `Screenshots` `Video`

settings.spec.ts • 1 failed test • ci-chrome

View Output Video

Test		Artifacts
[Settings] > [Focus Community Builder] > [Edit a new profile]		`Test Replay` `Screenshots` `Video`

Review all test suite changes for PR #3717 ↗︎

davehakkens commented 3 months ago

Nice to use retool for this @benfurber to keep it simple

Who do you imagine screening/sorting the feedback? dev team/moderators?
Would it be possible to add a label per instance? So we know from which instance the feedback comes in
Agree with @pizzaisdavid in the issue that 'Report a problem" would be better wording
Not sure sure about mobile. The button is quite prominent there, but not a strong opinion on it. Also up for trying.

benfurber commented 3 months ago

@davehakkens

Screening: Dev team
Label per instance: I've changed url to auto-populate, do you think that does the trick?
Updated wording
Mobile: Trying a smaller versioin, what do you think?

davehakkens commented 3 months ago

Nice. Yes all good to me, the auto url approuch is even better! But doesnt work here unknown, but perhaps due to test environment.

benfurber commented 3 months ago

Nice. Yes all good to me, the auto url approuch is even better! But doesnt work here unknown, but perhaps due to test environment.

Hhmmm, I was hoping that the preview branch would have that set the config field correctly... I'll have another go.

benfurber commented 3 months ago

@davehakkens In fact I'm confident enough I've got the full url that I've locked the field (if the page loads with a url provided as a param).

onearmy-bot commented 3 months ago

:tada: This PR is included in version 1.196.0 :tada:

The release is available on GitHub release

Your semantic-release bot :package::rocket: