feature_request.yaml 2.3 KB

1234567891011121314151617181920212223242526272829303132333435363738394041424344454647484950515253545556575859
  1. ---
  2. name: ✨ Feature Request
  3. description: Propose a new NetBox feature or enhancement
  4. labels: ["type: feature"]
  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: v3.2.5
  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. validations:
  28. required: true
  29. - type: textarea
  30. attributes:
  31. label: Proposed functionality
  32. description: >
  33. Describe in detail the new feature or behavior you are proposing. Include any specific changes
  34. to work flows, data models, and/or the user interface. The more detail you provide here, the
  35. greater chance your proposal has of being discussed. Feature requests which don't include an
  36. actionable implementation plan will be rejected.
  37. validations:
  38. required: true
  39. - type: textarea
  40. attributes:
  41. label: Use case
  42. description: >
  43. Explain how adding this functionality would benefit NetBox users. What need does it address?
  44. validations:
  45. required: true
  46. - type: textarea
  47. attributes:
  48. label: Database changes
  49. description: >
  50. Note any changes to the database schema necessary to support the new feature. For example,
  51. does the proposal require adding a new model or field? (Not all new features require database
  52. changes.)
  53. - type: textarea
  54. attributes:
  55. label: External dependencies
  56. description: >
  57. List any new dependencies on external libraries or services that this new feature would
  58. introduce. For example, does the proposal require the installation of a new Python package?
  59. (Not all new features introduce new dependencies.)