Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab Design
GitLab Design
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 252
    • Issues 252
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 1
    • Merge requests 1
  • Requirements
    • Requirements
    • List
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • GitLab.org
  • GitLab DesignGitLab Design
  • Issues
  • #274

Closed
Open
Created Feb 27, 2019 by Amelia Bauerly@ameliabauerlyDeveloper0 of 11 tasks completed0/11 tasks

Toggling data points on charts

Problem

ECharts allows us to toggle data points on and off. But, the feature is hidden so most people would probably miss that it's even there.

Two things to explore:

  • Is there a way we can better signal to users that this feature is available?
  • How should the toggling work? Should it grey out the data series or completely remove it from the chart? Default ECharts behavior is to grey it out; in the security dashboard, it currently disappears.

Solution

(What’s the solution? Why is it like that? What are the benefits?)

Example(s)

(One or more images showing the UX pattern. They don’t have to be in GitLab.)

Usage

(When do you use this pattern? And how?)

Dos and dont's

(Use this table to add images and text describing what’s ok and not ok.)

✅ Do 🛑 Don’t

Related patterns

(List any related or similar solutions. If none, write: No related patterns)

Links / references

Pattern checklist

Make sure these are completed before closing the issue, with a link to the relevant commit, if applicable.

  1. Read our contribution guidelines, especially the For GitLabbers section.
  2. Create a Sketch file in your progress folder just for this pattern and make sure that:
    1. You have not created a duplicate of an existing pattern, symbol, layer style, or text style.
    2. You have used the proper method for creating the pattern depending on the complexity. Atoms and molecules are symbols, organisms are groups.
    3. Typography uses text styles. When applicable, colors use shared styles.
  3. Ask a UXer to review your Sketch file, linking them to your latest commit so they know where to find it. If they have the capacity, they should assign themselves to this issue.
  4. QA of your Sketch file by the reviewer.
  5. Add your changes to the pattern library. When copying things over, watch out for duplicated symbols, layer styles, and text styles. Some of our recommended plugins can help you find and remove duplicates.
  6. QA of pattern library by the reviewer.
  7. Create an issue in the Design System to add the pattern documentation. Mark it as related to this issue.
  8. Add an agenda item to the next UX weekly call to inform everyone (if it's a new pattern, not yet used in the application).

/cc @gitlab-com/gitlab-ux

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking