GitLab Design issueshttps://gitlab.com/gitlab-org/gitlab-design/-/issues2022-06-22T21:00:00Zhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1994UX Showcase - June 22, 20222022-06-22T21:00:00ZRayana Verissimorverissimo@gitlab.comUX Showcase - June 22, 2022<!--
Title should be: UX Showcase {{Stage Group}} {{DATE}}
(e.g. "UX Showcase CI/CD - March 2nd, 2022")
-->
Hi team :wave:!
We have a UX Showcasing coming up on `June 22, 2022`.
I'll be your host :microphone: @tauriedavis ! Please add ...<!--
Title should be: UX Showcase {{Stage Group}} {{DATE}}
(e.g. "UX Showcase CI/CD - March 2nd, 2022")
-->
Hi team :wave:!
We have a UX Showcasing coming up on `June 22, 2022`.
I'll be your host :microphone: @tauriedavis ! Please add the topic you'd like to showcase below so I can fill out the agenda prior to the showcase.
Here's what you need to know:
* Each presentation is 15 minutes and you should come prepared with sufficient artifacts to tell a story. **You do not need to create any special deliverable (such as slides) in order to present.** You can simply walk everyone through a mock-up in Figma etc.
* Use your best judgment to determine what will most effectively convey the story: sharing handbook/issues, a few slides, a process diagram, a journey map, a series of mockups, a prototype, etc.
* Please make sure you leave some time for audience questions.
For more info, please refer to the [UX Showcase handbook page](https://about.gitlab.com/handbook/engineering/ux/ux-department-workflow/ux-showcase) and watch the [video recordings](https://www.youtube.com/playlist?list=PL05JrBw4t0Kq89nFXtkVviaIfYQPptwJz) of previous showcases.
## Presenters
1. @andyvolpe - UX Roadmaps
1. @seggenberger - Beautifying our UI Changes in 15.1
1. @jeldergl - GitLab Rebrand
1. @andlovu - Configure Scorecard for Kubernetes agents
Questions? Thoughts? Let's discuss it below :point_down:Taurie DavisAndy VolpeRayana Verissimorverissimo@gitlab.comJeremy ElderAli Ndlovuandlovu@gitlab.comSascha EggenbergerTaurie Davis2022-06-22https://gitlab.com/gitlab-org/gitlab-design/-/issues/1991UX Transition for Michael Le from Create::Editor to Create::Source Code2022-08-18T00:15:14ZMarcel van Remmerdenmvanremmerden@gitlab.comUX Transition for Michael Le from Create::Editor to Create::Source Code## Context
This issue is dedicated to the seamless transition of UX and Design responsibilities for ~"group::source code" to @mle.
#### Timeline for the transition
| Milestone | Primary focus | Work for ~"group::editor" | Work for ~"g...## Context
This issue is dedicated to the seamless transition of UX and Design responsibilities for ~"group::source code" to @mle.
#### Timeline for the transition
| Milestone | Primary focus | Work for ~"group::editor" | Work for ~"group::source code" |
| --- | --- | --- | --- |
| `15.1` | Majority ~"group::editor": | Preparing and setting up https://gitlab.com/groups/gitlab-org/-/epics/7959 | Getting familiar with https://gitlab.com/groups/gitlab-org/-/epics/8075 and planning research |
| `15.2` | 50/50 Split | Executing solution validaton for https://gitlab.com/groups/gitlab-org/-/epics/7959 | Collaborating with `@leducmills` on research for https://gitlab.com/groups/gitlab-org/-/epics/8075 |
| `15.3` | Majority ~"group::source code" | Support with MR reviews for VS code implementation | Continuing the work on https://gitlab.com/groups/gitlab-org/-/epics/8075 |
| `15.4` | Fully transitioned to ~"group::source code" | minimal to none | Up to `@tlinz` and `@mle` |Michael LeMarcel van Remmerdenmvanremmerden@gitlab.comMichael Lehttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1985Coverage for Rayana from 2022-06-14 until 2022-06-232022-06-28T12:00:19ZRayana Verissimorverissimo@gitlab.comCoverage for Rayana from 2022-06-14 until 2022-06-23## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [takin...## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
| Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
| -------- | -------------- | ---- | ------------------ | -------------------- |
| HIGH | Expensify approvals | n/a | @vkarnes | n/a |
| HIGH | Review/approve handbook MRs | [See MRs assigned](https://gitlab.com/dashboard/merge_requests?reviewer_username=rayana) | @vkarnes | n/a |
| HIGH | EB onboarding tasks and additional support | https://gitlab.com/gitlab-org/gitlab-design/-/issues/1999+ | @vkarnes | @gdoyle |
| HIGH | Pajamas MRs/questions | [See MRs assigned](https://gitlab.com/gitlab-org/gitlab-services/design.gitlab.com/-/merge_requests?scope=all&state=opened&reviewer_username=rayana) | Please use the reviewer roulette assignment or reach out to the `#design-system` Slack channel for support |
| MEDIUM | Host UX Showcase, June 22 | https://gitlab.com/gitlab-org/gitlab-design/-/issues/1994+ | @tauriedavis | n/a |
| MEDIUM | Responding to UX related questions or providing feedback to the CI/CD UX team | #ux_ci-cd | @jmandell (will be OOO 2022-06-16, 17) | @vkarnes |
| MEDIUM | Release group - answer design-related questions in milestone issues (in dev) | #s_release and https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/131+ https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/132+ | #ux_ci-cd | |
| LOW | Host, record, upload EMEA/Americas CI/CD UX sync | [Agenda doc](https://docs.google.com/document/d/1fCMY77lzlsjHaCeqEY6pIw_K4bS_JYlfYlLJpPPJfKQ/edit#) | @gdoyle | n/a |
| LOW | OKRs check in | https://gitlab.com/gitlab-org/gitlab-design/-/issues/1978+ | @vkarnes | #ux_ci-cd |
| LOW | Urgent requests not specified above | n/a | @vkarnes | n/a |
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed by your backups.
- [ ] https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/131+ https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/132+ - Please keep an eye on questions or in-flight MRs for Release that need support (see `Deliverables` section) - @gdoyle @v_mishra @nadia_sotnikova @katiemacoy
- [x] https://gitlab.com/groups/gitlab-org/-/epics/7899+ - @wleidheiser @cbalane
## π Parked tasks
List the larger responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
- https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/132+ - milestone issues that are not UX ready will need to wait to be picked up until I return from PTO.
- https://gitlab.com/gitlab-org/gitlab-design/-/issues/1919+ - paused until I return from PTO.
- https://gitlab.com/gitlab-org/gitlab/-/issues/364527+ - paused until I return from PTO, but the team is welcome to leave their input async.
## :book: References
Here are some references for how I and my group generally works:
- https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/ci-cd/
## :white_check_mark: Issue Tasks
<details><summary>Click to expand</summary>
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [ ] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [ ] Assign to anyone with a specific task or responsibility assigned to them
- [ ] Share this issue in your section, stage and group Slack channels
- [ ] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [ ] Assign back to yourself and remove others
- [ ] Review any Retrospective items with your counterparts and manager
</details>
<!-- Do not remove the items below -->
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offRayana Verissimorverissimo@gitlab.comValerie KarnesRayana Verissimorverissimo@gitlab.com2022-06-23https://gitlab.com/gitlab-org/gitlab-design/-/issues/1978Tracking Issue: FY23-Q2 UX OKRs for CI/CD2022-08-09T13:57:53ZRayana Verissimorverissimo@gitlab.comTracking Issue: FY23-Q2 UX OKRs for CI/CD# Overview
We use this issue to track our progress, discuss, and collaborate on the current [π UX department OKRs in Ally](https://app.ally.io/teams/39450/objectives?tab=0&time_period_id=135092&time_periods_mode=default&viewId=208933). ...# Overview
We use this issue to track our progress, discuss, and collaborate on the current [π UX department OKRs in Ally](https://app.ally.io/teams/39450/objectives?tab=0&time_period_id=135092&time_periods_mode=default&viewId=208933). This fiscal quarter will run from May 1, 2022 to July 31, 2022. Please leave a comment if you have any questions!
---
## Let's Contribute! :tada:
- The table below shows KRs where our team input is required. Please read their descriptions and post your questions in the original KR issues.
- Some of the KRs need to be updated manually by the DRIs. If youβre assigned to an item in the table below, make sure to check your name off in the respective KR tracking issue and leave a comment by pinging `@rayana` for awareness. This action will update the SSOT in Ally.
- If you are blocked or unable to deliver an item, communicate it directly with your manager as soon as possible and leave a status update in the respective KR issue.
## FY23-Q2 OKRs for CI/CD UX
| KR | DRIs | Status |
| ------ | ------ | ------ |
| **[100% of team members complete mid-year check in](https://gitlab.com/gitlab-org/gitlab-design/-/issues/2002)** | `@rayana` | β Complete |
| **[Resolve S1 and S2 SUS-impacting issues that are design complete](https://gitlab.com/gitlab-org/gitlab/-/issues/359914)** <br><br> You've completed the designs for the selected issues in Q1, and your PMs will schedule those for implementation in Q2. You will need to review the implementation MRs as they come in. | `@rayana @nadia_sotnikova @gdoyle @v_mishra @katiemacoy` | π’ On track |
| **[Get S2 SUS-impacting issues design complete](https://gitlab.com/gitlab-org/gitlab/-/issues/359967)** <br><br> Prioritize and work on the selected issue to get the the design complete in Q2. | `@rayana @nadia_sotnikova @gdoyle @v_mishra @katiemacoy` | π’ On track |
| [**Prepare JTBDs to support planned category maturity**](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1951) <br><br> Pland and prepare 1-2 JTBDs for the CM Scorecard process for the selected categories. | `@rayana @katiemacoy`| β Complete |
| [**Create UX Roadmaps**](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1953) <br><br> Create a UX roadmap with your PM for the selected stage groups. | `@rayana @gdoyle @katiemacoy` | π΄ At risk |
| [**Pajamas Migration Day**](https://gitlab.com/gl-retrospectives/ecosystem-stage/foundations-group/-/issues/16) <br><br> Schedule time this quarter to participate in the Migration Day and contribute by picking up issues ready to migrate. | `@rayana @nadia_sotnikova @gdoyle @v_mishra @katiemacoy` | β Complete |
| [**Improve the Product Designer Interviewing Process**](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1963) <br><br> Work with PM/EM to create a rubric for each interview question (per Level--Intermediate & Senior) to help guide interviewers in assessing candidates. | `@rayana` | π Behind |
### Status tracker
```
βͺοΈ Not started
π’ On track
π Behind
π΄ At risk
β Complete
```Rayana Verissimorverissimo@gitlab.comNadia Sotnikovansotnikova@gitlab.comVeethika MishraGina Doylegdoyle@gitlab.comKatie MacoyRayana Verissimorverissimo@gitlab.com2022-07-31https://gitlab.com/gitlab-org/gitlab-design/-/issues/1966Tracking Issue: JAM Team FY23 Q22022-07-29T18:35:34ZJustin MandellTracking Issue: JAM Team FY23 Q2# Overview
We use this issue to track our progress, discuss, and collaborate on the current [UX department OKRs](https://app.ally.io/teams/39450/objectives?tab=0&time_period_id=155986&viewId=208933)(:link: Ally). This fiscal quarter wil...# Overview
We use this issue to track our progress, discuss, and collaborate on the current [UX department OKRs](https://app.ally.io/teams/39450/objectives?tab=0&time_period_id=155986&viewId=208933)(:link: Ally). This fiscal quarter will run from `2022-05-01 to 2022-07-31`. Please leave a comment if you have any questions!
## Let's Contribute!
The list below only shows KRs where our team input is required. Once you complete a KR, please check your name off the list or within the issue provided to track that specific KR.
### 1. Positively impact SUS by burning down remaining S1 issues, supporting completion of S2 issues and continuing Pajamas migrations
[Get 35 S2 SUS-impacting issues design complete](https://gitlab.com/gitlab-org/gitlab/-/issues/359967)
* [ ] ~~@mfangman (https://gitlab.com/gitlab-org/gitlab/-/issues/345464+) (Secure)~~
* No longer an S2 --> S3
* [ ] ~~@beckalippert (https://gitlab.com/gitlab-org/gitlab/-/issues/345465+) (Secure)~~
* No longer an S2 --> S4
* [ ] ~~@beckalippert (https://gitlab.com/gitlab-org/gitlab/-/issues/346887+) (Secure)~~
* Replaced with https://gitlab.com/gitlab-org/gitlab/-/issues/359841 and given an S4
* [x] @andyvolpe (https://gitlab.com/gitlab-org/gitlab/-/issues/358192+) (Secure)
### 2. Make our UX department a "best place to work" for designers, researchers, and technical writers
[Complete 360 Reviews and/or Talent Assessment](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1952)
* β Team member completion tracked via checkboxes in above issue
### 3. Improve the Product Designer Interviewing Process
* [Standardize Product Designer Interview questions and create rubric](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1919)
* [x] @jmandell
* [Standardize Product Design Manager Interview questions and create rubric](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1929)
* [x] @jmandell
### 4. Help increase product maturity through strategic UX work
* key result title:Create and socialize UX roadmaps for 5 groups/stages
* [UX Roadmaps](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1953)
* [Socializing UX Roadmaps](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1954)
* [x] @andyvolpe
* [x] @jmandell
### 5. Help increase product maturity through strategic UX work
[Prepare 18 JTBDs to support planned category maturity](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1951)
1. Please confirm with your PMs in the above KR issue, that they still intend on increasing maturity. If they do not, they'll need to update the maturity date to reflect this.
* [x] Secret Detection (Security) @mfangman
* [ ] Infrastructure as Code (Configure) @andlovu
* [x] Incident Management (Monitor) @ameliabauerly
<!--
If a KR has its own tracking table, skip the checkboxes above and add the following comment:
β This KR has its own tracking table within the above Issue, please use it to track and discuss it.
-->
## Issue tasks
### :o: Opening Tasks
- [x] Manager: Assign to yourself and your design team.
- [x] Title the issue `Tracking Issue: UX OKRs for {{Group}} - FY{{YY}}-Q{{quarter number}}`
- [x] Fill in the KRs based on the UX Department OKRs.
- [x] Assign to team members with a specific task or responsibility assigned to them, @ them in the checklist.
- [x] Share this issue in your Slack channels and with the team members during your next 1:1.
### :x: Closing Tasks
- [x] Assign back to yourself and remove others.
- [x] Review any Retrospective items with your team.
---Justin MandellJustin Mandell2022-07-29https://gitlab.com/gitlab-org/gitlab-design/-/issues/1959Tracking Issue: FY23 Q2 - KRs for Team Planage2022-11-16T14:42:57ZBlair ChristopherTracking Issue: FY23 Q2 - KRs for Team Planage:calendar_spiral: [FY23 Fiscal Calendar](https://about.gitlab.com/handbook/finance/#fiscal-year)
### 1. :icecream: [Complete Mid Year Talent Assessment](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1955)
In this issue, we'll tra...:calendar_spiral: [FY23 Fiscal Calendar](https://about.gitlab.com/handbook/finance/#fiscal-year)
### 1. :icecream: [Complete Mid Year Talent Assessment](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1955)
In this issue, we'll track our KR progress for [Make our UX department a "best place to work" for designers, researchers, and technical writers.](https://app.ally.io/objectives/2038427?time_period_id=155985)
****
### 2. :cake: [Resolve 57 S1 and S2 SUS-impacting issues that are design complete](https://gitlab.com/gitlab-org/gitlab/-/issues/359914)
In Q1, we identified a number of S1 and S2 SUS-impacting issues to get to design complete by the end of the quarter. For Q2, our goal is to have them implemented in the product.
Note: If any issues listed below are not marked "Design complete" then they are carryovers from the Q1 KR and design should prioritize them early in Q2 for the development teams to pick up.
**There is a responsibility for the Product Manager, Product Designer and Developer for each Issue.**
****
### 3. :cookie: [Get 35 S2 SUS-impacting issues design complete](https://gitlab.com/gitlab-org/gitlab/-/issues/359967)
There are 61 issues listed below that we believe need design work in Q2. We need to narrow this list down to 35 that the UX department will commit to getting the design complete by the end of Q2 to be ready for development in Q3.
****
### 4. :coffee: [Prepare 18 JTBDs to support planned category maturity](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1951)
In Q2/Q3, there are 18 categories with a planned change of maturity. A [CM Scorecard](https://about.gitlab.com/handbook/engineering/ux/category-maturity-scorecards/) is needed for any category moving to Viable or higher maturity.
The following categories are to prepare 1-2 JTBDs as initial preparation for the CM Scorecard process. Categories listed for Q2 should be prioritized early in the quarter as a CM Scorecard is expected to be completed before the end of Q2.
@gitlab-com/gitlab-ux/planage-ux-teamBlair ChristopherBlair Christopherhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1958UX Coverage for Taurie Davis from 2022-04-28 until 2022-05-162022-05-20T17:46:02ZTaurie DavisUX Coverage for Taurie Davis from 2022-04-28 until 2022-05-16## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [takin...## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be a peer, your manager, or a peer/manager in a different department (e.g. product manager).
Responsibilities include reviewing merge requests, responding to UX related questions, providing feedback related to inflight development work, or responding to Slack inquiries.
| Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| High | Arkose Rapid Action - Attend or review agenda for daily stand ups and follow along with customization UI issue | https://gitlab.com/gitlab-org/gitlab/-/issues/356298 | @emilybauman | @kcomoli |
| High | Pajamas Migration OKR | https://gitlab.com/gitlab-com/Product/-/issues/3891#note_920080845 | @leipert | @cdybenko |
| High | Review candidates in greenhouse for open Foundations role | https://gitlab.greenhouse.io/sdash/5175611002 | @rdouglas-gitlab | @zkovacs |
| Med | Navigation questions - Be point person for any questions related to Navigation changes/research | N/A | @aregnery | @cdybenko |
| Med | Pajamas MRs/questions | N/A | @jeldergl | @aregnery |
| Med | Figma renewal in Coupa (Renewal due May 14). This is active in Coupa going through approvals. @adeolabadmos is our procurement contact. | https://gitlab.coupahost.com/requisition_headers/1533 | @clenneville | @jeldergl |
| Low | Urgent requests not specified above | N/A | @clenneville | - |
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed by your backups.
- [x] `Customize Arkose challenge UI` - https://gitlab.com/gitlab-org/gitlab/-/issues/356298 - @emilybauman
- [x] `Complete tracking for shared Pajamas OKR` - https://gitlab.com/gitlab-com/Product/-/issues/3891#note_920080845 - @leipert @cdybenko
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [x] Assign back to yourself and remove others
- [x] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offTaurie DavisTaurie Davishttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1957Get the GL Bot to auto remove issue weights upon workflow changes away from d...2023-08-23T12:26:12ZJustin MandellGet the GL Bot to auto remove issue weights upon workflow changes away from design### Problem to be solved
As part of better understanding a designer's work capacity it's recommended that team members utilize some system of [issue weighting](https://about.gitlab.com/handbook/engineering/ux/product-designer/#ux-issue-w...### Problem to be solved
As part of better understanding a designer's work capacity it's recommended that team members utilize some system of [issue weighting](https://about.gitlab.com/handbook/engineering/ux/product-designer/#ux-issue-weights). The easiest, most efficient, and GitLab value of dogfooding method would be to use the weight feature provided in our issues.
Unfortunately, many teams use the same issue that was used to discuss and track the design work as the development issue once the designs have been completed. This causes a problem because the weight from the previous design efforts will be retained regardless of the step in our product development flow the issue is currently in. Therefore causes engineering's capacity weights to be off unless a steadfast engineer has noticed this and manually removed the weight from the issue.
### Proposal
When an issue is moved from ~"workflow::design" to ~"workflow::planning breakdown" the GitLab Bot should automatically strip the weight from the issue resetting it back to nill.BacklogJustin MandellJustin Mandellhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1944Ensure Slack-to-GitLab workflows are seamless to minimize repetitive, manual ...2023-08-15T20:03:14ZKevin Chukchu@gitlab.comEnsure Slack-to-GitLab workflows are seamless to minimize repetitive, manual work for incident response teams## UX Theme
<!-- ### Theme statement. The combination of the beneficiary and need. (For instance; Reduce the effort for security teams to identify and escalate business-critical risks) -->
### Ensure Slack-to-GitLab workflows are sea...## UX Theme
<!-- ### Theme statement. The combination of the beneficiary and need. (For instance; Reduce the effort for security teams to identify and escalate business-critical risks) -->
### Ensure Slack-to-GitLab workflows are seamless to minimize repetitive, manual work for incident response teams
----
### Beneficiary
<!-- Who benefits from this theme? -->
- Incident response teams
#### Need & JTBD
<!-- What are the JTBD and needs related to this beneficiary/theme-->
- **JTBD:** I want to be able to integrate my tools together, so that all of my tools work together seamlessly and I don't have to spend time making the same updates in different tools.
- **Need:** Ensure that communication between different communications channels is seamless in incidents, so no important information gets lost.
#### Business objective
<!-- What is the business objective that will result from delivering this theme? These could be Sales rate / conversion rate, Success rate / completion rate, Traffic / visitor count, Engagement, or other measurable metrics.-->
Increase the number of Slack workspaces installing either the Slackbot or taking actions on GitLab issues from Slack.
### Confidence
<!--
How well do we understand the user's problem and their need?
- High confidence: themes validated by research and have no assumptions,
- Medium confidence: themes partially validated by customer feedback/insights though assumptions are still present,
- Low confidence: themes are assumptive and have no prior research or customer feedback/insights
-->
| Confidence | Research |
| --- | --- |
| Medium | [Monitor JTBD Validation Survey](https://gitlab.com/gitlab-org/ux-research/-/issues/1142) |
### Subthemes
<!-- Subthemes are more granular validated needs, goals, and additional details that the theme encompasses. These are typically reserved for themes in the next (1-3 milestones) column. Subthemes may also consist of existing feature or design issues that exist in GitLab and directly relate to the theme.
Note: This is not a backlog. If the subthemes can not be delivered in the theme timeframe then the theme is too big and needs to be broken down into multiple themes.
-->
#### Feature/solution subthemes
<!-- Use this table to track feature issues related to this theme (if applicable). Not all themes require subthemes as subthemes are typically discovered while working on the theme itself. Think of subthemes as if they were the result of design breaking down the issue into discrete work items.
Note: if feature issues already exist then you can add them to this table. Keep in mind that subthemes require validation if they are assumptive
-->
| Opportunity | Issue link | UX Weight | Workflow status |
| ----------- | ---------- | --------- | --------------- |
| Enable a fuller Slack-to-GitLab workflow | [Design discovery: Slack integration for incidents](https://gitlab.com/gitlab-org/gitlab/-/issues/364422) | 0 | :white_check_mark: |
| Enable a fuller Slack-to-GitLab workflow | [Design: Introduce incident management workflow to GitLab Slack App](https://gitlab.com/gitlab-org/gitlab/-/issues/359322) | 0 | :white_check_mark: | |
| Enable a fuller Slack-to-GitLab workflow | [Configure Slack channel in alert payload](https://gitlab.com/gitlab-org/gitlab/-/issues/254398) | 0 | ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow | [Allow for a separate place to define Slack notifications for incidents](https://gitlab.com/gitlab-org/gitlab/-/issues/367550) | 1| ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow | [Allow for the opening of incidents from Slack](https://gitlab.com/gitlab-org/gitlab/-/issues/344856) | 0| ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow | [Display Slack notification when an incident has been created](https://gitlab.com/gitlab-org/gitlab/-/issues/369365) | 0 | ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow | [Improve comment integration between Slack and GitLab](https://gitlab.com/gitlab-org/gitlab/-/issues/345063) | 0 | ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow |https://gitlab.com/gitlab-org/gitlab/-/issues/365366+ | 0 | ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow | https://gitlab.com/gitlab-org/gitlab/-/issues/365371+ | 0 | ~"workflow::ready for development" |
| Enable a fuller Slack-to-GitLab workflow |https://gitlab.com/gitlab-org/gitlab/-/issues/367571+ | 0 | ~"workflow::ready for development" |
#### Research subthemes
<!-- Use this table to track UX research related to this theme. This may include, problem validation and/or solution validation activities.
-->
| Opportunity | Issue link | Research type |
| ----------- | ---------- | --------- |
| Enable a fuller Slack-to-GitLab workflow | [Problem validation: Slack and incident management workflows](https://gitlab.com/gitlab-org/gitlab/-/issues/333030) | ~"UX problem validation" |
<!--
-->Next 1-3 releaseshttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1938Automatically assign MR reviews for Community Contributions to group designer2024-02-27T10:50:51ZMarcel van Remmerdenmvanremmerden@gitlab.comAutomatically assign MR reviews for Community Contributions to group designerWith the new changes to the UX MR review process, we should work on automating MR reviews for community contributions, so that they will be automatically assigned to the designer of the group.With the new changes to the UX MR review process, we should work on automating MR reviews for community contributions, so that they will be automatically assigned to the designer of the group.Marcel van Remmerdenmvanremmerden@gitlab.comMarcel van Remmerdenmvanremmerden@gitlab.comhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1921π Track Group Onboarding Learnings per Month - 2022 Career Development2023-06-20T23:11:16ZJustin Mandellπ Track Group Onboarding Learnings per Month - 2022 Career DevelopmentThis issue will allow me to gather and track the completion of each Stage's Product Designer Onboarding section I plan to complete a month based on my [Career Development goals for 2022](https://gitlab.com/gitlab-org/gitlab-design/-/issu...This issue will allow me to gather and track the completion of each Stage's Product Designer Onboarding section I plan to complete a month based on my [Career Development goals for 2022](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1888).
### Stage Onboarding
#### Configure
- [ ] Read [vision](https://about.gitlab.com/handbook/engineering/development/ops/configure/#vision)
- [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/direction/maturity/#configure).
- [ ] Watch Configure Research highlights (requires access to Dovetail, see Access requests section)
- [ ] [Terraform clips](https://dovetailapp.com/tags/69wKqLBHjwYYJuZZ9MiLN2) (\~9 minutes total)
- [ ] [Deployment clips](https://dovetailapp.com/tags/5TJD5srup1gR2qFMzh3hQ3) (\~13 minutes total)
- [ ] [Kubernetes clips](https://dovetailapp.com/tags/4F5VbTbRkrnrxDSVec1xrz) (\~2 minutes total)
- [ ] [Kubernetes & Deployment clips](https://dovetailapp.com/tags/3XOPcdO9XUTZqB7QtGBllm) (\~15 minutes)
- [ ] Complete [Kubernetes training](https://learnk8s.io/)
- [ ] Read [Terraform training](https://www.terraformupandrunning.com/) (this can be expensed)
- [ ] Work with PM (@nagyv-gitlab) to set up a demo project (super difficult task for a designer! Leave 3-4 days for it.)
#### Monitor - Respond
#### Secure & Protect
* [ ] Read its [vision](https://about.gitlab.com/direction/product-vision/#secure).
* [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/direction/maturity/#secure).
* [ ] See our team's [Secure UX](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/secure/) page - if you notice any updates needed, please create a merge request!
* [ ] Start collaborating with your assigned UX Buddy. You both should arrange a day to have regular 1:1 calls (at least once a week).
* [ ] Review [Secure & Protect 101 Mural](https://app.mural.co/t/gitlab2474/m/gitlab2474/1573242955373/e0edcc6d4be079e36a7e26eebb0950961b9506c7)
#### Create
#### Enablement
#### Plan
#### Manage - Compliance
* [ ] Read its [vision](/gitlab-org/gitlab-design/-/blob/master/FILL%20WITH%20PRODUCT%20STAGE%20VISION%20PAGE%20URL).
* [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/direction/maturity/).
* [ ] Explore its [features](/gitlab-org/gitlab-design/-/blob/master/FILL%20WITH%20PRODUCT%20STAGE%20FEATURE%20URL) and [roadmap](/gitlab-org/gitlab-design/-/blob/master/FILL%20WITH%20PRODUCT%20STAGE%20ROADMAP%20URL)
#### Manage - Import/Optimize
* [ ] Read its [vision](https://about.gitlab.com/direction/manage/#vision-themes).
* [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/direction/maturity/).
* [ ] Explore its [features](https://about.gitlab.com/handbook/product/categories/features/#manage) and [Import Roadmap Board](https://gitlab.com/groups/gitlab-org/-/boards/1459561?label_name%5B%5D=group%3A%3Aimport) and [Optimize Roadmap Board](https://gitlab.com/groups/gitlab-org/-/boards/1459561?label_name%5B%5D=group::optimize)
#### Growth
Here is a welcome issue for Growth UX - https://gitlab.com/gitlab-org/growth/team-tasks/-/issues/326
#### Fulfillment
Fulfillment has a UX onboarding template of its own - https://gitlab.com/gitlab-org/fulfillment-meta/-/blob/master/.gitlab/issue_templates/onboarding_UX.md
#### Verify - Pipeline Insights
#### Verify - Pipeline Authoring
#### Verify - Pipeline Execution
#### Verify - Runner/Testing
* [ ] [Runner UX](https://www.youtube.com/watch?v=7Ye6KJHNEEc&list=PL05JrBw4t0Kr1B8ktQVCMZbUkZbP-0RuE) - please add all Runner UX recordings to this playlist
* [ ] [Testing group](https://www.youtube.com/watch?v=X_6s3kjxdug&list=PL05JrBw4t0Kq53VUOvTk3VdXN79PA0SXT)
* [ ] [Kickoff videos: Testing](https://www.youtube.com/watch?v=hTnTR5GKh5Y&list=PL05JrBw4t0KradvCrf8fL2pggEn5D3w2k)
* [ ] [Kickoff videos: Runner](https://www.youtube.com/watch?v=KdB3ktbr8Io&list=PL05JrBw4t0KrcC7xS0y8a8S9PlElg48bZ)
* [ ] [CI/CD UX Team meetings](https://www.youtube.com/watch?v=ViEs54I5lHE&list=PL05JrBw4t0Kpap0GkV0SSuGnPhCM8jrAv)
* Stage, group, or category handbook pages
* [ ] Runner: [Team page](https://about.gitlab.com/handbook/engineering/development/ops/verify/runner/) | [Direction and Categories](https://about.gitlab.com/handbook/product/categories/#runner-group)
* [ ] Testing: [Team page](https://about.gitlab.com/handbook/engineering/development/ops/verify/testing/) | [Direction and Categories](https://about.gitlab.com/handbook/product/categories/#testing-group)
* [ ] [Runners](https://www.youtube.com/watch?v=JFMXe1nMopo&list=PL05JrBw4t0KorkxIFgZGnzzxjZRCGROt_&index=33&t=0s) (GL Learning)
#### Package
* [ ] Understand our [product hierarchy](https://about.gitlab.com/handbook/product/categories/#hierarchy).
* [ ] Get to know your [stage's teammates](https://about.gitlab.com/handbook/product/categories/#devops-stages).
* *I've set up coffee chats with everyone that was in a semi-friendly timezone for me* :smile_cat:
* [ ] Read its [vision](https://about.gitlab.com/direction/ops/#package).
* [ ] Review the [Package stage direction](https://about.gitlab.com/direction/package/).
* [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/direction/maturity/).
* [ ] Review the [Package category maturity plan](https://gitlab.com/groups/gitlab-org/-/epics/2972).
* [ ] Explore its [features](https://about.gitlab.com/direction/package/#categories) and [issues roadmap](https://gitlab.com/groups/gitlab-org/-/boards/1397751?scope=all&utf8=%E2%9C%93&label_name%5B%5D=group%3A%3Apackage)
* [ ] Learn more about how the Package team works on the [Package Group page.](https://about.gitlab.com/handbook/engineering/development/ops/package/)
* [ ] Review the [Package UX Vision page.](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/package/)
* [ ] Watch product demos and more on [GitLab Learn](https://about.gitlab.com/learn/)
* [ ] Look up Package videos on [GitLab Unfiltered Youtube channel](https://www.youtube.com/channel/UCMtZ0sc1HHNtGGWZFDRTh5A) and see if anything catches your attention.
* [ ] Review the existing Package research insights [in Dovetail.](https://dovetailapp.com/projects)
#### Release
* [ ] Read its [vision](https://about.gitlab.com/direction/release/).
* [ ] See where it stands in terms of [category maturity](https://about.gitlab.com/handbook/product/categories/maturity/).
* [ ] Explore its [features](https://about.gitlab.com/handbook/product/categories/features/#release) and [roadmap](https://gitlab.com/groups/gitlab-org/-/roadmap?scope=all&utf8=%E2%9C%93&state=opened&label_name%5B%5D=devops%3A%3Arelease)
* [ ] Watch product [demos](https://about.gitlab.com/handbook/marketing/product-marketing/demo/)
#### Ecosystem - Foundations
#### Ecosystem - IntegrationsJustin MandellJustin Mandellhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1901Figma > File structure and organization2023-01-20T19:19:37ZJeremy ElderFigma > File structure and organization## Purpose
This issue links up a few discussions and examples of how the UX team has been structuring and organizing Figma files, and the content within, so that we could more formally arrive at and document a shared solution.
**Benefi...## Purpose
This issue links up a few discussions and examples of how the UX team has been structuring and organizing Figma files, and the content within, so that we could more formally arrive at and document a shared solution.
**Benefits**:
- Better onboarding process.
- More efficient cross-stage collaboration when understanding the file itself doesn't have to be learned.
- More efficient stage collaboration and know where/what to reference in Figma.
- Documentable and repeatable.
- Provides a starting point to collectively iterate on as new Figma features are available.
- Allows us to also consider how team libraries and shared assets can be used.
**Considerations**:
- File performance and bloat.
- Branching process.
- File thumbnails and quick reference.
- Collaboration with engineers, PMs, and other counterparts.
- Use case for drafts vs. team files?
- Use case for projects vs. individual team file?
## The ask
This issue is to help facilitate the discussion in a central place so that we can move towards documenting a shared solution in an MR as well as update the [Figma for GitLab](https://www.figma.com/file/73OcYdBfOaK2xlChC3tbNX/) guide. Add your thoughts, comments, use case in comments/threads below.
### Resources
- [Figma for GitLab](https://www.figma.com/file/73OcYdBfOaK2xlChC3tbNX/)
- [File organization](https://www.figma.com/best-practices/team-file-organization/files/)
- [Keeping files organized for your team](https://www.figma.com/best-practices/guide-to-developer-handoff/file-organization/)
- [How we Organize our Files and Projects in Figma](https://graphcms.com/blog/how-we-organize-our-files-and-projects-in-figma)
- [The Library + Flow approach to organizing Figma files](https://uxdesign.cc/the-library-flow-approach-to-organizing-figma-files-70c02135c71f)https://gitlab.com/gitlab-org/gitlab-design/-/issues/1868UX coverage for Alexis Ginsberg, Plan:Product Planning & Project Management -...2022-03-16T14:42:22ZAlexis GinsbergUX coverage for Alexis Ginsberg, Plan:Product Planning & Project Management - March 3-11, 2022## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [takin...## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be a peer, your manager, or a peer/manager in a different department (e.g. product manager).
Responsibilities include reviewing merge requests, responding to UX related questions, providing feedback related to inflight development work, or responding to Slack inquiries.
| Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| `HIGH` | Reviewing merge requests | https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&state=opened&reviewer_username=uhlexsis | [GitLab review roulette](https://gitlab-org.gitlab.io/gitlab-roulette/?sortKey=stats.avg30&mode=show&order=-1&hourFormat24=true&visible=reviewer%7CUX) for UX reviews (eg Secure Designers like @andyvolpe ) | @mushakov for domain knowledge |
| `MEDIUM` | Responding to urgent Plan specific questions | GitLab todos, Slack | @mushakov for product questions | @badnewsblair for design questions |
## :muscle: Coverage Tasks
Include specific issue links for tasks to be completed by your backups.
- [GitLab review roulette:](https://gitlab-org.gitlab.io/gitlab-roulette/?sortKey=stats.avg30&mode=show&order=-1&hourFormat24=true&visible=reviewer%7CUX) Review MRs related to [epic linking](https://gitlab.com/groups/gitlab-org/-/epics/7546). Please ensure ~UX is labeled for MRs needing review :mag:
- If urgent help is needed with an MR, please ping Blair or a designer on the Secure team for triage.
## π Parked tasks
List the larger responsibilities that aren't moving forward until I return, such as creating a prototype or planning/conducting research.
- Future design iteration on [epic links](https://gitlab.com/groups/gitlab-org/-/epics/7546)
- ~"workflow::design" items for Tasks
- ~"workflow::design" items for Planning Hierarchy
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [ ] Assign back to yourself and remove others
- [ ] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1864UX Showcase APAC & Europe - February 16th, 20222022-04-29T18:41:30ZMarcel van Remmerdenmvanremmerden@gitlab.comUX Showcase APAC & Europe - February 16th, 2022Hi team :wave:!
**We have a UX Showcase for APAC & Europe coming up on February 16th, 2022**.
I'll be your host :microphone: (@mle)! Please add the topic you'd like to showcase below so I can fill out the agenda prior to the showcase.
...Hi team :wave:!
**We have a UX Showcase for APAC & Europe coming up on February 16th, 2022**.
I'll be your host :microphone: (@mle)! Please add the topic you'd like to showcase below so I can fill out the agenda prior to the showcase.
Here's what you need to know:
* Each presentation is 15 minutes and you should come prepared with sufficient artifacts to tell a story. **You do not need to create any special deliverable (such as slides) in order to present.** You can simply walk everyone through a mock-up in Figma etc.
* Use your best judgment to determine what will most effectively convey the story: sharing handbook/issues, a few slides, a process diagram, a journey map, a series of mockups, a prototype, etc.
* Please make sure you leave some time for audience questions.
For more info, please refer to the [UX Showcase handbook page](https://about.gitlab.com/handbook/engineering/ux/ux-department-workflow/ux-showcase) and watch the [video recordings](https://www.youtube.com/playlist?list=PL05JrBw4t0Kq89nFXtkVviaIfYQPptwJz) of previous showcases.
## Presenters
* `@katiemacoy`
* `@v_mishra`
* `@nadia_sotnikova`
* `@marcel.amirault`
Questions? Thoughts? Let's discuss it below :point_down:Michael LeMarcel AmiraultNadia Sotnikovansotnikova@gitlab.comVeethika MishraKatie MacoyMichael Lehttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1859UX Coverage for Austin Regnery from Feb 3-8 || Feb 13-182022-03-05T15:35:03ZAustin RegneryUX Coverage for Austin Regnery from Feb 3-8 || Feb 13-18## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [takin...## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
| Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| [![Priority badge](https://img.shields.io/badge/Priority-High-red.svg)](https://shields.io/) | UX Buddy onboarding guidance | [UX onboarding](https://gitlab.com/gitlab-org/gitlab-design/-/issues/1860) | @badnewsblair | @gitlab-com/gitlab-ux/manage-ux |
| [![Priority badge](https://img.shields.io/badge/Priority-Medium-orange.svg)](https://shields.io/) | Merge request reviews for %"14.8" | [Merge request list](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&state=opened&label_name[]=group%3A%3Acompliance&milestone_title=14.8¬[approved_by_usernames][]=aregnery&label_name[]=UX) | @dmoraberlin | @gitlab-com/gitlab-ux/manage-ux |
## :muscle: Coverage Tasks
The biggest thing is I don't want Sascha to feel isolated. Consider reaching out and checking in while I am away.
For any merge request reviews, I can prioritize those from Feb 9-11th but if there are a few last minute items trying to be squeezed in then they'll need attention.
## π Parked tasks
Nothing is actively on-hold. Compliance work will be transitioning to Sascha as he on boards in the coming weeks.
## :book: References
- [Group Process Handbook Page](https://about.gitlab.com/direction/manage/compliance/#how-we-approach-problems)
- [UX Compliance Validation Track Board](https://gitlab.com/groups/gitlab-org/-/boards/1576904?scope=all&label_name[]=UX&label_name[]=group%3A%3Acompliance)
- [Planning issue for 14.8](https://gitlab.com/gitlab-org/manage/general-discussion/-/issues/17402)
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [ ] Assign back to yourself and remove others
- [ ] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offAustin RegneryAustin Regneryhttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1843Have Bot append ~SUS label to all SUS related issues now and future2022-01-20T17:36:58ZJustin MandellHave Bot append ~SUS label to all SUS related issues now and future### Problem
UX has identified 10 issue labels that are meant to address our SUS scores:
- `~Actionable Insight`
- `~Low SUS Score`
- `~UX scorecard-rec`
- `~cm-scorecard-rec`
- `~UX debt`
- `~UI polish`
- `~accessibility`
- `~VP-UX Dogf...### Problem
UX has identified 10 issue labels that are meant to address our SUS scores:
- `~Actionable Insight`
- `~Low SUS Score`
- `~UX scorecard-rec`
- `~cm-scorecard-rec`
- `~UX debt`
- `~UI polish`
- `~accessibility`
- `~VP-UX Dogfooding`
- `~learnability`
- `~UI text`
- `~"pajamas::integrate"`
Due to the nature of how our boards work it's not possible to track each of these across groups on a single board. In order to allow for this more easily, we need to add a single label. The recommended label is ~"SUS"
If this SUS label is added to all of the above labels via the bot then we'll be able to create boards across groups (lists in a board) so they can be visualized more easily and therefore prioritized during milestone planning more efficiently.
### Recommendation
* **Present/Existing:** Have the issue bot (not sure what this bot's real name is?) automatically apply the ~SUS label across all existing issues that also have one of the above 10 labels already applied.
* **Future:** Have the issue bot automatically apply the ~SUS label to any newly created issue that also has one of the above 10 labels already applied.Justin MandellJustin Mandell2022-01-31https://gitlab.com/gitlab-org/gitlab-design/-/issues/1822Prep Discussion Around Future Hackathons2022-07-14T22:19:58ZJustin MandellPrep Discussion Around Future Hackathons## Observed Problem
Hackathons are great! But they often require team members to spend more, unplanned, time reviewing UX MRs. This is compounded by the fact that some teams are more heavily affected by the MRs that are created as their...## Observed Problem
Hackathons are great! But they often require team members to spend more, unplanned, time reviewing UX MRs. This is compounded by the fact that some teams are more heavily affected by the MRs that are created as their groups have higher visibility or usage than others. This may lead some of those less heavily affected teams to work as usual by picking up MRs as they have time as opposed to making the extra time to help pick up the surplus during Hackathons.
This is again compounded when a hackathon falls within a holiday-heavy month such as December.
#### Additional Problems
Many of these MRs are also written incorrectly, lacking descriptions or not meeting code review guidelines. This makes it difficult to review an issue as they now require additional digging and research to more completely understand the work being done.
* **Suggestion:** Have the MR reviewer follow the [guidelines](https://docs.gitlab.com/ee/development/code_review.html#community-contributions), ping the author for additional information/clarification. If the author does not respond, ping the EM and PM to take over.
## Possible Solutions
* Prior to a hackathon kicking off be sure to include a warning about team member capacity during Milestone planning.
* I'd like to discuss everyone's thoughts about what is a reasonable amount of time (e.g. velocity weights) a team member should expect to set aside?
* Teams with heavy MRs to be reviewed could triage issues that they can't get to, marking the line item in the #ux-community-contributions channel and ping the @ gitlab-com/gitlab-ux/designers group in the issue
* Look into how dev teams manage this today as they tend to have many more MRs to be reviewed than we doPedro Moreira da SilvaAndy VolpeRayana Verissimorverissimo@gitlab.comMarcel van Remmerdenmvanremmerden@gitlab.comJacki Bauerjbauer@gitlab.comJustin MandellPedro Moreira da Silvahttps://gitlab.com/gitlab-org/gitlab-design/-/issues/1812KR UI redesign session 6: Activity & Comments (spans Create, Plan, and Secure)2024-02-12T14:13:41ZJeremy ElderKR UI redesign session 6: Activity & Comments (spans Create, Plan, and Secure)From https://gitlab.com/groups/gitlab-org/-/epics/7151#note_735055147:
#### What are some challenges you're facing with the current design?
* Since comments can be threaded, comments don't always appear in chronological order, making i...From https://gitlab.com/groups/gitlab-org/-/epics/7151#note_735055147:
#### What are some challenges you're facing with the current design?
* Since comments can be threaded, comments don't always appear in chronological order, making it difficult to find certain things (namely- "what happened since I last looked at this?")
* On merge requests, comments can be on either the `Overview` tab or `Changes` tab. Diff comments appear in both places. Outdated diff comments appear only on the Overview
* All activity items are given equal weight, despite some being more important than others. For example, `@user merged this` is more important than `@user mentioned this in a comment`
#### What are some key areas you'd like addressed?
* Update different types of activity to call attention/decrease visibility depending on activity type
* Maybe combine certain activity types if the same type is listed multiple times
* brainstorm ideas to help users understand what happened since they last visited (this might be a bit too big for this OKR :thinking:)
#### How could this benefit other areas of the product?
This focuses mostly on Code Review and Plan (issues & epics) but also touches areas like Secure (activity on a reported vulnerability)
#### Links or screenshots.
[Slide deck from last UX showcase](https://docs.google.com/presentation/d/1kxEPX-oCU6Re8oHfKp-WBP86ZpP09jGu4gNwP_I0iwU/edit?usp=sharing) (Slides 8-11 highlight this problem in Code Review)14.10https://gitlab.com/gitlab-org/gitlab-design/-/issues/1805UX Coverage for Daniel Fosco for 2021-12-24 until 2021-12-312022-01-04T18:55:30ZDaniel FoscoUX Coverage for Daniel Fosco for 2021-12-24 until 2021-12-31## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [takin...## Intent
This issue describes how broader group and team members are facilitating a members of the UX Department to take meaningful time away from work. The intent is that the folks aren't required to "catch-up" before and after [taking a well-deserved vacation][time-off].
## :handshake: Responsibilities
List the priorities that the responsible backups need to cover. Backups can be a peer, your manager, or a peer/manager in a different department (e.g. product manager).
Responsibilities include reviewing merge requests, responding to UX related questions, providing feedback related to inflight development work, or responding to Slack inquiries.
| Priority | Responsibility | Link | Primary backup DRI | Secondary backup DRI |
| ----------------- | -------------------- | ------------------ | ----------- | --------- |
| HIGH | Reviewing Merge Requests | [MRs with Daniel as reviewer](https://gitlab.com/gitlab-org/gitlab/-/merge_requests?scope=all&state=opened&reviewer_username=dfosco) | @v_mishra | @rayana |
| MEDIUM | Respond to (urgent) team requests/questions in Slack | `#ux_ci-cd` or `#s_release` | @v_mishra | @rayana |
## :muscle: Coverage Tasks
Ongoing tasks that need to be covered will be listed under `workflow::design` in Release team's [Plan board](https://gitlab.com/groups/gitlab-org/-/boards/1489550?label_name[]=devops%3A%3Arelease&label_name[]=group%3A%3Arelease&label_name[]=Next%20Up). Those might require responding to UX-related questions and comments.
Total MR Reviews expected during coverage period: 1
| Task | Type | DRI | Notes |
| ------ | ------ | ------ | ------ |
| [New Environment Item](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/74418) ([issue](https://gitlab.com/gitlab-org/gitlab/-/issues/343028/)) | Ongoing MR Review | @v_mishra | This is an ongoing MR that is already reviewed, but might need another pass of :eyes: from UX |
## π Parked tasks
The current items below are being worked on for `14.7` and will not moving forward until I return. They have been scheduled with this PTO in mind however, and are expected to be finished within the milestone regardless.
See details on the [14.7 Planning issue](https://gitlab.com/gitlab-org/ci-cd/release-group/release/-/issues/88).
| Issue | Weight | Note |
|-------|--------|------|
| [Update Project Settings to be able to set approval count](https://gitlab.com/gitlab-org/gitlab/-/issues/344675) | 2 | |
| [Display Environment Tier on the Environments Page](https://gitlab.com/gitlab-org/gitlab/-/issues/322600/) | 2 | |
| [Add "Open live environment" Button to Pipeline List View](https://gitlab.com/gitlab-org/gitlab/-/issues/18441) | 3 | ~"UX FY21-Q4" |
| [UX Scorecard - Release: FY22-Q3-Q4 - Environment Management Viable](https://gitlab.com/gitlab-org/gitlab/-/issues/341526) | 3 | ~"UX research" |
| [Release Group - Release Orchestration JTBD Review](https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/12492) | 2 | ~"Jobs to be Done (JTBD)" |
## :book: References
Here are some references for how I and my group generally works:
- [Release Group UX](https://about.gitlab.com/handbook/engineering/ux/stage-group-ux-strategy/release/)
- [Release Group Planning](https://about.gitlab.com/handbook/engineering/development/ops/release/planning/)
- [Release Group](https://about.gitlab.com/handbook/engineering/development/ops/release/)
- [Deployment Direction](https://about.gitlab.com/direction/deployment/)
## :white_check_mark: Issue Tasks
### :o: Opening Tasks
- [x] Assign to yourself
- [x] Title the issue `UX Coverage for YOUR-NAME from XXXX-XX-XX until XXXX-XX-XX`
- [x] Add an issue comment for your retrospective titled: `:recycle: Retrospective Thread`
- [x] Add any relevant references including direction pages, ux handbook pages, etc
- [x] Fill in the Responsibilities table with broad based responsibilities
- [x] Fill in the specific Coverage Tasks with distinct items to complete and assignees
- [x] Assign to anyone with a specific task or responsibility assigned to them
- [x] Share this issue in your section, stage and group Slack channels
- [x] Ensure your PTO Ninja auto-responder points team members to this issue
### :x: Closing Tasks
- [x] Assign back to yourself and remove others
- [x] Review any Retrospective items with your counterparts and manager
<!-- Do not remove the items below -->
[time-off]: https://about.gitlab.com/handbook/engineering/ux/how-we-work/#time-offDaniel FoscoDaniel Fosco2022-01-04https://gitlab.com/gitlab-org/gitlab-design/-/issues/1803Drag & drop target indicator2022-05-12T16:32:59ZNick PostDrag & drop target indicator### Problem
We have a number of drag & drop interactions across the product such as issue lists and issue boards. Sometimes the content in each item looks very similar which makes it hard to see where a dragged item is being dropped.
#...### Problem
We have a number of drag & drop interactions across the product such as issue lists and issue boards. Sometimes the content in each item looks very similar which makes it hard to see where a dragged item is being dropped.
### Proposal
Similar to Notion, it would be nice to have a blue bar as an indicator for where the dragged item is being dropped...
![Screenshot_2021-11-15_at_17.54._2x](/uploads/607651c9354e2ca926a3bbd71a7a9c2c/Screenshot_2021-11-15_at_17.54._2x.png)