Project assignment from issue template not setting the Project when creating new issue by default

[fmir864]

Select Topic Area

Bug

Feature Area

Issues

Body

I have an issue template as below to assign one of my projects automatically when creating a new issue. It worked previously but from last week stopped working. Anything I'm missing here?

name: Feature Request
description: Request a new feature
title: "[Feature]: "
labels: ["enhancement"]
projects: ["myorg/1"]
body:
  - type: markdown
    attributes:
      value: |
        Please read and complete the full template below.
  - type: textarea
    id: feature-description
    attributes:
      label: What you need?
      description: Tell us, what do you need?
      placeholder: Feature details, screen designs, db scripts, etc.
    validations:
      required: true
  - type: checkboxes
    id: attachments
    attributes:
      label: Any attachments?
      description: Any attached screenshots/related docs. (You can drag files on to this issue)
      options:
        - label: I attached a sample screenshot/related docs.
          required: true

Guidelines

• I have read the above statement and can confirm my post is relevant to the GitHub feature areas Issues and/or Projects.

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[wotaen]

Upvoting this, we rely on this heavily and it does affect our development teams. Please fix it! Thank you

[simonjur]

hello, any updates on this?

[oliveryasuna]

This is definitely a new bug. It just stopped setting the project.

[bmunkholm]

Contacting support directly provided this answer that may be helpful to others as well:

Thanks for flagging this! We’re aware of a recent regression where the projects: ["OWNER/NUMBER"] field in YAML issue templates no longer auto-adds the created issue to the specified project. Engineering is investigating; we don’t have an ETA yet, but once a fix is deployed an update will be shared on our Changelog.

In the meantime, here are two reliable workarounds that restore your dashboards:

1. Enable the project’s Auto-add workflow for issues

• Open your project
• Click “Auto-add to project”
• Add a minimal filter such as:
  is:issue repo:"OWNER/REPO"
• Save and toggle the workflow to On
• Verification: Create a test issue with your template and confirm it appears in the project within a minute

2. Use a scoped filter per repo if your project aggregates multiple repos

• Duplicate the Auto-add workflow in the project for each repository you need
• Example filters:
  is:issue repo:"owner/support-repo"
  is:issue repo:"owner/app-repo"
• Verification: Create a test issue in each repo and confirm items land in the project

[fmir864]

I have about 35+ repos, and this won't be practical

[emileswain]

i might add, that you also only have a limited number of workflows you can add, making this feature (auto add to repo) absolutely pointless less you upgrade to enterprise level. you might as well use actions.

[rileybroughten]

Thank you for the report, this has been raised with the team and we will provide an update when it is fixed!