You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Love the library, as it reduces the amount of work we do in the UI and allows us a nice paper-trail for teams changing.
We have teams which are parented under an umbrella team for permissions reasons. When a new team is created via the script it'd be nice if we wouldn't have to go update the team to use the right parent team.
As far as implementation goes I think you'd need to:
Check if the team is in the metadata and needs creating and create it first
Otherwise check if it exists (and error if it doesn't)
This does introduce an ordering in how teams are created, but that should be relatively easy to code.
Thanks!
The text was updated successfully, but these errors were encountered:
Glad to hear this action is useful for your organization! (BTW, I'm curious what you searched to discover it.)
We haven't been using parent teams in my organization, but I can see how this would be useful in that setup. Are you interested in contributing this feature?
I try and do that before I go off and implement something myself.
And I should say so far it's worked as expected 🎉 . You've saved me a lot of manual UI work!
Are you interested in contributing this feature?
I am, but we're still in the process of defining our process for open-source contributions, so it'd likely be a few weeks at least before you'd see a PR from me 😢 . If you (or someone else) implements it in the meantime, I wouldn't mind.
👋
Love the library, as it reduces the amount of work we do in the UI and allows us a nice paper-trail for teams changing.
We have teams which are parented under an umbrella team for permissions reasons. When a new team is created via the script it'd be nice if we wouldn't have to go update the team to use the right parent team.
As far as implementation goes I think you'd need to:
This does introduce an ordering in how teams are created, but that should be relatively easy to code.
Thanks!
The text was updated successfully, but these errors were encountered: