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
{{ message }}
This repository was archived by the owner on Jan 25, 2020. It is now read-only.
new threads/channels/groups should be able to automatically be created for any integration impact is linked to, such that a new sub-context will become available inside of a chat context, when a new context is created within the integration.
sub-context: a channel or group, existing within an impact team.
Let's take github for example:
You should be able to associate an impact team to either a github organization, or a github team.
Whenever a new github team is added to a github organization that is associated to an impact team, it should automatically create a new sub-context inside the `impact team
Whenever a new github repository is added to a github team associated with an impact team, it should create a new sub-context
Considerations
Privacy/visibility settings of the new context item from the integration (new github team/repo), should carry over, or sync via LDAP, to the access and visibility of the sub-context in impact.
The privacy/visibiltiy settings could determine what type of sub-context is created. For example, if a github team is publicly visible, perhaps a channel is added to the impact team. However, if the github team is not publicly visible, then it creates a private group inside the impact team.