feature_request.yaml 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263
  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. <<<<<<< HEAD
  18. placeholder: v3.1.6
  19. =======
  20. placeholder: v3.1.7
  21. >>>>>>> develop
  22. validations:
  23. required: true
  24. - type: dropdown
  25. attributes:
  26. label: Feature type
  27. options:
  28. - Data model extension
  29. - New functionality
  30. - Change to existing functionality
  31. validations:
  32. required: true
  33. - type: textarea
  34. attributes:
  35. label: Proposed functionality
  36. description: >
  37. Describe in detail the new feature or behavior you are proposing. Include any specific changes
  38. to work flows, data models, and/or the user interface. The more detail you provide here, the
  39. greater chance your proposal has of being discussed. Feature requests which don't include an
  40. actionable implementation plan will be rejected.
  41. validations:
  42. required: true
  43. - type: textarea
  44. attributes:
  45. label: Use case
  46. description: >
  47. Explain how adding this functionality would benefit NetBox users. What need does it address?
  48. validations:
  49. required: true
  50. - type: textarea
  51. attributes:
  52. label: Database changes
  53. description: >
  54. Note any changes to the database schema necessary to support the new feature. For example,
  55. does the proposal require adding a new model or field? (Not all new features require database
  56. changes.)
  57. - type: textarea
  58. attributes:
  59. label: External dependencies
  60. description: >
  61. List any new dependencies on external libraries or services that this new feature would
  62. introduce. For example, does the proposal require the installation of a new Python package?
  63. (Not all new features introduce new dependencies.)