Review support information before sharing
A good ticket says what you did, what you expected and what happened, with the app version and system (filled in when you start from the app). Read anything you paste first: leave out passwords, tokens, private keys and private file contents. Crash reports and the activity log already remove tokens and passwords, but you still choose what to copy.
Done on gittree.app with your GitTree account, the same one you sign in to the app with.
On this page
Before you start
- You are about to open or reply to a ticket.
Where to find it
- The ticket form’s Description, and the app’s Report a Bug….
Steps
Describe the steps
Write the steps to reproduce it, what you expected and what happened instead.
Add context from the app
Start from Report a Bug… in the app so the version and system are filled in, and read the report or summary it copies before pasting.
Remove secrets
Before sending, delete any password, token, private key, internal address or private code from what you pasted.
Expected result
Support has what it needs, and nothing private left your computer.
If something goes wrong
You pasted a secret into a ticket
Revoke or change that secret right away where it was issued, then tell support in a reply so they can handle the message.
Questions
Who can read my ticket?
Only you and the GitTree team.