GitLab CI/CD UX Milestone Kick-off, 19 May 2020

Previous Meeting Next Meeting

⏯

youtube image

►

From YouTube: UX Kickoff 13.1 - Release:Release Management

Description

Welcome to the 13.1 Release Management UX kickoff! I am Rayana Verissimo, Sr. Product Designer at GitLab.

The Release Management Team is responsible for the categories of Release Evidence, Release Orchestration, Secrets Management, and GitLab Pages. In 13.1 we are taking a moment to improve visibility into performance, enhancing the backstage and technical aspects of GitLab that support the Release Management features.

I will focus on working hands on with some frontend issues, in order to burn down the UX Debt that was part of our backlog. UX Debt means that for a given issue, we failed to meet defined standards for our Design system or for usability and feature viability standards as defined in agreed-upon design assets.

In parallel, I’ll be working on some of the Release Orchestration items that are currently in the workflow:design phase.

- https://gitlab.com/gitlab-org/gitlab/-/issues/195692
- https://gitlab.com/gitlab-org/gitlab/-/issues/212063
- https://gitlab.com/gitlab-org/gitlab/-/issues/199429
- https://gitlab.com/gitlab-org/gitlab/-/issues/214082
- https://gitlab.com/gitlab-org/gitlab/-/issues/196168
- More about UX Debt: https://about.gitlab.com/handbook/engineering/ux/performance-indicators/#ux-debt

A

Hi, everyone welcome to the 13.1 release management UX kickoff. My name is Hana video I'm, a senior product designer at gate, lab working with the release management team. Our team is responsible for the categories of police, evidence, release orchestration secrets management and get lab pages for our journey release. Our team has decided that we would like to invest some time in the backstage and technical features that will support the greatest release management capabilities rather than investing in our typical Direction items.

A

I had a chance to choose which issues I would like to work on and I chose to focus on working on hands on UX Deb issues that were in our backlog. Ux. That means that, for a given issue, we fail to me defined standards for design system or usability and feature viability standards as defined in agreed-upon design assets. So the first issue I'm gonna, be working on will be polishing, the UI of the environments at work by fixing the x-axis padding on the Batchelor content.

A

This is a very small fix that will help clean up the UI very nicely. The second UX step issue is focus on improving the usability of the releases page by fixing the image of a fluid list when an image is added to the release. Notes that you can see right now, if you add an image that it's a bit wider than the content, then the card, the image will overflow and break the page layout in parallel. I will be working on some of the release, orchestration items there in the workflow design page.

A

The first item is identification of historical releases in the UI. The challenge here comes from the fact that no evidence is created and collected for a release with a date in the past, as it was it's not easily known, which milestone and issues were present at that historical data that at that point in time.

A

So the other story for this issue is, as a user I want to be able to identify release items that were created with a date in the past, so that I can understand what release and that release and know what to expect. Regarding the evidence, collection, which is not present in historical releases, the you wax for this issue is already proposed and our team is rooming it right now. The second issue on aims to help users choose a release, name in a semantic version.

A

This is an embassy, it's part of a broader effort on making sure that users can create semantic releases, and for now we want to be able to let release management quickly, see which name or versions they gave to previous releases, so that it can name a new item with confidence in a semantic way. The last issue involves a broader discussion and support environments. At the group level, production environments are special ones, and sometimes we could have several environments. They are used as production.

A

Currently, the growing heat lab roles leave the ability to edit environments and trigger a manual release to production really vulnerable. The low-hanging fruit identified here will be on improving the existing environments that work so that we can include pagination and also improve the visualization of environments that are added. On this view.

A

I'll be rooming this issue to cover the stories and designs assets, to include visibility into environments across projects to be shared by users within a group in different projects, administration of environments across project and creating context when a single environment is being used in different projects. So this this issue here it's going to be broken down into smaller pieces of design and engineering efforts. If any of these issues interests, you and you're excited to learn more, please reach out to me at Ayane or in any of these issues.

A

13.1 is going to be the bathroom news ever.