Follow-up from "Edited notifications docs" (#35390) · Issues · GitLab.org / GitLab

Marcel's follow-up items

The following discussions from !19341 (merged) should be addressed:

- You participate in an issue, merge request, or epic. In this context, *participate* means comment, or edit.
- You enable notifications in an issue, merge request, or epic. To enable notifications, click the **Notifications** toggle in the sidebar to *on*.

Additionally, I think it might be useful to mention that participating is in effect the same as turning on notifications manually. So, expanding the idea above:

- You participate in an issue, merge request, or epic. In this context, *participate* means comment, or edit, which will cause notifications to automatically be enabled.
- You manually enable notifications in an issue, merge request, or epic. To enable notifications, click the **Notifications** toggle in the sidebar to *on*.

@marcel.amirault started a discussion:

tune -> manage

The quantity of notifications can be overwhelming. GitLab allows you to manage the notifications you receive. For example, you may want to be notified about all activity in a specific project, but for others, only be notified when you are mentioned by name.

@marcel.amirault started a discussion:

Perhaps:

You can manage the notifications by adjusting:

@marcel.amirault started a discussion:

My preference for this type is to avoid list, sublist, list, sublist, etc. Also, I think the second item, notifications should be groups and projects, maybe?

- Notification email: The email address your notifications will be sent to.
- Global notification level: The default [notification level](#notification-levels) which applies to all your groups and projects.
- Receive notifications about your own activity: Check this checkbox if you want to receive notification about your own activity. Default: Not checked.

Optionally, bolded, but that's personal preference:

- **Notification email**: The email address your notifications will be sent to.
- **Global notification level**: The default [notification level](#notification-levels) which applies to all your groups and projects.
- **Receive notifications about your own activity**: Check this checkbox if you want to receive notification about your own activity. Default: Not checked.

@marcel.amirault started a discussion:

Clarification:

Your **Global notification settings** are the default settings for all projects and groups, unless you select different values for specific projects or groups.

@marcel.amirault started a discussion:

Like above, and changing italics to asterisks:

- Project: For each project, you can select a notification level. Your project setting overrides the group setting.
- Group: For each group, you can select a notification level. Your group setting overrides your default setting.
- Global (default): Your global, or *default*, notification level applies if you have not selected a notification level for the project or group in which the activity occurred.

- **Project**: For each project, you can select a notification level. Your project setting overrides the group setting.
- **Group**: For each group, you can select a notification level. Your group setting overrides your default setting.
- **Global (default)**: Your global, or *default*, notification level applies if you have not selected a notification level for the project or group in which the activity occurred.

@marcel.amirault started a discussion:
For a followup, we could have two nested lists, perhaps?

From profile:
- List
From project page:
- List
@marcel.amirault started a discussion:
Maybe just keep it all under group notifications?
@marcel.amirault started a discussion:
Like above, for a followup, we could have two nested lists, perhaps?

From profile:
- List
From group page:
- List
@marcel.amirault started a discussion:

I'd like to see this expanded in a followup with more details right here.

@marcel.amirault started a discussion:

Always?

Users will always be notified of the following events:

Mike's follow-up items

(originally from #35402 (closed); merged the follow-up issues)

The following discussions from !19341 (merged) should be addressed:

@mikelewis started a discussion:
I agree with Marcel but I'd prefer
- Bolded UI element label - Description.
(With the period only if most are full sentences per our list style.)

However, I'm happy if we document a style and stick to it.
@mikelewis started a discussion:

I think this should be "switch" the toggle to 'on'. Or switch the toggle to the 'on' position. Or, simply, you 'enable Notifications using the toggle..'. We should document a style on this.
@mikelewis started a discussion:

"you will be notified of"
@mikelewis started a discussion:

"Click your profile picture"?

Need to confirm/clarify our style
@mikelewis started a discussion:

Should be "Issues, epics, and merge request events"?
@mikelewis started a discussion:

Lowercase H per style