photoprism/.github/ISSUE_TEMPLATE/feature-request.md

46 lines
1.9 KiB
Markdown

---
name: Feature Request
about: Suggest a new feature or improvement
title: 'Category: Short Description (PLEASE CHANGE)'
labels: idea
assignees: ''
---
STOP! BEFORE YOU PROCEED: ARE YOU 100% SURE THAT THE PROBLEM AND THE PROPOSED SOLUTION ARE COMPLETELY CLEAR AND THAT NO SIMILAR ISSUE ALREADY EXISTS?
- Never use GitHub Issues if you have a general question, need help, or an issue has not (yet) been clearly identified
- When creating a new feature request, be sure to **answer all of the questions below** so that we and other community members have a good understanding of the problem and the proposed solution
- Note that all issue **subscribers receive an email notification** from GitHub for each new comment, so these should only be used for sharing important information and not for personal discussions/questions
BEFORE OPENING AN ISSUE, PLEASE CHECK OUR PUBLIC ROADMAP AND SEARCH EXISTING FEATURE REQUESTS:
<https://github.com/photoprism/photoprism/issues>
<https://link.photoprism.app/roadmap>
FOR GENERAL QUESTIONS, TECHNICAL SUPPORT, AND TO GET TO KNOW OTHER COMMUNITY MEMBERS:
<https://github.com/photoprism/photoprism/discussions>
PLEASE PROCEED ONLY IF YOU ARE 100% SURE THAT THE PROBLEM AND THE PROPOSED SOLUTION ARE COMPLETELY CLEAR AND THAT NO SIMILAR ISSUE ALREADY EXISTS.
**THANK YOU FOR YOUR CAREFUL CONSIDERATION!**
===============================================================================
**Is your feature request related to a problem? Please describe.**
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
**Describe the solution you'd like**
A clear and concise description of what you want to happen.
**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.
**Additional context**
Add any other context or screenshots about the feature request here.