Report Bugs

Clear and responsible bug reports help us make YourSitee safer, more reliable, and easier to use.

​

What is a bug?

A bug is unintended or unexpected behavior that prevents an existing YourSitee feature from working as designed. Examples include:

• A button does not respond
• A widget disappears from the public Sitee
• Changes are not saved correctly
• A page displays incorrectly on a supported device
• A feature produces an unexpected error
• The dashboard and public Sitee show different information
• A reproducible action causes the website to stop working

A feature request is not a bug. Requests for new functionality, product changes, or design improvements belong in the #suggestions forum on Discord.

​

What can be reported?

The public bug tracker is intended for reproducible technical problems affecting websites and services operated directly by YourSitee, including:

• The YourSitee dashboard
• Public Sitees
• Widgets and integrations
• Account and profile features
• Analytics
• Appearance and layout
• Subscription-related interface problems
• Non-sensitive security issues
• Other unexpected behavior on yoursit.ee and its subpages

Documentation typos and feature suggestions are not considered product bugs.

​

Where to report a bug

​

Before opening an issue

​

Search existing reports

Check the existing GitHub issues before creating a new report. If the same issue has already been reported, do not open a duplicate. Instead, add a comment only when you can provide useful new information, such as:

• Additional reproduction steps
• Affected browsers or devices
• Screenshots or videos
• Error messages
• Console output
• A different page or feature affected by the same problem
• Information about when the problem occurs

Avoid comments that only repeat the original report or ask when the issue will be fixed.

​

Confirm that the issue is reproducible

Try the action again and note whether the issue happens:

• Every time
• Only occasionally
• On one device or browser
• Only while logged in
• Only on the dashboard or public Sitee
• Only with a particular widget, account, or configuration

If you cannot reproduce the problem consistently, describe what happened immediately before it appeared.

​

How to submit a bug report

​

How to write useful reproduction steps

Reproduction steps should allow someone unfamiliar with the issue to trigger the same behavior. Example:

1. Open the YourSitee dashboard.
2. Add a YouTube widget.
3. Save the Sitee.
4. Open the public Sitee in a new tab.
5. Wait a few seconds.
6. The YouTube widget briefly appears and then disappears.

Include any conditions that matter, such as:

• A particular browser or screen size
• A specific widget setting
• Whether the account uses Free or Pro
• Whether the issue happens after refreshing
• Whether the problem occurs in private browsing
• Whether browser extensions are enabled

​

Information to include

A complete report should generally contain:

• A clear and descriptive title
• The affected YourSitee feature or page
• A detailed description
• Exact reproduction steps
• The expected result
• The actual result
• How often the problem occurs
• Browser name and version
• Operating system
• Device type
• Relevant URLs
• Screenshots or video
• Error messages or console logs, when available
• The impact of the issue

Do not publicly include:

• Passwords
• Access or refresh tokens
• Private API keys
• Payment information
• Private messages
• Other users’ personal information
• Security details that could be used to exploit the Service

​

Security vulnerabilities

Do not submit a public GitHub issue when a vulnerability could affect:

• User data
• Account access
• Authentication
• Authorization or permissions
• Session security
• Password resets
• Private information
• The availability or integrity of the platform
• Multiple accounts or users

Report these issues privately through one of the following channels:

• Email security@yoursitee.com
• Submit a GitHub Security Advisory

If you are unsure whether a report contains sensitive security information, use the private security channel.

​

Responsible testing rules

When testing YourSitee:

• Test only on accounts and Sitees you personally own
• Do not access or modify another user’s data
• Do not attempt to bypass account permissions
• Do not perform denial-of-service or availability testing
• Do not use brute-force attacks
• Do not send spam
• Do not use automated vulnerability scanners
• Do not perform timing attacks or similar intrusive testing
• Do not test third-party services that are not operated by YourSitee
• Stop testing if your actions could affect other users or the reliability of the platform
• Do not publicly disclose unresolved security findings

​

What happens after you submit a report?

The YourSitee team will review the issue and may:

• Confirm the bug
• Ask for additional information
• Add labels or update its status
• Mark it as accepted
• Link it to an existing issue
• Mark it as a duplicate
• Mark it as incomplete or out of scope
• Close it after the issue has been resolved

If more information is required, our team will reply directly under the GitHub issue. Keep an eye on the discussion so the investigation can continue. Please do not close the issue yourself after submitting it. The YourSitee team will close it once it has been resolved or otherwise handled.

​

Out-of-scope reports

A report may be considered out of scope when it involves:

• A third-party service not operated by YourSitee
• A feature request or product suggestion
• A duplicate of an existing report
• Insufficient information to reproduce the issue
• Speculation without a demonstrated technical impact
• Unsupported browsers or devices
• Browser extensions, custom scripts, or local configuration problems
• Automated scanner output without manual verification
• Intentional misuse of the platform
• Behavior that is working as designed
• An issue already being addressed through a known permanent fix

Reports that do not follow the issue template or provide enough relevant information may be closed or marked as incomplete.

​

Bug XP and rewards

Valid and helpful reports may receive Bug XP, badges, perks, or another form of recognition. Reports are more likely to qualify when they:

• Are the first valid report of the issue
• Follow the official template
• Include reliable reproduction steps
• Clearly explain the expected and actual behavior
• Provide useful screenshots or video
• Describe the impact of the issue
• Give our team enough information to begin investigating immediately

Rewards are not automatically granted to the first person who mentions a problem. If the first report is incomplete and a later report provides substantially clearer evidence or information that helps us reproduce and fix the issue, the later reporter may also qualify for recognition. The amount of Bug XP may depend on factors such as:

• Severity
• User impact
• Reproducibility
• Report quality
• Technical detail
• Whether the issue was previously known
• How much the report contributed to resolving the problem

Valid security contributions may also be recognized on the YourSitee acknowledgements page.

​

Bug Hunter levels and badges

Bug XP tracks your contributions as a bug hunter. Bug Seeker 0–999 XP

​

YourSitee Tester Squad

The Tester Squad is an invite-only program for active and trusted testers. Members may help test unreleased features, identify problems before public releases, and provide detailed technical feedback through an internal issue tracker. Active members may receive benefits such as Premium access for the duration of their participation. Learn more in YourSitee Tester Squad Program.

​

Frequently asked questions

​

Q: Are Bug Hunter badges transferable?

A: No. Bug Hunter badges are connected to the account that earned them and cannot be transferred to another user.

​

Q: Do Bug Hunter badges include Premium access or special permissions?

A: No. The badges recognize your contributions but do not automatically include Premium access, moderation permissions, or access to internal systems. Separate programs, such as the Tester Squad, may provide their own benefits.

​

Q: What happens if I stop reporting bugs after earning a badge?

A: Nothing. Once earned, a Bug Hunter badge remains on your account. :)

​

Q: How can I check my Bug XP?

A: On the YourSitee Discord server, use /xp view to view your Bug XP or /leaderboard to view the leaderboard.

​

Q: Can I report bugs through Discord?

A: No. Discord is no longer an accepted bug-reporting channel. Submit regular bugs through the official GitHub bug tracker.

​

Q: Where should I submit feature requests?

A: Submit feature requests and product ideas in the #suggestions forum on Discord, not in the GitHub bug tracker.

​

Q: What should I do if I accidentally publish a security vulnerability?

A: Remove any public details you can control and contact security@yoursitee.com immediately. Include the public link and explain what information was disclosed.

​

Related articles