01-feature_request.yaml 2.7 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859606162636465666768697071727374
  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.3
  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. - This is a very minor change
  40. - N/A
  41. default: 3
  42. validations:
  43. required: true
  44. - type: textarea
  45. attributes:
  46. label: Proposed functionality
  47. description: >
  48. Describe in detail the new feature or behavior you are proposing. Include any specific changes
  49. to work flows, data models, and/or the user interface. The more detail you provide here, the
  50. greater chance your proposal has of being discussed. Feature requests which don't include an
  51. actionable implementation plan will be rejected.
  52. validations:
  53. required: true
  54. - type: textarea
  55. attributes:
  56. label: Use case
  57. description: >
  58. Explain how adding this functionality would benefit NetBox users. What need does it address?
  59. validations:
  60. required: true
  61. - type: textarea
  62. attributes:
  63. label: Database changes
  64. description: >
  65. Note any changes to the database schema necessary to support the new feature. For example,
  66. does the proposal require adding a new model or field? (Not all new features require database
  67. changes.)
  68. - type: textarea
  69. attributes:
  70. label: External dependencies
  71. description: >
  72. List any new dependencies on external libraries or services that this new feature would
  73. introduce. For example, does the proposal require the installation of a new Python package?
  74. (Not all new features introduce new dependencies.)