Skip to content

docs(issue/template): simplify feature template #6657

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
kuny0707 merged 1 commit into from
Apr 9, 2026
+27 −71
Merged

docs(issue/template): simplify feature template #6657

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
98 changes: 27 additions & 71 deletions .github/ISSUE_TEMPLATE/request-a-feature.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,85 +7,41 @@ assignees: ''

---

<!--
Thank you for contributing to java-tron!
Please provide as much detail as possible to help us evaluate your feature request.
-->

## Problem Statement

<!-- Describe the problem this feature solves, the context/motivation, and who would benefit -->
# Summary
<!-- Provide a concise description of the problem and the proposed solution.-->

## Proposed Solution
# Problem
### Motivation
Copy link
Copy Markdown
Collaborator

@halibobo1205 halibobo1205 Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

### Motivation -> ### Motivation[optional] for if necessary ? or keep it the same as Alternative Solutions?

Copy link
Copy Markdown

@liuyifei001 liuyifei001 Apr 8, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Motivation is the key target of feature. That's why we do it, should not be optional.

<!-- Describe the context or motivation if necessary. -->

<!-- Describe your proposed solution in detail -->
### Current State
<!-- Describe the current behavior of the system. -->

### Specification
### Limitations or Risks
<!-- Explain the limitations, risks, or inefficiencies. -->

<!-- Provide technical specifications or requirements -->
# Proposed Solution

**API Changes** (if applicable)
<!-- Describe any new or modified APIs -->
### Proposed Design
<!-- Describe the proposed solution at a high level. Implementation details are optional but encouraged if relevant.-->

**Configuration Changes** (if applicable)
<!-- Describe any new configuration options -->
### Key Changes
<!-- List the main areas affected by this proposal, such as Module(s), Configuration and API. -->

**Protocol Changes** (if applicable)
<!-- Describe any changes to the TRON protocol -->
# Impact
<!-- Assess the expected impact of this change, such as Security, Stability, Performance, Developer Experience -->

## Scope of Impact

<!-- Select the system components that will be affected by this feature:
- Core protocol
- API/RPC
- Database
- Network layer
- Smart contracts
- Documentation
- Others, please specify
# Compatibility
<!--
* Breaking Change: Yes / No
* Default Behavior Change:
* Migration Required:
Provide details if any of the above is applicable.
-->

**Breaking Changes**
<!-- Will this feature introduce any breaking changes? -->

**Backward Compatibility**
<!-- How will this feature maintain backward compatibility? -->

## Implementation

**Do you have ideas regarding the implementation?**
<!-- Share any technical approaches or implementation details -->

**Are you willing to implement this feature?**
<!-- Let us know if you'd like to contribute the implementation -->

**Estimated Complexity**
<!-- Your assessment of implementation complexity, choose among
- Low (minor changes)
- Medium (moderate changes)
- High (significant changes)
- Unknown
-->

## Testing Strategy

<!-- How should this feature be tested? -->

**Test Scenarios**

**Performance Considerations**
<!-- Describe any performance implications -->

## Alternatives Considered (Optional)

<!-- Describe any alternative solutions or features you've considered -->

## Additional Context (Optional)

<!-- Add any other context, mockups, diagrams, or examples -->

**Related Issues/PRs**
<!-- Link to any related issues or pull requests -->
# References (Optional)
Copy link
Copy Markdown
Collaborator

@halibobo1205 halibobo1205 Apr 8, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

another Optional

<!-- TIPs, papers, related issues, prior art -->

**References**
<!-- Link to any relevant documentation, specifications, or discussions -->
# Additional Notes
- Do you have ideas regarding implementation? Yes / No
- Are you willing to implement this feature? Yes / No
Loading