Docs: Update bug_report.md

This commit is contained in:
Michael Mayer 2022-01-11 10:23:31 +01:00 committed by GitHub
parent 8f6077df53
commit fdf1f17cda
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -32,7 +32,7 @@ Steps to reproduce the behavior:
3. Scroll down to '....'
4. See error
If reporting a performance or indexing issue, please include the number and type of pictures in your library,
If reporting an Import, Indexing, or Performance issue, please include the number and type of pictures in your library,
as well as any configuration options you have changed e.g. for thumbnail quality.
**What behavior do you expect?**
@ -53,7 +53,7 @@ https://photoprism.app/contact
Learn how to diagnose frontend issues:
https://docs.photoprism.app/getting-started/troubleshooting/browsers/
IMPORTANT: Always provide a sample file and logs if it is an import, indexing, or metadata issue, otherwise we will not be able to process your report.
IMPORTANT: Always provide a sample file and logs if it is an Import, Indexing, or Metadata issue, otherwise we will not be able to process your report.
**Which software versions do you use?**
@ -66,24 +66,27 @@ IMPORTANT: Always provide a sample file and logs if it is an import, indexing, o
NOTE: The app version / build number can be found in *Settings* when you scroll to the bottom.
IMPORTANT:
1. Always provide database and operating system details if it is a backend, performance, import, or indexing issue.
2. Always provide web browser and operating system details if it is a frontend or performance issue.
1. Always provide database and operating system details if it is a Backend, Import, or Indexing issue.
2. Always provide web browser and operating system details if it is a Frontend issue.
3. If it is a Performance problem, you must provide ALL information.
**On what kind of device is PhotoPrism installed?**
This is especially important if you are reporting a performance, import, or indexing problem. You can skip this if you are reporting a problem found on our public demo, or if it is a completely unrelated issue, such as a broken page layout.
This is especially important if you are reporting a Performance, Import, or Indexing problem. You can skip this if you are reporting a problem found on our public demo, or if it is a completely unrelated issue, such as a broken page layout.
- Device / Processor Type (Raspberry Pi 4, AMD Ryzen, Intel,...)
- Physical Memory incl Swap Space (in GB)
- Storage Type (HDD, SSD, RAID, USB, Network Storage,...)
- anything else that might be helpful
IMPORTANT: Always provide device, memory, and storage details when you have a backend, performance, import, or indexing issue.
IMPORTANT: Always provide device, memory, and storage details when you have a Backend, Performance, Import, or Indexing issue.
**Do you use a proxy, load balancer, firewall, VPN, or CDN?**
**Do you use a Reverse Proxy, Firewall, VPN, or CDN?**
If yes, please specify type and version. You can skip this if you are reporting a completely unrelated issue.
IMPORTANT: Always provide this information if the issue is a performance, reliability, or frontend problem, such as connection errors, broken thumbnails, or video playback issues.
IMPORTANT:
1. Always provide this information when you have a Reliability, Performance, or Frontend problem, such as failed uploads, connection errors, broken thumbnails, or video playback issues.
2. If you are using NGINX, add its configuration and consider asking the NGINX community for advice as we do not specialize in supporting their product (which is known to be difficult to configure properly). We recommend using Traefik as reverse proxy instead.
# INCOMPLETE REPORTS CANNOT BE PROCESSED ☹️ #