01-feature_request.yaml 2.7 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273
  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.1.7
  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: dropdown
  31. attributes:
  32. label: Triage priority
  33. description: >
  34. Issue triage may be prioritized in some cases. Select whichever of the following
  35. conditions applies, if any.
  36. options:
  37. - I volunteer to perform this work (if approved)
  38. - I'm a NetBox Labs customer
  39. - N/A
  40. default: 2
  41. validations:
  42. required: true
  43. - type: textarea
  44. attributes:
  45. label: Proposed functionality
  46. description: >
  47. Describe in detail the new feature or behavior you are proposing. Include any specific changes
  48. to work flows, data models, and/or the user interface. The more detail you provide here, the
  49. greater chance your proposal has of being discussed. Feature requests which don't include an
  50. actionable implementation plan will be rejected.
  51. validations:
  52. required: true
  53. - type: textarea
  54. attributes:
  55. label: Use case
  56. description: >
  57. Explain how adding this functionality would benefit NetBox users. What need does it address?
  58. validations:
  59. required: true
  60. - type: textarea
  61. attributes:
  62. label: Database changes
  63. description: >
  64. Note any changes to the database schema necessary to support the new feature. For example,
  65. does the proposal require adding a new model or field? (Not all new features require database
  66. changes.)
  67. - type: textarea
  68. attributes:
  69. label: External dependencies
  70. description: >
  71. List any new dependencies on external libraries or services that this new feature would
  72. introduce. For example, does the proposal require the installation of a new Python package?
  73. (Not all new features introduce new dependencies.)