[martinwoodward]

The new project experience allows you to track issues that are in different projects, prioritise them alongside each other etc. I work at GitHub where we've been trying this out for a while and it's working pretty well so far for a bunch of the projects I work on when you need that cross-project visibility and co-ordination.

[dbingham]

I think a lot of these problems would be solved by just adding an "Issues" tab alongside the "Projects" tab at the organization level - with all the features that go along with that (Milestones, labels). Then you could have issues at the organizational level, separate from repositories, and that would allow you to better deal with stories spanning multiple repositories. Especially since these updates (which are fantastic by the way) seem to be adding support epics and the like, it wouldn't be unreasonable at all for epics to span multiple repositories (Frontend, backend, infrastructure or multiple microservices in a multi-repo setup). Conceptually, putting those issues on one of those repositories feels wrong. Putting them on the organization is much clearer.

[buro9]

What I need:

1. Issues that can be linked to other issues (regardless of repo), i.e. local issue blocked by remote issue

2. Projects that can contain issues from multiple repos, even a mix of public and private repos

Please say this is now possible, otherwise we too are looking at Linear, Jira, etc when we'd like to be looking at Github.

[munk-a]

For #1 hasn't this been possible for a long time via including the issue linking text: OrgName/project#12345 in either an issue body or comment text - or else including it in a commit message?

Due to #1 our org created a no-code repository for hosting all of our issues and it's worked out pretty well - PRs reference the ticket using the issue linking text above and it all works pretty seamlessly - the only slight hiccup is that we only write issues in the no-code repository since splitting issues across repo would cause milestoning issues for releases.

[martinwoodward]

It is indeed now possible. Give it a try and let us know what you think.

[mook]

Can projects now contain issues from multiple _orgs_? I've had worked on things that spanned orgs before, and as far as I know projects couldn't handle that.

I'm really glad subtasks is now a thing!