01-feature_request.yaml 2.3 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061
  1. ---
  2. name: ✨ Feature Request
  3. type: Feature
  4. description: Propose a new NetBox feature or enhancement
  5. labels: ["netbox", "type: feature", "status: needs triage"]
  6. body:
  7. - type: markdown
  8. attributes:
  9. value: >
  10. **NOTE:** This form is only for submitting well-formed proposals to extend or modify
  11. NetBox in some way. If you're trying to solve a problem but can't figure out how, or if
  12. you still need time to work on the details of a proposed new feature, please start a
  13. [discussion](https://github.com/netbox-community/netbox/discussions) instead.
  14. - type: input
  15. attributes:
  16. label: NetBox version
  17. description: What version of NetBox are you currently running?
  18. placeholder: v4.4.9
  19. validations:
  20. required: true
  21. - type: dropdown
  22. attributes:
  23. label: Feature type
  24. options:
  25. - Data model extension
  26. - New functionality
  27. - Change to existing functionality
  28. - Other
  29. validations:
  30. required: true
  31. - type: textarea
  32. attributes:
  33. label: Proposed functionality
  34. description: >
  35. Describe in detail the new feature or behavior you are proposing. Include any specific changes
  36. to work flows, data models, and/or the user interface. The more detail you provide here, the
  37. greater chance your proposal has of being discussed. Feature requests which don't include an
  38. actionable implementation plan will be rejected.
  39. validations:
  40. required: true
  41. - type: textarea
  42. attributes:
  43. label: Use case
  44. description: >
  45. Explain how adding this functionality would benefit NetBox users. What need does it address?
  46. validations:
  47. required: true
  48. - type: textarea
  49. attributes:
  50. label: Database changes
  51. description: >
  52. Note any changes to the database schema necessary to support the new feature. For example,
  53. does the proposal require adding a new model or field? (Not all new features require database
  54. changes.)
  55. - type: textarea
  56. attributes:
  57. label: External dependencies
  58. description: >
  59. List any new dependencies on external libraries or services that this new feature would
  60. introduce. For example, does the proposal require the installation of a new Python package?
  61. (Not all new features introduce new dependencies.)