-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
Severity 3 - Minor
Issue Summary
If a user has a private shared-connect channel in Slack, and the @Statuspage App had been added in one slack workspace, and the other slack workspace subscribes to a Statuspage, it will not add the StatusPage App on the subscribing slack workspace and thus not configure the subscription.
Steps to Reproduce
- Create two Slack workspaces
- Create a channel in the Slack workspace One (S1) as a Private channel.
- Share the channel with Slack workspace Two (S2)
- In accepting the invite on the S2 side, set the channel to private.
- Confirm the channel sharing was completed, and both workspaces had access to, and were in the channel.
- On SP1, add the Statuspage app (/invite @Statuspge) . Confirm the app was
present in the channel, and was visible by both the SP1 & SP2 Workspaces - Subscribe to a Statuspage Slack subscriptions, specifiying the Shared Connect Channel in the SP2 Workspace.
- We are in the situation, where the APP is installed in SP1, and the Subscription was made to SP2.
- You will see that the Statuspage App is not added to SP2, and the Channel is not integrated with Statuspage.
- Create an Incident in Statuspage - No notification will appear in channel.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available
- derives
-
STSPG-10430 Failed to load
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[STATUS-260] Slack Subscriptions into Shared Connect Channels do not invite and configure @Statuspage App if it has been added on other Slack workspace
| Workflow | Original: JAC Bug Workflow v3 [ 4249968 ] | New: JAC Bug Workflow v4 [ 4565927 ] |
| Assignee | Original: Abhay Sarraf [ 11b3b30e0c37 ] |
| Assignee | New: Abhay Sarraf [ 11b3b30e0c37 ] |
| Remote Link | New: This issue links to "STSPG-10430 (Statuspage Jira)" [ 648680 ] |
| Symptom Severity | Original: Minor [ 16130 ] | New: Severity 3 - Minor [ 15832 ] |
| Assignee | Original: Parker Hotchkiss [ photchkiss ] |
| Status | Original: Needs Triage [ 10030 ] | New: Long Term Backlog [ 12073 ] |
| Description |
Original:
h3. Issue Summary
If a user has a private shared-connect channel in Slack, and the @Statuspage App had been added in one slack workspace, and the other slack workspace subscribes to a Statuspage, it will not add the StatusPage App on the subscribing slack workspace and thus not configure the subscription. h3. Steps to Reproduce # Create two Slack workspaces # Create a channel in the Slack workspace One (S1) as a Private channel. # Share the channel with Slack workspace Two (S2) # In accepting the invite on the S2 side, set the channel to private. # Confirm the channel sharing was completed, and both workspaces had access to, and were in the channel. # On SP1, add the Statuspage app (/invite @Statuspge) . Confirm the app was present in the channel, and was visible by both the SP1 & SP2 Workspaces # Subscribe to a Statuspage Slack subscriptions, specifiying the Shared Connect Channel in the SP2 Workspace. # We are in the situation, where the APP is installed in SP1, and the Subscription was made to SP2. # You will see that the Statuspage App is not added to SP2, and the Channel is not integrated with Statuspage. # Create an Incident in Statuspage - No notification will appear in channel. h3. Expected Results a h3. Actual Results a The below exception is thrown in the xxxxxxx.log file: {noformat} ... {noformat} h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |
New:
h3. Issue Summary
If a user has a private shared-connect channel in Slack, and the @Statuspage App had been added in one slack workspace, and the other slack workspace subscribes to a Statuspage, it will not add the StatusPage App on the subscribing slack workspace and thus not configure the subscription. h3. Steps to Reproduce # Create two Slack workspaces # Create a channel in the Slack workspace One (S1) as a Private channel. # Share the channel with Slack workspace Two (S2) # In accepting the invite on the S2 side, set the channel to private. # Confirm the channel sharing was completed, and both workspaces had access to, and were in the channel. # On SP1, add the Statuspage app (/invite @Statuspge) . Confirm the app was present in the channel, and was visible by both the SP1 & SP2 Workspaces # Subscribe to a Statuspage Slack subscriptions, specifiying the Shared Connect Channel in the SP2 Workspace. # We are in the situation, where the APP is installed in SP1, and the Subscription was made to SP2. # You will see that the Statuspage App is not added to SP2, and the Channel is not integrated with Statuspage. # Create an Incident in Statuspage - No notification will appear in channel. h3. Workaround Currently there is no known workaround for this behavior. A workaround will be added here when available |