|
| 1 | +name: Feature Request |
| 2 | +description: Suggest a new feature or enhancement for the Payments Management System |
| 3 | +title: "[Feature]: " |
| 4 | +labels: ["enhancement", "triage"] |
| 5 | +assignees: [] |
| 6 | + |
| 7 | +body: |
| 8 | + - type: markdown |
| 9 | + attributes: |
| 10 | + value: | |
| 11 | + Thanks for suggesting a new feature! Please provide as much detail as possible to help us understand your request. |
| 12 | +
|
| 13 | + - type: dropdown |
| 14 | + id: feature-type |
| 15 | + attributes: |
| 16 | + label: Feature Type |
| 17 | + description: What type of feature is this? |
| 18 | + options: |
| 19 | + - New Payment Gateway Integration |
| 20 | + - New API Endpoint |
| 21 | + - Ledger Enhancement |
| 22 | + - Performance Improvement |
| 23 | + - Security Enhancement |
| 24 | + - Documentation |
| 25 | + - Developer Experience |
| 26 | + - Testing |
| 27 | + - Other |
| 28 | + validations: |
| 29 | + required: true |
| 30 | + |
| 31 | + - type: dropdown |
| 32 | + id: module |
| 33 | + attributes: |
| 34 | + label: Related Module |
| 35 | + description: Which module(s) would this feature affect? |
| 36 | + multiple: true |
| 37 | + options: |
| 38 | + - ayushmaanbhav-payment |
| 39 | + - ayushmaanbhav-ledger |
| 40 | + - ayushmaanbhav-gateway-provider |
| 41 | + - ayushmaanbhav-gateway-provider-common |
| 42 | + - ayushmaanbhav-event-processor |
| 43 | + - ayushmaanbhav-request-idempotency |
| 44 | + - ayushmaanbhav-commons |
| 45 | + - ayushmaanbhav-database |
| 46 | + - New module required |
| 47 | + - Not sure |
| 48 | + validations: |
| 49 | + required: true |
| 50 | + |
| 51 | + - type: textarea |
| 52 | + id: problem |
| 53 | + attributes: |
| 54 | + label: Problem Statement |
| 55 | + description: Is your feature request related to a problem? Please describe. |
| 56 | + placeholder: "A clear description of what the problem is. Ex: I'm always frustrated when..." |
| 57 | + validations: |
| 58 | + required: true |
| 59 | + |
| 60 | + - type: textarea |
| 61 | + id: solution |
| 62 | + attributes: |
| 63 | + label: Proposed Solution |
| 64 | + description: Describe the solution you'd like |
| 65 | + placeholder: "A clear description of what you want to happen..." |
| 66 | + validations: |
| 67 | + required: true |
| 68 | + |
| 69 | + - type: textarea |
| 70 | + id: alternatives |
| 71 | + attributes: |
| 72 | + label: Alternatives Considered |
| 73 | + description: Describe any alternative solutions or features you've considered |
| 74 | + placeholder: "List any alternative approaches..." |
| 75 | + |
| 76 | + - type: textarea |
| 77 | + id: api-design |
| 78 | + attributes: |
| 79 | + label: API Design (if applicable) |
| 80 | + description: If this involves new API endpoints, please provide a proposed design |
| 81 | + placeholder: | |
| 82 | + ``` |
| 83 | + POST /payment/new-endpoint |
| 84 | + Request: |
| 85 | + { |
| 86 | + "field1": "value1" |
| 87 | + } |
| 88 | + Response: |
| 89 | + { |
| 90 | + "success": true, |
| 91 | + "data": { ... } |
| 92 | + } |
| 93 | + ``` |
| 94 | + render: markdown |
| 95 | + |
| 96 | + - type: dropdown |
| 97 | + id: breaking-change |
| 98 | + attributes: |
| 99 | + label: Breaking Change |
| 100 | + description: Would this feature require breaking changes to existing APIs? |
| 101 | + options: |
| 102 | + - "No" |
| 103 | + - "Yes - Minor (backwards compatible with deprecation)" |
| 104 | + - "Yes - Major (breaking change)" |
| 105 | + - "Not sure" |
| 106 | + validations: |
| 107 | + required: true |
| 108 | + |
| 109 | + - type: dropdown |
| 110 | + id: priority |
| 111 | + attributes: |
| 112 | + label: Priority |
| 113 | + description: How important is this feature to you? |
| 114 | + options: |
| 115 | + - Low - Nice to have |
| 116 | + - Medium - Would significantly improve my workflow |
| 117 | + - High - Blocking my use case |
| 118 | + - Critical - Cannot use the system without this |
| 119 | + validations: |
| 120 | + required: true |
| 121 | + |
| 122 | + - type: textarea |
| 123 | + id: use-case |
| 124 | + attributes: |
| 125 | + label: Use Case |
| 126 | + description: Describe your use case for this feature |
| 127 | + placeholder: "Explain how you would use this feature..." |
| 128 | + validations: |
| 129 | + required: true |
| 130 | + |
| 131 | + - type: textarea |
| 132 | + id: additional |
| 133 | + attributes: |
| 134 | + label: Additional Context |
| 135 | + description: Add any other context, mockups, or screenshots about the feature request |
| 136 | + |
| 137 | + - type: checkboxes |
| 138 | + id: contribution |
| 139 | + attributes: |
| 140 | + label: Contribution |
| 141 | + description: Would you like to contribute to this feature? |
| 142 | + options: |
| 143 | + - label: I am willing to submit a PR for this feature |
| 144 | + - label: I can help with testing this feature |
| 145 | + - label: I can help with documentation for this feature |
0 commit comments