simplify the create Issue workflow to not require the use of github templates about gatsby-theme-newrelic HOT 7 CLOSED

It's not horrible to have the issue type as part of the issue template. The main downside to doing this vs. having a label is that it's harder to filter to just bugs (for instance). I'd suggest we start here and adjust as needed.

from gatsby-theme-newrelic.

Yes, I'm saying it's probably fine to not have separate issue templates.

That said, I don't think I've seen the selection process as designed, so maybe I should see that before having too strong of an opinion here.

from gatsby-theme-newrelic.

Ah! This isn't bad at all.

So in the feedback case, would we have separate 'thumbs up' and 'thumbs down' templates and go straight to the relevant template (skipping the selection process) when you click those buttons?

from gatsby-theme-newrelic.

@djsauble that's correct, we just thought we apply the same approach we did for feedback submission to the issue creation workflow, just bypassing the screen to select the issue template on github.

from gatsby-theme-newrelic.

I wanted to check in with @djsauble on this from a UX perspective. This approach means we'd have no issue selection step when a user clicks the create issue button, but we could still keep the issue templates in Github, for those that go through the issue filing process on github.

I also think we'd want this functionality in theme, and I need to confirm if OSS really needs to drive a user through a template selection as well.

from gatsby-theme-newrelic.

@djsauble just confirming, you are supporting not using the selection of an issue template? OR keeping it as today?

from gatsby-theme-newrelic.

Essentially a use clicks on Create an Issue button, and on all DECO sites are taking to github new issues screen where they have to decide and select a template to use. From there, they just complete the issue.

from gatsby-theme-newrelic.