GraphQL API teams are not associating with new components in Compass UI?

[John Medina]

By using GraphQL to get Compass TeamIDs (refer to: searchTeams Query), and using the results in the createComponent GraphQL mutation (refer to: createComponent mutation) we're seeing that our team isn't fully being associated with the new component.

The details view of the component shows the ownership (eg: https://<org>.atlassian.net/compass/component/<component id>), but listing all component by team x isn't showing the component. We also can't see the component assigned to the team on their team page eg: https://<org>.atlassian.net/compass/people/team/<team id>).

Our theory is that there is a mismatch in the teamIDs being returned from the GraphQL vs interactions with the UI.

GraphQL returned teamID format: ari:cloud:identity::team/XXXXXXXX-XXXX...

UI call teamID format: ari:cloud:teams::team/XXXXXXXX-XXXX...

[John Medina]

There were issues uploading the pseudo code-blocks for the graphQL queries, but here are screenshots of them.

[Andrei]

Hi John, thank you so much for flagging this.

Our theory is that there is a mismatch in the teamIDs being returned from the GraphQL vs interactions with the UI.

Yeah, your intuition here is spot on.

We've raised this with one of our engineering teams and they'll address this as soon as possible.

In the interim, just so you can get unblocked, what you could do is replace the type identifier ( i.e. the `ari:cloud:identity::team` bit ) with `ari:cloud:teams::team` on the id that's sent back by the Teams Query. The ID bit is the same, so everything else should just work.

Apologies for the hassle here and thank you again for taking the time to explain this so thoroughly.

[John Medina]

Hi Andrei, 

Thank you for confirming our theory. We have put that workaround in place for now.

Could you post an update here when this bug is fixed so we know when we to remove the temporary workaround?

[Andrei]

Will do!

[John Medina]

Hello @Andrei ,

My team and I were just revisiting this work on this project and thought we would probe this discussion again. Have there been any updates on this bug?

Thanks,

John