Missing chat message integration for epics

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

This issue is about IntegrationSlack chat_message service.

Summary

This is difficult to show but easy to reproduce. We have slack integration setup but it appears there is no way to configure chat message for epics. Creation of an epic, commenting on an epic and closing an epic are all very important activity that needs to be kept an eye on. If there are TODOs on epics they do show up, but the general chatter via slack integration is something that is missing.

I think what is needed is an implementation of chat_message integration for Epics - similar to issue_message here. What are we missing?

Steps to reproduce

  1. Create a group named group1
  2. create a project under group1, named project 1
  3. Create a slack integration for the project using standard steps
  4. Create an issue (issue1) and verify that slack integration sends the message on the configured slack channel
  5. Add a comment on issue1 and verify that a message on the slack channel
  6. Add an epic epic1 under group1 - no message on slack
  7. Add comments on epic1 - no message on slack

There is just no slack integration possible on the group level at the moment - and we are losing out on a lot of chatter on the product since we started using epics, and it took a while to realize that. The only things we are really notified about is when we @mention someone but we don't really want to mention everyone and the purpose of the slack integration is that things just show up and those who are interested can take a look. It's quite an important thing that is missing.

Example Project

What is the current bug behavior?

Creation of epic or adding comment to an epic does not send a message on slack.

What is the expected correct behavior?

Creation of epic or adding comment to an existing epic sends a message on slack similar to how slack integration on projects (creation of issue and comments on issue).

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖