Skip to content

Commit 38d94ad

Browse files
authored
feat: add feature request issue template (#3910)
<!-- Thanks for sending a pull request (PR)! Here are some tips for you: 1. If this is your first time, please read our contributor guidelines: [Contributing to Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md) 2. Ensure you have added or run the appropriate tests for your PR 3. If the PR is work in progress, mark it a draft on GitHub. 4. Please write your PR title to summarize what this PR proposes, we are following Conventional Commits style for PR titles as well. 5. Be sure to keep the PR description updated to reflect all changes. --> ### What changes were proposed in this PR? <!-- Please clarify what changes you are proposing. The purpose of this section is to outline the changes. Here are some tips for you: 1. If you propose a new API, clarify the use case for a new API. 2. If you fix a bug, you can clarify why it is a bug. 3. If it is a refactoring, clarify what has been changed. 3. It would be helpful to include a before-and-after comparison using screenshots or GIFs. 4. Please consider writing useful notes for better and faster reviews. --> This PR adds an issue template for creating feature requests. It adds fields and drop-downs for users to select. ### Any related issues, documentation, discussions? <!-- Please use this section to link other resources if not mentioned already. 1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves #1234` or `Closes #1234`. If it is only related, simply mention the issue number. 2. If there is design documentation, please add the link. 3. If there is a discussion in the mailing list, please add the link. --> Resolves #3908 ### How was this PR tested? <!-- If tests were added, say they were added here. Or simply mention that if the PR is tested with existing test cases. Make sure to include/update test cases that check the changes thoroughly including negative and positive cases if possible. If it was tested in a way different from regular unit tests, please clarify how you tested step by step, ideally copy and paste-able, so that other reviewers can test and check, and descendants can verify in the future. If tests were not added, please describe why they were not added and/or why it was difficult to add. --> N/A. This only adds a template. ### Was this PR authored or co-authored using generative AI tooling? <!-- If generative AI tooling has been used in the process of authoring this PR, please include the phrase: 'Generated-by: ' followed by the name of the tool and its version. If no, write 'No'. Please refer to the [ASF Generative Tooling Guidance](https://www.apache.org/legal/generative-tooling.html) for details. --> No. Signed-off-by: Yicong Huang <[email protected]>
1 parent 9322ae6 commit 38d94ad

1 file changed

Lines changed: 80 additions & 0 deletions

File tree

Lines changed: 80 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,80 @@
1+
# Licensed to the Apache Software Foundation (ASF) under one
2+
# or more contributor license agreements. See the NOTICE file
3+
# distributed with this work for additional information
4+
# regarding copyright ownership. The ASF licenses this file
5+
# to you under the Apache License, Version 2.0 (the
6+
# "License"); you may not use this file except in compliance
7+
# with the License. You may obtain a copy of the License at
8+
#
9+
# http://www.apache.org/licenses/LICENSE-2.0
10+
#
11+
# Unless required by applicable law or agreed to in writing, software
12+
# distributed under the License is distributed on an "AS IS" BASIS,
13+
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
14+
# See the License for the specific language governing permissions and
15+
# limitations under the License.
16+
17+
name: Feature Request
18+
description: Suggest a new feature or improvement.
19+
labels: ["triage"]
20+
type: "Feature"
21+
body:
22+
- type: markdown
23+
attributes:
24+
value: |
25+
Thanks for suggesting a feature! Please provide as much detail as possible to help us evaluate your idea.
26+
27+
- type: textarea
28+
id: summary
29+
attributes:
30+
label: Feature Summary
31+
description: Clearly describe what the feature is and the problem it solves.
32+
placeholder: Describe your feature idea and what problem it addresses.
33+
validations:
34+
required: true
35+
36+
- type: textarea
37+
id: proposal
38+
attributes:
39+
label: Proposed Solution or Design
40+
description: Explain how you imagine this feature working. Include examples, diagrams, or pseudo-code if relevant.
41+
placeholder: Describe your proposed solution or design approach.
42+
validations:
43+
required: true
44+
45+
- type: dropdown
46+
id: impact
47+
attributes:
48+
label: Impact / Priority
49+
description: How important is this feature?
50+
options:
51+
- (P0)Critical – blocks existing use cases
52+
- (P1)High – significantly improves user experience
53+
- (P2)Medium – useful enhancement
54+
- (P3)Low – nice to have
55+
default: 2
56+
validations:
57+
required: true
58+
59+
- type: dropdown
60+
id: affected-area
61+
attributes:
62+
label: Affected Area
63+
description: Which part of the system does this feature relate to?
64+
multiple: true
65+
options:
66+
- Workflow Engine (Amber)
67+
- Workflow UI
68+
- Hub
69+
- Storage / Metadata
70+
- Deployment / Infrastructure
71+
- Other
72+
73+
- type: checkboxes
74+
id: terms
75+
attributes:
76+
label: Code of Conduct
77+
description: By submitting this issue, you agree to follow [Apache Code of Conduct](https://www.apache.org/foundation/policies/conduct).
78+
options:
79+
- label: I agree to follow Apache Code of Conduct
80+
required: true

0 commit comments

Comments
 (0)