1
0
mirror of https://github.com/laurent22/joplin.git synced 2024-12-21 09:38:01 +02:00
joplin/.github/ISSUE_TEMPLATE/bug_report.md
Helmut K. C. Tessarek 483b2e769f
DO NOT create screenshots of text !!!
If there's text to select, do it. Why create a screenshot? Screenshots are helpful for GUI/UI/UX elements, but useless and highly annoting for text. Is copying text really that hard and complicated?

Oce upon a time I asked a customer to send me an error message (so that I could search for it in the code base and in traces). That customer created a screenshot of a terminal, with only half the error message and then put that image into a word document and sent that to me. Besides the fact that I did not have Word, what would I have done with an image? Argh!!!!!!!
2021-11-17 09:25:34 -05:00

53 lines
1.2 KiB
Markdown

---
name: "\U0001F41B Bug Report"
about: Report a reproducible bug or regression in Joplin.
title: ''
labels: bug
assignees: ''
---
<!--
Please provide a clear and concise description of what the bug is. (In the section Steps To Reproduce.)
Include screenshots for UI problems if needed.
DO NOT create screenshots of text !!! Copy and paste the text into a code block.
Please test using the latest Joplin release to make sure your issue has not already been fixed.
-->
<!--
IMPORTANT: If you are reporting a clipper bug, please include an example URL that shows the issue.
Without the URL the issue is likely to be closed.
-->
## Environment
Joplin version:
Platform:
OS specifics:
<!--
Platform can be one of: macOS, Linux, Windows, Android, iOS, terminal (or a combination)
OS specifics: e.g. OS version, Linux distribution, Android/iOS version...
-->
## Steps to reproduce
1.
2.
3.
<!--
Issues without reproduction steps are likely to stall.
-->
## Describe what you expected to happen
## Logfile
<!--
Please attach a debug log. Issues without a debug log are likely to stall.
For information on how to collect a log file: https://joplinapp.org/debugging/
-->