Introduce a new design for Project.integrations GraphQL field

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

What

In the !108418 (merged), we deprecated the Project.services field, and we need to come up with a replacement as Project.integrations.

As per !108418 (comment 1243380434) and !108418 (comment 1253122173), we want a new design of the .integrations field.

Why

As per comments !108418 (comment 1243380434):

With the JiraIntegration the only one that has a __typename that isn't BaseIntegration. (and so doesn't need a serviceType or type, really). It feels like the type and serviceType fields are a bit of a non-GraphQL smell that we could fix by some design.

If we could take this opportunity to define (for now, what could be very generic) types per integration, that could be a good step in the direction we are likely to want to go in future.

and !108418 (comment 1253122173):

the current design is quite poor and doesn't make a lot of sense as a GraphQL response.