01-feature_request.yaml 2.3 KB

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