feature_request.yaml 2.0 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354
  1. ---
  2. name: ✨ Feature Request
  3. about: Propose a new NetBox feature or enhancement
  4. labels: ["type: feature"]
  5. issue_body: false
  6. body:
  7. - type: markdown
  8. attributes:
  9. value: "**NOTE:** This form is only for submitting well-formed proposals to extend or
  10. modify NetBox in some way. If you're trying to solve a problem but can't figure out how,
  11. or if you still need time to work on the details of a proposed new feature, please start
  12. a [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: v2.10.4
  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: "Describe in detail the new feature or behavior you'd like to propose.
  33. Include any specific changes to work flows, data models, or the user interface."
  34. validations:
  35. required: true
  36. - type: textarea
  37. attributes:
  38. label: Use case
  39. description: "Explain how adding this functionality would benefit NetBox users. What
  40. need does it address?"
  41. validations:
  42. required: true
  43. - type: textarea
  44. attributes:
  45. label: Database changes
  46. description: "Note any changes to the database schema necessary to support the new
  47. feature. For example, does the proposal require adding a new model or field? (Not
  48. all new features require database changes.)"
  49. - type: textarea
  50. attributes:
  51. label: External dependencies
  52. description: "List any new dependencies on external libraries or services that this
  53. new feature would introduce. For example, does the proposal require the installation
  54. of a new Python package? (Not all new features introduce new dependencies.)"