link to bug tracker in Support menu

[fastfasterfastest]

I think it would be helpful if the Support menu (upper right) contained a link (or links) to "Browse or Submit bugs". If possible it would be nice if such link was "context sensitive" so when you are on jquery.com it takes you to the jquery bug tracker, when you are on jqueryui.com it takes you to the jqueryui bug tracker, etc.

[gnarf]

i think there might be a page on contribute with links to bug trackers and explaination of each

[ajpiano]

http://contribute.jquery.org/triage/ has it, but it needs an anchor. context specific bugs link would actually be kind of useful anyway....the "Bugs/Issue Tracker" link in the footer is already sort of useless/strange on certain sites, e.g., jquery.org, where it still links to jquery core issues.

[fastfasterfastest]

That page (http://contribute.jquery.org/triage/) sounds like a good target for a new link in the Support menu, perhaps directly to one of the last sections on that page.

I think it is quite common to find links to help/tech-support/report-a-problem etc. in "support" sections on various web sites. Currently you can find that/those links on the "home page" of the jquery.com, jqueryui.com etc., but I think it would be helpful and useful if they existed in the Support menu as well - accessible from any page. If such new link/links cannot be "context sensitive" as described above, then a link to http://contribute.jquery.org/triage would be useful, I think.

[ajpiano]

Yeah, I meant to say that as well -- I think we should definitely link to that triage page, with an anchor to the actual list, in the Support menu

[ajpiano]

In short, 👍

[scottgonzalez]

The triage page isn't geared toward users submitting bugs. Even if we linked directly to the list of issue trackers, the text at the top of the section would be confusing for users who are looking for support.

[Krinkle]

In jquery/jquery.com#237, we consolidated many support pages into https://jquery.com/support/ which is linked from the "Support" menu and includes a section at the bottom about bug reports.

https://jquery.com/support/#found-a-bug
Found a bug?
For reporting bugs in libraries, documentation, or content, the project's GitHub issues tracker should be used. All jQuery projects can be found at https://github.com/jquery

I propose adding a "Report a bug" explicilty in the Support menu, but am unsure which of these three destinations to pick:

1. https://github.com/jquery/ - Let the user land here, and pick their repository, and follow the same discovery path that probably most people need to follow regardless, assuming our git repo is a fairly common landing place. They then find their way to "Issues", potentially performing a search first, then click "New issue". There, now three steps further, they are greeted with a template about minimal test cases, and latest jQuery version etc.
2. https://contribute.jquery.org/bug-reports/ - This contains a more fleshed out version of the information in the template, with the benefit of receiving it immediately upon the jquery.com menu link, instead of after several steps. Also, on this page starts with how to ask for support from chat/StackOverlow first. Do we still prefer that? Also, the URLs are actually clickable/linked so people are more likely to follow "how to reduce a test case" and e.g. use CodePen/JSBin. This web page then sends you to https://github.com/jquery/jquery/issues once done.
3. https://jquery.com/support/ - Linking this would take the recommendation to ask for support first and literally drop people there first. If they go past the Learning Center, API Docs, Chat, StackOverflow, they then find the "Found a bug" heading and go to https://github.com/jquery from there.

Thoughts?

[Krinkle]

Summary of jquery_dev Matrix chat today:

• Between these three links, @timmywil prefers https://contribute.jquery.org/bug-reports/.
• Timmy raisees that despite this page doing a good job to discourage invalid bug reports, adding exposure from a prominent link on the site, may increase bug reports, especially invalid ones, beyond our capacity to triage (the team isn't as large as it used to be).
• @mgol suggests we try it. We agree to try it and see how it goes.