+1, this is an important feature for my team. We use a monorepo on GitHub, and run only 1 project in Sentry, but we have many projects in ClubHouse (product, platform, analytics, ...) that all tie into the same Sentry project.

The obvious workaround for an end-user creating a new story is to just change the project in ClubHouse after adding, but this is 1) annoying, and 2) doesn't address linking to existing issues in other projects.

@miketheman wondering if you came across this one?

@mkj28 I hadn't, thanks for pointing it out.

In thinking about this, it seems like adding a config flag to search all projects might work, default to search only the configured project might solve the problem.

I think keeping the project value required makes sense as that makes it explicit on where new stories go, even if that is then manually duplicated across multiple sentry projects.

Does that sound like it would solve the need?

At least for us - that would work great. We can search all projects if flag enabled, and keep the project listed as the default one for new stories.... yes.

I believe the linked PR will solve the linking case - I don't know how common the case @ssalka brings up with a mono-sentry approach to create new stories is - but this ought to cover searching for existing stories.