A good title is short and descriptive. It should be a one-sentence executive
summary of the issue, so the impact and severity of the bug you want to report
can be inferred from the title.

Provide a clear, focused, specific, and concise summary of the bug you encountered. Explain why you think this is a bug that should be reported. Adhere to the following principles:

• concise summary of the bug you encountered. Explain why you think this is a bug
  that should be reported. Adhere to the following principles:
• Explain the what, not the how – don't explain how to reproduce the bug here, we're getting there. Focus on articulating the problem and its impact as clearly as possible.
• Keep it short and concise – if the bug can be precisely explained in one or two sentences, perfect. Don't inflate it – the maintainer and future users will be grateful for having to read less.
• One bug at a time – if you encountered several unrelated bugs, please create separate issues for them. Don't report them in the same issue, as this makes attribution difficult.
  

Attaching a link preview will always help the maintainer view the issue from your side and most likely detect the problem faster. If possible always attach a preview of the bug in a video format or animated image (GIF).

Please use Imgur or Gyazo for your links.