New Issues Not Being Auto-Added to Project Board

Thanks for replying @nadiajoyce, I know github isn’t a PM tool but bulk moving of issues would solve literally all of my current road blocks. Bonus would be also to have the ‘project’ selection available in issue templates and PR templates so we can “auto-add to project” ourselves from issue creation by choosing the appropriate template.

Also, I thought for a second I could just use the filtering for the project board to handle my milestones, but it looks like milestones aren’t availble to be used as filters on the project board so that was a dead-end as well.

If there is a better place to submit this idea or are you aware of an issue already posted I can add my support to, please let me know, thanks!

3 Likes

@efcarey Posting in the Community Forum with your ideas is a-okay! We do usually recommend people write into private support with feature requests, but we do see lots of people posting here in the forum as well. We always take any feature reqeusts and feedback we see here and share it internally, so your ideas will get seen!

1 Like

Just gonna add myself to the list of people who think it’s really important to be able to do something like this.

My situation: My team is dabbling with using GH for project management.  My developers all want to use Issues and PRs, because they want to be able to specify details, and they want to work at a per-repo level.  My boss likes Kanban boards, both because he likes the visual layout, and because he has more things he needs to juggle so he wants less detail.  The existence of organization-level Projects seemed like a two-birds-with-one-stone solution, because my boss conceptually groups multiple microservices as part of a single conceptual “chunk” of his architecture diagram (and he’s right).  And I don’t want to have to manually synchronize with Trello every day, and I’m too lazy to go look at Atlassian products.

Currently, every day I have to open every Issue and PR that might not have been added to the Project, and make sure it’s in the Project.  I can’t even see which ones need fixing without opening them individually!  This is currently a pain point that makes me wonder if I should look at some other tooling.

Potential solutions:

Ideally, I could automate this at a Repo level.  Ideally I could specify, per-repo, one or more Projects that Issues would be auto-added to, and the same thing for PRs.

Also ideally, in the list of Issues (ditto for PRs), there’d be a way to show what Projects an Issue has been assigned to.  Maybe a column where if there’s no Project it’s blank, and if there is a Project then you can hover to see a list, or something?  Heck, even just a number that counts how many Projects the Issue has been added to?

And then bulk Project-assignment (for both Issues and PRs) is another option, that could be an alternative to the auto-assignment feature I described above.  I imagine something like the way labels work in gmail?

5 Likes

You can provide similar feature as pull request templates. 
Allow us to add a file in git repository with the project name if it’s present you can auto-assign it 

5 Likes

would really love to have this too. or at least as @jholman suggests, an ability to view, filter and/or bulk update from the issues list. my current workaround is to filter by no:project to see new issues that were added, but i do need to keep an eye out for new issues that happened to be added to a different project than the one i want everything in.

2 Likes

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.

Cheers,

Chris

4 Likes

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”).

5 Likes

+10000 

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!)

Any updates? 

Thanks GitHub!

3 Likes

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).)

4 Likes

Strong +1 for this. For our team this is the dealbreaker to use Github Projects as our PM tool and replace other tools such as browser extensions on top of Github Issues.
Please prioritize this or at least bulk adding issues to a project.
+1000

4 Likes

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.

6 Likes

Hi any idea if this feature is available yet or not ?

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.

9 Likes

Hi everyone!

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:

  1. When would it be possible to collectively add issues to a certain project? By this I mean situation like this: I tick a couple of issues and add all of them to project. Now everytime I want to add couple of issues to the project I have to open each end every issue, one by one, to make it happen. It’s super not user friendly and because of that it’s harder to monitor project’s progress. 
  2. When all new issues I create will be automatically added to a certain project? 

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? :slight_smile:

15 Likes

+1 for this thing.

is there any life sign on the status of this?

Yes another +1 for this.

This is just one in a long list of things that annoy me about how many times you have to click in github to do anything (another being that there is no way to directly create an issue from the project board view - so annoying)!

1 Like

Yet another +1, hoping that this will get some attention.

I would like to have

  • new issue automatically added in a given project
  • move issues to “in progress” when assigned (or anther collumn, based on your automation settings)
  • create issue and add tags directly from the dashboard (lower priority)
4 Likes

This should be the default.

3 Likes

I too would love to see this function as everybody else is dreaming of.  It would make the project tool so much more useful for us.

2 Likes

Our team consistently has problems “losing” issues. We would very much benefit from this feature. Thanks!

2 Likes