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
Language is hard, and sometimes we don't all express the same features using the same terms. To improve issue submission completion rates, I'd like to explore allowing clicks on root products and intermediate feature branches to trigger the display of feature-selector-bottom-panel-content and an appropriate repo
"Why?": Why would this be impactful?
This will help ensure we're capturing more issues and reducing user confusion and frustration when the exact area can't easily be surfaced (for whatever reason).
"How?" How should this feature work?
Clicking on each node would default to the "main" or most appropriate repository. There will be times when the repo may not be the best choice but – for WPcom at least – we could default to wp-calypso for both the root "WordPress.com" selection and first-level branches immediately under that.
Example:
The text was updated successfully, but these errors were encountered:
"What": What is your idea?
Language is hard, and sometimes we don't all express the same features using the same terms. To improve issue submission completion rates, I'd like to explore allowing clicks on root products and intermediate feature branches to trigger the display of
feature-selector-bottom-panel-content
and an appropriate repo"Why?": Why would this be impactful?
This will help ensure we're capturing more issues and reducing user confusion and frustration when the exact area can't easily be surfaced (for whatever reason).
"How?" How should this feature work?
Clicking on each node would default to the "main" or most appropriate repository. There will be times when the repo may not be the best choice but – for WPcom at least – we could default to
wp-calypso
for both the root "WordPress.com" selection and first-level branches immediately under that.Example:
The text was updated successfully, but these errors were encountered: