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: For Open Home Foundation staff only - Propose a strategic opportunity for the Home Assistant roadmap
2
+
description: For Open Home Foundation staff only - Log an idea or propose a roadmap opportunity
3
3
type: Opportunity
4
-
labels: ["status: proposal"]
5
4
body:
6
5
- type: markdown
7
6
attributes:
@@ -10,169 +9,101 @@ body:
10
9
11
10
**This form is restricted to Open Home Foundation staff and authorized contributors only.**
12
11
13
-
If you are a community member wanting to influence the roadmap, please submit your ideas to the [Feature Requests](https://github.com/orgs/home-assistant/discussions) instead. The product team monitors feature requests and incorporates them into roadmap opportunities.
12
+
If you are a community member wanting to suggest a feature or improvement, please use [Feature Requests](https://github.com/orgs/home-assistant/discussions) instead. The product team monitors these and incorporates relevant signals into roadmap items.
14
13
15
14
---
16
15
17
16
### For authorized contributors
18
17
19
-
Thanks for proposing a roadmap opportunity! 🗺️
18
+
Thanks for adding to the roadmap! 🗺️
20
19
21
-
Roadmap opportunities represent significant strategic initiatives that will be tracked on our project boards and broken down into actionable work. These are larger than individual features and require careful planning and coordination.
20
+
This form covers everything from early ideas and hunches to fully shaped opportunities ready for the betting table. Fill in what you can — not every field is relevant at every stage.
22
21
23
-
Before submitting, please:
24
-
- Verify you are authorized to create roadmap opportunities
25
-
- Search existing issues to avoid duplicates
26
-
- Ensure this is a strategic opportunity, not a single feature request
27
-
- Consider if this aligns with Home Assistant's values: local control, privacy, choice, and sustainability
28
-
- Reference any related feature requests that this opportunity addresses
22
+
Before submitting, please search existing issues to avoid duplicates.
29
23
30
24
- type: textarea
31
-
id: goals
25
+
id: problem_statement
32
26
attributes:
33
-
label: Goals
27
+
label: Problem statement
34
28
description: |
35
-
Provide a short description of the goal of the opportunity and the rationale behind it.
36
-
37
-
What problem does this opportunity solve? Why is it important for Home Assistant's future?
38
-
placeholder: |
39
-
Example:
40
-
- Improve the onboarding experience for new users by reducing setup complexity
41
-
- Enable Home Assistant to better serve non-technical users
42
-
- Reduce support burden by making common tasks more intuitive
29
+
Describes the problem you want to solve. Include who is impacted by the problem and why solving it matters to them or to OHF. Clearly link back to OHF's goals.
43
30
validations:
44
31
required: true
45
32
46
33
- type: textarea
47
-
id: vision
34
+
id: scope
48
35
attributes:
49
-
label: Vision
36
+
label: Scope & Boundaries
50
37
description: |
51
-
Provide a longer description of what we want to achieve, with anything that can be used to support the vision, a prototype, or simply a write-up.
52
-
53
-
Paint a picture of what success looks like. Include any supporting materials, mockups, research, or examples.
38
+
Define what we plan to achieve, and what we already consider out of scope for this opportunity. Be specific about what is included and what is explicitly excluded to prevent scope creep.
54
39
placeholder: |
55
-
Example:
56
-
We envision a streamlined onboarding flow that guides new users through:
57
-
1. Initial setup with automatic discovery of local devices
58
-
2. Creation of their first automation using a wizard-style interface
59
-
3. Dashboard customization with suggested cards based on their devices
40
+
#### In scope
41
+
-
60
42
61
-
This would reduce the time to first "wow moment" from hours to minutes...
43
+
#### Not in scope
44
+
-
62
45
validations:
63
-
required: true
46
+
required: false
64
47
65
48
- type: textarea
66
-
id: scope
49
+
id: foreseen_solution
67
50
attributes:
68
-
label: Scope & Boundaries
51
+
label: Foreseen solution
69
52
description: |
70
-
Define what we plan to achieve, and what we already consider out of scope for this opportunity.
71
-
72
-
Be specific about what is included and what is explicitly excluded to prevent scope creep.
73
-
placeholder: |
74
-
**In Scope:**
75
-
- New user onboarding flow
76
-
- Device auto-discovery improvements
77
-
- Basic automation creation wizard
78
-
- Default dashboard improvements
79
-
80
-
**Out of Scope:**
81
-
- Advanced automation features
82
-
- Custom component installation
83
-
- Multi-user account management
84
-
- Mobile app changes (separate opportunity)
53
+
The foreseen solution solving the problem described above, shaped enough to understand what the solution is and what it means to build it. This is a starting point for discussion and an eventual decision on if we want to build it, not a detailed specification. A low-fidelity way of visualizing the solution is welcome.
85
54
validations:
86
-
required: true
55
+
required: false
87
56
88
57
- type: textarea
89
-
id: plan
58
+
id: community_feedback
90
59
attributes:
91
-
label: Plan
60
+
label: Community signals
92
61
description: |
93
-
How we plan to achieve what we want to achieve. Include the breakdown into Epics and the prioritization between them.
94
-
95
-
This should be a high-level roadmap of the major work areas and their dependencies.
What prompted this? Link to any Discussions, feature requests, Discord threads, or other signals that informed this item. Leave blank if this came from internal thinking.
111
63
validations:
112
-
required: true
64
+
required: false
113
65
114
66
- type: textarea
115
-
id: related_feature_requests
67
+
id: risks_and_open_questions
116
68
attributes:
117
-
label: Related Feature Requests
69
+
label: Risks & open questions
118
70
description: |
119
-
List the feature requests from the Feature Requests repository that this opportunity addresses.
120
-
121
-
This helps demonstrate community demand and ensures we're building what users need.
What are we uncertain about? Are there technical, UX, or strategic risks? How do we plan to address or investigate them?
126
72
validations:
127
73
required: false
128
74
129
75
- type: textarea
130
-
id: additional_context
76
+
id: appetite
131
77
attributes:
132
-
label: Additional Context
78
+
label: Appetite
133
79
description: |
134
-
Any additional information, links, research, or context that would be helpful.
135
-
136
-
Include links to related issues, research, prototypes, etc.
80
+
Roughly how much time are we willing to invest in this opportunity? Use relative sizing (e.g. small / medium / large) or cycle count. This is not a commitment but rather a signal to help prioritise at the betting table.
137
81
placeholder: |
138
-
- User research findings: [link]
139
-
- Prototype/mockup: [link]
140
-
- Similar implementations in other projects: [links]
141
-
- Technical design documents: [link]
82
+
Example: Medium — roughly 1–2 cycles of focused work across frontend and core.
142
83
validations:
143
84
required: false
144
85
145
86
- type: textarea
146
-
id: decision_log
87
+
id: execution_issues
147
88
attributes:
148
-
label: Decision Log
89
+
label: Execution issues
149
90
description: |
150
-
Any big decisions we took along the way as a log, so that contributors can reflect on them.
151
-
152
-
This section will be updated as the opportunity progresses. Leave empty for now if this is a new proposal.
91
+
Populated once a bet is approved. Add links to the tracking issues created in core, frontend, and any other relevant repositories.
153
92
placeholder: |
154
-
**2024-06-30**: Decided to focus on web interface first, mobile app improvements will be separate opportunity
155
-
**2024-07-15**: Chose wizard-style interface over single-page setup based on user research
156
-
**2024-08-01**: Agreed to integrate with existing device discovery rather than building new system
93
+
- home-assistant/core#12345
94
+
- home-assistant/frontend#67890
157
95
validations:
158
96
required: false
159
97
160
98
- type: textarea
161
-
id: qa
99
+
id: decision_log
162
100
attributes:
163
-
label: Q&A
101
+
label: Decision log
164
102
description: |
165
-
Any recurring questions that pop up, answered by the opportunity owner so that we can reference them back.
166
-
167
-
This helps address common concerns and reduces repetitive discussions.
168
-
placeholder: |
169
-
**Q: Will this affect existing users' setups?**
170
-
A: No, this only affects new user onboarding. Existing configurations remain unchanged.
171
-
172
-
**Q: How does this relate to the mobile app experience?**
173
-
A: Mobile app improvements are considered a separate opportunity. This focuses on web interface only.
174
-
175
-
**Q: What about users who prefer manual configuration?**
176
-
A: Advanced/manual configuration will remain available. This adds a guided path, doesn't replace existing options.
103
+
Record key decisions, pivots, and betting table outcomes with dates. This helps contributors understand the history of the item and reduces repetitive discussions.
0 commit comments