Skip to content
GitLab
Next

Ensure we (GitLab) use all our features.

Definition of the "do we use it?": someone on the team clicks on the link at least once and month to gain some new information.

Interviewed different people and collected their feedback into a google doc.
https://docs.google.com/document/d/1n0WaJKfenTzewXUm5H59azorI3TIdhdHlBnwleNElBM/edit?usp=sharing

Feature name Do we use it? Can we use it? Must Improve/Issue Action Items
Across All Products Macro UX Patterns Not scheduled
Contribution analytics No No Graphs are unreadble Scheduled for 11.0
Burndown charts Yes(GCP migration) Yes and No Burndown charts don't exist at the group level Scheduled for 10.8
Service Desk Yes Yes
  • Tries to replace email
  • Email works just fine
  • Needs private comments
  • We aren't beating Zendesks workflow. Have a long way to go there.
  • Support is
  • Legal was going to use it but it didn't make sense.
 In a good enough state right now. Product should review if private comments are a possibility
Container Registry yes
  • Add audit log
  • Known Docker upstream bug: delete a tag and other tag that belong to it delete those other tags get deleted as well
  • Container images retention policy
 Schedule a PR for docker that will fix this outstanding bug
Issues board Yes Yes
  • Subgroup support
  • The UI doesn't make sense to many outside of product. Trello is much easier.
  • Sub groups can be really confusing to users, i.e. Labels and the milestones and ancestors groups and projects.
 Full Subgroup support by 11.0.
Speak with UX to make paradigms more clear.
Approvals Yes Yes
  • Multiple blocking groups
  • Some don't feel like we are using it properly.
  • Should accept approvers from multiple groups, like FE, BE, UX and Product.
 Talk to UX and Product about implementing missing features.
Epics and roadmaps Yes Yes https://about.gitlab.com/direction/#portfolio-management-and-issue-management
Deploy Boards No No No. We don't have any apps to deploy yet. Find applications of ours that will fit into the paradigms of deploy boards and use them.
Auto DevOps Yes (Cloud Native charts) Yes and no See https://gitlab.com/charts/gitlab/blob/master/.gitlab-ci.yml Enable it for our internal apps. https://gitlab.com/gitlab-com/version-gitlab-com/issues/111 and https://gitlab.com/gitlab-com/license-gitlab-com/issues/79.
Application performance monitoring Yes (Cloud Native charts) Yes We deploy GitLab and have monitoring enabled, see https://gitlab.com/charts/gitlab/environments/190276/metrics
 Find more applications of ours that will fit into the paradigms of application performance monitoring and use them.
Cycle analytics No No No one uses it. The data is not that interesting. A lot of the data is empty for CE and EE. We have so much activity and we just have no data. We think the concept is interesting but it's not useful, interesting. It would be really interesting to know within GitLab, how long did it take for someone to respond to a MR. See where things are slowing down in the pipeline. Overlaps with: https://gitlab.com/gitlab-org/ux-research/issues/24 & https://gitlab.com/gitlab-org/gitlab-ce/issues/37195. Users aren’t currently utilising Cycle Analytics as it’s too restrictive - it doesn’t support their workflow or report the data they need. First and foremost, users want a way to track and report on existing project progress (via dashboards) as opposed to retrospectively looking at project progress (via Cycle Analytics). Internally, it's a similar situation: &135 (closed) (Team dashboard)
Cohorts No No No one uses it because it just isn't useful. Do UX Research to figure out how to make the data more interesting.
Review Apps Yes Barely Pain to get working. Lot's of custom configurations just to get it working. Hard to get it working at all. 
        </td>
        <td> <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/43442">Setup review apps for CE/EE</a><br/>Do UX Research to figure out how to make it easy to use on it's own.</td>
    </tr>
    <tr>
        <td>GitLab Pages</td>
        <td>Yes</td>
        <td>Yes</td>
        <td>Review app support, and <a href="https://gitlab.com/gitlab-org/gitlab-ce/issues/30548">missing subgroup support</a>
        </td>
        <td>Talk to Product about getting review app support in gitlab pages.</td>
    </tr>
    <tr>
        <td>Cluster integration</td>
        <td>No</td>
        <td>No</td>
        <td>No. We don&#39;t have any apps to deploy yet.</td>
        <td>Find some applications that will fit into the flow of cluster integration and use it.</td>
    </tr>
    <tr>
        <td><a href="https://docs.gitlab.com/ee/ci/multi_project_pipeline_graphs.html">Multi-project pipelines</a></td>
        <td>No</td>
        <td>No</td>
        <td>We really need this but not in the way we have it implemented. It needs to be a first class citizen, see <a href="https://gitlab.com/gitlab-org/gitlab-ee/issues/933#note_57971984">https://gitlab.com/gitlab-org/gitlab-ee/issues/933#note_57971984</a></td>
        <td>Do UX Research to figure out how to make it a more useful feature.</td>
    </tr>
    <tr>
        <td><a href="https://docs.gitlab.com/ee/user/project/merge_requests/sast.html">SAST</a></td>
        <td>Yes and No</td>
        <td>Yes</td>
        <td>Standard job config, languages support, report content.
Enable it for more projects
Dependency Scanning Not yet (added in %10.7) Yes (added in %10.7) Standard job config, languages support, report content None
Container Scanning ? Yes (with whitelisting) Standard job config, whitelisting, report content None
DAST Yes and No Yes Standard job config, languages support, report content None
Code Quality Yes and No Yes Standard job config None
Blocking manual actions No Yes and No Using blocking manual actions with GitLab QA Do UX Research to figure out how to make the data more interesting.
Edited by Takuya Noguchi