You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
description: Report a specific problem that needs solving in Roo Code
3
-
labels: ["proposal", "enhancement"]
1
+
name: Enhancement Request
2
+
description: Propose an improvement in plain language focused on user benefit
3
+
labels: ["enhancement"]
4
+
title: "[ENHANCEMENT] "
4
5
body:
5
6
- type: markdown
6
7
attributes:
7
8
value: |
8
-
**Thank you for submitting a feature request for Roo Code!**
9
-
10
-
This template helps you describe problems that need solving. Focus on the problem - the Roo team will work to design solutions unless you want to contribute the implementation yourself.
11
-
12
-
**Quality over speed:** We prefer detailed, clear problem descriptions over quick ones. Vague requests often get closed or require multiple rounds of clarification, which wastes everyone's time.
13
-
14
-
**Before submitting:**
15
-
- Search existing [Issues](https://github.com/RooCodeInc/Roo-Code/issues) and [Discussions](https://github.com/RooCodeInc/Roo-Code/discussions) to avoid duplicates
16
-
- For general ideas, use [GitHub Discussions](https://github.com/RooCodeInc/Roo-Code/discussions/categories/feature-requests) instead of this template.
9
+
Thank you for helping improve Roo Code!
10
+
Please focus on the problem and the desired behavior in plain language.
17
11
18
-
- type: markdown
12
+
- type: textarea
13
+
id: problem
19
14
attributes:
20
-
value: |
21
-
## ❌ Common mistakes that lead to request rejection:
22
-
- **Vague problem descriptions:** "UI is bad" -> Should be: "Submit button is invisible on dark theme"
23
-
- **Missing user impact:** "This would be cool" -> Should explain who benefits and how
24
-
- **No specific context:** Describe exactly when and how the problem occurs
25
-
15
+
label: Problem (one or two sentences)
16
+
description: What problem are users facing?
17
+
placeholder: e.g., "Users often click Copy Run by mistake and duplicate runs unintentionally."
18
+
validations:
19
+
required: true
26
20
27
21
- type: textarea
28
-
id: problem-description
22
+
id: context
29
23
attributes:
30
-
label: What specific problem does this solve?
31
-
description: |
32
-
**Be concrete and detailed.** Explain the problem from a user's perspective.
33
-
34
-
✅ **Good examples (specific, clear impact):**
35
-
- "When running large tasks, users wait 5+ minutes because tasks execute sequentially instead of in parallel, blocking productivity"
36
-
- "AI can only read one file per request, forcing users to make multiple requests for multi-file projects, increasing wait time from 30s to 5+ minutes"
37
-
- "Dark theme users can't see the submit button because it uses white text on light grey background"
38
-
39
-
❌ **Poor examples (vague, unclear impact):**
40
-
- "The UI looks weird" -> What specifically looks weird? On which screen? What's the impact?
41
-
- "System prompt is not good" -> What's wrong with it? What behaviour does it cause? What should it do instead?
42
-
- "Performance could be better" -> Where? How slow is it currently? What's the user impact?
43
-
44
-
**Your problem description should answer:**
45
-
- Who is affected? (all users, specific user types, etc.)
46
-
- When does this happen? (specific scenarios/steps)
47
-
- What's the current behaviour vs expected behaviour?
48
-
- What's the impact? (time wasted, errors caused, etc.)
49
-
placeholder: Be specific about the problem, who it affects, and the impact. Avoid generic statements like "it's slow" or "it's confusing."
24
+
label: Context (who is affected and when)
25
+
description: Who encounters this and in what situation?
26
+
placeholder: e.g., "Happens when browsing the Runs list; most visible for new users."
50
27
validations:
51
28
required: true
52
29
53
-
54
30
- type: textarea
55
-
id: additional-context
31
+
id: desired
56
32
attributes:
57
-
label: Additional context (optional)
58
-
description: Mockups, screenshots, links, user quotes, or other relevant information that supports your proposal.
33
+
label: Desired behavior (conceptual, not technical)
34
+
description: Describe what should happen in simple terms.
35
+
placeholder: e.g., "Ask for confirmation before copying a run."
36
+
validations:
37
+
required: true
59
38
60
39
- type: textarea
61
-
id: roo-code-tasks
40
+
id: constraints
62
41
attributes:
63
-
label: Roo Code Task Links (Optional)
64
-
description: |
65
-
If you used Roo Code to explore this feature request or develop solutions, share the public task links here.
66
-
This helps maintainers understand the context and any exploration you've done.
67
-
Example: https://app.roocode.com/share/task-id
68
-
placeholder: Paste your Roo Code share links here, one per line
42
+
label: Constraints / preferences (optional)
43
+
description: Any considerations like performance, accessibility, or UX expectations.
44
+
placeholder: e.g., "Keep it quick and unobtrusive; keyboard accessible."
69
45
70
46
- type: checkboxes
71
47
id: checklist
@@ -74,128 +50,42 @@ body:
74
50
options:
75
51
- label: I've searched existing Issues and Discussions for duplicates
76
52
required: true
77
-
- label: This describes a specific problem with clear impact and context
53
+
- label: This describes a specific problem with clear context and impact
78
54
required: true
79
55
56
+
- type: textarea
57
+
id: roo-code-tasks
58
+
attributes:
59
+
label: Roo Code Task Links (optional)
60
+
description: If you explored this with Roo Code, share public task links for context.
61
+
placeholder: Paste your Roo Code share links here, one per line
**🎯 Just reporting a problem?** You can click "Submit new issue" right now! The sections below are only needed if you want to contribute a solution via pull request.
88
-
89
-
**⚠️ Only continue if you want to:**
90
-
- Propose a specific solution design
91
-
- Implement the feature yourself via pull request
92
-
- Provide technical analysis to help with implementation
93
-
94
-
**For contributors who continue:**
95
-
- A maintainer (especially @hannesrudolph) will review this proposal. **Do not start implementation until approved and assigned.** We're a small team with limited resources, so every code addition needs careful consideration. We're always happy to receive clear, actionable proposals though!
96
-
- Join [Discord](https://discord.gg/roocode) and DM **Hannes Rudolph** (`hrudolph`) for guidance on implementation
97
-
- Check our [Roadmap](https://github.com/orgs/RooCodeInc/projects/1/views/1?query=sort%3Aupdated-desc+is%3Aopen&filterQuery=is%3Aissue%2Copen%2Cclosed+label%3A%22feature+request%22+status%3A%22Issue+%5BUnassigned%5D%22%2C%22Issue+%5BIn+Progress%5D%22) to see open feature requests ready to be implemented or currently being worked on
98
-
99
-
- type: checkboxes
100
-
id: willingness-to-contribute
101
-
attributes:
102
-
label: Interested in implementing this?
103
-
description: |
104
-
**Important:** If you check "Yes" below, the technical sections become REQUIRED.
105
-
We need detailed technical analysis from contributors to ensure quality implementation.
106
-
options:
107
-
- label: Yes, I'd like to help implement this feature
108
-
required: false
109
-
110
-
- type: checkboxes
111
-
id: implementation-approval
112
-
attributes:
113
-
label: Implementation requirements
114
-
options:
115
-
- label: I understand this needs approval before implementation begins
116
-
required: false
117
-
118
-
- type: textarea
119
-
id: proposed-solution
120
-
attributes:
121
-
label: How should this be solved? (REQUIRED if contributing, optional otherwise)
122
-
description: |
123
-
**If you want to implement this feature, this section is REQUIRED.**
124
-
125
-
**Describe your solution in detail.** Explain not just what to build, but how it should work.
126
-
127
-
✅ **Good examples:**
128
-
- "Add parallel task execution: Allow up to 3 tasks to run simultaneously with a queue system for additional tasks. Show progress for each active task in the UI."
129
-
- "Enable multi-file AI processing: Modify the request handler to accept multiple files in a single request and process them together, reducing round trips."
130
-
- "Fix button contrast: Change submit button to use primary colour on dark theme (white text on blue background) instead of current grey."
131
-
132
-
❌ **Poor examples:**
133
-
- "Make it faster" -> How? What specific changes?
134
-
- "Improve the UI" -> Which part? What specific improvements?
135
-
- "Fix the prompt" -> What should the new prompt do differently?
136
-
137
-
**Your solution should explain:**
138
-
- What exactly will change?
139
-
- How will users interact with it?
140
-
- What will the new behaviour look like?
141
-
placeholder: Describe the specific changes and how they will work. Include user interaction details if relevant.
67
+
Optional (for contributors): You can stop here if you're just proposing the improvement.
142
68
143
69
- type: textarea
144
70
id: acceptance-criteria
145
71
attributes:
146
-
label: How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
147
-
description: |
148
-
**If you want to implement this feature, this section is REQUIRED.**
149
-
150
-
**This is crucial - don't skip it.** Define what "working" looks like with specific, testable criteria.
151
-
152
-
**Format suggestion:**
153
-
```
154
-
Given [context/situation]
72
+
label: Acceptance criteria (optional)
73
+
description: Define what “working” looks like with specific, testable outcomes.
74
+
placeholder: |
75
+
Given [context]
155
76
When [user action]
156
77
Then [expected result]
157
78
And [additional expectations]
158
79
But [what should NOT happen]
159
-
```
160
-
161
-
**Example:**
162
-
```
163
-
Given I have 5 large tasks to run
164
-
When I start all of them
165
-
Then they execute in parallel (max 3 at once, can be configured)
166
-
And I see progress for each active task
167
-
And queued tasks show "waiting" status
168
-
But the UI doesn't freeze or become unresponsive
169
-
```
170
-
placeholder: |
171
-
Define specific, testable criteria. What should users be able to do? What should happen? What should NOT happen?
172
-
Use the Given/When/Then format above or your own clear structure.
173
80
174
81
- type: textarea
175
-
id: technical-considerations
82
+
id: proposed-solution
176
83
attributes:
177
-
label: Technical considerations (REQUIRED if contributing, optional otherwise)
178
-
description: |
179
-
**If you want to implement this feature, this section is REQUIRED.**
180
-
181
-
Share technical insights that could help planning:
182
-
- Implementation approach or architecture changes
183
-
- Performance implications
184
-
- Compatibility concerns
185
-
- Systems that might be affected
186
-
- Potential blockers you can foresee
187
-
placeholder: e.g., "Will need to refactor task manager", "Could impact memory usage on large files", "Requires a large portion of code to be rewritten"
84
+
label: Proposed approach (optional)
85
+
description: If you have an idea, describe it briefly in plain language.
188
86
189
87
- type: textarea
190
-
id: trade-offs-and-risks
88
+
id: risks
191
89
attributes:
192
-
label: Trade-offs and risks (REQUIRED if contributing, optional otherwise)
193
-
description: |
194
-
**If you want to implement this feature, this section is REQUIRED.**
195
-
196
-
What could go wrong or what alternatives did you consider?
197
-
- Alternative approaches and why you chose this one
0 commit comments