Doesn't work with organizations?

[pat-s]

Issue: https://github.com/mlr-org/mlr/issues/2309 Project board: https://github.com/orgs/mlr-org/projects/1

I assigned the label and removed it but nothing happened in the board.

Maybe because the project board is in the organization and not directly in the repo?

[pat-s]

Made the org project public -> didnt' help

Move the project board only to the repo -> didn't help

Any permissions I am missing here?

[pat-s]

Also doesn't work in my own acc: https://github.com/pat-s/sperrorest/projects/1

[saerdnaer]

The problem is that the issue has already to be on the board, before the added_label action works for this issue. You can add an issue to an board e.g. via an 'inbox' column with the new_issue action.

[pat-s]

Thanks for the reply! Tested it and still doesn't work for me. Added the "inbox" column but it didn't work.

Permissions are all set.

Board: https://github.com/pat-s/sperrorest/projects/1 Issue created afterwards: https://github.com/pat-s/sperrorest/issues/47

[benjamin-antupit]

@philschatz This is also an issue for me and my organization's project. I love the idea of this extension, but my team likes organization-wide projects so we can organize info from different repositories. Link to project.

[saerdnaer]

https://github.com/pat-s/sperrorest/projects/1

@pat-s Maybe remove the parameter for new_issue. We use following configuration in our organisation board inbox column, which works fine:

[odusseys]

Same here, doesn't seem to work at organization level

[efcarey]

Not working at the org level, any ideas on this?

[danielcrowley]

Hi @philschatz happy to look at this, but is this

1. Something that works for you? (but not us)
2. Something that was working, but it's been broken?
3. Never expected to work? (from this https://github.com/philschatz/project-bot/blob/90c9a04322090e20e7ed5aa5cd56a2d69960e6eb/src/index.js#L76 I'm guessing this isn't the case)

[danielcrowley]

Ok there's a line limiting it to the first 10 projects (Both repo and org), looks like it's last ones first. I've closed boards so I have less than 10 and everything is working.

What's the preferred behaviour?

1. Flip it so it looks at the most recent projects?
2. Look at more projects (it looks at all cards in each project, so could slow down updates)
3. Put up with 10 projects!

[AneMengshoel]

I have not been able to get the "new issue" to work. I would like that when a new issue is created, it automatically is added to the project. I've tried both with the name of the repo and without...

[gaocegege]

I forked the repo and ran it locally. Then I found that the graphql here https://github.com/philschatz/project-bot/blob/master/src/index.js#L124 cannot get the cards of the org-level projects. Thus it cannot do anything because the bot cannot get the automation rules from the project.

I think it may be a bug or feature of the GraphQL API provided by GitHub.

No idea about how to fix it.

/cc @jlewi @hamelsmu

[gaocegege]

Code here https://github.com/philschatz/project-bot/blob/master/src/index.js#L67 can get the cards of the org-level projects. Thus we can add cards, but cannot move cards for org-level projects

[gaocegege]

After a deeper dive, I think we could support org-level projects now, but cannot support user-level projects becuase of https://github.community/t5/GitHub-API-Development-and/Resource-not-accessible-by-integration-when-requesting-GitHub/td-p/13829

[MarkLyck]

any update on this?