Alerts > Dismissible
A common question I am asked is: Should this alert be dismissible?
In the design system we currently say:
Alerts may contain a dismiss button and an action button depending on the situation.
There is no guidance on when or when not to include the option to dismiss. We should add more guidance to help here.
Decisions:
- Update alert documentation:
Add dismissal rules and use cases:
Dismissal
Alerts may contain a dismiss action and may include an additional action button depending on the use case.
Dismissable alerts
Alerts that can be removed by the user and can reappear if an action or system event reproduces the alert.
Use dismissable alerts when the user's task is not blocked if they do not take action.
- The user dismisses a system-generated alert notifying them their .gitlab-ci.yml config file has an issue. Alert reappears the next time the config problem stops a process from running.
Non-dismissable alerts
Alerts that can only be removed after a system condition is met.
Use non-dismissable alerts when the user is prevented from completing a task until a system-condition is met.
- The user encounters an alert notifying them their license has expired. The alert is only removed when they have uploaded a new license in the admin area.
- Follow-up conversation about including a "remind later" function within alerts in issue: #406 (closed)