Every new issue with auto assigned project `AYON backlog`

[jakubjezek001]

Is there an existing issue for this?

• [X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?

Currently every new issue needs to have manually assigned AYON backlog.

How would you imagine the implementation of the feature?

It would be great if this had been done automatically. Status could be set to New.

Are there any labels you wish to add?

• [X] I have added the relevant labels to the feature request.

Describe alternatives you've considered:

No response

Additional context:

No response

[philnewm]

Thats good stuff :+1: The idea itself is pretty easy to implement since github provides a bunch of built in event triggers like one for issues

```yaml
name: Auto-assign Issues to Backlog Project

on:
  issues:
    types: [opened]  # Triggers when a new issue is created

jobs:
  add_to_project:
    runs-on: ubuntu-latest

    steps:
    - name: Add issue to project
      env:
        GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
      run: |
        ISSUE_NUMBER=${{ github.event.issue.number }}
        PROJECT_ID=YOUR_PROJECT_ID  # Replace with your project ID

        gh project item-add $PROJECT_ID --issue $ISSUE_NUMBER

The bigger challenge here is to implement a standardized approach for all intended repositories.
Cause mainting such globally wnated workflows on a per repo basis is simply pointless.

So I see too options here
* Implement a workflow which can create PRs for multiple repos at once to suggest workflow updates
* Implement [workflows on organization](https://docs.github.com/en/actions/sharing-automations/creating-workflow-templates-for-your-organization) level so hopefully all repos can just inherit them

[mkolar]

You might be missunderstanding backlog.

Each issue that is worth considering to be worked on goes on the backlog. But Code owners of repos are responsible for doing the first issue triage and getting them in there. This would pollute the backlog with all random publicly created issues as well, which is really not desired.

If you create an issue on your own managed repo, put it in the backlog too (assumption is that as code owner you have a good reason) if someone else creates an issue on a repo they don't manage, the code owner should triage it first

[philnewm]

That makes total sense to me, so not fully automated.