Skip to content

Conversation

@adityaraute
Copy link

Summary

Fixes #5650
Adds a new Issue Form for Feature Requests

Checklist

@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Apr 6, 2025

CLA Signed

The committers listed above are authorized under a signed CLA.

@adityaraute adityaraute marked this pull request as ready for review April 6, 2025 09:34
@mgol
Copy link
Member

mgol commented Apr 6, 2025

Thanks for the PR. Please sign our CLA, we cannot merge contributed code otherwise.

@adityaraute adityaraute changed the title Create Feature Request.yml Create Feature Request Issue Form Apr 7, 2025
@adityaraute
Copy link
Author

Thanks for the PR. Please sign our CLA, we cannot merge contributed code otherwise.

Done!

Copy link
Member

@mgol mgol left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR.

I tried this on my fork but it doesn't work. I recommend you to temporarily enable issues on your jQuery fork and to set the patch-1 branch as the main one and you'll be able to check what's needed. In particular, I think we need a config.yml file: https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/configuring-issue-templates-for-your-repository#configuring-the-template-chooser

Also, if we want to introduce a feature request form, please make sure the path to report regular bug reports is at least not harder than it was - maybe we need to create a form for bug reports as well, even if for now it won't ask that many questions (we can always improve it later)?

@adityaraute
Copy link
Author

I recommend you to temporarily enable issues on your jQuery fork and to set the patch-1 branch as the main one and you'll be able to check what's needed.

I had done this before creating the PR. Not sure what's the issue is about. I'll look into the link you shared.

maybe we need to create a form for bug reports as well

I'll add in this PR itself

@adityaraute adityaraute marked this pull request as draft April 15, 2025 20:20
@adityaraute
Copy link
Author

Screenshots:

  1. When you click on New Issue
    {617CEF99-95E1-4B23-AB53-15E4A9CDCB28}

  2. Bug Report Form
    {A44FA18F-2975-4C4A-9B7B-C90D572A48AB}

  3. Feature Request Form
    {6C99B482-F26A-4213-B23D-43A63EFFA5A7}

Hope you are able to replicate this in your repo

@adityaraute adityaraute marked this pull request as ready for review April 15, 2025 20:41
@adityaraute adityaraute requested a review from mgol April 24, 2025 18:05
@timmywil timmywil changed the title Create Feature Request Issue Form Docs: Create Bug and Feature Request Issue Form Oct 13, 2025
@timmywil timmywil changed the title Docs: Create Bug and Feature Request Issue Form Create Feature Request Issue Forms Oct 13, 2025
@timmywil timmywil changed the title Create Feature Request Issue Forms Docs: Create Bug and Feature Request Forms Oct 13, 2025
name: Bug Report
description: Report a bug encountered in JQuery.
title: "[BUG]: "
labels: ["bug", "triage"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think we want these labels.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have Bug (starting with an uppercase letter) in Core, we could add it here as well. The Refined GitHub extension adds a separate tab for issues with such a label.

Agreed about triage.

name: Feature Request
description: Request a feature to be added to JQuery.
title: "[FEAT]: "
labels: ["enhancement", "triage"]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No new labels required. We have other labels for this.

@timmywil
Copy link
Member

  1. Could we remove the existing issue template if/when we add these?
  2. The filenames seem inconsistent: bug_report.yml and Feature Request.yml. I'd like to change the latter to feature_request.yml.

@@ -0,0 +1,26 @@
name: Bug Report
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's use consistent naming, BTW. This file is named bug_report.yml, the other one is Feature Request.yml. I'd prefer bug-report.yml & feature-request.yml, it'd be more consistent with how we name files.

id: wiki
attributes:
label: Have you checked existing issues?
description: Before submitting this issue, please check if a similar issue has been raised in the repository [here](https://github.com/jquery/jquery/issues?q=is%3Aissue%20label%3ABug%20).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Avoid linking from generic text like "here", it's bad for accessibility: https://granicus.com/blog/why-click-here-links-are-bad/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

New Issue Forms / Templates

3 participants