-
Notifications
You must be signed in to change notification settings - Fork 1.7k
SUPPORT SUPERDAY TASK: LOLU #33680
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SUPPORT SUPERDAY TASK: LOLU #33680
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
PR Summary
Added a new 'Report a bug' section to the support menu, providing a streamlined way for users to submit GitHub issues, though this may create inconsistency with the existing SupportModalButton implementation.
- Potential conflict between new GitHub button and existing
SupportModalButton
component which already handles bug reporting for cloud users - Consider leveraging existing
supportLogic
andSupportForm
infrastructure instead of direct GitHub links - Ensure consistent behavior between cloud and self-hosted instances by coordinating with the existing preflight-based conditionals
- Could benefit from integrating with the established severity level selection system from
SupportForm
1 file reviewed, 1 comment
Edit PR Review Bot Settings | Greptile
{/* Report a bug */} | ||
<Section title="Report a bug"> | ||
<p> | ||
Found a bug or issue? Help us improve PostHog by reporting it on GitHub where our | ||
engineering team can track and fix it. | ||
</p> | ||
<LemonButton | ||
type="secondary" | ||
fullWidth | ||
center | ||
to="https://github.com/PostHog/posthog/issues/new?template=bug_report.md" | ||
targetBlank | ||
className="mt-2" | ||
> | ||
Report a bug on GitHub | ||
</LemonButton> | ||
</Section> |
There was a problem hiding this comment.
Choose a reason for hid 8000 ing this comment
The reason will be displayed to describe this comment to others. Learn more.
style: Make sure to add a data-attr to the bug report button for analytics tracking, consistent with other buttons in the component.
{/* Report a bug */} | |
<Section title="Report a bug"> | |
<p> | |
Found a bug or issue? Help us improve PostHog by reporting it on GitHub where our | |
engineering team can track and fix it. | |
</p> | |
<LemonButton | |
type="secondary" | |
fullWidth | |
center | |
to="https://github.com/PostHog/posthog/issues/new?template=bug_report.md" | |
targetBlank | |
className="mt-2" | |
> | |
Report a bug on GitHub | |
</LemonButton> | |
</Section> | |
{/* Report a bug */} | |
<Section title="Report a bug"> | |
<p> | |
Found a bug or issue? Help us improve PostHog by reporting it on GitHub where our | |
engineering team can track and fix it. | |
</p> | |
<LemonButton | |
type="secondary" | |
fullWidth | |
center | |
to="https://github.com/PostHog/posthog/issues/new?template=bug_report.md" | |
targetBlank | |
className="mt-2" | |
data-attr="report-bug-github" | |
> | |
Report a bug on GitHub | |
</LemonButton> | |
</Section> |
@abigailbramble Please review |
Problem
Users currently need to navigate to GitHub manually to report bugs or issues they encounter while using PostHog. This creates friction in the bug reporting process and may result in fewer bug reports being submitted, which impacts product quality and user experience.
The support menu is the natural place users look for help, but it currently lacks a clear path for bug reporting, potentially leading to bugs being reported through less optimal channels or not reported at all.
Changes
LemonButton
that opens GitHub's bug report template directly in a new tabDid you write or update any docs for this change?
How did you test this code?
https://github.com/PostHog/posthog/issues/new?template=bug_report.md
)targetBlank
prop)https://github.com/user-attachments/assets/4be22356-9a2a-46e2-ad1e-3e1313bc0199
