Skip to content
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

How to Report an Issue - Read these Instructions Before Posting! #2760

Closed
deilann opened this issue Feb 5, 2014 · 0 comments
Closed

How to Report an Issue - Read these Instructions Before Posting! #2760

deilann opened this issue Feb 5, 2014 · 0 comments

Comments

@deilann
Copy link
Contributor

deilann commented Feb 5, 2014

Please check the Habitica Help Guild if you are unsure whether what you are experiencing is actually a bug. There is also helpful troubleshooting information in that guild as well as a list of known issues. You can also see known mobile issues via Menu > About > Support.

To report a bug: on mobile, please go to Menu > About > Support. On web, please go to Help > Report a Bug. If possible please avoid just straight emailing us, as going through the aforementioned forms will send us useful troubleshooting information along with your report.

In the rare cases when you need to log a GitHub issue, a moderator or staff member will advise you of that. Mods and staff have dark blue or purple names. If any other players suggest that you create a GitHub issue, please post to the Report a Bug guild instead.


To report a serious exploit affecting user privacy / security / finances:

If you find a bug in Habitica that affects the security or privacy or finances of players, please send us a bug report as noted above and please don't mention the bug in any public location, as that would allow other people to use the exploit maliciously. Habitica will fix all exploits as rapidly as possible, and then will inform any players that might have been affected.


To make a feature request / suggestion:

Feature requests or suggestions should not be made via Github or via bug reporting channels. Please use our Request a Feature form here: https://docs.google.com/forms/d/e/1FAIpQLScPhrwq_7P1C6PTrI3lbvTsvqGyTNnGzp1ugi1Ml0PFee_p5g/viewform?usp=sf_link


When a moderator or staff member asks you to create a new issue in GitHub:

  1. Sign up for a Github account, or sign in if you already have one. This will allow you to get an email update on any issue you create or respond to.
  2. Create a new issue by clicking here, or on the green "New Issue" button near the top right of the Issues page.
  3. Include your User ID. If you can access the website, go to User Icon -> Settings -> API to find it (it is a long string of random characters and is not the same as your Habitica name). If you can only access the mobile apps, you can find it under Settings > Account Details (tap on it to copy it to the clipboard). Do not tell us your API Token which is in the same location as the User ID but which must be kept secret.
  4. Include the other information requested on the new issue page (browser, operating system, etc).
  5. If the problem is related to a party or guild, also include the Group ID, which you can find on the party or guild page in the bottom of the left-hand column. Paste the ID as text, not screenshots.
  6. Include any JavaScript errors that may be displayed (see Chrome Console instructions for how to do that).
  7. Update us if you have any new info, or if the problem resolves itself!

To view known bugs

If you'd like to look through existing issues to see if your bug has been reported, view the most common issues first, and if you don't find a relevant one there, view all open issues. You can search by adding keywords to the "Filters" box then hitting enter on your keyboard. Often, a common issue will have bold text near the top telling you how to fix it, so you don't need to leave a comment. Note that even if you find an issue that's related to your situation, it's very often better for you to report it as described at the top of this page.

@deilann deilann closed this as completed Feb 6, 2014
deilann added a commit that referenced this issue May 18, 2014
@Alys Alys mentioned this issue Aug 19, 2014
@Alys Alys changed the title How to Report an Issue How to Report an Issue - Read these Instructions Before Posting! Sep 17, 2014
@HabitRPG HabitRPG locked and limited conversation to collaborators Sep 26, 2014
@HabitRPG HabitRPG unlocked this conversation Jan 26, 2015
@HabitRPG HabitRPG locked and limited conversation to collaborators Jan 27, 2015
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants