|
1 | 1 | --- |
2 | 2 | name: ✨ Feature Request |
3 | | -description: Propose a new feature or enhancement |
| 3 | +description: Propose a new NetBox ACLs Plugin feature or enhancement |
4 | 4 | title: "[Feature]: " |
5 | 5 | labels: ["enhancement"] |
6 | 6 | body: |
7 | 7 | - type: markdown |
8 | 8 | attributes: |
9 | 9 | value: > |
10 | | - **NOTE:** This form is only for submitting well-formed proposals to extend or modify |
11 | | - NetBox in some way. If you're trying to solve a problem but can't figure out how, or if |
12 | | - you still need time to work on the details of a proposed new feature, please start a |
13 | | - [discussion](https://github.com/ryanmerolle/netbox-acls/discussions) instead. |
| 10 | + **NOTE:** This form is only for submitting well-formed proposals to |
| 11 | + extend or modify NetBox ACLs Plugin in some way. If you're trying to |
| 12 | + solve a problem but can't figure out how, or if you still need time to |
| 13 | + work on the details of a proposed new feature, please start a |
| 14 | + [discussion](https://github.com/netbox-community/netbox-acls/discussions) |
| 15 | + instead. |
| 16 | + - type: input |
| 17 | + attributes: |
| 18 | + label: NetBox ACLs Plugin version |
| 19 | + description: What version of NetBox ACLs are you currently running? |
| 20 | + placeholder: v2.0.0 |
| 21 | + validations: |
| 22 | + required: true |
14 | 23 | - type: input |
15 | 24 | attributes: |
16 | 25 | label: NetBox version |
17 | 26 | description: What version of NetBox are you currently running? |
18 | | - placeholder: v3.6.3 |
| 27 | + placeholder: v4.5.0 |
19 | 28 | validations: |
20 | 29 | required: true |
21 | 30 | - type: dropdown |
22 | 31 | attributes: |
23 | 32 | label: Feature type |
24 | 33 | options: |
25 | | - - New Model to plugin |
26 | | - - Change to existing model |
27 | | - - Add a function |
28 | | - - Remove a function |
| 34 | + - Data model extension |
| 35 | + - New functionality |
| 36 | + - Change to existing functionality |
29 | 37 | validations: |
30 | 38 | required: true |
31 | 39 | - type: textarea |
32 | 40 | attributes: |
33 | 41 | label: Proposed functionality |
34 | 42 | description: > |
35 | | - Describe in detail the new feature or behavior you are proposing. Include any specific changes |
36 | | - to work flows, data models, and/or dependencies. The more detail you provide here, the |
37 | | - greater chance your proposal has of being discussed. Feature requests which don't include an |
| 43 | + Describe in detail the new feature or behavior you are proposing. |
| 44 | + Include any specific changes to work flows, data models, and/or the user |
| 45 | + interface. The more detail you provide here, the greater chance your |
| 46 | + proposal has of being discussed. Feature requests which don't include an |
38 | 47 | actionable implementation plan will be rejected. |
39 | 48 | validations: |
40 | 49 | required: true |
41 | 50 | - type: textarea |
42 | 51 | attributes: |
43 | 52 | label: Use case |
44 | 53 | description: > |
45 | | - Explain how adding this functionality would benefit NetBox users & specifically this plugin. What need does it address? |
| 54 | + Explain how adding this functionality would benefit NetBox ACLs Plugin |
| 55 | + users. What need does it address? |
46 | 56 | validations: |
47 | 57 | required: true |
48 | 58 | - type: textarea |
49 | 59 | attributes: |
50 | 60 | label: External dependencies |
51 | 61 | description: > |
52 | | - List any new dependencies on external libraries or services that this new feature would |
53 | | - introduce. For example, does the proposal require the installation of a new Python package? |
| 62 | + List any new dependencies on external libraries or services that this |
| 63 | + new feature would introduce. For example, does the proposal require the |
| 64 | + installation of a new Python package? |
54 | 65 | (Not all new features introduce new dependencies.) |
| 66 | +... |
0 commit comments