Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Automatically add labels to issue when they are raised from MDN #4496

Closed
Tracked by #5156
Rumyra opened this issue Aug 17, 2021 · 3 comments
Closed
Tracked by #5156

Automatically add labels to issue when they are raised from MDN #4496

Rumyra opened this issue Aug 17, 2021 · 3 comments
Labels
engineering-request enahncement requests from community, writers and partners needs decision from engineering 🚉 platform keeping the platform healthy

Comments

@Rumyra
Copy link
Contributor

Rumyra commented Aug 17, 2021

When issues are raised via the 'Report a problem with this content' link on MDN, we have information about where the issue is coming from, plus it's a new issue.

Labels should be:

  • Which area of content is applicable, such as Content: CSS - this can be derived from the URL, even if it's not a perfect science it's a good start for issue triagers
  • needs-triage label - currently we are adding these manually so issue triagers can seach via this label, automatically adding this would save this work
@peterbe
Copy link
Contributor

peterbe commented Aug 17, 2021

Doesn't it already do that? This is what I see after having clicked that "Report a problem with this content" link.
Screen Shot 2021-08-17 at 2 45 15 PM

@Rumyra
Copy link
Contributor Author

Rumyra commented Aug 23, 2021

So looking into this it would be good to check through what's being added, some issues are coming through with no labels - maybe this is 'check auto issue labelling'

@schalkneethling
Copy link

As we have needs-triage automatically added, we are good here for now.

Repository owner moved this from Backlog to Done in Yari Platform Engineering Jan 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
engineering-request enahncement requests from community, writers and partners needs decision from engineering 🚉 platform keeping the platform healthy
Projects
Development

No branches or pull requests

3 participants