Update bug/feature templates to track if submitter requests assignment (#510)
An additional datapoint that can be helpful during triage of bugs and features is if the submitter is interested in being the implementer as well. Updating the bug_report and feature_request templates to help track this.
This commit is contained in:
		
							
								
								
									
										10
									
								
								.github/ISSUE_TEMPLATE/bug_report.md
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										10
									
								
								.github/ISSUE_TEMPLATE/bug_report.md
									
									
									
									
										vendored
									
									
								
							@@ -48,3 +48,13 @@ Run the following commands in Powershell and copy/paste the output.
 | 
				
			|||||||
 | 
					
 | 
				
			||||||
**Additional context**
 | 
					**Additional context**
 | 
				
			||||||
<!-- Add any other context about the problem here. -->
 | 
					<!-- Add any other context about the problem here. -->
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					**Requested Assignment**
 | 
				
			||||||
 | 
					<!--
 | 
				
			||||||
 | 
					Some people just want to report a bug and let someone else fix it.
 | 
				
			||||||
 | 
					Other people want to not only submit the bug report, but fix it as well.
 | 
				
			||||||
 | 
					Both scenarios are completely ok. We just want to know which one it is.
 | 
				
			||||||
 | 
					Please indicate which bucket you fall into by keeping one and removing the other.
 | 
				
			||||||
 | 
					-->
 | 
				
			||||||
 | 
					If possible, I would like to fix this.
 | 
				
			||||||
 | 
					I'm just reporting this problem.  I don't want to fix it.
 | 
				
			||||||
 
 | 
				
			|||||||
							
								
								
									
										11
									
								
								.github/ISSUE_TEMPLATE/feature_request.md
									
									
									
									
										vendored
									
									
								
							
							
						
						
									
										11
									
								
								.github/ISSUE_TEMPLATE/feature_request.md
									
									
									
									
										vendored
									
									
								
							@@ -41,3 +41,14 @@ Things we are explicitly not doing or supporting or that are out of scope, inclu
 | 
				
			|||||||
<!--
 | 
					<!--
 | 
				
			||||||
Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage.
 | 
					Show as much of the experience as needed to explain the idea. This can be as simple as a napkin drawing but can also be a code prototype, or a design comp. Keep it simple at this stage, as it can be refined later during the pre-production stage.
 | 
				
			||||||
-->
 | 
					-->
 | 
				
			||||||
 | 
					
 | 
				
			||||||
 | 
					**Requested Assignment**
 | 
				
			||||||
 | 
					<!--
 | 
				
			||||||
 | 
					Some people just want to suggest a feature and let someone else implement it.
 | 
				
			||||||
 | 
					Other people want to not only suggest a feature, but implement it as well.
 | 
				
			||||||
 | 
					Both scenarios are completely ok. We just want to know which one it is.
 | 
				
			||||||
 | 
					We are likely to prioritize the review of feature requests if they already have someone who can implement them.
 | 
				
			||||||
 | 
					Please indicate which bucket you fall into by keeping one and removing the other.
 | 
				
			||||||
 | 
					-->
 | 
				
			||||||
 | 
					If possible, I would like to implement this.
 | 
				
			||||||
 | 
					I'm just suggesting this idea.  I don't want to implement it.
 | 
				
			||||||
 
 | 
				
			|||||||
		Reference in New Issue
	
	Block a user