|
1 | | -name: ✨ Feature request |
2 | | -description: Suggest a new feature or improvement |
3 | | -title: '[Feature Request]: ' |
4 | | -labels: [enhancement, no-priority] |
| 1 | +name: "✨ Feature request" |
| 2 | +description: "Suggest a new feature or improvement" |
| 3 | +title: "[Feature Request]: " |
| 4 | +labels: |
| 5 | + - "enhancement" |
| 6 | + - "no-priority" |
5 | 7 |
|
6 | 8 | body: |
7 | | -- type: markdown |
8 | | - attributes: |
9 | | - value: > |
10 | | - Thanks for suggesting a feature! |
11 | | - |
12 | | - - Please search the existing feature request to see if there has been a similar issue filed. |
13 | | - |
14 | | - - If a feature has been filed before, but not followed up by a contributor, you can develop the feature yourself by checking the development documentation [here](https://docs.cipp.app/dev-documentation/cipp-dev-guide/setting-up-for-local-development). |
15 | | - |
16 | | - - Repeat feature requests are allowed if the previous request has been closed for more than 30 days |
17 | | - |
18 | | - - drive-by feature requests without effort will be closed. |
19 | | - |
20 | | - - A feature request has 14 days to be fullfilled before automatically being closed. if you want to work on the feature yourself use the phrase "I'd like to work on this please!" |
21 | | - |
22 | | - - Feature requests that are detrimental to security will also be closed without notice. |
23 | | -- type: textarea |
24 | | - attributes: |
25 | | - label: Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole. |
26 | | - validations: |
27 | | - required: true |
28 | | -- type: textarea |
29 | | - attributes: |
30 | | - label: PowerShell commands you would normally use to achieve above request |
31 | | - validations: |
32 | | - required: false |
| 9 | + # Introductory Markdown |
| 10 | + - type: markdown |
| 11 | + attributes: |
| 12 | + value: | |
| 13 | + **Thank you for suggesting a new feature or improvement for CIPP** |
| 14 | +
|
| 15 | + Before creating a request, please: |
| 16 | +
|
| 17 | + 1. Check that you have an active sponsorship, only users that are sponsoring CIPP at the $99,- sponsorship level can create feature requests. |
| 18 | + 1. Search existing **open and closed** feature requests to avoid duplicates. |
| 19 | + 2. Note that **repeat feature requests** are permitted if a previous request was closed more than 30 days ago. |
| 20 | + 3. Consider implementing the feature yourself by reviewing the [development documentation](https://docs.cipp.app/dev-documentation/cipp-dev-guide/setting-up-for-local-development). |
| 21 | + 4. Feature requests that lack sufficient detail or feasibility may be closed at any time. |
| 22 | + 5. **This request will auto-close in 14 days** if no meaningful progress or collaboration occurs. |
| 23 | + 6. If you would like to work on this feature, comment `"I'd like to work on this please!"` |
| 24 | + 7. Any request that is detrimental to security or the product’s stability will be closed without notice. |
| 25 | +
|
| 26 | + # Checkboxes for Confirmations |
| 27 | + - type: checkboxes |
| 28 | + id: confirmations |
| 29 | + attributes: |
| 30 | + label: "Please confirm:" |
| 31 | + description: "Check all boxes that apply." |
| 32 | + options: |
| 33 | + - label: "**I have searched existing feature requests** (open and closed) and found no duplicates." |
| 34 | + required: true |
| 35 | + - label: "**me or my organization is currently an active sponsor of the product at the $99,- level." |
| 36 | + required: true |
| 37 | + |
| 38 | + - type: textarea |
| 39 | + id: problem-statement |
| 40 | + attributes: |
| 41 | + label: "Problem Statement" |
| 42 | + description: | |
| 43 | + **What problem does this feature solve or what gap does it fill?** |
| 44 | + Provide a concise explanation. For example: |
| 45 | + - "When I need to enable MFA for all users, it takes a lot of time to do it per user. I'd like to enable this for all users in button press" |
| 46 | + - "To update a user property for exchange I need to go through 5 portals and 2 systems to be able to make a change." |
| 47 | + validations: |
| 48 | + required: true |
| 49 | + |
| 50 | + # Field 2: Benefits for MSPs |
| 51 | + - type: textarea |
| 52 | + id: msp-benefits |
| 53 | + attributes: |
| 54 | + label: "Benefits for MSPs" |
| 55 | + description: | |
| 56 | + **How would this feature help MSPs in their day-to-day tasks or overall operations?** |
| 57 | + - Does it reduce manual work? |
| 58 | + - Does it improve security or scalability? |
| 59 | + - Does it offer clarity or automation to commonly repeated tasks? |
| 60 | + validations: |
| 61 | + required: true |
| 62 | + |
| 63 | + # Field 3: Value or Importance |
| 64 | + - type: textarea |
| 65 | + id: feature-value |
| 66 | + attributes: |
| 67 | + label: "Value or Importance" |
| 68 | + description: | |
| 69 | + **Why is this feature particularly valuable or important to add?** |
| 70 | + - If it's critical, explain why. |
| 71 | + - If it's optional or nice-to-have, describe how it still adds notable value. |
| 72 | + validations: |
| 73 | + required: true |
| 74 | + |
| 75 | + # Optional field for PowerShell commands |
| 76 | + - type: textarea |
| 77 | + id: powershell-commands |
| 78 | + attributes: |
| 79 | + label: "PowerShell Commands (Optional)" |
| 80 | + description: | |
| 81 | + If you currently achieve this functionality or a similar workaround using PowerShell, please share your scripts or snippets here. |
| 82 | + This information helps contributors understand the existing workflow and aids in development. |
| 83 | + validations: |
| 84 | + required: false |
0 commit comments