Exports · GitLab

GitLab issues export to dashboard

Upload the file you already download from GitLab. Every Number reads it with no setup, picks a screen, and puts a receipt on every number.

The question behind this file

How many issues were opened and closed per milestone this month, and how does time spent compare to estimates?

What you get

By person

One row per person, with their numbers side by side.

Assignee says who handled each issue, so time spent is compared person by person.

You can switch it to Pipeline, This period vs last, Breakdown, Key numbers under “How it's read”.

Click any number for its receipt: the rule, the rows it used, and the rows it left out.

Getting the file

  1. Download it from GitLab

    In your GitLab project, go to Plan, then Work items, filter to issues, and choose Actions, then Export as CSV. The file arrives by email.

    GitLab's guide

  2. Know what a row is

    One row is one issue.

  3. Upload it as it is

    No cleanup first. Title rows, totals rows and repeated headers are skipped and listed in each receipt.

The 26 columns we tested with, from GitLab's documentation

ID · IID · Title · Description · Type · URL · State · Confidential · Locked · Milestone · Labels · Author · Author Username · Assignee · Assignee Username · Created At (UTC) · Updated At (UTC) · Closed At (UTC) · Due Date · Start Date · Parent ID · Parent IID · Parent Title · Time Estimate · Time Spent · Weight

How we know

This file is one of the 100 in our reading test. The column names are GitLab's; the rows were generated to fit them, since we don't have your file. Your export may have more or fewer columns, and Every Number shows how it read each one before you build.