GitLab issueshttps://gitlab.com/gitlab-org/gitlab/-/issues2024-03-26T00:02:19Zhttps://gitlab.com/gitlab-org/gitlab/-/issues/451924Docs: "Manage your code" needs organization2024-03-26T00:02:19ZSuzanne SelhornDocs: "Manage your code" needs organizationThe docs under [**Manage your code**](https://docs.gitlab.com/ee/topics/manage_code.html) need more organization. Right now the bulk of the content is in two large buckets (**Repositories** and **Merge requests**). The content should be ...The docs under [**Manage your code**](https://docs.gitlab.com/ee/topics/manage_code.html) need more organization. Right now the bulk of the content is in two large buckets (**Repositories** and **Merge requests**). The content should be grouped into smaller chunks to aid with user learning.
For example, the Web Editor, Web IDE, and Remote development pages are all about how/where you edit your code.
The content should be grouped in a way that the user can build a mental model of how the product works, just by looking at the left nav.BacklogSuzanne SelhornSuzanne Selhornhttps://gitlab.com/gitlab-org/gitlab/-/issues/451272Catalog system notes in merge requests2024-03-21T18:02:14ZVeethika MishraCatalog system notes in merge requestsBefore raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, y...Before raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, your first port of call should be the Community Forum. Your issue may have already been reported there by another user. Please check:
* https://forum.gitlab.com/
If you feel that your issue can be categorized as a reproducible bug or a feature proposal, please use one of the issue templates provided and include as much information as possible.
Thank you for helping to make GitLab a better product.
<!-- template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Default.md -->Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/446073Restrict form-action CSP directive2024-03-28T00:58:37ZDominic CoutureRestrict form-action CSP directiveOur current `form-action` CSP isn't restrictive at all https://gitlab.com/gitlab-org/gitlab/-/blob/f7281682d3fe94261c2a7d6a2846cf379cda26c8/lib/gitlab/content_security_policy/config_loader.rb#L43
This can be used to bypass CSP as demons...Our current `form-action` CSP isn't restrictive at all https://gitlab.com/gitlab-org/gitlab/-/blob/f7281682d3fe94261c2a7d6a2846cf379cda26c8/lib/gitlab/content_security_policy/config_loader.rb#L43
This can be used to bypass CSP as demonstrated in https://portswigger.net/research/using-form-hijacking-to-bypass-csp
`form-action 'self'` should be mostly fine but we probably POST to customers.gitlab.com, Jira, GCP/AWS and other such providers in some integrations so this will need to be carefully rolled out.BacklogDominic CoutureDominic Couturehttps://gitlab.com/gitlab-org/gitlab/-/issues/442534Track color_mode_id background batch migration and finalize after completion2024-02-26T16:58:02ZScott de JongeTrack color_mode_id background batch migration and finalize after completionhttps://docs.gitlab.com/ee/development/database/batched_background_migrations.html#finalize-a-batched-background-migrationhttps://docs.gitlab.com/ee/development/database/batched_background_migrations.html#finalize-a-batched-background-migrationBacklogScott de JongeScott de Jongehttps://gitlab.com/gitlab-org/gitlab/-/issues/442489Database migrate theme_id and color_mode_id to user_preferences table2024-02-26T16:58:03ZScott de JongeDatabase migrate theme_id and color_mode_id to user_preferences tableFrom: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142772#note_1781587674
The `users` table is wide, including columns which are not necessarily required for general users database table usage. This includes `theme_id` and `col...From: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/142772#note_1781587674
The `users` table is wide, including columns which are not necessarily required for general users database table usage. This includes `theme_id` and `color_mode_id` columns which can be migrated to `user_preferences` to save column space on the `users` table.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/442437Add logic to Vuex action to capture the selected components2024-02-20T15:01:50ZDavid PisekAdd logic to Vuex action to capture the selected componentsBefore raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, y...Before raising an issue to the GitLab issue tracker, please read through our guide for finding help to determine the best place to post:
* https://about.gitlab.com/getting-help/
If you are experiencing an issue when using GitLab.com, your first port of call should be the Community Forum. Your issue may have already been reported there by another user. Please check:
* https://forum.gitlab.com/
If you feel that your issue can be categorized as a reproducible bug or a feature proposal, please use one of the issue templates provided and include as much information as possible.
Thank you for helping to make GitLab a better product.
<!-- template sourced from https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/Default.md -->Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/440710Display blocked users in the context of the User Profile2024-02-20T16:15:16ZChristina Lohrclohr@gitlab.comDisplay blocked users in the context of the User Profile## Problem
It looks like we display blocked users in the context of Your Work. [Test](https://gitlab.com/uchetta). That doesn't really make sense, it should probably still be in the context of Profile, just like when you visit someone e...## Problem
It looks like we display blocked users in the context of Your Work. [Test](https://gitlab.com/uchetta). That doesn't really make sense, it should probably still be in the context of Profile, just like when you visit someone else's User Profile. [Example](https://gitlab.com/lohrc). This might have been overlooked when the new navigation was rolled out.
![Screenshot_2024-02-06_at_22.01.46](/uploads/f31c0c15ae99e6817218143c34b3cd76/Screenshot_2024-02-06_at_22.01.46.png)
## Proposal
Display blocked users in the context of the User Profile.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/435949Refactor super sidebar initialisation to use presenter2024-03-28T17:17:53ZLukas 'ai-pi' Eipertleipert@gitlab.comRefactor super sidebar initialisation to use presenterThe super sidebar initialisation code could be a little better. It uses a lot of instance variables and passes them into several helpers. We could potentially refactor this into a presenter to have more clean, testable code.
See also th...The super sidebar initialisation code could be a little better. It uses a lot of instance variables and passes them into several helpers. We could potentially refactor this into a presenter to have more clean, testable code.
See also this discussion: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/140054#note_1698555585Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/435348Refactor to remove `app/assets/javascripts/whats_new/index.js`2024-03-28T17:25:09ZMiguel Rinconmrincon@gitlab.comRefactor to remove `app/assets/javascripts/whats_new/index.js`The following discussion from !138902 should be addressed:
- [ ] @mrincon started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138902#note_1683711668): (+4 comments)
> **Question:** Do we need the element `...The following discussion from !138902 should be addressed:
- [ ] @mrincon started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138902#note_1683711668): (+4 comments)
> **Question:** Do we need the element `#js-whats-new-app` to be in the rendered in the page in the first place?
>
> We use `display_whats_new?` to decide if we render this in the `page.html.haml`, but we are also checking `this.sidebarData.display_whats_new` in this component.
>
> Could create a div or use `<component>` directly in this component that mounts this async?
See more at https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138902#note_1694685765Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/435281Audit the static pages on GitLab2024-03-05T21:19:34ZAmmar AlakkadAudit the static pages on GitLab<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
Related to #344672.
### Proposal
After reviewing the addition of [a new static page on Customers Portal](https://gitlab....<!-- This template is a great use for issues that are feature::additions or technical tasks for larger issues.-->
Related to #344672.
### Proposal
After reviewing the addition of [a new static page on Customers Portal](https://gitlab.com/gitlab-org/customers-gitlab-com/-/merge_requests/4008) it was observed that we could make some improvements on the HTML/CSS of these pages.
We'd like to get UX input on the static pages in [`public` folder](https://gitlab.com/gitlab-org/gitlab/-/tree/master/public), if it needs any improvement.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/434900Secondary text color contrast2024-01-31T00:27:02ZScott de JongeSecondary text color contrast`gl-text-gray-400` is used for secondary text and lacks sufficient contrast (`3.5:1`) on a white background to satisfy `4.5:1` contrast required by [WCAG 1.4.3: Contrast (Minimum) (Level AA)](https://www.w3.org/WAI/WCAG21/Understanding/c...`gl-text-gray-400` is used for secondary text and lacks sufficient contrast (`3.5:1`) on a white background to satisfy `4.5:1` contrast required by [WCAG 1.4.3: Contrast (Minimum) (Level AA)](https://www.w3.org/WAI/WCAG21/Understanding/contrast-minimum.html).
Current usage of `gl-text-gray-400`: https://sourcegraph.com/search?q=context:global+repo:gitlab.com/gitlab-org/.*+%28gl-text-gray-400%7C%24gray-400%29&patternType=regexp&sm=1&groupBy=repo
Suggestion to use `gl-text-secondary` (`grey-500`) to ensure consistency and have a contrast score of `4.67:1`.
See: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/139334 and https://design.gitlab.com/product-foundations/color#accessibilityBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/434429Replace $t-gray-a-08 usage with suitable color primitive2024-03-08T04:09:02ZScott de JongeReplace $t-gray-a-08 usage with suitable color primitiveFrom: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137738#note_1683175903
A couple of instances of `$t-gray-a-08` exist to leverage a light shade of gray that inverts for dark mode. These should be updated to suitable `$gray-50...From: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137738#note_1683175903
A couple of instances of `$t-gray-a-08` exist to leverage a light shade of gray that inverts for dark mode. These should be updated to suitable `$gray-50`/`$gray-100` shades to ensure they are updated as expected. Border usage can be updated to `$border-color` to align with consistent styles throughout the platform.
Once updated the override in `_dark.scss` can be removed to ensure alpha shades are static between modes.
Usage examples:
- https://sourcegraph.com/search?q=context:global+repo:gitlab.com/gitlab-org/gitlab.*+%24t-gray-a-08&patternType=structural&sm=0&groupBy=repo
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/133709
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137347
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/137738#note_1689259164Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/434152Simplify new_dropdown_view_model helper2024-03-28T17:18:07ZLukas 'ai-pi' Eipertleipert@gitlab.comSimplify new_dropdown_view_model helperThe `NewDropdownHelper#new_dropdown_view_model` is still used in the new nav. But after https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138918 is merged we should have a look whether it can be simplified.
It has capabilities like ...The `NewDropdownHelper#new_dropdown_view_model` is still used in the new nav. But after https://gitlab.com/gitlab-org/gitlab/-/merge_requests/138918 is merged we should have a look whether it can be simplified.
It has capabilities like rendering partials, which are definitely not used in the new nav.Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/434046Investigate usage of toggleContainerClass in epic utils2024-03-28T17:18:45ZLukas 'ai-pi' Eipertleipert@gitlab.comInvestigate usage of toggleContainerClass in epic utilshttps://gitlab.com/gitlab-org/gitlab/-/blob/f47a4b87234a6206e5e28e6a13373ae7d578955e/ee/app/assets/javascripts/epic/utils/epic_utils.js#L21-27 seems to be unused. We probably can remove it, given that the righthand sidebar works in Epics...https://gitlab.com/gitlab-org/gitlab/-/blob/f47a4b87234a6206e5e28e6a13373ae7d578955e/ee/app/assets/javascripts/epic/utils/epic_utils.js#L21-27 seems to be unused. We probably can remove it, given that the righthand sidebar works in Epics:
![](https://gitlab.com/gitlab-org/gitlab/uploads/61a916e8cdcae77ff337a00834e837b2/Screen_Recording_2023-12-05_at_17.46.49.webm)Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/433504Buttons not fully displayed when 'System header and footer' message is active2024-01-02T12:53:07ZMenco BoltButtons not fully displayed when 'System header and footer' message is active<!-- This issue template can be used as a starting point for a UX Issue. This is not a feature request, rather an issue that is being created for a product designer to solve a problem.
The goal of this template is to ensure we have capt...<!-- This issue template can be used as a starting point for a UX Issue. This is not a feature request, rather an issue that is being created for a product designer to solve a problem.
The goal of this template is to ensure we have captured all the information available to the product designer so they can approach the problem creatively and efficiently. Please add links to SSOT if this informatin exists elsewhere. -->
### Who will use this solution?
Anyone who is watching pipeline jobs
### What problem do they have?
The buttons (retry job, delete job, new issue) on the top of the right column aren't fully displayed when a message (ether header, footer or both) in 'System header and footer' is active.
![image](/uploads/11d560572ccb85b1fc4bdf090e42877b/image.png)
### When do they have the problem?
When a message in 'System header and footer' is active
### Where in the app do they have the problem and at what frequency (if known)?
When they try to work on pipeline jobs
### Why will a design help them?
### What is the JTBD and/or Tasks?
### Is this problem supported by user research (please link relevant research issue/s)?
### Known technical constraints
### How does this help the business?Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/433277Docs: Confirm we don't have old nav steps in the docs2024-03-25T17:39:29ZSuzanne SelhornDocs: Confirm we don't have old nav steps in the docsWe've had some reports that our docs might not represent the new navigation. We've run multiple queries and searched for many strings. However, we can't be 100% sure we've gotten everything.
We need to go through the docs, page by page,...We've had some reports that our docs might not represent the new navigation. We've run multiple queries and searched for many strings. However, we can't be 100% sure we've gotten everything.
We need to go through the docs, page by page, to confirm that we don't have anything that still references the old nav.
The steps for how to write navigation steps are [here](https://docs.gitlab.com/ee/development/documentation/styleguide/#how-to-write-navigation-task-steps), but we also want to **keep an eye out for text that's not in task format** because this is the most likely to have been missed.
If you notice screenshots that are out of date, please open an issue and assign it to me. (You're welcome to fix it, but you don't need to.)
## Task
1. Assign yourself to the issue so you have it.
1. Open [this spreadsheet](https://docs.google.com/spreadsheets/d/15gGLsfWBAcbjAOQaZk2EDaThIBzj5FLYEKS9Qteuz9w/edit?usp=sharing).
1. Put your name next to the files you've checked.
1. Get fame and admiration.BacklogAchilleas PipinellisRussell DickensonMarcel AmiraultAmy QuallsSuzanne SelhornLorena CiutacuJon GlassmanLysanne PintoAchilleas Pipinellishttps://gitlab.com/gitlab-org/gitlab/-/issues/431617Add webide as a sidebar menu2023-11-13T18:43:38ZKassio Borgeskborges@gitlab.comAdd webide as a sidebar menu#### Problem
I frequently have to open the webide when I'm navigating other parts of a project. Today, I have to navigate to the project home/repository page, to then open the webide.
#### Proposed solution
Add the webide on the `Code...#### Problem
I frequently have to open the webide when I'm navigating other parts of a project. Today, I have to navigate to the project home/repository page, to then open the webide.
#### Proposed solution
Add the webide on the `Code` menu on the sidebar.
![image](/uploads/cd444ffbd6ddeab78e4bd881ed5cdca7/image.png){width=400}Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/430289Add snowplow tracking for all selections in global search modal2023-12-18T20:01:03ZTerri Chutchu@gitlab.comAdd snowplow tracking for all selections in global search modal## Proposal
Add snowplow click data to track all selections from the global search modal.
The following discussion from !135498 should be addressed:
- [ ] @jrushford started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_...## Proposal
Add snowplow click data to track all selections from the global search modal.
The following discussion from !135498 should be addressed:
- [ ] @jrushford started a [discussion](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/135498#note_1627045849): (+7 comments)
> Would you mind doing the BE review please @ghavenga?
>
> @veethika could you please do the UX review? please note that the design in the issue has the options in a different order, it was much easier to make it in the order it is now, is this ok for you? The mockup is in the issue https://gitlab.com/gitlab-org/gitlab/-/issues/414996Backloghttps://gitlab.com/gitlab-org/gitlab/-/issues/430055Explore removing SCSS color mixins to allow CSS custom properties to be used ...2024-03-03T22:43:55ZScott de JongeExplore removing SCSS color mixins to allow CSS custom properties to be used for all colorsCurrently we require SCSS variables to be used for colors as there are instances of `lighten()`/`darken()` etc. in use in the codebase and by Bootstrap.
CSS custom properties used for colors would enable greater efficiency for different...Currently we require SCSS variables to be used for colors as there are instances of `lighten()`/`darken()` etc. in use in the codebase and by Bootstrap.
CSS custom properties used for colors would enable greater efficiency for different modes e.g. dark mode.
How practical is it to remove SCSS color functions such as:
1. Maintain SCSS and CSS colors in parallel, where SCSS colors are deprecated but added to support CSS compilation where color methods are used.
1. Update [Bootstrap to v5 to use CSS custom properties](https://getbootstrap.com/docs/5.2/customize/css-variables)
1. Vendorize Boostrap dependancy locally, remove package, and replace color methodsBackloghttps://gitlab.com/gitlab-org/gitlab/-/issues/429836Improve findability of groups/projects when setting notifications preferences2024-03-05T21:14:26ZJacki Bauerjbauer@gitlab.comImprove findability of groups/projects when setting notifications preferences## **Problem to solve**
On this page - https://gitlab.com/-/profile/notifications?page=2, if you have a lot of groups and projects (possible with inheritance) it's very hard to find to browse or search for any specific ones you want to...## **Problem to solve**
On this page - https://gitlab.com/-/profile/notifications?page=2, if you have a lot of groups and projects (possible with inheritance) it's very hard to find to browse or search for any specific ones you want to set preferences for.
## **Possible solutions**
- Add ability to search all, not just current page
- Allow filtering by starred groups/projects, current notification setting, other attributes
- Remove pagination and show all on one page so Ctrl-F can be used
## **Screenshot** ![image](/uploads/a8c1e8f692cbc5ffff9581b1b963734c/image.png)Backlog