Can we unsolve this? Selecting a project on an issue is a workaround and is the opposite of expected automation.
What the OP and everyone responding are intuitively expecting is the following:
* Testers can open issues.
* Issues will automatically be added to a project column, e.g. "to do" or "backlog"
* Developers don't have to manually add all issues but can just browse through the designated column and triage.
Chiming in to say no auto-adding issues/PRs is my biggest blocker to wanting to use GH Projects as our team's primary PM tool. We've been using Waffle.io but they've announced shutdown, so we're looking at alternatives.
Echoing what @deepakmahakale said, one relatively simple implementation would be to allow issue/PR templates to set the project -- you can already set other metadata this way, so this seems like a natural thing to allow. Beyond implementing the auto-add-to-project feature everyone here is asking for, setting the project in a template seems like an obvious thing template users would want more generally.
Any updates on auto-addding new issues/PRs to projects, is this actively being worked on? I was initially really confused that the option to "Move all newly added issues and pull request here" does not actually do what it says.
The naming "project" for a "board" is also a bit confusing, since a lot people refer to a "repository" on GH as a "GitHub project" (and that aids in misunderstand what is meant by "when an issue is added to a project").
This is literally how i assumed it would work and what i assume most github repos are used like (since they usually represent one project anyways!)
I spent some time trying to get this to work as expected, reading documentation and experimenting. I then searched and found this topic. I appreciate that github developers have constraints on their effort so may not implement every feature request promptly but this is continuing to confuse and frustrate users. May I make a request that, until this feature be implemented, the documentation be updated to describe the workflow more clearly. I like many others believed that new issues created in linked repositories would be added to the project via the configured automation. It would be a fairly simple and fast task to update the documentation to explain that this does not happen.
Further, one may consider the "Add cards" view as the triage view (in lieu of automation not working as expected), i.e. one may filter the "Add cards" to show issues from linked repositories which are not yet added to the project. This makes the "Add cards" list the equivillent to the triage list, i.e. everything reported that is not yet tasked. This was not evident until at least one reprository was added to the project so may also need to be documented.
(Using the "Add cards" list for triage would be more intuitive if it could be moved to the left side (for left to right users).)
Can we unsolve this message? The description is clearly explaining a different expectation for how Project Issue automation should work. I would love to have issues automatically added to a project on creation.
Except for new issues not being auto added to a project board I have other things which drive me crazy when it comes to project view. Please see my concerns below:
I wish it can be taken care of pretty soon because most of us (either devs or PMs) are struggling with such little aspects which make our lives harder. Wouldn't it be better to work smarter not harder? :)