Page MenuHomePhabricator
Create Task
Maniphest T301189

Explore Phabricator → Slack integration
Closed, ResolvedPublic
Actions

Description

I'm moving this from a thread on WMF Slack and collecting a few notes.

@DLynch wondered if anyone has set up a feed of new tickets from Phabricator to Slack.

There's some consensus that Slack admin changes would require review from ITS/Legal/Security.

@mmodell mentions https://github.com/etcinit/phabulous

@matmarex came up with a hack-around approach to this using Herald rules and Slack's ability to receive mail:

https://phabricator.wikimedia.org/p/Slack_connector_for_Editing_team_triage/

I wrote:

my plate is kind of full at the moment, but i can probably file a task for this and push on it periodically. it's something i haven't taken a lot of direct interest in out of a general distaste for slack and its silo-ization of so much of our important technical communication, but that ship has very clearly sailed at this point. at least displaying phabricator here might encourage people to document / interact with things in public more.

I'll try to follow up on this as I get more up to speed on Phab.

Somewhat related:

  • T288117 - Show previews for Phabricator links in Slack (and other messaging apps)

cc: @bcampbell for awareness on the Slack admin side of things.

Related Objects

Event Timeline

brennen created this task.Feb 7 2022, 9:10 PM
Restricted Application added a subscriber: Aklapper. · View Herald TranscriptFeb 7 2022, 9:10 PM
bcampbell added a comment.Feb 7 2022, 10:01 PM

Hey @brennen we currently use the Slack "email a channel" for a couple different hacky purposes. I don't think implementing for your team would necessarily require a Legal/Security review. Who would be able to access the Slack channel email address on the Phabricator side of things?

Our Slack is currently configured to allow any user to create an email address for a Slack channel, but it is possible for us to restrict sending emails to channels by domain using an allowlist. Ideally, we would have it set up this way with an associated approval process, but that doesn't exist currently.

Going with the phabulous Slack bot solution would require an ITS/Legal/Security review (https://office.wikimedia.org/wiki/Slack#Slack_App_approval_process).

brennen moved this task from INBOX to Seen on the Release-Engineering-Team board.Feb 7 2022, 10:03 PM
brennen edited projects, added Release-Engineering-Team (Seen); removed Release-Engineering-Team.
brennen added a comment.Feb 7 2022, 10:18 PM

I don't think implementing for your team would necessarily require a Legal/Security review. Who would be able to access the Slack channel email address on the Phabricator side of things?

Yeah, I didn't expect so. So far as I know, email addresses are only visible to the user in Phabricator.

Going with the phabulous Slack bot solution would require an ITS/Legal/Security review (https://office.wikimedia.org/wiki/Slack#Slack_App_approval_process).

We'll probably pursue something like that at some point. Asking any team who wants this in a channel to manage a Phab user and Herald rules feels pretty clunky, even if it doesn't have any other downsides.

Aklapper moved this task from To Triage to External on the Phabricator board.Mar 27 2022, 1:00 PM
Aklapper mentioned this in T331517: Test task.Mar 9 2023, 2:08 PM
Aklapper triaged this task as Low priority.Jul 13 2023, 5:52 PM

Would T321790: Allow tools to use phabricator webhooks be relevant?

gmodena subscribed.Sep 12 2023, 10:54 AM
Aklapper closed this task as Resolved.Nov 14 2023, 5:49 PM
Aklapper added a subscriber: Slack_connector_for_Editing_team_triage.

@Slack_connector_for_Editing_team_triage exists, thus Phabricator → Slack integration has been explored by at least by one WMF team. :)
Thus resolving. See that account description for more info.

Content licensed under Creative Commons Attribution-ShareAlike (CC BY-SA) 4.0 unless otherwise noted; code licensed under GNU General Public License (GPL) 2.0 or later and other open source licenses. By using this site, you agree to the Terms of Use, Privacy Policy, and Code of Conduct. · Wikimedia Foundation · Privacy Policy · Code of Conduct · Terms of Use · Disclaimer · CC-BY-SA · GPL