Change: Extends allNotifications with optional filters

[CGoodwin90]

General Checklist

• Affected Issues have been mentioned in the Closing issues section
• Documentation has been written/updated
• PR title is ready for inclusion in changelog

Database Migrations

• If your PR contains a database migation, it MUST be the latest in date order alphabetically

Extends allNotifications to have an optional name & type input.

[shreddedbacon]

Just re-based and pushed (didn't change any code) before finalising review

[shreddedbacon]

This works fine, but I'm wondering if this is the best approach to this now.

The name and type filters are nice, but I don't know if this is something that is really useful for anyone that isn't a platform-owner. Type is also sort of irrelevant because of the way the resolver works with fragments.

With organizations also being a thing, the likelihood of someone using this that isn't a platform-owner is probably low.

I can't recall if there was a specific reason for these changes or not though, but maybe we can get away without this change for now?

[CGoodwin90]

This works fine, but I'm wondering if this is the best approach to this now.

The name and type filters are nice, but I don't know if this is something that is really useful for anyone that isn't a platform-owner. Type is also sort of irrelevant because of the way the resolver works with fragments.

With organizations also being a thing, the likelihood of someone using this that isn't a platform-owner is probably low.

I can't recall if there was a specific reason for these changes or not though, but maybe we can get away without this change for now?

It was just so we had a way to retrieve unassigned notifications, right now once created they're essentially lost to the void until assigned to a project. I think there were some commands in the cli where this might be useful, but not super necessary. Happy to proceed without it for now though.

[shreddedbacon]

It was just so we had a way to retrieve unassigned notifications, right now once created they're essentially lost to the void until assigned to a project. I think there were some commands in the cli where this might be useful, but not super necessary. Happy to proceed without it for now though.

Ahh that's right. Yeah, I think it might need some adjustments, so maybe we can bump this to 2.22.0 instead. I'll add some review comments with some suggested changes.