Update Slack's `GitLab` app description to communicate support for notifications

added to epic &8670 (closed)

changed title from Update Slack's GitLab Landing Page to communicate support for Notifications in the GitLab for Slack App to Update Slack's {++}GitLab {+for Slack App l+}anding page to communicate support for notifications

changed the description

added UX devopsmanage groupintegrations [DEPRECATED] sectiondev typefeature labels

assigned to @lvanc

mentioned in epic &8670 (closed)

Setting label(s) Category:Integrations based on ~"group::integrations".

added Category:Integrations label

marked this issue as blocking #381012 (closed)

changed milestone to %Backlog

changed milestone to %15.7

added Deliverable label

@lvanc I don't think this requires engineering support. I think we'll just need to have the content created and submit via the App Directory before the next App Submission. Or, at minimum the change could likely be done at any time for the landing page content.

We could probably test by updating the App Name to GitLab for Slack since we're already making these changes (see Docs).

@.luke Do you agree? Any opposition to updating the app name to align with our docs?

@g.hickman It sounds like GitLab for Slack would be okay by Slack's title policy:

If your Slack app integrates with another service, include the name of that service in your app name. If you do not own the service, make sure to not infringe on any trademarks or copyright (e.g., “Task notifications for Slack” rather than “Slack task notifications”).

But to be honest, when I look at things like the Apps we have installed, I think the more concise GitLab is probably better - people know that it's "for Slack" because the context of "for Slack" is very strong! It would seem to me a bit redundant for this app to be named GitLab for Slack:

@.luke That's a good point. Maybe for the app itself, we use GitLab, but everywhere else it's GitLab for Slack. I thought there may be a chance to create some consistency with other integrations like the GitLab for Jira app. But that's a solid point. @lvanc?

In either case, when we do update the basic info to include details about the slack notifications within the app, will that require an app submission? Or will the page update without a review? I don't recall how that played out last time.

when we do update the basic info to include details about the slack notifications within the app, will that require an app submission?

@g.hickman Yes, these details all get published when we republish our Slack app to the Slack App Directory. We're able to change the App Home contents at any time though.

@.luke Ah ok, we do need to "republish" and get changes approved, including the contents in the description. I thought there were some bits from the App Directory page we could change at will, but that must be only the App Home. Thanks for confirming.

@g.hickman in regards to the naming of the app, I agree with @.luke's comment:

...It would seem to me a bit redundant for this app to be named GitLab for Slack

To me is also seems potentially confusing adding App to the title: GitLab for Slack App. This also seems redunant.

If the goal is to consolidate all of the Slack related integrations into a single app, I would vote for just calling it GitLab as well.

Preview:

GitLab for Slack app	GitLab

@lvanc Would you agree with this?

"Maybe for the app itself, we use GitLab, but everywhere else it's GitLab for Slack.

@lvanc I wonder as well if we may need to revisit how we display the apps in GitLab, in our project settings:

Screenshot from testing env

Maybe in the product UI, we just refer to the service (GitLab <> Slack), but in docs and marketing, GitLab for Slack app. Thoughts?

@g.hickman I am good with your suggestion:

Maybe for the app itself, we use GitLab, but everywhere else it's GitLab for Slack.

I can see the need for saying: GitLab for Slack on the project integrations list view and in our docs and marketing.

Do you still think we need to include the word: App?

Note: we should update: https://gitlab.com/gitlab-org/manage/integrations/team/-/blob/main/integrations/slack.md#terms when this issue is resolved.

@lvanc As we discussed today, I think primarily we want to be consistent. We have the GitLab for Jira app as well. I'd like to pick an approach for when we are communicating about our integrations in docs/marketing.

I would clarify that in the Integrations list view, I think this could be confusing or redundant so in any product UIs, I think we could stick to using just GitLab or Slack (GitLab in the Slack app directory, or in the app itself when the app appears, or Slack in the project settings list view). If we have two integrations with a 3rd party, we could add context -- Slack app / Slack integration, or Slack slash commands, Slack notifications.

Integrations and app both seem somewhat generic and extraneous, so I can see the point there. If we choose to remove this, I'd prefer we do it soon and stick to it. And that we apply this logic across the board (such as updating the GitLab for Jira app terminology in product UIs.

@lvanc Capturing here the conversation with @dfrhodes regarding how we reference integrations in-app (or in product UIs) vs in marketing/docs:

cc @tichen

added backend label

set weight to 1

I'll label workflowready for design as backend can update the app details once we have the new copy supplied.

added workflowready for design label

added workflowdesign label and removed workflowready for design label

changed title from Update Slack's GitLab{- for Slack App landing page-} to communicate support for notifications to Update Slack's GitLab{+ app description+} to communicate support for notifications

marked this issue as blocking #384226 (closed)

mentioned in issue #384226 (closed)

@lvanc @g.hickman This is the only blocking issue of #384226 (closed) - if we were to decide what the updated description should be within a couple of days, then we could submit the app for review #384226 (closed) within %15.7 otherwise that issue would be at risk of slipping.