`new_issue` doesn't work in organization project

[MarkLyck]

I have 2 identical projects.

one at the repo level,
one at the organization level.

they both have the same automation card:

###### Automation Rules

<!-- Documentation: https://github.com/philschatz/project-bot -->

- `new_issue` **c1-frontend-v4**
- `unassigned_issue`

The one on the repo level works just fine. When I create a new issue, it automatically gets assigned to the project in the right column.

However, nothing happens in the organization project."

The repository is private.
The organization project is private.

I have tried setting the organization project to public, but that did not help.
I have tried removing the repo name and just use this:

 - `new_issue`

I have tried prefacing the repo name with the org name

 - `new_issue` **my_org/c1-frontend-v4**

I have tried renaming the organization project (they both had the same name before)

our organization has 29 open project boards. (I saw 1 comment in another issue, regarding that project bot might only recognize the first 10 boards?) - could be related.

Interestingly enough, while new issues do not appear on the board. If I use other automation rules like assigning, or labels. Those automation work just fine once I have manually added the ticket to the board.

Any idea why new_issue does not work on the organization level?

[stevejr]

Any update on this issue? I would like to use the bot but it needs to support Org projects. Thanks.

[MatFillion]

I works for me on an organisation project, that's the first thing I tried.