@ekigbo Here is the MR to add these guidelines to Pajamas: Add error handling cases (!5761).

What does this MR do?

This MR adds error handling guideline specific to the Dashboard panel (https://design.gitlab.com/components/dashboard-panel).

Closes #1889

Screenshots or screen recordings

Integrations

• GitLab: mr_url
• CustomersDot: mr_url
• Duo UI: mr_url
• Status Page: mr_url
• Docs: mr_url
• Switchboard: mr_url

Does this MR meet the acceptance criteria?

This checklist encourages the authors, reviewers, and maintainers of merge requests (MRs) to confirm changes were analyzed for conformity with the project's guidelines, security and accessibility.

Toggle the acceptance checklist

Conformity

• The “What does this MR do?” section in the MR description is filled out, explaining the reasons for and scope of the proposed changes, per “Say why not just what”.
  • For example, if the MR is focused on usage guidelines, addressing accessibility challenges could be added in a separate MR.
• Relevant label(s) are applied to the MR.
• The MR is added to a milestone.
• Added the ~"component:*" label(s) if applicable.
• A changeset is added when this MR will do a patch, minor, or major update. More information can be found in doc/publishing-packages.md.

Components

• GitLab UI's contributing guidelines.
• If the MR changes a component's API, integration MR(s) have been opened (see integrations above).

Documentation

• If creating a new component page from scratch, it follows the page template structure.
• Content follows the GitLab Documentation Style Guide when appropriate.
• Related pages are cross-linked, where helpful. Component pages have related components and patterns defined in their Markdown front matter.
• If embedding a Figma file, it follows the Figma embed guide.
• Review requested from any GitLab designer or directly from a maintainer or trainee maintainer.
• Maintainer review follows the Pajamas UX maintainer review checklist.

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• Security reports checked/validated by a reviewer from the AppSec team

Accessibility

If this MR adds or modifies a component, take a few moments to review the following:

• All actions and functionality can be done with a keyboard.
• Links, buttons, and controls have a visible focus state.
• All content is presented in text or with a text equivalent. For example, alt text for SVG, or aria-label for icons that have meaning or perform actions.
• Changes in a component’s state are announced by a screen reader. For example, changing aria-expanded="false" to aria-expanded="true" when an accordion is expanded.
• Color combinations have sufficient contrast.

Libor Vanc (02b3b70c) at 19 Mar 01:20

Libor Vanc (6e2280d3) at 19 Mar 00:58

Link

This would open the dynamic panel with the error details. See Move dashboard panel errors to dynamic panel (gitlab-org/gitlab#523311).

@ekigbo Just a heads up. Since the app chrome has changed after this issue was initially opened, I updated the issue to now use the dynamic panel, instead of the drawer to hold the error details. See updated mockups in the the issue description. Also, moving this to workflowplanning breakdown.

/cc @blabuschagne

Insufficient permissions

Link:

https://docs.gitlab.com/user/permissions/#application-security-group-permissions

Link

This should link to the docs for the specific metric, for example: https://docs.gitlab.com/user/group/issues_analytics/

Higher tier required

Should be displayed as an Empty state not and not an Error as suggested in the Pajamas guidelines.

Closing this issue since this will be addressed in UX: Define error handling and messaging for das... (gitlab-org/gitlab-services/design.gitlab.com#1889).

@rutshah @diegocapetown Thanks for the questions. Here is how I am thinking about this...

Explore->Analytics Dashboards-> CI/CD Analytics

• This dashboard would live outside our current group/project hierarchy
• Since this dashboard would be initially group only, It would only include group / sub-group filters
• The dashboard could also support multiple groups
• In the future, this dashboard could support project filtering

The goal is that the dashboard will exist in one place.

Linking

The details of this are still TBD and we will continue to collaborate on this more once our teams gets closer to diving into this, but at a high level, I still see it working as you mentioned:

• Explore->Analytics Dashboard -> Engineering Intelligence -> Pipeline Performance Trends -> Filtered view of CI/CD Analytics

For Project level

What's the plan for the current dashboards under Analyze in this new design?

We have been in the process of migrating and consolidating the ones with the most usage out of the group/project hierarchy and deprecating the dashboards with low to no usage. See Group::Optimize Dashboard Feature Deprecations ... (gitlab-org#19129).

/cc @lfarina8 @blabuschagne feel free to add anything I may have missed.