feature_request.yaml 4.5 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182
  1. name: Feature Request
  2. description: Suggest an idea for this project
  3. title: 'feat: '
  4. labels: ['triage']
  5. body:
  6. - type: markdown
  7. attributes:
  8. value: |
  9. ## Important Notes
  10. ### Before submitting
  11. Please check the **open AND closed** [Issues](https://github.com/open-webui/open-webui/issues) AND [Discussions](https://github.com/open-webui/open-webui/discussions) to see if a similar request has been posted.
  12. It's likely we're already tracking it! If you’re unsure, start a discussion post first.
  13. #### Scope
  14. If your feature request is likely to take more than a quick coding session to implement, test and verify, then open it in the **Ideas** section of the [Discussions](https://github.com/open-webui/open-webui/discussions) instead.
  15. **We will close and force move your feature request to the Ideas section, if we believe your feature request is not trivial/quick to implement.**
  16. This is to ensure the issues tab is used only for issues, quickly addressable feature requests and tracking tickets by the maintainers.
  17. Other feature requests belong in the **Ideas** section of the [Discussions](https://github.com/open-webui/open-webui/discussions).
  18. If your feature request might impact others in the community, definitely open a discussion instead and evaluate whether and how to implement it.
  19. This will help us efficiently focus on improving the project.
  20. ### Collaborate respectfully
  21. We value a **constructive attitude**, so please be mindful of your communication. If negativity is part of your approach, our capacity to engage may be limited. We're here to help if you're **open to learning** and **communicating positively**.
  22. Remember:
  23. - Open WebUI is a **volunteer-driven project**
  24. - It's managed by a **single maintainer**
  25. - It's supported by contributors who also have **full-time jobs**
  26. We appreciate your time and ask that you **respect ours**.
  27. ### Contributing
  28. If you encounter an issue, we highly encourage you to submit a pull request or fork the project. We actively work to prevent contributor burnout to maintain the quality and continuity of Open WebUI.
  29. ### Bug reproducibility
  30. If a bug cannot be reproduced with a `:main` or `:dev` Docker setup, or a `pip install` with Python 3.11, it may require additional help from the community. In such cases, we will move it to the "[issues](https://github.com/open-webui/open-webui/discussions/categories/issues)" Discussions section due to our limited resources. We encourage the community to assist with these issues. Remember, it’s not that the issue doesn’t exist; we need your help!
  31. - type: checkboxes
  32. id: existing-issue
  33. attributes:
  34. label: Check Existing Issues
  35. description: Please confirm that you've checked for existing similar requests
  36. options:
  37. - label: I have searched for all existing **open AND closed** issues and discussions for similar requests. I have found none that is comparable to my request.
  38. required: true
  39. - type: checkboxes
  40. id: feature-scope
  41. attributes:
  42. label: Verify Feature Scope
  43. description: Please confirm the feature's scope is within the described scope
  44. options:
  45. - label: I have read through and understood the scope definition for feature requests in the Issues section. I believe my feature request meets the definition and belongs in the Issues section instead of the Discussions.
  46. required: true
  47. - type: textarea
  48. id: problem-description
  49. attributes:
  50. label: Problem Description
  51. description: Is your feature request related to a problem? Please provide a clear and concise description of what the problem is.
  52. placeholder: "Ex. I'm always frustrated when... / Not related to a problem"
  53. validations:
  54. required: true
  55. - type: textarea
  56. id: solution-description
  57. attributes:
  58. label: Desired Solution you'd like
  59. description: Clearly describe what you want to happen.
  60. validations:
  61. required: true
  62. - type: textarea
  63. id: alternatives-considered
  64. attributes:
  65. label: Alternatives Considered
  66. description: A clear and concise description of any alternative solutions or features you've considered.
  67. - type: textarea
  68. id: additional-context
  69. attributes:
  70. label: Additional Context
  71. description: Add any other context or screenshots about the feature request here.